Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

200% screen causes dmddevice settings to be halved when saved and doubled when read. #443

Open
ivo71 opened this issue Oct 12, 2023 · 0 comments

Comments

@ivo71
Copy link

ivo71 commented Oct 12, 2023

I initially reported this on vpx github, but someone suggested to post it here.

Describe the bug
I am not sure if this is a bug or if this is just supposed to be different in vpx 10.8 vs 10.7.
When leaving the playfield screen accidentally at 200%, versions before 10.8 save the settings of the external dmd correctly in dmddevice.ini. When at 200% and starting 10.8 and saving the position of the external dmd, the saved settings are halved and when loading a table with the correct dmd position settings, the value is doubled before it is displayed. For example when the dmd position is saved at x=4400, then 10.8 will display it on x=8800, which then results in seeing only the dmd window (using alt-tab) with a pinballX logo in it. When positioning the virtual dmd on 0,0 and dragging it to the right place on the backscreen and saving the settings while vpx 10.8 is loaded at 200% playfield screen setting, the saved settings will be halved (x=2200 instead of 4400, etc.).

To Reproduce
Steps to reproduce the behavior:

set windows playfield screen at 200%
start vpx 10.8 and load a pinball machine.
save correct settings of external dmd.
check dmddevice.ini and notice that the saved settings will be half of the actual setting.
Or, when loading a pinball machine in vpx 10.8 while playfield screen is at 200%, the dmd will not be shown and alt-tab will show a windows with the vpx 10 logo instead of the virtual dmd.

Expected behavior
Position of DMD correctly saved and displayed without being affected b the 200% setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant