You just looked at it or did you do something with the information provided?

From your image it seems like your game isn't big enough to fill the entire screen..

Try using another fullscreen option and adjusting your background, scrolling and alike..

The tut explains how the different settings work and adresses their pros and cons..

I would need a lot more information..

If the way C-7 explained to find your problem isn't working for you, this still applies:

No capx, no steps or clear explanation how to reproduce = nothing to investigate.

Tutorial: Supporting multiple screen sizes

If this doesn't help, could you share your capx, for this problem should not exist if your game is set up correctly..

should be draggable, just like actions, just make sure the whole event is selected, not just condition(s)..

Do you mean this?

Array1 compare value at 0,0,0 = Array2.at(0,0,0)

In my opinion that kinda defeats the purpose of the array object..

Array has x and y -direction (and even z if needed)

Which you can take advantage of..

if you just wat to put all the information in a string, using the dictionary object might be a better option...

They are exactly the same...

If they are exactly the same, they would act exactly the same..

So, one more time:

Ui layer paralax 0,0

other layers paralax 100,100

All items on the UI layer should be within the dotted line..

If this doesn't work, share your capx..

The scrolling should work on the layers with normal paralax, you don't want the Ui to scroll..

Make sure everything that should scroll is not on the UI layer..

You could just look at your setup in layout 1, the same setup should work for layout 2..

Did you forget to put the UI layers paralax to 0,0 in the second layout?

I'm not really sure what kind of example..

on one layout set global variable

on other layout add a condition checking the global variable

so something like

normally variable coinmultiplier = 1

on the menu layout:

on button pressed

set variable to 2

on the game layout

on collision with coin

add coinmultiplier*10 to coins

Well you can't do anything with the information, before you have it, so there will always be this (very small) waiting time..

Best way to do anything about it would be to only show the stuff that is being affected after it is affected..

for example a (fast) fade-in could look cool, without the user having the idea it was to disguise something..