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

Messenger of the Gods double mouse cursor; window incorrectly captured #1104

Closed
emxd opened this issue Jan 29, 2022 · 4 comments · Fixed by #1105 or #1108
Closed

Messenger of the Gods double mouse cursor; window incorrectly captured #1104

emxd opened this issue Jan 29, 2022 · 4 comments · Fixed by #1105 or #1108

Comments

@emxd
Copy link

emxd commented Jan 29, 2022

Describe the bug
Messenger of the Gods is an old czech point and click adventure game. The game starts and technically works, but instead of running at 640x480 full screen it runs in a window in the middle of the screen with wrong dimensions (not 640x480) and also it has 2 mouse cursors. One mouse cursor is the classic Windows mouse cursor that is captured in a 640x480 box in the upper left corner of the screen. The other mouse cursor is the game cursor that works inside the game window. The game mouse cursor copies the movements of the Windows cursor. Some graphical deformations are also created because of the wrong window size. The game was originally a DOS game that was wrapped as a Windows game at the last minute.

Expected behavior
To be able to run the game full screen at 640x480 resolution. This would hopefully also fix the double mouse cursor problem.

Video
https://icedrive.net/s/TayQx8GiWY4GR69NRawhBzu92TNk

Environment (please complete the following information):

  • otvdm 2252
  • Win10 20H2

Additional context
link to the game -> https://www.old-games.ru/game/download/get.php?fileid=13824&modal=1
Tried running the game with the 640x480 compatibility set, but it made no difference. The game was still captured in a window with the 2 mouse cursors.

Trace
set WINEDEBUG=+all,-snoop,-ldt,-fixup,-module,-global,-local,-disasm,-syslevel,-thunk
https://icedrive.net/s/uRaWuGG67A2Xx5SAwAWh8kWAxwwA

@cracyc
Copy link
Contributor

cracyc commented Jan 30, 2022

This program uses dispdib so it's difficult enough to make it work at all, note that it doesn't work in ntvdm. #1105 is really the best that I can do right now. The program grabs the cursor into the upper left, if you use the windows key to break it then you can maximize the window and the windows pointer is hidden. The main issue then is you can't point to the very top.

@emxd
Copy link
Author

emxd commented Jan 30, 2022

Thank you, this is still very useful. I used autohotkey to turn it into a borderless window and now it's basically identical to full screen 640x480.

https://i.ibb.co/GWpWBnJ/1.png

The only exception being the white aspect ratio bars on the side instead of the usual black bars. Come to think of it, would it be possible to make the background surface not white, but black? To have the usual black bars. I could technically change the desktop resolution to 4:3 and get black bars that way, but this would be nicer.

Edit: Taking it back, it seems that I can run the game with the 640x480 compatibility flag + borderless window maximization from autohotkey and I get a nice 640x480 full screen with the black bars. I'm not sure how much the dispdib emulation can be improved, but this seems good enough. Certainly better than I expected.

Again, thank you. You can close the ticket if there's nothing to add.

@cracyc
Copy link
Contributor

cracyc commented Jan 30, 2022

It's possible to make it borderless by default but that will make it harder to use other programs that use dispdib like Out of this world. Another problematic one is Burncycle which takes over the pointer when it has focus which makes it impossible to move or resize the window, wonder if autohotkey would help with that.

@emxd
Copy link
Author

emxd commented Jan 31, 2022

@cracyc
One more thing. If I go to the main menu -> settings -> back the game crashes with a 005 error. I checked and 005 is a file access error. I did try some basic things like removing read only flags with

attrib -r *.* /s /d

and moving the game directory to a place with an 8.3 filename but none of that helped. If you've got the time could you take a look? Thank you

here's a video https://icedrive.net/s/bhBiWQ496RwPCVPz1f3WXiBAjvZN

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