The latest UF3P does not have this fix, or I would not be here. I am installing this fix and going back to a save where I am on the Observation deck and have the objectives to disable the death ray and reach the bridge. I hope it works.
EDIT: This fix worked for me! I completed the rest of the Zeta quests without a problem. Endorsed!
I'm glad you do it. Enjoy your game This strange location for DLC-s have something with achievements and Live in common. But FOSE (which required for more and more mods) require DLC-s to be placed in the DATA folder.
@ alexp1 Sorry for your troubles. I have no idea what can cause it, the whole fix is some small edits in one script only. Do you have Zeta DLC installed in DATA folder or in My Documents? If last- it can create problems with many mods.
Edit: also, if this is the wrong place to post this, I apologise - I couldn't see anywhere else any more obvious to put it though --------------------------- Well- this thread was created for such things, so nothing to worry ">
Actually I was just coming back here to say I'd solved the problem - I installed the Fallout Mod Manager to see if perhaps the file had somehow been corrupted, hoping that it might fix it - it didn't. The first time I ran FMM, it suggested moving the DLC files to the game data directory, but said there might be some side effects with regard to savegames, so I didn't do it. I then still got CTD, so next time I ran it, I ok'd the moving of the DLC files, and ran it, and hey presto, not only does the game not crash, but I don't end up with the glitch either!
So yes, probably my fault for not reading around the subject enough (and possibly Bethesda's fault for downloading the files to an odd place - to be honest I had no idea where they were, or that moving them would have any effect).
Thank you anyway - you would have solved my problem if I hadn't stumbled upon the solution myself ">
@ alexp1 Sorry for your troubles. I have no idea what can cause it, the whole fix is some small edits in one script only. Do you have Zeta DLC installed in DATA folder or in My Documents? If last- it can create problems with many mods.
Edit: also, if this is the wrong place to post this, I apologise - I couldn't see anywhere else any more obvious to put it though --------------------------- Well- this thread was created for such things, so nothing to worry
On my machine, the fix for This Galaxy Ain't Big Enough causes Fallout to crash to desktop before the main menu has even been reached - if I select the one for Agatha's Song only, the main menu loads fine... however I've got the Mothership Zeta bug.
If it helps, I'm running Win7 x64 Ultimate, Fallout is patched to v1.7 and installed in D:\Games\Fallout 3, and I don't have any mods installed at all, bar the two files included in this download.
Again, I don't know if this will help (it might) - I have Visual Studio installed, and it gives me the option to debug when stuff crashes - here's the error message it gives:
Unhandled exception at 0x004e869c in Fallout3.exe: 0xC0000005: Access violation reading location 0x00000034.
It also shows the (dis)assembly code instruction at which it crashes:
004E869C movecx,dword ptr [edi+34h]
Visual Studio says that at this point in the code, the value of edi is zero, which presumably it shouldn't be - I assume it's meant to point somewhere valid in memory which has/will have something useful 0x34 bytes away from it...
If it's any help I can post some more assembly from around it, although I'm not really holding out any hope that anyone will be able to help ">
Edit: also, if this is the wrong place to post this, I apologise - I couldn't see anywhere else any more obvious to put it though ">
10 comments
EDIT: This fix worked for me! I completed the rest of the Zeta quests without a problem. Endorsed!
This strange location for DLC-s have something with achievements and Live in common. But FOSE (which required for more and more mods) require DLC-s to be placed in the DATA folder.
Actually I was just coming back here to say I'd solved the problem - I installed the Fallout Mod Manager to see if perhaps the file had somehow been corrupted, hoping that it might fix it - it didn't. The first time I ran FMM, it suggested moving the DLC files to the game data directory, but said there might be some side effects with regard to savegames, so I didn't do it. I then still got CTD, so next time I ran it, I ok'd the moving of the DLC files, and ran it, and hey presto, not only does the game not crash, but I don't end up with the glitch either!
So yes, probably my fault for not reading around the subject enough (and possibly Bethesda's fault for downloading the files to an odd place - to be honest I had no idea where they were, or that moving them would have any effect).
Thank you anyway - you would have solved my problem if I hadn't stumbled upon the solution myself
Sorry for your troubles.
I have no idea what can cause it, the whole fix is some small edits in one script only. Do you have Zeta DLC installed in DATA folder or in My Documents? If last- it can create problems with many mods.
Edit: also, if this is the wrong place to post this, I apologise - I couldn't see anywhere else any more obvious to put it though
---------------------------
Well- this thread was created for such things, so nothing to worry
If it helps, I'm running Win7 x64 Ultimate, Fallout is patched to v1.7 and installed in D:\Games\Fallout 3, and I don't have any mods installed at all, bar the two files included in this download.
Again, I don't know if this will help (it might) - I have Visual Studio installed, and it gives me the option to debug when stuff crashes - here's the error message it gives:
Unhandled exception at 0x004e869c in Fallout3.exe: 0xC0000005: Access violation reading location 0x00000034.It also shows the (dis)assembly code instruction at which it crashes:
004E869C movecx,dword ptr [edi+34h]Visual Studio says that at this point in the code, the value of edi is zero, which presumably it shouldn't be - I assume it's meant to point somewhere valid in memory which has/will have something useful 0x34 bytes away from it...
If it's any help I can post some more assembly from around it, although I'm not really holding out any hope that anyone will be able to help
Edit: also, if this is the wrong place to post this, I apologise - I couldn't see anywhere else any more obvious to put it though
The Zeta bug in particular has been plaguing me for a while and this does indeed seem to fix it. Cheers!