Movement not working

Alpharius#9750

New Member
Mar 24, 2023
1
0
20
I try to move around the map but the arrows don’t work properly and the down arrow doesn’t work and they’re in a position they probably shouldn’t be in
 

Attachments

  • A3E4D828-14EF-40C0-A72A-458777E63AF9.png
    A3E4D828-14EF-40C0-A72A-458777E63AF9.png
    251 KB · Views: 7

Theron

Well-Known Member
Nov 8, 2018
3,666
1,391
44
Make sure you're on the latest version: 0.9.045.

They added the ability to move the control overlay in the Options->Controls menu. But I don't see the map.
 

Jacques00

Administrator
Moderator
Aug 26, 2015
5,140
1,270
Make sure you're on the latest version: 0.9.045.

They added the ability to move the control overlay in the Options->Controls menu. But I don't see the map.
The option to move the controls should be in the options menu--in the Control Overlay card.
 

Jacques00

Administrator
Moderator
Aug 26, 2015
5,140
1,270
I try to move around the map but the arrows don’t work properly and the down arrow doesn’t work and they’re in a position they probably shouldn’t be in
Um... I'm not sure why your buttons have printed out that way, but yes, make sure you are playing the latest version. I may have to look into why the buttons look that way on your device...

-----

Edit: I think I have an idea of what is going on. It seems your device browser is interpreting the .svg components (what the buttons are made of) in a way were parts are being rendered (mostly) correctly, such as the icons, but some parts (the actual button graphics) in different units--probably substituting the transformation or transformation-origin in pixels while the other parts are in more scalable units.

If this is the case, there's not much I can personally do on my end. However, if you can bear with it, try going into the options and disabling the Control Overlay. This will allow you to play the game with the regular buttons (though they may be a bit small for your device).

If there are more reports of this issue, I'll try to look into it further. The solution may be to rebuild the controls so they are no longer dependent on transformations.
 
Last edited:

Jacques00

Administrator
Moderator
Aug 26, 2015
5,140
1,270
Okay, I looked into this issue a little more and my suspicions of the transform-origin is most likely what it is. I'm assuming this value is not being interpreted properly on your device. I have removed the transform-origin parameters and made some other edits to compensate. This should hopefully fix the issue for you in the next release.