pmw57
-
Posts
95 -
Joined
-
Last visited
-
Days Won
1
Everything posted by pmw57
-
In regard to the same crashing trouble from Anvil to the Gottshaw Inn, I see that there's another Wayshrine of Zenithar between the inn and Kvatch. I'll take short odds on it being another pilgrim causing the trouble there too.
-
My crash report has been supplied to the Oblivion Reloaded group, at https://forums.nexusmods.com/index.php?/topic/2367124-oblivion-reloaded/page-704&do=findComment&comment=41057710
-
I gave myself a detect life spell, and when entering in to the troubled cells, only saw one life form in there. A Pilgrim of Zenithar with an id of 01006AD6 Issuing the following console command results n successfully getting through the trouble area, with EquipmentMode enabled. prid 01006ad6 tai Pilgrm of Zenithar processing is OffTime to double check. Get the crash first, then issue the above commands to confirm success. Yep, and when near the pilgrim, if I enable his processing once again things go crash. I think we've found what's causing the problem.
-
Narrowing the problem further, I've been testing by toggling the AI with the tai command. tai All AI processing is Off player.tai Player AI processing is Off player.tai Player AI processing is OnTurning off the AI except for me, results in no crash. I tried the same with the combat ai but with no success there. This seem to imply that some kind of creature that's spawning in a neighboring cell is the causing the issue.
-
I can skirt around the East from cell 6 1 to 7 1, around to 8 1 and 8 0 and back to 7 0 at the Inn, yet when carry on through to where 6 0 should be it crashes. How about from West? 6 1, to 5 1, to 4 1, and when going in to 4 0 it crashes. How far South do I have to go, before I can enter the Y coordinate 0 successfully? 1 0 is good, 2 0 is good, and I barely get in to 3 0 before there's trouble. After charting this out, the trouble area seems to be roughly a square from the 6 0 to 4 -2. Entering any cells within that area cause trouble. Which means, that 5 -1 and 5 -2 seem to be the centre of the problem.
-
No, quite the opposite, which means I'm the same. With them enabled things crash, and with them disabled you can cross over in to the area successfully. You can use the sdt and tdt commands to see the cell coordinates of the area that you were having trouble moving in to when equipment mode is enabled.
-
I can now reproduce the CTD. When travelling South from Horn Cave towards Ill Omen, it occurs when moving from cell 6, 1 to cell 6, 0. You can see this happen when the Oblivion Reloaded.ini file is edited so that CombatMode and EquipmentMode are set to 0. From the Oblivion console, set the debug text to mode 0, and toggle it on, with: sdt 0 tdtand you will see the PC Cell transition from "Wilderness 6 1" at the fallen tree to a long strange name of "xxxxxxxxObGateRandNV001old 6 0" It's when crossing in to that "xxxxxxxxObGateRandNV001old" area that the crash occurs for me. And as for the Gottshaw Inn, travelling East in to cell -44 -4 is okay, but any further in to -43 -4 causes the CTD when CombatMode and EquipmentMode are enabled.
-
Make sure that the dll has actually been installed, boy genius!
-
Gah! No wonder I wasn't able to experience the CTD. The OblivionReloaded.dll file wasn't being installed, and I eventually found that it was due to a user error. Yes, mine. When installing OR I accidentally chose No to a question about installing the OBSE dll file, after which it seemed impossible to get Wrye Bash to recognise it again. Finally I stumbled on how to reverse this mistake. - In the Wrye Bash settings menu (found at the bottom of the screen) export the list of allowed/disallowed OBSE plugin DLL's - Edit the list, removing the disallowed plugins that you don't want to be removed - From the settings menu, import in the updated list, and (important this) choose to not merge with the existing list, so that the existing list gets replaced. - Delete the Oblivion Reloaded installer - From the packaged Oblivion Reloaded installer, unpack to a project - Check in the General tab that the .dll file is now there - Install the project, and be damned careful to NOT HIT THE NO BUTTON, and instead press the YES button Finally, regain sanity after cursing yourself and all of your misdeeds.
-
Could that work better by unpacking to a second installer, where that second installer has everything deleted except for the ini files? That would allow you to install OR, and to then use the OR ini installer to update and anneal any changes. Is that more along the lines of what you are intending?
-
While checking out the revamping of the guide, I've just noticed an interesting detail in the Oblivion Reloaded section. Does this really mean to delete all the other files? Including the shader files and OblivionReloaded.dll and OblivionReloaded.esp ?
-
Is there anything that I can do to experience this crash, so that further exploration of what causes it can occur? I have the DVD release of Oblivion, and I don't know if you're running this version or the Steam version, nor if either have subtle differences between them. I'm wanting the opposite of what most people coming to this channel are seeking. What changes can I make so that I experience the CTD when going to Gottshaw Inn?
-
Excellent news. I had a fresh install of Oblivion (with old oblivion.ini folder moved elsewhere) on which I couldn't get it to crash, so this has me wondering what I could do to experience the CTDs, so that I may improve my troubleshooting techniques. Once you had a reliable CTD (reliability is vital here), what were the main techniques that you used to help narrow down the issue? Did they extend much further than ini configuration? If it's any help, the OR forum has a good post about EquipmentMode causing a crash based on uInterior Cell Buffer, and more useful I think is this post on several EquipmentMode issues and the benefits developers gain from good reports about these issues.
-
Thank you for the recognition. I have been tempered in the fires of JavaScript support over at sitepoint.com, which seems to have had some good impact on how I approach things.
-
I don't blame ya. Having unstable hardware is the most frustrating thing of all because it affects all sorts of different things in random ways.
-
There might be something in my process that can help you then. I didn't do this when testing just OR and OOO, but I have an extensive process to help ensure Oblivion stability. For example, here is my full list of 235 installers and 200+ installed mods 1. Wrye Bash is used to manage them. 2. BOSS is used to order them, with several added rules to improve how things are placed. 3. After ordering it's back in to Wrye Bash to right-click on the Bashed Patch and choose Rebuild Patch (CBash *beta*) 4. TES4LODGen is next used to generate the distant objects 5. Run Oblivion Mod Manager and then close, to update a file in preparation for Land Magic 6. Land Magic fixes minor tears in the landscape, and helps to bring everything together. 7. TES4LL is used last to generate the distant landscape It doesn't have to all be done every time, for example if the mod doesn't affect the outside landscape then the last 4 steps don't have to be done, but that process has resulted in the most stable environment for Oblivion.
-
Was he? Last I saw he has said two significant things about it, nothing confirming the CTD on his part yet. First, when you provided your step-by-step install process: and later when you questioned him further:
-
Don't even bother testing Oblivion yet until you have confirmed that the system changes you've made result in a more stable computer system. Use the tsts that showed your SSD was so sad, for example. It might be that the SSD is not the root cause for example.
-
And knight spines! Herring fillet, eel flesh, and knight spines all contain the reference to RSWD that's causing the problem. Excellent! I could not have asked for a more reliable way to demonstrate that your hard drive is buggered and needs to be replaced ;-)
-
Hey @hishutup I have something for you. You know the issue that Alive Waters Updated causes when you rebuild the Bashed patch, and you get a python warning with: mgef: RawMGEFCode(RSWD) mgef not found in bush.mgef_nameThat's caused by two ingredients, herring fillet and eel flesh, that each contain a reference to Resist Water Damage, which doesn't exist anymore. Removing that effect from each of the ingredients allows the rebuild to proceed without any trouble. I put the details in this post in their forum thread.
-
Not to burst your bubble, but the reason for such excessive stress testing is to gather confirming evidence about may be at fault. It would be quite a shame to go to the expense of a new hard drive only to find that you still have the same problem, because that wasn't what was causing the issue in the first place. Good luck.
-
Yes, I think that it would indeed. Ahh, that will be the free version limitation. I think that there are other burn-in tests that run properly longer. Most hard drive manufacturers provide stress-testing software for their devices from their website.
-
Did you know that burn-in tests are supposed to be run continuously for 24 hours? Another possible avenue is to stress-test your GPU. https://www.geeks3d.com/gputest/
-
Now that it's all but confirmed to be an issue outside of Oblivion, stress-testing with burn-in software will help to reveal where any hardware issue may be hiding.
-
No, it's best not to worry about that at this stage.
