Need to know. F3???

I've never had the F3 bug happen to me which doesn't mean it solved for good but I haven't heard of the f3 bug for a while so it might be gone for good.
 
*crosses fingers* So do I ...:)
 
If you're talking about the bug that the F3 key sometimes crashes the game if you're using Windows XP operating system (listed in Bamspeedy's thread of known bugs), I still have this problem even with the 1.22 patch. It's annoying, and I haven't been able to figure out any pattern of when it happens. I try to remember to save the game before I use the F3 key.
 
It happened just recently to me. However, i had a few things running in the background and hadn't restarted the system for quite some time. I almost always save the game before hitting F3 just out of habit now anyway.
 
The F3 (the button that calls up the military advisor) bug still also applies to v 1.22 if you've left the military advisor as the last one looked at and latter use the mouse to click on the advisors icon.

It's a CNR bug that happens only occasionally. It seems to be related to the minimap that gets called up with the advisor. You can of course recover the game with the autosave file. I just don't use F3 and always click another advisor before closing the advisor list. <So far that has prevented the crash>
 
I've had the F3 problem once or twice, but I never nailed down what I did to trigger it. In fact, reloading that turn and going to F3 didn't cause it to crash.
 
Originally posted by SewerStarFish
The F3 (the button that calls up the military advisor) bug still also applies to v 1.22 if you've left the military advisor as the last one looked at and latter use the mouse to click on the advisors icon.

It's a CNR bug that happens only occasionally. It seems to be related to the minimap that gets called up with the advisor. You can of course recover the game with the autosave file. I just don't use F3 and always click another advisor before closing the advisor list. <So far that has prevented the crash>

Now this is some very useful info. Thanks! :goodjob:
 
I haven't seen the F3 bug after the official version of Civ3 Conquests was released...
 
Originally posted by watorrey
What's a CNR bug?

Can Not Reproduce

( I think )
 
Haven't see this bug in awhile since the 1.22 upgrade.

I have almost learned to save every time before calling up the F3 screen, but then
I use the F3 screen less now than I used to.

PF
 
I had never seen the F3 bug until I changed from Me to XP.

It has occurred for me 3 times in probably 200+ hours of Conquest v1.22 play. I've used F3 and have left the Military advisor as the last advisor seen numerous times without problem.

Everytime it has crashed, I tried to reproduce it [ 'cause I just love posting on the bug board and being told "Sorry but that isn't a bug" ] by loading the last autosave and repeating the steps. Each time the crash did not repeat {CNR}. I just figured it was a relatively well known bug that was yet to be fixed because it doesn't effect game mechanics and is recoverable.
 
CORRECTION, bug still exists.

Method to reproduce:
1. must be in one of two last eras
2. must have lots of units
3. must have F3 screen in Unit view [not city]
4. must be in war situation.

Those are the basics, it only happens about 10% of the time, in oder to trigger it:
5. capture city[ies]
6. hit F3.

Seems to happen most often after captured 2-4 cities and can either be after those captures or at the end of the turn. Wait at end of turn is turned on.

Also had it happen with F4 key. Oh, and your covernment is either republic or commie.

PF
 
hm, those are lots of steps necessary to reproduce that bug, which makes me think that it isn't that bad as some people say...
 
I've never had a F3 crash, although I don't spend much time playing civ either and only play one mod. Out of paranoa, I only use the F3 key when I'm done playing and got it saved already so if it crashes it only helps me exit the game faster so I'm hoping for the crash instead of fearing it (positive use of a crash situation). Unfortunately I never get the crash.
 
Back
Top Bottom