\nThanks.
\nSee an example below. Chart on the left represents click screen coordinates, on the right -room coordinates
![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F349155%2F70ab25cfafc7d73e385e08e9cf57e17a%2FCoords.png?generation=1675850524161881&alt=media\")
So I've been doing some EDA on the dataset and it seems that screen coordinates (columns screen_coor_x, screen_coor_y) represent absolute screen coordinates (probably centroid of a touch) and there seem to be two distinct screen resolutions. Something like 640x800 and 1920x1400. I assume these coordinates were recorded at High and Normal Quality modes. Unfortunately, the HQ column in the dataset is missing, and the actual screen resolution has to be imputed (with potential errors). My question to @alexmlfranklin. Is my logic correct? Can the HQ column be provided as it is currently empty? I'm also curious if playing at fullscreen changes how the coordinates are recorded.
\nThanks.
\nSee an example below. Chart on the left represents click screen coordinates, on the right -room coordinates
So I've been doing some EDA on the dataset and it seems that screen coordinates (columns screen_coor_x, screen_coor_y) represent absolute screen coordinates (probably centroid of a touch) and there seem to be two distinct screen resolutions. Something like 640x800 and 1920x1400. I assume these coordinates were recorded at High and Normal Quality modes. Unfortunately, the HQ column in the dataset is missing, and the actual screen resolution has to be imputed (with potential errors). My question to @alexmlfranklin. Is my logic correct? Can the HQ column be provided as it is currently empty? I'm also curious if playing at fullscreen changes how the coordinates are recorded.
\nThanks.
\nSee an example below. Chart on the left represents click screen coordinates, on the right -room coordinates
I think this is caused by resizing the window. When we start the game, it pops out a window of size 660x880. If we resize the window (or go to full screen) then the screen_coor_x can become larger than 880 and screen_coor_y can become larger than 660. I found that 95% of users keep the window in the popped out 660x880 size.
Great question, and thanks for your answer Chris! We can confirm that screen_coor depends on the size of the window, which can be resized by the player on some platforms. We can also confirm that both screen_coor and room_coor do not change based on whether the game is rendered in high quality.
", "rawMarkdown": "Great question, and thanks for your answer Chris! We can confirm that screen_coor depends on the size of the window, which can be resized by the player on some platforms. We can also confirm that both screen_coor and room_coor **do not** change based on whether the game is rendered in high quality.", "votes": null } ], "comments": [ { "id": 2145306, "author_name": "cdeotte", "author_url": "", "post_date": "02/14/2023 23:25:20", "content": "I think this is caused by resizing the window. When we start the game, it pops out a window of size 660x880. If we resize the window (or go to full screen) then the screen_coor_x can become larger than 880 and screen_coor_y can become larger than 660. I found that 95% of users keep the window in the popped out 660x880 size.
Great question, and thanks for your answer Chris! We can confirm that screen_coor depends on the size of the window, which can be resized by the player on some platforms. We can also confirm that both screen_coor and room_coor do not change based on whether the game is rendered in high quality.
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "2134892": "So I've been doing some EDA on the dataset and it seems that screen coordinates (columns screen_coor_x, screen_coor_y) represent absolute screen coordinates (probably centroid of a touch) and there seem to be two distinct screen resolutions. Something like 640x800 and 1920x1400. I assume these coordinates were recorded at High and Normal Quality modes. Unfortunately, the HQ column in the dataset is missing, and the actual screen resolution has to be imputed (with potential errors). My question to @alexmlfranklin. Is my logic correct? Can the HQ column be provided as it is currently empty? I'm also curious if playing at fullscreen changes how the coordinates are recorded.\nThanks.\nSee an example below. Chart on the left represents click screen coordinates, on the right -room coordinates", "2145306": "I think this is caused by resizing the window. When we start the game, it pops out a window of size 660x880. If we resize the window (or go to full screen) then the `screen_coor_x` can become larger than 880 and `screen_coor_y` can become larger than 660. I found that 95% of users keep the window in the popped out 660x880 size.", "2147662": "Great question, and thanks for your answer Chris! We can confirm that screen_coor depends on the size of the window, which can be resized by the player on some platforms. We can also confirm that both screen_coor and room_coor **do not** change based on whether the game is rendered in high quality." }, "source": "meta" }