Hebe Vollmaus
10-27-24, 12:07 PM
Hi all.
1. Mouse jumps are needed in-game.
2. There is no bug!
3. A so called "fix" or a solution cannot be made without original game-sources, so there can only be a workaround.
A bit longer description:
--
1. Mouse jumps are needed in-game.
If in doubt please check for yourself as follows:
o make a copy of sh3.exe
o rename original sh3.exe to sh3_ORIG.exe
o rename copy of sh3.exe back to sh3.exe
o with a HEX-editor search in sh3.exe for "SetCursorPos"
o change to "SetCaretPos" and append in HEX-view 0x00 (as it is one letter shorter)
o start the game and see for yourself
Hint:
Cursor is what Windows calls your MousePointer.
Caret is what Windows calls your blinkin Cursor for example in a CommandPrompt.
By changing the 1st to 2nd the game no longer moves your mouse around.
The game is no longer playable. All the Views, when the Mouse is captured, like innert Periscope, UZO, or Bridge, moves like stupid. Showing uncontroled and unusable behavior.
So the SetCursorPos is needed which means Mouse jumps are needed in-game.
o delete sh3.exe
o rename sh3_ORIG.exe back to sh3.exe
--
2. There is no bug!
As you may have seen by reproduce the steps above, the game works as intended.
There is no bug in original SH3 in relation to MouseJumps and FireButton.
The so called "Fire Button Bug" jumps in as a problem only when various so called "Resolution-fix" (res-fix) is in-use. These "simple" (simple in case of SH3-GUI-programming) things do stretch things to the right positions for the requested resolution on screen, but do not stretch also Mouse positions requested by the game.
--
3. A so called "fix" or a solution cannot be made without original game-sources, so there can only be a workaround.
This should be self-explanatory.
As of today i have not seen a working freely available workaround for the mouse-jumps.
There may or may not one on the future, but this is like talking about "unreleased eggs".
For example there still exist things as EXE-patches and DLL-patches for other things.
For this "Fire Button Bug" there still exist enough workarounds as already shown in older posts here on Subsim. Button de-aktivation, or use of various GUI-replacements as so called "widescreen mods" for bigger Screens like 1920x1080.
https://www.subsim.com/radioroom/showpost.php?p=1885634&postcount=5
I like to append one which is often forgotten in those tips: Move the Firebutton by yourself.
Greetings.
--
563 Mods found (100 activated)
1. Mouse jumps are needed in-game.
2. There is no bug!
3. A so called "fix" or a solution cannot be made without original game-sources, so there can only be a workaround.
A bit longer description:
--
1. Mouse jumps are needed in-game.
If in doubt please check for yourself as follows:
o make a copy of sh3.exe
o rename original sh3.exe to sh3_ORIG.exe
o rename copy of sh3.exe back to sh3.exe
o with a HEX-editor search in sh3.exe for "SetCursorPos"
o change to "SetCaretPos" and append in HEX-view 0x00 (as it is one letter shorter)
o start the game and see for yourself
Hint:
Cursor is what Windows calls your MousePointer.
Caret is what Windows calls your blinkin Cursor for example in a CommandPrompt.
By changing the 1st to 2nd the game no longer moves your mouse around.
The game is no longer playable. All the Views, when the Mouse is captured, like innert Periscope, UZO, or Bridge, moves like stupid. Showing uncontroled and unusable behavior.
So the SetCursorPos is needed which means Mouse jumps are needed in-game.
o delete sh3.exe
o rename sh3_ORIG.exe back to sh3.exe
--
2. There is no bug!
As you may have seen by reproduce the steps above, the game works as intended.
There is no bug in original SH3 in relation to MouseJumps and FireButton.
The so called "Fire Button Bug" jumps in as a problem only when various so called "Resolution-fix" (res-fix) is in-use. These "simple" (simple in case of SH3-GUI-programming) things do stretch things to the right positions for the requested resolution on screen, but do not stretch also Mouse positions requested by the game.
--
3. A so called "fix" or a solution cannot be made without original game-sources, so there can only be a workaround.
This should be self-explanatory.
As of today i have not seen a working freely available workaround for the mouse-jumps.
There may or may not one on the future, but this is like talking about "unreleased eggs".
For example there still exist things as EXE-patches and DLL-patches for other things.
For this "Fire Button Bug" there still exist enough workarounds as already shown in older posts here on Subsim. Button de-aktivation, or use of various GUI-replacements as so called "widescreen mods" for bigger Screens like 1920x1080.
https://www.subsim.com/radioroom/showpost.php?p=1885634&postcount=5
I like to append one which is often forgotten in those tips: Move the Firebutton by yourself.
Greetings.
--
563 Mods found (100 activated)