![]() ![]() One could either modify a live distro to embed the necessary software, or simply run the install process with a USB key as target, then boot from it just like an internal disk and proceed to install WINE and remaining software. ![]() Then if I close and load the game with the cursor in bottom-right:Īnd if I launch the game with the mouse in the middle, it will work fine.Not sure it does exist, but shouldn't be hard to do by hand. This is the mouse area that will be available when I'll load my state: If I press "Run" when my mouse in the top-left corner: I made a bit more testing, the problem seems to be because the mouse cursor when you launch the game is not at the same place as the ingame cursor, let me try to explain with a save state I made in Monkey Island 2 with PUAE core with the ingame cursor more or less in the middle of the screen: is there anything the DOSBox core can do about initial placement of mouse cursor or is that something on the RA side? The question could RA centre the cursor at game startup? This isn't exactly a proper solution but it definitely masks the problem. (Then again, perhaps they move at the same speed in terms of pixels-per-second?) The result is that if you move the mouse cursor up and down several time the in-game cursor finally "overtakes" the system cursor and from now on it will always reach the screen border faster than the system cursor.Īlso, when entering game focus mode, RA centres the in-game cursor, which shows RA has the ability to capture and modify that cursor. More specifically it moves faster than than the system screen - this is clearly visible when you enter and exit game focus mode so that both the system and in-game cursors become visible. Interestingly, the in-game cursor moves at a different speed than the system cursor. This results in a perceived inability to move the cursor lower - because the system cursor can't be moved past the screen's bottom border. The result is that if you now move the mouse cursor down the invisible OS system will reach the border sooner than the visible in-game cursor. In case of Warcraft 2 it is placed towards the upper-left corner on the game logo: When a game launches the (invisible) system cursor is placed in the centre of the screen, but the (visible) in-game DOS cursor is not necessarily centred. Yes, this is exactly the problem! Here's a bit more insight into what's going on: On my Linux VM however there's definitely something wrong: I originally reported this as a DOSBox-SVN core bug ( libretro/dosbox-svn#58) but the core authors claims this is a limitation of RA and other cores that use the mouse suffer from the same problem. It is then obvious that the restriction in the game cursor movement comes from the OS cursor reaching the lower border of the screen and not being able to move past it. It is instructive to enable and then immediately disable Game Focus mode - then you can see both the DOS game cursor and the OS cursor moving at the same time. If I enable Game Focus the problem instantly disappears. Same happens to other games that use the mouse (Syndicate, Settlers 2). After moving the cursor around it unlocks at some point and can move on the whole area of the screen. Notice how the mouse cursor is placed on "Show Credits" button - at this point it is impossible to move the cursor lower, which makes the "Exit Program" button unreachable. For example, consider this screenshot from Warcraft 2 menu running on DOSBox core: In games that use mouse, the initial mouse movement area is restricted. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |