Major iOS bug with parallax

I found a really major bug in iOS. When dealing with parallax when an object is created on a layer with a different parallax value and then moved to another layer it totally mess it up. I was very suprised to find this bug since iOS usually is very stable and bugfree for me and this is not happening in any of the other runtimes (have tested windows, android and flash). This is such an obvious bug that it is hard for me to see that it could have been present from the beginning and not squashed yet. Maybe it got introduced in later builds? I have tested both the previous Fusion build and now also have the latest build (285.8) with this bug still present.

I have made an isolated example of the bug where if you click an object is created by another object that is on a layer with a parallax value of 0.9 and then moved to another layer with a normal value of 1.0. I have recorded a video of this where you can see the same app running both on my regular Fusion runtime and then on the iOS device. On the iOS device the object is totally out of place: https://dl.dropboxusercontent.com/u/...-06_174424.wmv

Have also created a bugbox ticket for this, but I really need this to be fixed as soon as possible, I am at the end of porting my game to mobile and I have a publisher waiting for the game to be ready, this obviously makes my development be at a total standstill now until this is resolved :/

Since it is working as it should on all other platforms it should not be to hard to find the code error for the iOS runtime I hope?

Bugbox ticket: http://bugbox.clickteam.com/issues/3590

How do one know if anyone have looked at the bug?

As soon as someone can look into they will comment on it - in the bug tracker.
Your report is good with a nice example to reproduce it so I am sure they will look into it before they do the next build of the exporter.

I wonder if its related to a bug where a quick backdrop moves out of place for no reason. Seems similar a little bit.

Thanks Jeff!

I would really greatly appreciate it if someone would look at it soon since my development has been totally stalled for a week now because of this bug and I have a big publisher waiting for me to deliver the game :/

Is there any way to know when this will be looked at? It was three weeks since I reported the bug and I have heard nothing from Anders about even looking at it or any response to message to him. Do he even work on the iOS exporter now since working on Fusion 3?
It is extremely frustrating since my development have been basically totally stopped for almost a month since I can't do anything until it has been resolved. All I can do is sit and roll my fingers and hope the publisher I have on hold will not pull out.

sorry to play devil's advocate on this Outcast, but can you just create it on the layer you need to move it to? Wouldn't that get your port finished?

I need to create it at the location of another object, and that object is on another layer so that does not work. I have really tried to find a workaround, but there seem to be none. Also in other events I have it move between several layers to check position and collision so that does not work either.

this bug have been fixed by Anders, should be available next release.

wow, Anders is still live on ios XD great stuff! :D

Sorry for the bad news but Anders fixed another issue, not this one. ;)

And this one is not easy/quick to fix safely so it won't be for the build 286 (in theory).

& there again we have the famous "in theory" XDXDXD

keep up the great work guys :)

About it not being an easy/quick fix. It is working in all other runtimes, Windows, Android, Flash etc. It is just on iOS this is happening, so is it not just some code error or something that needs to be adjusted in iOS to match the other runtimes?

>> It is just on iOS this is happening, so is it not just some code error or something that needs to be adjusted in iOS to match the other runtimes?

Unfortunately no.

It should be fixed now, fingers crossed.

Thanks Yves! I *might* finally also have found a workaround. Testing it now so not totally sure yet though so fingers crossed here also.

Unfortunately it seems my workaround does not work without creating new problems :/ Would be really happy to try out this fix!

I've sent you a PM.