I don't think you can fix this with the bullet behavior on the text object. With the sprite object you can flip it and mirror it.

Use either "move forward" or "move at angle" with every tick:

every tick --> move -X*dt

or

every tick --> move X*dt at angle 180

where "X" is the number of pixels that you want the text to move over one second.

The move at angle option is more versatile because you have more control over the angle of motion.

Example .capx

Example html

You're welcome <img src="smileys/smiley1.gif" border="0" align="middle" />

+1

I would go a (big) step further and ask for a native timeline. That would be awesome!!!

Ashley

Sorry for being impatient, I know this isn't some major thing but I want to wrap up my graduate project and deliver it to my department for archiving purposes.

Since I figured that this bug crashes the application that I am about to deliver, I would like to know if it's something easy to fix, or should I remove the save/load system from my project, since it isn't really important for the archiving process (the difference for the University will be on the version, v1.00 vs v1.01 if I manage to fix it) ...?

By the way, I will get back about this very soon, with official honors, thanks to the scirra team and all that jazz! My professors didn't expected the result I got out from C2 and they were very interested about the software.

Best regards,

Elias

I think I am about to get use to it. I would still prefer the mouse scroll to zoom directly though, or the option to do so.

The thing that I am terrified is the habit of zooming with alt+scroll wheel as in Photoshop, in C2 this can cause unexpected crashes...<img src="smileys/smiley19.gif" border="0" align="middle" />

daoluong

that did the trick for me, thank you!

This isn't a bug.

In your "menu" event sheet, your last event (#10) is an "audio stop all".

This is what interrupts the audio after 1 click.

Disable this event and you'll see that the audio plays just fine.

Link to .capx file (required!):

http://www.eli0s.com/Tests/save_load_error/save_load_error.capx

example

Steps to reproduce:

1. Drive the filter frequency cut off with a variable that change over time

2. Save

3. Load

Observed result:

The game freezes. If the filter effect is applied but the parameter doesn't change with the variable, the system works. The problem occur when you enable the effect parameter and change the frequency with the variable.

Some times a javascript error prompt comes up, I can't reproduce it now but I have taken a screen capture of it:

JavaScriptError

Expected result:

It shouldn't freeze the game

Browsers affected:

Chrome: Yes

Firefox: n/a does not support advanced audio

Internet Explorer: n/a does not support advanced audio

Node-Webkit: Yes

Operating system & service pack:

Win7 64bit SP1

Construct 2 version:

146

Scavengrove my project also has a ton of color effects and the water background effect on a few layers...

I don't know if your findings reflect to my case, I guess we'll just have to wait and see :)

Thanks for trying to figure this out though!

Ashley It is good to hear that this is taken care off.

I had already reverted back to the stable v.146 with no trouble at all.

A bonus gain from this incident is that while I was using the 147 beta, I tried the new windows 7 color theme and after uninstalling the 147 and reinstalling the 146, the theme remained! In the preferences it doesn't show up as an option though, it's there on the event sheet just to please my eyes :)

I get the same result but it's impossible to create an example capx right now and my project is too big and complicated, a million things could trigger this problem...

I have the same problem! I didn't realize this before and it caught me by surprise! The day after tomorrow I present my graduation project (made with construct) and I hopped that I would make a robust menu in the time that I have left...

If this is by design then it's very counter-intuitive, ESC is the default menu key in every game I have ever played!

Pressing ESC to call the menu, then go full screen and then use some resume button is the only thing that I can think of as a workaround, but it's a terrible one, muscle memory alone makes me hit ESC all the time!

If it's a limitation then this is a serious one!

I hope that it's a bug and it will be fixed by Ashley soon.