Hi andziana,

thanks for your reply via pm. i worked a bit more on the initial test. download the updated rope test from below.

dl.dropboxusercontent.com/u/25721687/rope2_singlefile.capx

See if you like this better:

dl.dropboxusercontent.com/u/25721687/Hacker_CRN.capx

Hi EncryptedCow, didn't understand your problem in full, maybe you can elaborate. however when you disable the 3rd condition in event 3 in the duplicator_e event sheet (spr_duplicator pick by unique ID) you can move the duplicator block to another position. don't know if that helps.

Link to .capx file (required!):

dl.dropboxusercontent.com/u/25721687/HeightBugTest-v001.capx

Steps to reproduce:

1. Run the demo and watch the sequence of sprites being created.

2. A sequence of sprites (1 big green, 1 small blue, 1 small blue) will be created. After a short gap the sequence will restart.

Observed result:

The vertical position of the second small sprite is different than the others even though the same code is used. I have noticed this to occur when different sized sprites are created. The timing is also important since the error seems to depend on which sprites are on screen or maybe which ones have just been destroyed. (e.g. when I changed the timer to 4 seconds the result is different and all sprites are created in the centre)

Expected result:

I expected the objects to be created in the same position given that the same code is used.

Browsers affected:

Chrome: yes

Firefox: yes

Internet Explorer: yes

Operating system & service pack:

Win 7 SP1 (2 machines) and a few Ice Cream Sandwiches

Construct 2 version:

Release 128.2 (32 bit)

Yo!

Check out the below:

dl.dropboxusercontent.com/u/25721687/gameWIP_CRN.capx

Am not sure if the result is what you had in mind, but your logic is now working on individual sprites.

Yo!

Is this what you had in mind?

dl.dropboxusercontent.com/u/25721687/TouchRotate_CRN.capx