I can't tell you any more than i have about it. When C3 loads the z order bar is empty, the only way i can get info to show again is to close the bar and reopen it.

Same here. The only time i can get it to show any info is if i undock it then go into menu > view then select z order bar again. Then it shows the various layers and the object.

Chrome on mac.

I'm not using C3 to bug hunt on your behalf, i'm using it to evaluate whether to subscribe. I don't have time to read through the novel you call a guide or sign up to any more of websites. Honestly you make it feel like your doing me the favour. All the info i know is posted here already. Hopefuly you can look into it.

C3 is working correctly, it's the logic that a wrong.

every 4 seconds "centre" is playing so it switches to "right", then immedialty it executes the code below, since its now "right" this condition becomes true so it changes to "left", then does the same for "Centre" again.

You could try,

every 4 seconds... set variable to 0.

(sub events)

animation centre playing AND variable = 0, set animation to "right", set variable to 1.

animation right playing AND variable = 0, set animation to "left", set variable to 1.

animation left playing AND variable = 0, set animation to "centre", set variable to 1.

setting the variable to 1 stops the line below from becoming true until another 4 seconds pass.

Imagine if the transition function was called twice, the second time it would destroy the first functions transition sprite before a new one was created.

Thanks, but i don't think its a graphics card issue. It works normally after the editor is restarted which suggests a editor issue to me.

I guess they're ignoring this thread because i haven't posted it in the bug forum, but i'm not signing upto yet another website.

I can't give any more info than what i've already said here and i've taken the time to bring it to their attention so hopefully they'll want to look into it.

Ashley

Heres how the bug happens.

https://www.dropbox.com/s/5j3jyfu0c3kxxjv/offset2.gif?dl=0

Ashley

Ok i can reproduce this bug now, it appears to be when you use "force own texture" and blend modes, save the project using "download a copy", use the same file name. Once the file is overwritten and downloaded the layer suddely jumps up offsetting all the objects bounding boxs. Restarting C3 or reloading the projects fixs it again.

Theres definatly a bug here, i don't know whats triggering it or how to reproduce it. Working with blend modes makes the bounding boxs on the layout offset. Restarting C3 restores it to normal when it happens.

Any one else been using "force own texture" and blend modes noticed anything?

https://www.dropbox.com/s/8vu4fdou3ek5lh4/offset.gif?dl=0

I'm on chrome for mac.

I don't trust browser storage.

If c3 is like c2 then construct doesnt update the internal object list until the next loop. When the object is created you can store its UID in a variable then use in the family object pick by uid.

Strange, after a restart i'm having trouble reproducing this issue now.