cj chitwood wrote:Alright... So...
I downloaded from CVS SimGear 1.9.0 and FlightGear Source 1.9.0 and Data 1.9.0. Took a long time, to say the least. I didn't realize when I started Data that I was downloading every available airplane. But no bother, saves me the trouble later on.
I start it up, and there's the box. Ah, but wait, we now can browse the properties.
File, Browse Internal Properties (or hit "/").
Go to sim/rendering/camera-group
Select "near-field" and make it "0" (zero). Hit set, close property browser, black box is gone.
Problem is, if you reset the scenario, you have to do this all over again. I think I recall being able to set properties in the .fgfsrc file, and if so, no prob. Otherwise, this would get annoying for e.g. chopper practice.
[edit]
So, found an easier way.
Whatever options you want in your .fgfsrc file, go for it. Then, add to the end of the file, the following line:
--config=/path/to/your/config.xml
(changing it, of course, to suit the actual path)
Then, create the xml file mentioned above and insert the following:
- Code: Select all
<PropertyList>
<sim>
<rendering>
<camera-group>
<near-field>
0
</near-field>
</camera-group>
</rendering>
</sim>
</PropertyList>
in my case, all of my FlightGear data is in
/usr/local/share/FlightGear/data
and I have system.fgfsrc there (which is no different from having it in .fgfsrc except that it's systemwide now no matter what user runs it). So, the last line of my system.fgfsrc file is:
--config=/usr/local/share/FlightGear/data/noblackbox.xml
Works for me. However, I do notice what I think may be a tradeoff: My Cessna's cockpit isn't completely rendered when e.g. I look up and to the left (into the wing root). Oh well. No more often than I look there, I can live with it to get rid of the black box.
[edit 3!]
alternatively, as a line in ~/.fgfsrc or $FG_ROOT/system.fgfsrc, add
--prop:/sim/rendering/camera-group/near-field=0
Much easier. It's funny, I found that and I wasn't even looking for it. There was a blurb about --prop in the multiplayer part of the manual.
[/edit 3!]
To the developers: Should I have changed a different property instead? Maybe used some value a little larger than zero? I'll play with it, but I'll check back here, too...
[/edit]
Question for the developers: What is the purpose of having "two cameras" as I've read it called? Why have one near and one far renderer? I'm curious, not complaining...
thanks,
CJ
[edit 2]
Oh, and check out this screenshot: http://gallery.dennettesdesigns.com/mai ... temId=1708
Turns out, my clouds are still broken, as I expected, but what I didn't expect was the prop arc to blank them out entirely. I'll just keep clouds3d disabled for now... They're nice, but I don't need them (considering Microsoft FS98 was the best I'd used up until now).
[/edit 2]
this is a very helpful solution
From a programming perspective can this method be applied to FG 1.9 to correct the black box