Cheat Engine

[JJXB]

I've been poking around in vegas 2 trying to see if i can modify the FOV amongst other things. However i can only get so far before I run into problems.

I already know how to do the search for the FOV values and how to eliminate the false values that aren't modifiable in any way. The only trouble is assessing the code that modifies it.

[deama1234]

[JJXB]

[deama1234]

So, you just want to change your default FOV, no other ones?

[JJXB]

[deama1234]

You could see what accesses one of the instructions then find out which one is the FOV you use without any zooms; then isolate it from the rest. Then modify it to whatever you want, then if the script detects anything other than the "normal FOV", make it inject a fake FOV.

[JJXB]

sorry for the slow reply, was playing other things and real life got in the way of doing other things.

coming back with a fresh mind on it though, before i can check for the value, i need to be able to monitor the value. i've already alloc'd and registered the symbols to store the value for easy viewing in the cheat table. but i can't seem to get the [esi+30] into the [esi30] memory (esi30 being the registered symbol). i tried:

[JJXB]

Okay, something i've done with it got it to stop acting strange with some of the FOV's. Still ain't perfect but looks like the detection is at least half kicking in now as it should.

[JJXB]

Okay, looking at it, the one function i have fundamentally no understanding as to it's contribution is

[JJXB]

bumping in the hopes someone can help me shed more light on how this works than i've already done.

[JJXB]

Little to no progress on the FOV front i'm afraid. i have managed to find out more general camera variables however. trouble with it is that i can't seem to get the stuff to stick if i change things because the game's code that manages any of the camera variables (including FOV it seems) loops, writes and reverts any changes in a matter of milliseconds.
So i figured it'd be best if i uploaded what i have in a cheat table as is and let others look at the ct to see if they can catch anything i couldn't. I'll still look at doing things with this as i want to learn more and do more but i am seriously needing some help with figuring out how the numbers get fed into the loop and how I can influence those numbers before or after they enter said loop in a reliable fashion.

[JJXB]

As the thread title says, PROGRESS!
went back to the drawing board and finagled some way of having a readily modifiable FOV with caveats.
Current process is this:
Compare [EDI+30],49.725
if equal or greater , Compare [EDI+30],62
if less or equal, run the code to add [FOVVALAdd] into the process (with adjustable FOVVALADD, if zero it won't add anything)
in the event that first check is less or second check is greater, it just executes standard FOV routine so it only changes anything between 49.725 and 62 (49.725 being crouching FOV and 61.something being sprint FOV).

Very limited use case thus far but it catches all the instances that i'd want to change the FOV (Standing, Crouching, Sprinting Etc) while leaving alone more precise aiming modes. Still has weird anomalys but i will upload the .CT file for your examination/criticism (kind of messy and stuff but progress is progress, right?).
i'm gonna build up a beta Trainer for this to enable the code change that also allows for changing the amount the FOV is modified and post it up later.

[JJXB]

not had time to work on it the past month or so due to various reasons unfortunately. plus most of my CT files have gone kaput because i've lost them in a laptop move (massive upgrade). however the fact i uploaded my last bout of progress on this did help me make sure to get it back in this case. for all my other personal projects i have to start from scratch but i have no real issue in doing so because where would i challenge myself otherwise?

i do plan on doing more work at some point but at the second i gotta tweak vegas 2 since now on my new laptop it runs at 160+ fps at 1920x1080. that and i need to break my FO: new vegas addiction

[deama1234]

You should do floating point comparisons with the FPU, otherwise you can have "weird" things happen.

[JJXB]

how would you go about doing AA code for FPU comparisons?

I know that the fld dword ptr [edi+30] tends to load the FOV itself into the FPU Extended Register from [edi+30] but the edi address tends to vary based on the current viewmode (zoomed, not zoomed etc).

my script currently modifies by first comparing what [esi+30] is then if it's between 49 and 62 float, doing a modified routine of doing the fld then an fadd with a custom var(whatever number is in FOVADDVal as a value) before moving onto the fmul. if it's below 49 or above 62 then it just only does the fld then fmul like standard.

when it comes down the FOVADDVal custom var, i made it flexible enough that i could manipulate it by adding an entry to the table to add to it on the fly and test. but if i want to define it in the script i only have to write a value to add before the checks for the base FOV kick in.

download my CT and have a look yourself if you think i might be doing something wrong for sure though. it's why i made it available to d/l here, to make sure others could check over it without any trouble.