So naturally I assumed if I use choose(0,1) in this event, it will first choose a random number (0 or 1) and then pick instances with id equal to that number.
But what happens is that this event actually checks each instance separately, and for each instance calculates a new random number and compares id with this number. So it can pick one instance (which seems correct), but it can also pick two instances or none.
Also, resetting opacity on start of the layout doesn't fix the issue, because all objects are reset anyway when the layout is restarted.
i already seen the example i think if is the one saying
i never seen the pick being used like that before, and for me doesn't make sense, as i know the Sprite object if you don't tell the system what instance should pick, it picks all of them and considers all the same object( you get what im saying? it can be confusing or i might be having a wrong idea of how the object instances work it's possible). that's what i seen so far since i installed Construct 5 years back, and that never was changed it was always like that, also i remember something about sprite.objects specifically or any object that is put initially on the screen, is that if u don't specify instance the system automatically picks the 1st put instance in screen and considers that instance like a "master instance" and if u add a 2nd instance and u don't specify it, it picks the "master instance" but takes in account the 2nd instance anyway.
so you can have 5 sprites, but when you are saying
system check if the sprite.id equals with this value that you pick random, the system picks all the data available and gets a true on everything he picks, suddenly sprite.id = to 1,2 and even 0 at the same time, creating the current glitch. and the display of the opacity, is just a lag feedback(because of wait 2 seconds then restart, which sometimes can persist even though you restart the layout.), and probably because of the overlap in computing. atleast that's what i was thinking at back then when i typed the message, it might not be the case, and they might work like you say though lol (im laughing at my own confusion here not at you, not trying to be rude :D) ... i never used the comparison like that.
that's why i was saying the choose(0,1) above in my opinion is just miss usage.
anyway did you had the same problem on a older C2/C3 version? like going back .10 .20 versions?
btw did i told you? that when i runned your example in C2 my C2 started opening himself up like non-stop? :O lol that was the latest stable version ... insane XD i think that is a bug i wanna investigate now! (maybe it was because of the = choose() :O the plot twist would be amazing... anyway im derailing my ADD started kicking in... over-editing my post just now ... im curious if there is any other reason of the =choose() behaving that way than the reasons displayed so far.