On Sat, 2009-04-04 at 17:58 +0200, Stefan Ram wrote:
> On Fri, Apr 03, 2009 at 01:41:40PM -0600, Ron Jensen wrote:
> >The mouse changes mode via the right mouse button. There are 3 modes,
> >normal, flight controls and view. It sounds like you are in the flight
> >control mode. Try hitting the right mouse button twice to cycle back to
> >normal mode... The cursor should change, but I believe some Windows
> >builds have a problem with that.
>
> Thanks for your answer, Ron!
>
> In the meantime, I have subscribed to the mailing list so that
> I can reply. (However, I quote your answer from the web
> archive, because it is not readable in my e-mail program,
> which does not seem to be abled to decode it correctly. My
> e-mail program has decoded your e-mail into a sequence
> consisting mainly of non-printing characters.)
For some reason my client decided to send the message base64 encoded.
Sorry.
> Thanks for the explanation of the mouse! I might have skipped
> this when reading the manual, because I expected to use the
> keyboard only. Another thing I had to find out was that in
> order to increase the throttle I had to hold down the /middle/
> mouse button.
>
> >I"m not really sure what's going on with your keyboard. One thought I
> >had... Using the »File/Browse Internal Properties« dialog
> >check /input/.
> >Do you have a keyboard/ property?
> >How about a keyboard[1]/?
>
> »/input/keyboard« exists, but »/input/keyboard[1]« doesn't.
Scratch that idea, then :)
> I also observed some nasal error reports when starting the
> program. Usually, they do not change, when I use other
> options:
> Possibly, something might be wrong with the value of
> »getprop("/sim/fg-home")« in Nascal scripts.
>
> I added this to my startup batch file:
>
> SET FG_HOME="C:\FlightGear"
>
> in front of the invokation FlightGear, but the behavior has
> not changed. An example batch file looks like this:
>
> SET FG_HOME="C:\FlightGear"
> SET FG_ROOT="C:\FlightGear\data"
> SET FG_SCENERY="C:\FlightGear\data\scenery"
> C:\FlightGear\bin\Win32\fgfs.exe
> --fg-root="C:\FlightGear\data"
> --fg-scenery="C:\FlightGear\data\Scenery"
> --aircraft=c172p
> --airport=EDDI
> --enable-auto-coordination
> --geometry=1024x768
> --enable-hud
>
> (The last line was wrapped in this e-mail.)
> (A parameter fg-home is not accepted by the program.)
any property can be set on the command line with --prop: e.g.
--prop:"/sim/fg-home"="C:/temp"
Also, fgfs uses %APPDATA% to create a value for /sim/fg-home if it isn't
supplied.
While we are on the subject, what is the value of /sim/fg-home for you?
> I tend to believe that these error messages are not related to
> the keyboard problem, which seems to be a low-level (osg-related?)
> problem, while nas scripts seem to be more high-level scripts.
Mr. Franz agrees with you here, I believe.
Thanks,
Ron
------------------------------------------------------------------------------
_______________________________________________
Flightgear-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-users
