i think i know how to fix the movement sliding bug

[DarkACB]

i noticed (along with everyone else) that the sliding bug only occurs when you stop while moving the mouse. so i thought, why not just make an autohotkey script to restrict the mouse from moving for, like, a hundredth of a second after w, a, s or d is released? i am confident that this would fix the problem by simply making the bug impossible to recreate. problem is that fallout nv, like most 3d games, uses delta movement to move the camera, and i dont know what the **** im doing. so after trying to make an autohotkey script, i give up and turn to steam.

im hoping that someone else with this problem who knows autohotkey much better than me will see this post and make a script to fix it.

my idea for the function of the script would be to:

1) check if w, a, s or d is released, then ignore it if it is

2) while still ignoring the release, stop the movement of the camera

3) release the keys and mouse

4) finally, (and most importantly) it must use DllCall("mouse_event", uint, 1, int, x, int, y, uint, 0, int, 0) to work with the actual game

P.S. i dont know if that exact line of code needs to be used, so if anyone is going to make the script, feel free to edit that code if it works better.

[DarkACB]

so far, and surprisingly, i havent recieved a fix on the autohotkey forums and i really dont want to repost since im pretty sure its against the rules. just wanted to say that mostly in order to bump this post. lol. im also surprised i havent even got a comment on this yet either.

[talgaby]

Problem with games like this is that they usually use old input methods and injecting a script at OS level is simply too high since they take input from lower. This is why sometimes it is difficult to create a standard autoclick script for some games, even though that problem has some really basic AHK solutions.

[DarkACB]

i have tested a script that moves the mouse in the game. it definitely works.

[DarkACB]

it just has to call the "mouse_event" to work, since the only problem is the way almost every 3d game handles the mouse.

[Killertruth186]

I kind of do have the camera just looked up and spinning around like crazy when i was trying to use the trackpad on my laptop during the gameplay, i had then later fixed that by simply disconnecting and reconnecting my trackpad ribbon cable.

[DarkACB]

not to sound mean or anything, but, how is this related?

[Killertruth186]

Originally posted by DarkACB:

not to sound mean or anything, but, how is this related?

Ah, sorry. That was the camera movement. But i used to have movement issue once with some games, as it turns out it was just the keys on my keyboard on my laptop.

[DarkACB]

Originally posted by CovertBrony:

Originally posted by DarkACB:

not to sound mean or anything, but, how is this related?

Ah, sorry. That was the camera movement. But i used to have movement issue once with some games, as it turns out it was just the keys on my keyboard on my laptop.

this is a bit different. its actually the game itself moving the character a few feet after stopping. i dont know if theres a fix but what im trying to do is to simply make the bug impossible to recreate.

[Killertruth186]

Originally posted by DarkACB:

Originally posted by CovertBrony:

Ah, sorry. That was the camera movement. But i used to have movement issue once with some games, as it turns out it was just the keys on my keyboard on my laptop.

this is a bit different. its actually the game itself moving the character a few feet after stopping. i dont know if theres a fix but what im trying to do is to simply make the bug impossible to recreate.

Yeah, I thought it was the software for me at first. Until I disassembled my laptop keyboard and noticing that the "w" key was sticking. I was only going forward a few feet after stopping as well. It is important to eliminate the hardware factor before the software factor. So that way you wouldn't have the software breaking other mechanics.