I've had this problem ever since TGF. I'll create an object and make it a global object and it does just that. Temporarily.
After so long the global object still says it's a global object but if I edit the object in one frame it stays the same in the other frames. What's causing this and how do I get around it?
This has also bothered me for a long time. The best solution i came up with was to avoid the situatuion as much as possible by finishing all objects art and coding in one level, then copying and pasting it , then making whatever changes necessary to make all the other levels.this is a lame solution and had hoped this sould be a thing o the past in MMF2. I hope someone else has a better solution.
Also, if things arent really global, it makes you wonder if any file-size is really being saved by making them global. the art must be stored seperately per frame if it can not update across all frames.
I'll be keeping an eye on this post to see if there's a real solution.
Well one idea I had is to make one huuuuuuuge frame and turn off the handle collisions even out of frame but that'd make you run in to the need for programming a ton of scrolling boundaries so you don't accidentally end up in another level.
In other words I'd much rather do the global object method if there's a solution.
This happens A LOT to me, also global objects behaviors NEVER EVER get updated in other frames. This is really annoying for me, but also this is in the wrong forum...
Some cases that were causing this issue have been fixed in recent builds. Make sure you use the build 246.
If you use the build 246 and this problem still happens, note what changes you did to the object and let me know.
Benicle, I've just tried to change a behavior of a global object and it was changed in other frames too... If you can reproduce this issue, please post or send me an example (but make sure to build it from scratch with the build 246). Thanks!
Well it did happen in build 246 but I have no idea what I did to make it happen since it's nearly impossible to tell when it happens precisely.
I'm almost certain I didn't do anything to the object to make this happen, it's just I come back to edit it later and it's global-ness no longer functions.
That's not possible, you must have modified a property of the object or something else.I'm almost certain I didn't do anything to the object to make this happen
Maybe the instances of the global object were disconnected in a previous build and you saw it only while editing the application in the build 246? Unless you have build it from scratch with the build 246 or 245?Well it did happen in build 246
I built it from scratch with build 246, but I'll see if I can't replicate the issue later after I wake up tomorrow since I need some sleep now. :p
OK thanks !
It's exciting that you've tackeled at least some of the causes. Thanks much Yves. I'll definately report any issues with this and try and figure out how to recreate the issue.
I love MMF and have always been impressed with the thoughtfulness and hard work that clickteam has put into their products.
Posting Permissions
Reply With Quote