exoscoriae / eXoDOS

eXoDOS
69 stars 3 forks source link

Viper (1998) #5099

Closed Python-Exoproject closed 3 months ago

Python-Exoproject commented 5 months ago

This game is the only one running on Dosbox 0.63 so if we can move it off this then we can remove 0.63 from the emulator folder for eXoDOS. To that end the Staging guys have figured out the issues the game has on later versions and forks of dosbox (https://github.com/dosbox-staging/dosbox-staging/issues/3585) but will not be implementing it as its not worth the complexity to the code for one game.

They also discovered however that dosbox X is compatible with specific settings in the conf, so here is the required conf (dosbox.zip)

This requires we use the version of x in the 'X2' folder so switch the game to use that in dosbox.txt

exoscoriae commented 3 months ago

mouse isn't capturing in x2

Tried to force lock it using ctrl-f10 and the mouse didn't react

exoscoriae commented 3 months ago

seems it was because int33 was disabled in the conf is there a reason for that?

I have re-enabled it.

moved it to x2 with the mouse re-enabled

Python-Exoproject commented 3 months ago

The game is less stable with int33=true and will occasionally give just a black screen. Int33 is dosbox x way of saying internal mouse driver=true.

The reason the mouse didnt work is because I had intended to provide the external mouse driver "amouse.com" which allows the game to have a mouse even with the internal driver disabled with int33=false, however it looks like I added it to the conf but overlooked adding it to the zip archive I posted.

Here is the mouse driver: AMOUSE.zip. Put it in the game folder and set int33 back to int33=false. You should still have a fully functioning mouse in the game and it will be more stable

exoscoriae commented 3 months ago

cool. done