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.)
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.
>Also, in /devices/status/.
>? Do you have a keyboard/ property?
>How about a keyboard[1]/?
»/devices/status/keyboard« exists, but
»/devices/status/keyboard[1]« doesn't.
>Does /devices/status/keyboard/event change numbers with every keypress?
While I hold any key (even the shift key), the color of the
entry »meta = 'false' (bool)« is changed from white to gray.
»/devices/status/keyboard/event« always shows:
.
..
key = '0' (int)
modifier/
pressed = 'false' (bool)
(Where »'« actually is a similar character from Windows-1252,
that has been replaced by »'« in this mail.)
This text never changes, whatever key I press.
I also observed some nasal error reports when starting the
program. Usually, they do not change, when I use other
options:
Model Author: Unknown
Creation Date: 2002-01-01
Version: $Id: c172p.xml,v 1.20 2008\09\01 15:14:33 torsten Exp $
Description: Cessna C-172
FGMultiplayMgr - No receiver port, Multiplayermode disabled
Nasal runtime error: non-scalar in string context
at C:\FlightGear\data\Nasal\aircraft.nas, line 347
called from: C:\FlightGear\data\Nasal\aircraft.nas, line 989
Nasal runtime error: bad\missing argument to split()
at C:\FlightGear\data\Nasal\string.nas, line 226
called from: C:\FlightGear\data\Nasal\string.nas, line 193
called from: C:\FlightGear\data\Nasal\io.nas, line 231
Nasal runtime error: No such member: catalog
at C:\FlightGear\data\Nasal\aircraft.nas, line 391
called from: C:\FlightGear\data\Nasal\gui.nas, line 343
called from: C:\FlightGear\data\Nasal\aircraft.nas, line 508
called from: C:\FlightGear\data\Aircraft\c172p\Nasal\liveries.nas, line 3
Nasal runtime error: No such member: catalog
at C:\FlightGear\data\Nasal\aircraft.nas, line 391
called from: C:\FlightGear\data\Aircraft\Instruments-3d\ki266\ki266.nas, line
38
called from: \nasal[0]\c172p[0], line 2
Nasal runtime error: non-scalar in string context
at C:\FlightGear\data\Nasal\globals.nas, line 155
Initializing Nasal Electrical System
Scaling image 'C:\FlightGear\data\Textures.high\Signs\black.png' from
(4096,128) to (2048,128)
Scaling image 'C:\FlightGear\data\Textures.high\Signs\red.png' from (4096,128)
to (2048,128)
Scaling image 'C:\FlightGear\data\Textures.high\Signs\framed.png' from
(4096,128) to (2048,128)
Scaling image 'C:\FlightGear\data\Textures.high\Signs\yellow.png' from
(4096,128) to (2048,128)
power up
One of them mentions »io.nas«. Line 231 of io.nas reads:
var home = string.normpath(getprop("/sim/fg-home"));
Line 155 of »globals.nas« is:
var path = getprop("/sim/fg-home") ~ "/Nasal";
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.)
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.
Stefan
------------------------------------------------------------------------------
_______________________________________________
Flightgear-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-users
