(0.99.7) I can confirm this when using the application runtime. It works as it should with Direct-X runtime.

In the application runtime, text horizontal and vertical alignment become left and top.

I reported it: https://sourceforge.net/tracker/?func=d ... id=1003219

double click the layout

Yes. In the lower right corner, choose Project, then in that: Application 1 (or application name here) > Layouts, and double click a layout.

Probably just your cap's .persist file was corrupt, or wasn't saved properly, or something. It's just the file telling Construct what event sheets and layouts to open the next time you open your cap. You could even delete the .persist file without problem.

I'm.. not sure. I'd suggest changing from ball behavior to bullet behavior, or 8-direction or something else if that doesn't work out right.

Start the bullet facing straight down. When it hits a wall, if it was going at -90 make it go at 90.

If that breaks for some reason, make a new variable set to 0. When the bullet hits a wall and the variable's 0, set the variable to 1 and make the bullet face up. If the bullet hits a wall and the variable's 1, set the variable to 0 and make the bullet face down.

Or work with Y positions. If it goes down past Y position something, make it angled up. If it goes up past the Y position there, make it angled down.

I totally know what's going on with the bomb, too. Notice in debug mode how the bomb's angle is always increasing further away from its starting angle?

In other words, it's sloowly turning toward heading sideways. Your event is always moving it to your paddle X position, certainly, but.. let's say you could disable it for a moment in gameplay. You'd see the ball heading rather sideways, with little vertical velocity. Most of its speed would be going toward moving it horizontally.

You might want to either limit its angles to -90 and 90 only, or make something custom that always goes up and down between the top and bottom boundaries or some set Y positions. I don't know what would be best.

Hmm, okay then. I was chasing the wrong thing, anyways.

I managed to fix the problem where the ship spawn events wouldn't work right after losing and restarting. To fix it:

Change your layout transition style from "Fade" to "None" in both the Event Sheet and End Events sheets.

I experimented changing things to use simply set times, every 2500 ms, that kind of thing, and it didn't fix it.. but changing it from Fade to None layout transition works.

(Also, totally unrelated to any issues here; it's not an issue, and it doesn't seem to affect anything in this case, but in the future: You could use a MouseKeyboard object in just one layout, and set it global. Then you don't need to place a MouseKeyboard in other layouts, and you can use it in their event sheets too.)

I could download it.

I'm using 0.99.62.. for some reason this game crashed on me after 30 seconds to a couple of minutes. Except for this last try, where I could see the behavior your described. At least I THINK the ball/bomb slowed down.

I haven't worked with "Timer", so I'm confused about evaluating Timer>0 in so many places. It appears after one second Timer is always going to be above zero.

And I'm not sure if "Every 30000 * (1 + random(3) ) milliseconds" is actually viable or not. Maybe someone else knows?

Likewise with "Every global('SpawnRate') milliseconds".

I've just not tried that kind of thing before.

Edit: As for links to Dropbox - if you put it in the "Public" folder, then you can click on the file there, and "Copy public link", and hand that out.

I made a program to automatically save screenshots one takes with the printscreen key. I have found it to be pretty useful for a couple of games I play. , if you're interested.

I've also been toying with making a sort of text to speech application, using prerecorded sounds which are played together. h+ell+oh. k+uh+n+s+t+r+uh+k+t. That sort of thing. I'm using the Direct-X runtime, however, as I am calling functions with a delay. It's not exactly a game, at least, and looks like an application. :b

It's more fun to use than the command-line C version I made years ago, and more advanced, too.

Someone could make a simple text editor, for sure.

I could see it being used for a paint program of some kind, too, if you don't mind using the Direct-X runtime.

Strange. I found "add waypoint at mouse" works, it will queue them up, but it doesn't work if I do "add waypoint at object" a few times in a row, each time with a different sprite. Same with "add waypoint at position". It just doesn't move. I assumed the example I gave would work, sorry.

spritefluidredux.exe runs for me too. Heh, pretty. And interesting. It's a nice effect. Even more fun to play with.

You might be able to use GetToken(), and NumTokens()

For example, let's say you're storing the file contents in a global named file_contents, i.e., Global: Set 'file_contents' to File.LoadFileToString(AppPath & "file.txt")

Well, NumTokens(global('file_contents'),NewLine) should tell you how many lines there are in the file_contents global.

So, you could possibly do this:

For "loopname" from NumTokens(global('file_contents'),NewLine) - 10 to NumTokens(global('file_contents'),NewLine):

with the action: System: Set 'somevar' to global('somevar') & GetToken(global('file_contents'),LoopIndex,NewLine)

And set your text box to show global('somevar')

Or you could clear the text box's text first, and instead have your action set the text box's text to: Editbox.Text & GetToken(global('file_contents'),LoopIndex,NewLine) ..if it's an editbox.

I hope I made enough sense. I'm tired.

fluid.exe and meshfluid.exe both crash for me as well. meshfluidredux.exe runs.

It is fun to play with, indeed.

[quote:33cbhmh4]what cpu/ram configs do you guys have?

AMD Athlon 64 X2 6000+ (dual core)

4GB ram. DDR.. I forget what speed. It might be running at DDR-800 speed.

I'm using Windows XP SP2. 32-bit, so only 3.25 GB is available.

I can't see the link... Could you post it again?

Add or use a layer above your others, with the scroll rates at 0%

In this layer, create a gradient, big enough to fill your game's viewport. The top end of the gradient is black at 100% opacity. The bottom end is white, with 50% or so opacity (or making it dark gray at 100% opacity seems to work).

Add the Magnify effect to it. Magnification 60% or so. That should do it.

Or maybe one of us could repost it on dropbox, etc.?