I boot up the game which worked just fine in the latest stable release. However the latest stable update (212) breaks the preview immediately. The game doesn't even have time to boot before I get the error message:
SyntaxError: let is a reserved identifier
http://localhost:50000/video_plugin.js, line 469 (col 2)
I opened another game project which didn't have a video plugin active and it ran just fine. The first boot after adding it however gave the same results.
Attach a Capx
https://docs.google.com/uc?authuser=0&i ... t=download
Description of Capx
It's a gamejam game I made in about 2 days with an added video instance to it. Remove the video and disable the debugger sheet and you have yourself a tidy little foul mouthed video game on your hands.
Steps to Reproduce Bug
Operating System and Service Pack
Windows 7 SP1
Construct 2 Version ID
There is no source set for the video. What is it meant to be?
zenox98 There's no source. I tried it on my main project as well which has tons of videos with sources and it ended up with the same result. It's the plugin itself that's the issue, not the source.
After adding a source it does indeed still crash.
Mhhhm. This makes me unable to work on my game as Firefox's the only browser capable of running really big projects :/. Hope it gets fixed soon.
It must be the following that is the culprit:
[quote:2ek3v0qk]Fixed a bug that could cause choppy video playback in the latest Google Chrome releases
Hopefully, Ashley will notice and release a quick fix, although pre-testing releases (maybe by the mods?) may be a better idea in future :/
You can temporarily remove the video plugin from your project, which should at least allow you to continue work on it.
Develop games in your browser. Powerful, performant & highly capable.
It also fails for me doing a node.js preview with the following error:
zenox98 Not really no because then I have to reimplement all the video instances later? I'll rather work on something not dependent on the engine, like concepting.
Gah. This will teach me not to make changes in a stable release (which I already knew I shouldn't...)
It's pretty much a typo and r212 only went out a couple of hours ago, so I don't think it warrants a .2 release - I'll update the download for r212 shortly with a fix.
OK, as of this post (5:30pm BST), the r212 download has been updated. Can you try re-downloading it and verify it is fixed?
Ashley Did you upload the new build to Steam? Not sure if I've downloaded it but the bug's still there.
Ashley Rebooted the computer, got the update, and it works gloriously. Thanks for such a rapid response!
Just re-downloaded and all is OK now.
Fixed my problem.