I've did the exact same settings except the > In the Hook tab select "Inject suspended process" under injection mode. The game still has the same issue with the mouse, and it crashed a couple of times.
Is there somewhere a checklist of options that i need to change in order to make it work ?
Appreciate the time !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
nothing connected except the mouse, keyboard and the monitor. I had reconnected the mouse with no effect. Whats strange is that it worked 1st day, not perfect, but still... and nothing changed.
Now looking for a fix i saw that the gameplay can be improved using these tools to emulate older configs, but you need to know what to change...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have managed to start the game, the issue that persists is the mouse - its stuck looking at the floor, seems like the game interprets a continuous command to look down and right for the mouse, no matter the settings tried.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This mouse problem is often due to a problem in Microsoft DirectInput that at some point changed its behavior. If the problem is what I think you should fix it following these steps:
use the last DxWnd release downloaded from SourceForge (I imagine that you already did, but just in case ...)
set the menu "Options -> Expert mode". This will enable the full set of DxWnd features
update the game configuration and enter the "Input" tab
check two flags in this panel, that is "Hook dinput" and "Emulate mouse relative movement".
In case this doesn't work, maybe the game uses DirectInput version 8, in this case try to clear "Hook dinput" and set the "Hook dinput8" flag.
Hopefully it may work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
just to mention - i have both autoconfig and mw4 exe's in DxWnd - and I am changing in both the same settings.
mouse buttons works, cause i can shoot, just the torso is not, its like you press right and down continuously....just looking at mud...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know if mine version is 2.0 because I can't install 2.0 patch (error 0036), but I don't think it's either 1.5 or 3.0. With the in-game mouse enabled (and the Mouse X Axis Torso setting) and some DxWnd tweaking it works here in Win7. You can try my test profile, but unfortunately the profile for Win7 may not work in Win10.
Update:
Looking in the game folder, I see MW4.ICD, which is definitely an exe. If the game is not hooked, you can try "Hook-Shared hook" flag yet.
The game uses dinput.dll (not dinput8.dll). Windows 10 had far more dinput problems with older games than Win7. There must be a problem somewhere.
All I see in log about mouse is message=0x200(WM_MOUSEFIRST/MOUSEMOVE)
Fixes for dinput are in the Input-DirectInput section, but you probably tried the flags there. Maybe @gho will have better catches when he tries it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My testbed is set, but the behavior is puzzling. After a few crash with default configuration, I set the uploaded configuration "Mechwarrior 4 Ve02.dxw" and things went better, though I had a few unreplicable crash. In the end I was able to play the training mission and I never had input problems with the mouse control.
Curiously, in these circumstances if I try to apply my trick of hooking dinput and setting the emulate relative mouse control, then the mouse is blocked at the center of the window. The problem with this trick is that it can't be used always, it works only when needed.
But I suppose you're having some different kind of problem that I can't replicate.
If you have any cursor movement enhancer tool (I can't dream which one, but there's plenty of them) try disabling it.
Otherwise, you should set logging options to capture input and post here the log file in the hope that it may tell something. The logging options to catch this strange effect are quite rich, so try to replicate the event quickly because the log file will grow at a rocket speed! During the experiment try to move the locked cursor, then kill the game.
I tested this game a long ago. I needed the Use offscreen 3D tweak as well.
The game mouse is working fine, I initially forgot to have the setting enabled in the menu.
Additionally, when switching menus, the game errored with a CreateBlade code error, but it continue to work, until you saw the game isn't playable with artifacts everywhere.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
log seems pretty long but i just fired up the game, went to instant action, and used the mouse to fire and try to torso twist. it has 35mb and cant be attached here. what is the max size for attachments?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ach, I forgot to ask you to set also the "Hook dinput" flag to get some meaningful log.
Never mind, I tried to capture some logs on my testbed. As I said, if I set the "Emulate mouse relative movement" flag I get a blocked cursor, but there is another flag that can fix this, that is the "input:ForceAbsoluteAxis" tweak (this flag is in the "Tweak" configuration tab!).
I am pretty sure that our systems don't behave in the same way, but this is something that it is worth trying:
1) set the "Input / Hook dinput flag" and the "input:ForceAbsoluteAxis" tweak
2) if this doesn't work, try setting ALSO the "Input / Emulate mouse relative movement" flag
3) as a last resort, if all is not working, you could repeat the two steps but using "the "input:ForceRelativeAxis" tweak, though in theory this should not work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
same issue. setting "input:ForceRelativeAxis" tweak and emulate relative movement made the mouse stuck in the menus as well, so worse.
new log with flag Input->DirectInput-> Hook dinput set
Hi,
I have tried to get MW4 to work, actually it worked once, in window mode, but next day the game starts and i cant use the mouse anymore. its just stuck looking at mud. Trying to find a fix I saw a message recommending DxWnd: https://bg.battletech.com/forums/computerconsole-games/mw4-any-of-them-in-windows-10/
I've did the exact same settings except the > In the Hook tab select "Inject suspended process" under injection mode. The game still has the same issue with the mouse, and it crashed a couple of times.
Is there somewhere a checklist of options that i need to change in order to make it work ?
Appreciate the time !
Any chance you have some USB controller attached to your PC that has taken over the game controls?
nothing connected except the mouse, keyboard and the monitor. I had reconnected the mouse with no effect. Whats strange is that it worked 1st day, not perfect, but still... and nothing changed.
Now looking for a fix i saw that the gameplay can be improved using these tools to emulate older configs, but you need to know what to change...
Note:
"Inject suspended process" is now "Inject DLL" if I'm not mistaken, you should try it.
I have managed to start the game, the issue that persists is the mouse - its stuck looking at the floor, seems like the game interprets a continuous command to look down and right for the mouse, no matter the settings tried.
This mouse problem is often due to a problem in Microsoft DirectInput that at some point changed its behavior. If the problem is what I think you should fix it following these steps:
Hopefully it may work.
:(
tried -same result.
with 1st settings mouse did not work at all.
with Directinput 8 it worked in the menus, but not in game.
clearing any other settings for mouse - works in menus, not in game..
damn...
Blind shot - Input-Joystick-Hide joystick
Just an idea.
nope :(
just to mention - i have both autoconfig and mw4 exe's in DxWnd - and I am changing in both the same settings.
mouse buttons works, cause i can shoot, just the torso is not, its like you press right and down continuously....just looking at mud...
What MechWarrior 4 is this, have you used any patches?
mw4 original iso from https://www.myabandonware.com/game/mechwarrior-4-vengeance-dh3#download
with MW4 Update 2.0 patch applied.
I don't know if mine version is 2.0 because I can't install 2.0 patch (error 0036), but I don't think it's either 1.5 or 3.0. With the in-game mouse enabled (and the Mouse X Axis Torso setting) and some DxWnd tweaking it works here in Win7. You can try my test profile, but unfortunately the profile for Win7 may not work in Win10.
Update:
Looking in the game folder, I see MW4.ICD, which is definitely an exe. If the game is not hooked, you can try "Hook-Shared hook" flag yet.
Last edit: huh 2022-12-09
I'm going to try to make a testbed and see ...
@huh - tried everything, issue still present.
let me know what info you need for that testing....
The game uses dinput.dll (not dinput8.dll). Windows 10 had far more dinput problems with older games than Win7. There must be a problem somewhere.
All I see in log about mouse is message=0x200(WM_MOUSEFIRST/MOUSEMOVE)
Fixes for dinput are in the Input-DirectInput section, but you probably tried the flags there. Maybe @gho will have better catches when he tries it.
My testbed is set, but the behavior is puzzling. After a few crash with default configuration, I set the uploaded configuration "Mechwarrior 4 Ve02.dxw" and things went better, though I had a few unreplicable crash. In the end I was able to play the training mission and I never had input problems with the mouse control.
Curiously, in these circumstances if I try to apply my trick of hooking dinput and setting the emulate relative mouse control, then the mouse is blocked at the center of the window. The problem with this trick is that it can't be used always, it works only when needed.
But I suppose you're having some different kind of problem that I can't replicate.
If you have any cursor movement enhancer tool (I can't dream which one, but there's plenty of them) try disabling it.
Otherwise, you should set logging options to capture input and post here the log file in the hope that it may tell something. The logging options to catch this strange effect are quite rich, so try to replicate the event quickly because the log file will grow at a rocket speed! During the experiment try to move the locked cursor, then kill the game.
nothing used for cursor/mouse. i even killed the manufacturer driver tool.
where is dxwnd saves the log? i used the seetings you posted but i cant find where it was saved...
If you set the logging as in the picture and launched and exited the game, dxwnd.log should be in the game folder.
In the game folder, file dxwnd.log
I tested this game a long ago. I needed the Use offscreen 3D tweak as well.
The game mouse is working fine, I initially forgot to have the setting enabled in the menu.
Additionally, when switching menus, the game errored with a CreateBlade code error, but it continue to work, until you saw the game isn't playable with artifacts everywhere.
log seems pretty long but i just fired up the game, went to instant action, and used the mouse to fire and try to torso twist. it has 35mb and cant be attached here. what is the max size for attachments?
Compress the log with Winzip, 7-zip or Winrar. Then he will definitely fit in here.
done
Ach, I forgot to ask you to set also the "Hook dinput" flag to get some meaningful log.
Never mind, I tried to capture some logs on my testbed. As I said, if I set the "Emulate mouse relative movement" flag I get a blocked cursor, but there is another flag that can fix this, that is the "input:ForceAbsoluteAxis" tweak (this flag is in the "Tweak" configuration tab!).
I am pretty sure that our systems don't behave in the same way, but this is something that it is worth trying:
1) set the "Input / Hook dinput flag" and the "input:ForceAbsoluteAxis" tweak
2) if this doesn't work, try setting ALSO the "Input / Emulate mouse relative movement" flag
3) as a last resort, if all is not working, you could repeat the two steps but using "the "input:ForceRelativeAxis" tweak, though in theory this should not work.
same issue. setting "input:ForceRelativeAxis" tweak and emulate relative movement made the mouse stuck in the menus as well, so worse.
new log with flag Input->DirectInput-> Hook dinput set