On Dec 29, 2007 3:34 PM, Syd&Sandy <> wrote:
> On Sat, 29 Dec 2007 15:24:06 -0600
> "Curtis Olson" <c <[EMAIL PROTECTED]>> wrote:
>
> > I've never had a problem with the --fov=xx option. Are you saying that
> is
> > now broke? Crap, you are right, at least in the OSG version. <sigh>
> time
> > to go waste my afternoon trying to track this down ... </sigh>
>
> Well i did find this in options.cxx ....
> {"fov", true, OPTION_FUNC, "", false, "",
> fgOptFov },
>
> the rest in the list are BOOLs followed by a property ....
> Doesn't make sense to me ... yet :)
Yes, and when you specify --fov=XX then this sets
/sim/current-view/field-of-view to XX
However, viewmgr.cxx happily overrides this based on other values which
apparently have been added to preferences.xml in the mean time. There is a
config section now for each view with a default fov listed there. So
basically this means the --fov option has been broken and you new need to
modify preferences.
Looking at this, I'm not saying the current behavior is bad, but we need a
way to set the default fov from the command line ...
--prop:/sim/view/config/default-field-of-view-deg=25 does work, and that
actually makes more sense than a --fov= option which doens't make clear
which view is getting set.
So maybe we just need to update --fov=XX option to modify the new property
name that is being used so the option will still do something sensible.
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
