Quantcast

Jump to content

» «
Photo

[SA] Y-axis sensitivity issue

5 replies to this topic
aStiffSausage
  • aStiffSausage

    Formerly Oksu

  • Members
  • Joined: 30 Sep 2010
  • Finland

#1

Posted 18 September 2013 - 08:16 PM

I've been messing around a bit with sensitivity through CLEO, and I noticed an issue with Y-axis sensitivity. It's not actually adjusted whenever you change the value, either with memory writing or through options, it's appears to be a constant value.

What this means, when you set the sensitivity in options to lowest, X-axis movement (left/right) is at it's slowest while Y-axis movement (up/down) is still fast. Setting sensitivity to highest value will leave Y-axis movement speed to same value as it was before, while X-axis movement is increased. Setting the sensitivity to around 5-7 kind of works, but that just seems silly.

Just asking, is there a mod, or another memory address, which sets Y-axis sensitivity to same which X-axis is?

Address used to change sensitivity, also changes the sensitivity in options:
0xB6EC1C - [float] Mouse sensitivity


DK22Pac
  • DK22Pac

  • Feroci
  • Joined: 12 Apr 2009
  • Ukraine
  • Best WIP Mod 2014 [Grand Theft Auto 3D Contribution]
    Contribution Award [Mods]

#2

Posted 18 September 2013 - 09:16 PM

Possibly this?

0xB6EC18

aStiffSausage
  • aStiffSausage

    Formerly Oksu

  • Members
  • Joined: 30 Sep 2010
  • Finland

#3

Posted 18 September 2013 - 09:58 PM Edited by oksa8, 19 September 2013 - 12:23 AM.

Yes, thank you! The sensitivity works as it should when I set Y-axis to match X-axis after slowing them down. I made this little "fix"-script, which seems to work okay for me. The problem seems to be really common, so why not share it? Though I'd like to know if this has any flaws in it:

 

{$CLEO}
0000:NOP
while true
wait 0 ms
0A8D: 0@ = read_memory 0xB6EC1C size 4 virtual_protect 0
0A8D: 1@ = read_memory 0xB6EC18 size 4 virtual_protect 0
    if
    8045:   not 0@ == 1@  // (float)
    then
    0A8C: write_memory 0xB6EC18 size 4 value 0@ virtual_protect 0
    end
end

ThirteenAG
  • ThirteenAG

    Gangsta

  • Feroci
  • Joined: 29 Dec 2008
  • None
  • Contribution Award [Mods]

#4

Posted 19 September 2013 - 12:42 AM

I have the same script for VC 1.0, made a while ago.

{$CLEO}
0000:
wait 100

while true
05E0: 0@ = read_memory 0x94DBD0 size 4 virtual_protect 1  //X
wait 1000
05DF: write_memory 0xA0D964 size 4 value 0@ virtual_protect 1           //Y
end

aStiffSausage
  • aStiffSausage

    Formerly Oksu

  • Members
  • Joined: 30 Sep 2010
  • Finland

#5

Posted 19 September 2013 - 01:07 AM

ThirteenAG

 

I'm thinking of the possibility, what if, let's say, player has modified FOV-values when aiming with sniper rifle, and also has modified mouse sensitivity to get smoother mouse movement while aiming. He's then faced with a problem that only his X-axis sensitivity is changed, whereas Y-axis sensitivity is still the same. Just tried that out myself and it seems to work properly, both while changing sensitivity from options and while modifying X-axis sensitivity with another script.

 

I'm just a bit worried usually when it comes to memory coding... That's why I'd like to know if that's good way to do it. :)


DK22Pac
  • DK22Pac

  • Feroci
  • Joined: 12 Apr 2009
  • Ukraine
  • Best WIP Mod 2014 [Grand Theft Auto 3D Contribution]
    Contribution Award [Mods]

#6

Posted 19 September 2013 - 09:39 PM

Your code looks fine.

Another way to get this result - patch all references to 0xB6EC1C with 0xB6EC18;





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users