Is there a bug in Fusion 2.5 where objects set to not move at start is ignored?
I've got an object with Bouncing Ball movement and the Moving at Start box is NOT ticked and there are NO events to make it move and yet at the start of the frame it's moving. WTF?
Hmm, I can't make ANY new objects stop moving. Bouncing Ball, Path movements. Any I set to Stop in a Start of Frame event are moving at the start and it's the FIRST event in the whole game.
Is there a limit to how many events you can have in one frame? Because no matter what objects I create with movements I can't ****ing stop them!!
EDIT
Yeah, stop movement as event no longer works for anything. I'm now having to set speed to 0 instead. This ****'s ****ed up.
Odd, both work fine for me (move at start checkbox, "stop" command)
sure there is no conflicting event later?
(like setting the speed of the object to some amount?)
Nope. I checked everything, it's weird. I can only set speed to 0 for any new objects, setting to not move at start no longer works!
Very odd, can you post an .mfa showing the issue?
hi soopytwist I wonder if it could be that the ingame engine is being bugged out from lots of objects? How many physics objects do you have on screen at one time? The physics engine may not be able to handle a lot of objects (could be wrong but that would be my first guess)
Have you tried creating a new blank project and try it then? Also Fusion is all up to date for you?
Can you upload an MFA file?
I haven't heard of anyone else having this problem. So it would be interesting to see if your MFA has the same problem on other peoples computers.
LOL. I think I solved it. While putting together an mfa of the problem (I didn't want to include my entire game for upload) I discovered what the problem is.
The objects I was creating were all clones of another object which has a qualifier. That qualifier is in an event that makes any object with it move when the player is on screen (in the same room). Therefore every time I made a new object with bouncing ball or path movement (with either the "Moving at start" unticked for the bouncing ball movement or a Stop event for the path type) the objects would move at the start because of the event making any object with the same qualifier start moving - overriding the stop event at the start of the frame!
While I did look at events associated with the objects to try and solve why this was happening I did not look at events for the qualifier.
*roll eyes emoji*
Posting Permissions
Reply With Quote