[Trivial Psychic]

The debug builds of any builds this month, will want you to change "inital" to "initial" for the turret animation code, and also to remove the quotation marks from around it.  Release builds won't complain.  As for the other bug, I'm not sure.

[Petrarch of the VBB]

I've never had any trouble with the 3D radar, either. Other than it being vastly confusing.

[Cobra]

yeah, the 3D Radar was a little confusing at first.

[CaptJosh]

I gave up on it when I found that it was virtually useless for intermittent contacts. You can't really tell where those are with 3d radar.

[Cobra]

well, for me, once i see the flashing contacts, i just turned to the general area. that i saw it. from there it was easy.

[CaptJosh]

If there's only one set of flashing contacts, sure. Try when there's 4 groups. Like in the second mission in The Great War.

[Cobra]

i did the same thing with that, too.

[CaptJosh]

Sure you did...Want to make your nose grow longer?

[Cobra]

.....OK. It's easier for some of us and not so easy for others.

[CaptJosh]

*thinks someone is boasting idly to try to make himself look better*

[jr2]

I've had that problem with the 3d radar, too, and asked if someone could make an in-game switch for 2D / 3D radar.  (Mantis bug ID 0000768 , closed because submitting feature requests with Mantis is taboo!) (Even though there's a severity selection drop-down labeled "feature request".)  However, I've found that if you can make yourself calculate where the "average" of the faint radar contacts seem to be centered, memorize that spot, and turn towards it, which would mean relying on those circle things for reference, then you can sometimes find a target.  Oh, and while you're flying on instruments, don't hit any asteroids...now I know why your wingmen always run into you...!   

http://www.hard-light.net/forums/index.php/topic,37095.msg757569.html#msg757569
http://www.hard-light.net/forums/index.php/topic,36622.msg755854.html#msg755854

[Dark Hunter]

I use that technique... it's actually quite easy to read blips on 3-D radar once you get used to it.

[bfobar]

<-- has no trouble decyphering 3d radar fuzz either.

[Cobra]

OK, it looks like the 20060323 build fixed it.

[jr2]

... I didn't say it was exactly easy to follow 3d radar that's fuzzy... in fact, it can be rather hard...  It depends on how may blips, and the number of targets on your radar view.  If you've got tons any combination of the following: asteroids, friendly ships, hostile ships, or cargo containers, it can get hairy awful fast.  You usually end up following your wingmen.  (Which is a bad idea... wingmen usually act pretty stupid unless their actions are scripted or controlled by you.)

Oh, and while you're flying on instruments, don't hit any asteroids...now I know why your wingmen always run into you...!   

And I did put in a feature request to get a 2d/3d switch, because 2d is sooo easy: line up the target to the center of the screen and ta-da! 
PS Normal (non-fuzzy) 3d is easy to get the hang of:  Just try your yaw and pitch controls while you're escorting a convoy that you know where they are in relation to your radar screen... the circles surrounding the gauge are for your reference.

[Dark Hunter]

Never done that for me, although I'm convinced that it is making up errors. It keeps finding errors in either campaigns I download, which is dumb because any good campaign maker would make sure they are error-free before releasing them, or in flawless custom-built tables. It's driving me a bit insane......

[Trivial Psychic]

The thing is, they may have been made to retail specs, and FSO specs are much stricter.  Just try to run Inferno R1 without the SCP patch.  Even the official patch is out of date.  Shadow0000 managed to upgrade R1 significantly, but existing campaigns need almost constant maintenance if they want to be playable under newer FSO builds.  Keep that in mind when you're playing on of those campaigns.

[Shadow0000]

Yes, is true, if you try to play S:AH with INF + the SCP Patch it will just crash. Most Campaings have no singnificant or massive errors, however that's apply to FS2 Retail or the SCP version which was used to build them, you have to consider that.

[karajorma]

They shouldn't need constant maintenance. They should just need to be brought up to spec once and then work thanks to backwards compatibility.

The stricter FSO specs are due to the fact that those errors did cause crashes from time to time.

[Cobra]

****... looks like i found what's causing all the lockups:

Error: Malloc Failed!

File:\fs2_open\code\globalincs\windebug.cpp
Line: 1680
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------