Hold on...I think I've got some good info about this in my spam folder...

Whoa...just opening the project made C2 freeze and then turn black. Thought it had crashed, but it finally came back up.

...and, after a bit more testing, it finally lagged up/crashed. Took about 3 previews, each slower than the last. C2's interface slowed down and finally froze and corrupted.

Never seen anything like this.

ErekT

Not the most elegant solution, but wouldn't it be possible to batch process those kind of changes and drop the results into the animations folder directly?

Also, what about 'link to original source file'?

https://www.scirra.com/manual/48/image- ... ons-editor

Thanks Ashley.

—

Exports fine for me too. I'm on r190. I replaced one of my node exporters (win32) with the previous version (0.10.5) for performance reasons. All other exporters are stock. I'm only able to test on windows.

The 32-bit version runs as expected. The 64-bit version crashes when I try to type or paste in a name. Don't know why that would be happening, but I guess it's a separate issue.

Need more info. Does this happen in different projects? Could it be a particular plugin? Can you provide a capx?

Q3D v2 is looking seriously awesome. Love the trippy new fps demo.

Anyway, I have to go to bed.

And not dream about disembodied floating heads in space.

Oh well.

At least I can fling magic balls at them and make them flash.

I am inescapably reminded of the The Drinky Crow Show. Wonder why?

This would be great. +1

—

Yes, a few different people have reported this issue, but no comment yet from the devs.

Here is the most relevant bug report; if you are seeing the same symptom, please drop a comment here:

https://code.google.com/p/chromium/issu ... ?id=422000

Unknow01

Have you tested chrome canary? It's got really good vsync most of the time; if it fails try resizing the window. Here's the link:

https://www.google.com/chrome/browser/canary.html

What about the older version of node-webkit? If you are on r190, you can switch out the current node with the older, stabler one by swapping a few files. I wrote a guide on this here:

update-guide-fix-jank-in-r190-node-webkit-export_t119896

Don't expect firefox to work very well under any circumstances; it's by far the worst of current browsers, exhibiting unstable performance on anything more complicated than a simple web game. They're supposed to be working on this, but...

Hey, this thread is back!

plauk

Hmm...I'm still seeing the same bug as before; if I start canary windowed, vsync fails, terrible jank. Resize/Maximize/Fullscreen corrects vsync, starting Maximized/Fullscreen locks vsync correctly from the start. So, 90% there...but the same as it was a week ago.