Offline
and here is my question, is this a bug from cs2d? Can anyone check that out with fullscreen and normal screen (850x480)
ps: Mode 1 (checking mouse position of the screen) works fine, but mode 2 is maybe bugged
Forum
CS2D
Scripts Clientdata
Clientdata
9 Antworten
1 
and here is my question, is this a bug from cs2d? Can anyone check that out with fullscreen and normal screen (850x480)
ps: Mode 1 (checking mouse position of the screen) works fine, but mode 2 is maybe bugged
CS2D Bug Reports. 
mp_hudscale (any mode > 0)?Mode 1 of
reqcld is designed to work with mp_hudescale, mode 2 however is NOT designed to work with mp_hudscale.Unfortunately all this scaling stuff is a complicated/tricky topic. It wasn't possible to automatically make this specific mode fully compatible with the new resolution for all cases.
If you are using
mp_hudscale > 0 AND are drawing HUD elements at the position you get from clientdata mode 2 you will have to do manual script adjustments.If you however are using the position from
clientdata mode 2 to do things on the map directly, it will work fine without further adjustments. No matter which mp_hudscale you use. reqcld to handle this case.At the moment you either have to scale/position stuff manually (you can get the resolution of a player with
player) or you can combine reqcld 0 and 1 to get the cursor position + the map scrolling offset (it's a bit complicated because you have to cache values since it's asynchronous stuff.Sorry for the bad news. Unfortunately not all scripts can work out of the box with the new resolution stuff.
Mora: *sigh*again: There are two use cases for mode 2. One should always work, one doesn't work right with custom resolutions. I can't make both work at the same time.
working: when you use the coordinates to do stuff on the map. like clicking tiles or other objects on the map
not working: when you use the coordinates to render HUD text / images.So it's not exactly a bug. It's a choice. For use case one.
idk why it have differences, since cursor just working like an object on the map.
Please DC, can you help me with a correct calculation of X and Y depending on a players resolution?
In the beginning, it worked fine, but now it went banana
1
2
3
4
2
3
4
if mode == 2 then x = math.floor(x-((player(id, "screenw")-850)/2) y = math.floor(y-((player(id, "screenh")-480)/2) blocksize = ((((player(id, "screenw")/850)*32)+((player(id, "screenh")/480)*32))/2)
1