I had hoped that by going to version 1.6.1820 I would get rid of 2 little problems that are still there:
1. the cursor on the mini map will fail to show the surrounding terrain at any given time. I save the game when that happens and then reload that save
and all is well
2. At times the cursor will not show up on the mini map at all and the save reload thing will fix it. I was just wondering if anyone else had these little problems.
The graphics MOD on Nexus for MW is really good to BTW
Lawrence
Full Version: A better looking game
This happens to me also.
I find that if I go inside a building (generating an autosave) wait 60 secs for the game to catch up then go back outside the map has updated and every thing is fine. This used to happen to me in Morrowind all the time.
I think it has to do with how much of the information in ram has had a chance to offload to the hard drive.
Sometimes if I've been playing a while I use it as a signal to save and restart. Note I did not say quicksave and reload because I read somwhere that Oblivion dosn't completely clear the ram (in this case write every thing ram to the drive) unless you acutally quit to desktop.
Thanks,
Stormraven aka Darkstormraven
I find that if I go inside a building (generating an autosave) wait 60 secs for the game to catch up then go back outside the map has updated and every thing is fine. This used to happen to me in Morrowind all the time.
I think it has to do with how much of the information in ram has had a chance to offload to the hard drive.
Sometimes if I've been playing a while I use it as a signal to save and restart. Note I did not say quicksave and reload because I read somwhere that Oblivion dosn't completely clear the ram (in this case write every thing ram to the drive) unless you acutally quit to desktop.
Thanks,
Stormraven aka Darkstormraven
If you're referring to the bug where it stops clearing the fog of war, I've found that crossing a cell border fixes this.
The console command TB (ToggleBorders) helps with this.
The console command TB (ToggleBorders) helps with this.
QUOTE(Darkstormraven @ Dec 13 2007, 06:21 AM) 
This happens to me also.
I find that if I go inside a building (generating an autosave) wait 60 secs for the game to catch up then go back outside the map has updated and every thing is fine. This used to happen to me in Morrowind all the time.
I think it has to do with how much of the information in ram has had a chance to offload to the hard drive.
Sometimes if I've been playing a while I use it as a signal to save and restart. Note I did not say quicksave and reload because I read somwhere that Oblivion dosn't completely clear the ram (in this case write every thing ram to the drive) unless you acutally quit to desktop.
Thanks,
Stormraven aka Darkstormraven
I find that if I go inside a building (generating an autosave) wait 60 secs for the game to catch up then go back outside the map has updated and every thing is fine. This used to happen to me in Morrowind all the time.
I think it has to do with how much of the information in ram has had a chance to offload to the hard drive.
Sometimes if I've been playing a while I use it as a signal to save and restart. Note I did not say quicksave and reload because I read somwhere that Oblivion dosn't completely clear the ram (in this case write every thing ram to the drive) unless you acutally quit to desktop.
Thanks,
Stormraven aka Darkstormraven
This type of thing also happened to me. I never use autosave or quick save as I have read here they can cause trouble. I use 6 rotating saves and al ways put one in at the start of a quest.
Lawrence
QUOTE(madgamer @ Dec 13 2007, 10:32 PM)
QUOTE(Darkstormraven @ Dec 13 2007, 06:21 AM)
This happens to me also.
I find that if I go inside a building (generating an autosave) wait 60 secs for the game to catch up then go back outside the map has updated and every thing is fine. This used to happen to me in Morrowind all the time.
I think it has to do with how much of the information in ram has had a chance to offload to the hard drive.
Sometimes if I've been playing a while I use it as a signal to save and restart. Note I did not say quicksave and reload because I read somwhere that Oblivion dosn't completely clear the ram (in this case write every thing ram to the drive) unless you acutally quit to desktop.
Thanks,
Stormraven aka Darkstormraven
I find that if I go inside a building (generating an autosave) wait 60 secs for the game to catch up then go back outside the map has updated and every thing is fine. This used to happen to me in Morrowind all the time.
I think it has to do with how much of the information in ram has had a chance to offload to the hard drive.
Sometimes if I've been playing a while I use it as a signal to save and restart. Note I did not say quicksave and reload because I read somwhere that Oblivion dosn't completely clear the ram (in this case write every thing ram to the drive) unless you acutally quit to desktop.
Thanks,
Stormraven aka Darkstormraven
This type of thing also happened to me. I never use autosave or quick save as I have read here they can cause trouble. I use 6 rotating saves and al ways put one in at the start of a quest.
Lawrence
Actualy my understanding is that the autosave.bak is the most reliable save. Just delete the autosave.ess and change the extention on the autosave.bak to ess. Me I just rename the autosave.bak to save.ess or start.ess and restart the game from that point.
I also think its good advise to exit the game completely before restarting. (I actually reboot before restarting just to make sure the ram has been completely reset)
I believe I came across this information in the Construction Set WIKI but it might have been on the Unofficial Site. http://www.uesp.net/wiki/Main_Page I know it takes time away from the game, but doing a little reasearch can make the game a better play.
Stormraven aka Darkstormraven
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.