Runtime Error

[mcshame]

Been playing alot and the build has been performing really well.  However, just ran into a problem.

 

When leaving the museum, I'm heading to the Monument and as I approach the location in the picture, I get a Visual C++ Runtime error.

 

Anyone see this before and any way to fix or workaround it?

 

 

[GrantSP]

Have you doctored the screenshot at all to remove details about the calling programme, or is this just another example of how "helpful" Windows error messages are?

 

Without knowing what programme is making that error message it is going to be very hard to determine how to fix it.

I'm assuming FO3 is fine as it would most likey crash if it suffered a C++ error.

Are you running an ENB and is that still active after the message?

Any tools on your system running in the background? GPU enhancers or overlays, game boosters, messaging apps or anything really, probably those apps that may need to make refresh calls to the screen, since you mention a transition from inside to outside happened. (That may be just coincidental though.)

[mcshame]

No doctoring, it occurred while outside, always occurs when I approach the same location. Closed all applications. I went back to an earlier save and tried again and the problem didn't reoccur. There were two super mutants there, now I have a new problem...

Edited April 17, 2016 by mcshame

[GrantSP]

That's good, Windows errors are hard to track, Super-mutants are easy!

[mcshame]

That's good, Windows errors are hard to track, Super-mutants are easy!

I just spent hours trying to clear the museum, man it was hard on this build! Then I had to resort to fast travel to go home to lick my wounds.  I have very limited ammo and had to try to get to the Monument and there are 2 Behemoths and Super Mutants everywhere.  This is gonna hurt! 

 

My pathetic playthrough is here...it isn't pretty! lol

 

https://www.youtube.com/playlist?list=PLGMfhccIQVO-A_3CQuzXfmkazGNgXqLgW

Edited April 17, 2016 by mcshame

[mcshame]

I again was having problems all night with stability at that spot and couldn't get to the memorial. Tried again this morning, and it was working, just had to fire a mini nuke at them (without being to close) and running like hell to the Paladins. Mission accomplished. Onwards! I can see what people say about Fallout 3 being unstable. But, it is really fun and worth working thru. Does New Vegas suffer the same way or is it "more" stable?

Edited April 17, 2016 by mcshame

[Kelmych]

I've never seen the Visual C++ error in FO3. I've always tried to keep up on adding the most recent versions; I'm still running Windows 8.1. for a little while before I move to WIn 10. I'm not sure if any of the runtime extenders or perhaps utilities need the Visual C++ runtime tools.

 

My approach to the FO3 museum area, as it was for several of the more challenging areas, is to sneak until I could target a SuperMutant with a long range sniper weapon and take a shot or perhaps two and then run away for a short time. Then repeat. After the first shot if I remain for any period of time they run toward me and ... I aimed using the cursor in first person and these weapons almost always have scopes; I generally find VATS to be fairly ineffective for long range shots. VATS shows fairly low probabilities on shots that I can often hit using the scope without VATS.

 

I think FNV is a bit more stable. I don't remember as many challenging outdoor battles as FO3 has.