I read through it and didn' t need to change much for my needs.

There's still people about, and I'm suprised you've not had any reply from support, though this isn't something they'd likely be able to help you with.

I have emailed you something that does what you need.

I wrote the book below. It doesn't explain 'everything' but it was well received.

https://www.youtube.com/watch?v=r7Q9vKjPSNY

Thanks adent42 my solution for now has been to adjust the firing frequency differently according to the movements of the spaceship, maybe you could also get a more precise and better effect, but I'm v

I can work on fixed price (based on my $14 per hour rate estimate), I do need a list of the assets to calculate.

Hey @UltraLionBlu nice to hear from you again! Yes please if you get time try to get it working, thanks!

ONCE UPON A TIME IN THE KINGDOM – (Looping)

The behavior you are describing makes sense. If your projectile launches at a constant speed and you're moving, then you will close or increase the distance between player and then projectiles.

I have not yet had time to try, these days I try and in case I will let you know. But I don't know if I will be able to conclude something: P

Forwards the bullets are closer together, backwards much further apart.

Not yet, we're still working on the android release and the windows build. Unfortunately due to the nature of this particular crash, even when we get to it I won't have a solid timeframe, but we are a

@adent42 any idea when you will have a fix for this crash? I had to go back to .98.

The viewer and the tool use the same engine, so unless you're somehow using an old version of the viewer, that wouldn't likely be the source of difference.

Hope you will help us

Feel free to contact us for your Art related queries.

I'm having some issues with the viewer and i don't really know why... I have a game in which you have the move around the screen and drag some objects in order to finish the game correctly.

not quite. i was thinking more just using the constrain behaviour within your actor to constrain attribute linearVelocityX (min, ( ....)), no rule though.

Is this what you suggested? If not, would you mind elaborate it?