Nice.

Just noticed that it's now a 113 MB download. OK for me (took about 30 secs) but may be a little large for some. You might want to consider splitting the packs, or create a separate area for Early-Adopters, or some other way of reducing the size. Just throwing it out there :)

Many thanks.

Are you on a PC? Linux? Mac?

What's the version number of Firefox? Have you tried it in Opera or I.E.?

Since it appears to work for us, we need more info from you on what system you are trying to run this on.

I followed your example exactly and it didn't crash for me. Tried it using the Text object instructions, and with others like WebStorage and it still doesn't crash.

Have you got the very latest build ? Ashley had to do another fix on R61 and re-release it.

I can't see what the problem is (!??) :/

The opening animation plays, then I pressed <SPACE> to go to the next layout, then pressed <SPACE> again and the game starts. At no time did it freeze or stop working. It all seems to work fine.

Am I missing something :)

Runs fine on my system - steady 60 FPS approx 125 MB VRAM, even the big room. But that is at 800x600 as I can't display the higher resolution.

Which makes me think why do you want to run it at such a high resolution? It would limit the audience IMO.

Quite nice looking up to now :)

Dunkelseele

This thread is over 3 years old!

Look HERE for the original thread and caps, although whether they will still function with the much newer version of Construct Classic is anyone's guess.

1-8th generally means inclusive, so I expect they return tomorrow.

Didn't freeze for me. Works as expected.

Here ya go.

Exe size: 3,423 KB.

Would appear that there is nothing wrong, perhaps ?

This isn't a bug. See the release log HERE, specifically:

"Sprite: ImageWidth and ImageHeight expressions (formerly 'OriginalWidth' and 'OriginalHeight' in Classic). Returns the size of the animation frame image, regardless of if the object has been resized."

vidi

Forgot to mention, the way it works now, there is no need for the Wrap behavior.

I'm not certain why it didn't work. It should, but it seems to me that Wrap has a problem dealing with more than one instance when they leave the layout. Just guessing :/

My hack involved setting the Origin to the far left, then checking when the cloud reached the far right, and resetting it's x-position to '0-cloud.width' so it starts again. That's all I meant by boundary check. The boundary at the far right of the screen.

I don't think this is a good enough solution, but at least it works :)