Coordinates seem to be wrong.

[BadTrip]

Hello, I have following configuration:

OS: Win10
GPU: NVIDIA GeForce RTX 3060
Monitors: 2 Screens side by side with a resolution of 3840x2160 each

I've tried to control a full screen application running in 3840x2160 fullscreen mode on one monitor by automated mouse-clicks. But AutoIt seems to have a completely different coord system than I have.

Using @DesktopWidth and @DesktopHeight returns a resolution of 2194x1234 not 3840x2160 (no matter if the fullscreen application is running or not). That's also the range where MouseCoords are within (or 4388x1234 if I move the mouse to lower-right of 2nd screen). But if I capture the full screen application to clipboard using alt-printscreen and pasting it to paint, it has a resolution of 3840x2160 like it should be.

Trying around with AutoItSetOption's PixelCoordMode or MouseCoordMode didn't help. Even Au3Info_x64.exe is using this strange coordinate system.

Where is the problem located here?

 

I've located another problem. Not in AutoIt itself but here in Forum after posting this possible bug report. Something seems to be wrong with users and especially moderators. If you are going to report a possible bug and using the word "game" inside the post to give an accurate bug description in order to solve the problem, your post will be locked and the word "bug" will be removed from topic by a forum moderator. It seems that some words trigger any automated reaction in some users or moderators heads, regardless of the posts content or the context the word "game" was used. There was absolutely no reference to what game it is about or if it even might be a self programmed game, trying to test the usability with AutoIt. There was no reference or hint of how this game was going to be automated, just that I've noticed something strange even without having it running.

If you member Andreik and moderator Melba had read the post you would have noticed, that the problem also occurs without having a game running. Therefore it didn't violate the rule about " Do not ask for help with AutoIt scripts, post links to, or start discussion topics on the following subjects:  [....] Launching, automation or script interaction with games or game servers, regardless of the game.". The subject is the AutoIt coord modes and not a game. But instead of simply replacing the buzzwords you don't like, the topic itself gets locked without giving a solution. What the heck!

 

Edited November 7, 2023 by Melba23

[Melba23]

BadTrip,

Your own words:

Quote

I've tried to control a game running in 3840x2160 fullscreen mode on one monitor by automated mouse-clicks. But AutoIt seems to have a completely different coord system than I have.

So the thread ran foul of the forum rules and was locked - end of story.

Now to this thread. Rather than a polite request to myself or another Mod to reconsider the locking, you repost exactly the same content (changing a single word) and thus fall foul of the forum rules again:

Quote

7. Do not repost the same question if the previous thread has been locked - particularly if you merely reword the question to get around one of the prohibitions listed above.

Plus you go off on a rant against the Forum Mods and members. And you expect us to react how exactly?

=======================================================================================

Given that the screen dimensions you quote are exactly 1.75 multiples of each other, I imagine you have your display resolution set to that value. I suggest you search the forum for "DPI-aware" - you will find lots of threads dealing with that, one of which might well help. Do let us know if that was the problem.

M23

P.S. Everyone else please keep out - let him stew in his own juice for a while.

Edited November 7, 2023 by Melba23
Speeling!

[BadTrip]

Thanks for helping now. After searching the the Forum for "dpi-aware" I found the solution in this thread
 

Adding the line

If @OSVersion = 'WIN_10' Then DllCall("User32.dll", "bool", "SetProcessDpiAwarenessContext" , "HWND", "DPI_AWARENESS_CONTEXT" -2)

solved the problem and AutoIt functions and constants are now related to my real resolution after adding this line to my script. (Windows 10 only!)

 

 

 

53 minutes ago, Melba23 said:

So the thread ran foul of the forum rules and was locked - end of story.

no it didn't. I did not ask about for help with AutoIt scripts, posted links to, or started  discussion topic on the subject "Launching, automation or script interaction with games". I did it about topic "coordinate problem" that's obviously more known by "dpi-aware". Factually the question if the application that I used when trying AutoIt is playable or not, does not matter, not a single bit! The fact that I found the solution in a thread that's not about games proves my statement. How many of forum search results for "dpi-aware" are about games? I did not violate this rule.

 

1 hour ago, Melba23 said:

7. Do not repost the same question if the previous thread has been locked - particularly if you merely reword the question to get around one of the prohibitions listed above.

Maybe this time I violated the forum rules. But consider that there's absolutely no need to repost the same question again, if the moderator is doing a good job and simply answering a question instead of closing the thread. What do you think, would this thread exist if you had answered my question in my first thread already? Obviously you were able to help but instead of doing that, you only refered to rules and prevented other people to help me with closing the thread. Therefore the only way to get the problem solved was to repost the same question. If you never heard about something that's called "dpi-aware" before it's also hard to search the forum for it. So simply try to be a better mod and help users  instead of closing their threads and I predict that this rule number 7 will be violated less

 

regards

[Melba23]

BadTrip,

Glad you found the solution.

======================================================================

You were condemned by your very own words in the OP of your first thread. You came across a problem in running your game automation and were trying to solve it - thus any solution would apply to that automation and hence be against the rules. The second thread you posted was in direct violation of a rule. However, as the solution was so simple I decided that you at least deserved a chance - which I gave you. And in return I get another wordwall of how you were hard done by - well, basta!

Now you can argue with yourself for a week.

M23