SureAI

Hi, my saved game seems to be corrupted, when i load it my character has a strange behaviour: he indipendently moves very very slowly to a side, if i press a direction, the animation works but really really really slow. Even autosave is corrupted the same way. Other controls (jump, shoot, enter diary ecc) seems to work well.
This bug is started after a crash (return to desktop). Previously i had other crashes, but nothing bad happened...

I've uploaded my save, hope it helps...

Delete the "bUse Joystick=1" line in your Oblivion.ini.

Wow, fast one!! Thank you!

Now i have another problem: sometimes, when i open up the menu, the game freezes and i have to kill the process.

After your answer, i've played for about 10 minutes, i pressed Space to open a crate and got the freeze (actually, the menu gets open, THEN the game freezes).
Reloading...
This time i press ESC, play for about 10 minutes, click on Save Game and... freeze! Like above, Save Menu opens then the game freeze.

Hope this is an easy-to-fix bug too!

This will have to wait for Hoxyd. Until then, try the following: delete your Oblivion.ini, and then start Nehrim WITHOUT the launcher, just through the Oblivion.exe.

Sadly i have problems with joystick again, no matter that i launch from Oblivion.exe or from the NehrimLauncher.
Situation: in Nehrim folder i have a Nehrim_default.ini WITHOUT bUse Joystick=1, in Oblivion folder i have no .ini files (actually, i have changed the name of Oblivion_default.ini, anyway there is NO bUse Joystick=1 in there). I tried many combinations without lucky.
Now i'll try to temporary disable the XBox360 controller, meanwhile i hope you find a fix.

wrong ini file. it's the one stored in the user/my documents folder. the precise path varies depending on which version of windows you use.

----edit

for example (this is what it would be on my syetem, win7 btw)
"c:\users\user\my documents\my games\oblivion\oblivion.ini"

Ouch...
Thank you, i can recover others .ini, right? (that's why they're named "default", i guess they're used on first boot... )
By the way, disabling the controller in Device Manager works like a charm, it could be a turnaround.