» Tue Nov 10, 2009 11:16 am
Hello!
Stumbled on two issues that also might be related to BC. First one, not sure if it has been already reported, is a colision issue on Bravil Docks. If I walk through the steps right in front of me in this http://i279.photobucket.com/albums/kk145/koki373737/bravildocks.jpg, I fall through them.. Im using BC Full 4.3.5, UL Bravil Borrowifields 1.32 and BCBravil Borrowfields patch FULL 2.7. I guess thats the reason why several NPCs are taking a bath around there : )
The other issue is a bit more hairy. Its not game breaking but since its persistent, I think its ok to report. I noticed that after traveling to Bravil for the first time, I started to get a honk from weOCPs when quiting to main menu, Then I found out that if I save, go to the main menu, ignore the honk, and load the same game again, then on the next time I quit to main menu it CTDs for real, even with weOCPS. And then, with that savegame, the problem seems to persist, even if I quit the game completelly. Similar behavior if I remove weOCPs.. the first quit to main menu seems to work. But if I save, quit to main menu, load and save, then every quit to main menu from then on, with that savegame, starts to CTD.
After a bit of test, I tracked the problem to specific cells... so if I enter Bravil, no problem.. cell (16,-11), (15,-11), no problem (quiting to main menu working fine, no honks). But when I enter 15,-9, the problem starts. And after visiting that cell, if I, for example, fast travel from there to City Isle, save, quit the game completelly, run it again, load the savegame and quit to main menu, the issue repeats itself.. first time weOCPS honks, next time CTDs. Using Arthmoor?s guide on tracking glitched spaws, and after some tests, I found out that if I disable BC - Full City Defences the problem vanishes. Checking TES4EDIT, it seems BC-FCD doesnt touch this specific cell, so perhaps the issue is on a surrouding cell thats being loaded on memory. (if my tests make any sense at all, that is)
Sorry if the explanation is a bit confuse... if its a real issue, it seems to be very specific. I guess I wouldnt even bother to try to report if it wasnt a persistent issue. Thanks!