Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Norman Vine wrote: Jim Wilson writes: Also F8 (Cycle fog type) and F9 (toggle textures) no longer work. Should thes bindings be removed? F8 seems to work on my machines Sigh It looks like F9 needs to get fixed again. This is a *very* useful essential debugging feature for anyone interested in seeing what is 'really' happening during rendering It is also a good indicator as to whether or not 'GL state' is being kept track of properly This functionality has been removed about three months ago. It is no longer possible to use the scenery without textures. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Atlas and recent rework of Airports
Dave Perry wrote: The recent changes from default.apt.gz to basic.dat.gz and runways.dat.gz breaks the use of Atlas. Even the CVS Atlas is still looking for default.apt.gz. Will we try to update Atlas before the FG9.3 release? I don't think we should delay the release because of Atlas since it isn't directly related to FlightGear. We haven't seen the developer of Atlas on the FlightGear mailing lists for more than a year now. That said, it would be nice to update Atlas to support the new layout. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson [EMAIL PROTECTED] wrote: If someone has the TeX utils (and tex4ht) setup on their system, the FGShortRef.* could use an update. Attached below is a list of changes that need to be made. I'm listening - thanks for your input, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] next release ...
Erik Hofman [EMAIL PROTECTED] wrote: Martin Spott wrote: Shift-b _schould_ toggle the parking brake and it does so on _most_ aircrafts - some by LeeE have additional very nice gimmicks. Someone posted Ctrl-b for the speed brake but none of the aircraft that I tried has a working one. The F-16 and Fokker 100 have a working speedbrake. Oh yes, they look _really_ nice on the F-100 ! Unfortunately I didn't manage to get this one airborne because the engines don't work any more after the recent JSBSim turbine update. See other thread Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] new FGSimTurbine
Martin Spott [EMAIL PROTECTED] wrote: Unfortunately I didn't manage to get this one airborne because the engines don't work any more after the recent JSBSim turbine update. Oh, I have to start counting with [1] instead of [0]. Wouldn't it be nice if we could set [1,2] instead of being required to add two lines to the ~/.fgfsrc ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: keyboard mappings and Short Ref doc
Misc keyboard controls CTRL + B Speedbrake. Still does not work on the YF-23. While testing I found an interesting effect. Usually I'm running FG with: --start-date-lat=2002:04:11:11:11:11 When I did a reset via menu I was suddenly sitting in the dark (on KHAF). Can anyone reproduce ? I have the impression that the reset has its own initialization routines and does not use the same set of routines that are being run on startup: The startup iitialization routines have been fixed recently - there seems to be some duplication for the reset function, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Wireeframe and Flat Shaded Display
Frederic BOUVIER wrote: I noticed that recently the ambient color disappeared from materials.xml. Unfortunately, fgsd was relying on this property to draw the scenery. I had to develop a routine that loads the texture and compute the average color on the fly. That's another issue. You should set the defaults as defined in the header of the file if no color/ambient/diffuse/specular or shininess is defined. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] key bindings - English
Here's a key map for English keyboards, showing what keys are used/unused.
It's incomplete because I haven't figured out all the codes yet, and no, I
haven't seen anything helpfull in glut.h. It would be nice to have this for
other keyboards as well, and placed in the Docs directory.
codekeysbinding
_
000
001 [Ctrl][A] Autopilot - toggle altitude lock
002 [Ctrl][B] Speedbrake - toggle speedbrake 0.0-1.0
003 [Ctrl][C] Panel - toggle clickable hotspots
004 [Ctrl][D]
005 [Ctrl][E]
006 [Ctrl][F]
007 [Ctrl][G] Autopilot - toggle glide slope lock
008 [Ctrl][H] Autopilot - toggle heading lock
009
010
011
012
013 [Enter] Autopilot - increase heading; rudder right
014 [Ctrl][N] Autopilot - toggle nav1 lock
015
016
017
018 [Ctrl][R] CCW - toggle winding
019 [Ctrl][S] Autothrottle - toggle lock
020 [Ctrl][T] Autopilot - toggle terrain lock
021 [Ctrl][U] Autopilot - add 1000ft altitude
022 [Ctrl][V] View - select view[0]
023 [Ctrl][W] Autopilot - toggle wing leveler
024
025
026
027 [Esc] Prompt and Quit FlightGear
028
029
030
031
032 [SPACE] Engine - fire starter on selected engine
033 ! [Shift][1] Engine - select engine[0]
034[Shift][']
035 # [Shift][3] Engine - select engine[2]
036 $ [Shift][4] Engine - select engine[3]
037 % [Shift][5]
038[Shift][7]
039 ' ['] ATC - display dialog
040 ( [Shift][9]
041 ) [Shift][0]
042 * [Shift][8]
043 + [Shift][=] Zoom - in
044 , [,] Brake - left
045 - [-] Zoom - out
046 . [.] Brake - right
047 / [/]
048 0 [0] Autopilot - increase heading; rudder left
049 1 [1] Elevator trim - decrease
050 2 [2] Autopilot - increase altitude; elevator increase
051 3 [3] Autothrottle - decrease; throttle decrease
052 4 [4] Aileron - left
053 5 [5] Controls - center
054 6 [6] Aileron - right
055 7 [7] Elevator trim - increase
056 8 [8] Autopilot - decrease altitude; elevator decrease
057 9 [9] Autothrottle - increase; throttle increase
058 : [Shift][;]
059 ; [;]
060[Shift][,]
061 = [=] Zoom - set default
062[Shift][.]
063 ? [Shift][/]
064 @ [Shift][2] Engine - select engine[1]
065 A [Shift][A] Speed-up - decrease
066 B [Shift][B] Parking brake - toggle
067 C [Shift][C] Scripting - test
068 D [Shift][D]
069 E [Shift][E]
070 F [Shift][F]
071 G [Shift][G] Gear - down
072 H [Shift][H]
073 I [Shift][I]
074 J [Shift][J]
075 K [Shift][K]
076 L [Shift][L]
077 M [Shift][M] Warp - decrease
078 N [Shift][N]
079 O [Shift][O]
080 P [Shift][P] Panel - toggle
081 Q [Shift][Q]
082 R [Shift][R]
083 S [Shift][S]
084 T [Shift][T] Warp - decrease delta
085 U [Shift][U]
086 V [Shift][V] View - scroll in reverse
087 W [Shift][W] 3DFX - toggle full screen
088 X [Shift][X] View - increase field of view
089 Y [Shift][Y]
090 Z [Shift][Z] Visibility - decrease
091 [ [[] Flaps - decrease
092 \ [\]
093 ] []] Flaps - increase
094 ^ [Shift][6]
095 _ [Shift][-]
096 ` [`]
097 a [A] Speed-up - increase
098 b [B] Brakes - all
099 c [C] Cockpit - toggle 2D/3D
100 d [D]
101 e [E]
102 f [F]
103 g [G] Gear - up
104 h [H]
105 i [I]
106 j [J] Spoilers - decrease
107 k [K] Spoilers - increase
108 l [L] Tailwheel - toggle lock
109 m [M] Warp - increase
110 n [N]
111 o [O]
112 p [P] Pause
113 q [Q]
114 r [R] Replay
115 s [S] Panel - swap
116 t [T] Warp - increase delta
117 u [U]
118 v [V] View - scroll forward
119 w [W]
120 x [X] View - decrease field of view
121 y [Y]
122 z [Z] Visibility - increase
123 { [Shift][[] Engine - decrease magneto on selected engine
124 | [Shift][\]
125 } [Shift][]] Engine - increase magneto on selected engine
126 ~ [Shift][`] Engine - select all engines
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
147
149
150
151
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257 [F1] Load flight
258 [F2] Tile cache - force reload
259 [F3] Screen capture
260 [F4] Lighting - force update
261
[Flightgear-devel] Some Win-bugs and questions
Hi, I´ve downloaded the newest official windows FlightGear binary with data. 1.I startet runfgfs.bat, but I couldn´t see the KSFO airport! 2-3 Months later I tried to start fgfs.exe in the Bin/Win32 directory, it worked fine and I could see the aiport building! 2. When FlightGear runs I can hear all the time the marker-beacons! 3. Is there any option to disable anti-aliasing in FlightGear, because the ground textures look much better without anti-aliasing? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Wireeframe and Flat Shaded Display
Frederic BOUVIER wrote: Erik Hofman wrote: Frederic BOUVIER wrote: I noticed that recently the ambient color disappeared from materials.xml. Unfortunately, fgsd was relying on this property to draw the scenery. I had to develop a routine that loads the texture and compute the average color on the fly. That's another issue. You should set the defaults as defined in the header of the file if no color/ambient/diffuse/specular or shininess is defined. Yes and No. If you want to show your scenery in FG untextured, you'll need some color information. (fgsd always show the scenery untextured ) Ah, that *is* the same issue, but then you meant the r,g and b color (and not ambient) tag. Using the same default color for all kind of material (except the few that have a special setting ) will give you a rather boring landscape. True. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] key bindings - English
David Culp wrote: Here's a key map for English keyboards, showing what keys are used/unused. It's incomplete because I haven't figured out all the codes yet, and no, I haven't seen anything helpfull in glut.h. It would be nice to have this for other keyboards as well, and placed in the Docs directory. On UNIX key's are defined in: /usr/include/X11/keysymdef.h Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Wireeframe and Flat Shaded Display
Erik Hofman wrote: Frederic BOUVIER wrote: I noticed that recently the ambient color disappeared from materials.xml. Unfortunately, fgsd was relying on this property to draw the scenery. I had to develop a routine that loads the texture and compute the average color on the fly. That's another issue. You should set the defaults as defined in the header of the file if no color/ambient/diffuse/specular or shininess is defined. Yes and No. If you want to show your scenery in FG untextured, you'll need some color information. (fgsd always show the scenery untextured ) Using the same default color for all kind of material (except the few that have a special setting ) will give you a rather boring landscape. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Some Win-bugs and questions
[EMAIL PROTECTED] wrote: Hi, Hi, I´ve downloaded the newest official windows FlightGear binary with data. 1.I startet runfgfs.bat, but I couldn´t see the KSFO airport! 2-3 Months later I tried to start fgfs.exe in the Bin/Win32 directory, it worked fine and I could see the aiport building! There is an issue, corrected in CVS, where the buildings don't show up when specifying a relative path for FG_ROOT (the implicit behaviour of runfgfs.bat ) 2. When FlightGear runs I can hear all the time the marker-beacons! it is the morse ID of the selected marker (don't remember if it is a VOR or an NDB ). Tune your NAV frequency so that it don't receive the signal. 3. Is there any option to disable anti-aliasing in FlightGear, because the ground textures look much better without anti-aliasing? If there is an option, it is in your driver setup, in the display properties. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Some Win-bugs and questions
[EMAIL PROTECTED] writes: I´ve downloaded the newest official windows FlightGear binary with data. 1.I startet runfgfs.bat, but I couldn´t see the KSFO airport! 2-3 Months later I tried to start fgfs.exe in the Bin/Win32 directory, it worked fine and I could see the aiport building! 2. When FlightGear runs I can hear all the time the marker-beacons! 3. Is there any option to disable anti-aliasing in FlightGear, because the ground textures look much better without anti-aliasing? You would probably be *much* happier turning up your anisotropic texture filtering to it's maximum level. This makes runway textures much clearer when you view them at a sharp angle (like during take off, landing, and taxiing.) For linux/nvidia this is an environment variable setting. For windows this is probably a setting in your driver properties (just guessing.) It makes a huge difference if you have a GeForce 3 or better, it's an improvement, but less of one with a GeForce 2 or less. I don't have any current experience with other chipsets so someone else will have to speak for that. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [OT] PalmOS/GPS Moving Map?
I just bought a (relatively) cheap clip-on GPS for my Palm Vx. It came with Magellan mapping software containing a database of detailed U.S. city street maps, but nothing for outside city areas (!!). Does anyone know of a simple PalmOS low-res moving map program, that just shows coastlines, lakes, rivers, towns and cities (as points), and possibly a couple of major highways? Even lower-res than vmap0 would be fine. Thanks, and all the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] gear door sequencing
Has anyone made an exterior model with proper gear door sequencing yet (i.e. 1. gear handle up 2. gear door opens 3. gear comes up 4. gear door closes)? Is there a way to do this in the animation config? If not, we'll need a gear door sequencing subsystem. Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear door sequencing
David Culp [EMAIL PROTECTED] said: Has anyone made an exterior model with proper gear door sequencing yet (i.e. 1. gear handle up 2. gear door opens 3. gear comes up 4. gear door closes)? Is there a way to do this in the animation config? The answer is yes. Take a look at the c310u3a model to see an example of gear door operation. Also you could look at the 747 to get a similar idea. The 747 model doesn't have gear doors (i'm working on that), but it does rotate the gear up before stowing it. Both examples should give some hints on how to use the min, max, and factor to have animations occur while the gear property value gradually moves from 0.0 to 1.0 and vice versa. We probably don't need a gear animation subsystem, but it might be helpful to have a generic timer subsystem that could be used for things like this. A similar case would be the 747-400 glass cockpit display that shows the text GEAR UP for just 10 seconds after the gear up sequence is complete. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT] PalmOS/GPS Moving Map?
On Wed, Sep 24, 2003 at 10:53:34AM -0400, David Megginson wrote: I just bought a (relatively) cheap clip-on GPS for my Palm Vx. Does anyone know of a simple PalmOS low-res moving map program, I use the cumulus program http://cumulus.kflog.org/ on my Zaurus. It is from Germany, and is build for the soaring community. You enter your sailplane type, and it calculates the gliding distance to the next waypoint. I had to modify the input to accept ethernet, and with that patch it works fine with NMEA position reports from fgfs. Wendell ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear door sequencing
David Culp wrote: Has anyone made an exterior model with proper gear door sequencing yet (i.e. 1. gear handle up 2. gear door opens 3. gear comes up 4. gear door closes)? Is there a way to do this in the animation config? If not, we'll need a gear door sequencing subsystem. I did that with the A320. I used interpolation tables like this : animation typerotate/type object-nameGearDoorRight.1/object-name object-nameGearDoorRight.3/object-name property/gear/gear[2]/position-norm/property interpolation entry ind0.0/ind dep0.0/dep /entry entry ind0.2/ind dep90.0/dep /entry entry ind0.8/ind dep90.0/dep /entry entry ind1.0/ind dep0.0/dep /entry /interpolation center x-m-0.719/x-m y-m0.099/y-m z-m-4.552/z-m /center axis x-1/x y0/y z0/z /axis /animation My sequence has only 3 states : 1. gear door opens, 2. gear comes up, 3. gear door closes. Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Speedbrake and Cont+B
There has been some posts lately about people not being able to get the speedbrakes to work with cont+B(me included).So tonight I took a look at the keyboard bindings XML and there was no Cont+B listed so I added the following between Cont+A and Cont+C and now the speedbrakes work fine for me key n=2 nameCtrl-B/name descToggle speedbrake/desc binding commandproperty-toggle/command property/controls/flight/speedbrake/property /binding /key This has probably been fixed in CVS as I am only using the 9.2 binary release.But all the keyboard XML files I have did not have the Cont+B binding. So if you are using a not so new copy of FG you might like to add the above and see how you go. Cheers Innis _ E-mail just got a whole lot better. New ninemsn Premium. Click here http://ninemsn.com.au/premium/landing.asp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Martin Spott [EMAIL PROTECTED] said: Jim Wilson [EMAIL PROTECTED] wrote: If someone has the TeX utils (and tex4ht) setup on their system, the FGShortRef.* could use an update. Attached below is a list of changes that need to be made. I'm listening - thanks for your input, Does this mean you've got tex4ht and can do this? Thanks! BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Some keys we just can't do that with but maybe something like ~ could be further identified as the upper left on the main keyboard. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear door sequencing
Wow Fred! It's been a while since I tried the A320. That's a fantastic model, and the gear door sequencing looks great. Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson wrote: BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Some keys we just can't do that with but maybe something like ~ could be further identified as the upper left on the main keyboard. Well, on french keyboards, we have to hold SHIFT to get the digits, so SHIFT+1 is already 1. The companion of '1' is '' and can be obtained without holding SHIFT. Combinaisons of characters are not the same from keyboards to keyboards so you can't assume that '!' is SHIFT+1 everywhere. This to say that I have difficulties to start all engines with the keyboard, and I don't speak about flaps that is the third glyph that requires Alt-Gr too. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear door sequencing
David Culp wrote: Wow Fred! It's been a while since I tried the A320. That's a fantastic model, and the gear door sequencing looks great. Thanks, It is still missing the speedbrakes, slat and reverse. BTW, as a non native english speaker, I need some clarifications on terminology. Am I correct when I say : Slat are in front of the wing, Speedbrakes are on the top of the wing ( the extrados ? ) and can be used flying, Reverse are small doors on the engine nacelle that open once the plane is landed and try to stop before the end of the runway. Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT] PalmOS/GPS Moving Map?
Wendell Turner wrote: I use the cumulus program http://cumulus.kflog.org/ on my Zaurus. It is from Germany, and is build for the soaring community. You enter your sailplane type, and it calculates the gliding distance to the next waypoint. Hey, they even have two images showing Enschede (the first two images after New version), the city I live in! Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear door sequencing
Am I correct when I say : Slat are in front of the wing, Yes. Actually, if it slides forward then it is called a slat. If it rotates down from a hinge it is called a leading edge flap. Together they are sometimes called leading edge devices or LED. Speedbrakes are on the top of the wing ( the extrados ? ) and can be used flying. Yes. Sometimes they are called spoilers, and it isn't always clear. Sometimes, if they are on top of the wing, they are called both at the same time. Reverse are small doors on the engine nacelle that open once the plane is landed and try to stop before the end of the runway. Yes. The part of the engine cowling that moves backwards is often called a reverser sleeve. Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson [EMAIL PROTECTED] wrote: Martin Spott [EMAIL PROTECTED] said: Jim Wilson [EMAIL PROTECTED] wrote: If someone has the TeX utils (and tex4ht) setup on their system, the FGShortRef.* could use an update. Attached below is a list of changes that need to be made. I'm listening - thanks for your input, Does this mean you've got tex4ht and can do this? Thanks! Hmmm, currently I'm the only maintainer of this document. This means I really _should_ (TM) do that ;-) I'll do my best as time permits. BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Nope. I have to repeat myself here - people simply don't listen what I'm talking about! Users with a German keyboard _have_ to use these keys. We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q is the only 'correct' identification for the key you need to press here. I refuse to deal with different keyboard layouts in the manual - this has to be solved in the software. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Martin Spott [EMAIL PROTECTED] wrote: [...] We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q [...] ^ Errr I mean @, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] key bindings - English
David Culp [EMAIL PROTECTED] wrote: Here's a key map for English keyboards, [...] I assume that there are differences between British and American keyboards, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Martin Spott [EMAIL PROTECTED] said: Hmmm, currently I'm the only maintainer of this document. This means I really _should_ (TM) do that ;-) I'll do my best as time permits. We could just move that out of the way and do a plain text file with the correct info (I'm talking about the copy in the base package /Docs folder). BTW one thing came to mind. The doc probably should show a few different keys when possible to reduce confusion for non-english users. For example, !,@,#,$ could be listed as SHIFT+1, SHIFT+2, SHIFT+3, SHIFT+4, which will work with most keyboard layouts. Nope. I have to repeat myself here - people simply don't listen what I'm talking about! Users with a German keyboard _have_ to use these keys. We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q is the only 'correct' identification for the key you need to press here. I refuse to deal with different keyboard layouts in the manual - this has to be solved in the software. Ah ok. That's a problem for another release. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] SimGear hanging CVS update lock in new directory
cvs server: failed to create lock directory for `/var/cvs/SimGear-0.3/SimGear/simgear/structure' (/var/cvs/SimGear-0.3/SimGear/simgear/structure/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/var/cvs/SimGear-0.3/SimGear/simgear/structure' cvs [server aborted]: read lock failed - giving up Think something got left behind. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] autopilot autothrottle fix
This has been on my local copy for a while (well tested :-)) It fixes a problem with the auto throttle jumping around needlessly. Adjustments are calculated based on the last calculated autothrottle setting rather than reading the throttle setting from the property tree. Patch is contained here: http://www.spiderbark.com/fgfs/newauto.diff.gz Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: keyboard mappings and Short Ref doc
On Wednesday 24 September 2003 11:52, Martin Spott wrote: Misc keyboard controls CTRL + BSpeedbrake. Still does not work on the YF-23. While testing I found an interesting effect. Usually I'm running FG with: YASim doesn't support speedbrakes or have a speedbrake control so I've used the spoiler control to actuate the aileron/flaps speedbrake. This used to be 'j' 'k' - not sure what it is atm:) LeeE --start-date-lat=2002:04:11:11:11:11 When I did a reset via menu I was suddenly sitting in the dark (on KHAF). Can anyone reproduce ? I have the impression that the reset has its own initialization routines and does not use the same set of routines that are being run on startup: The startup iitialization routines have been fixed recently - there seems to be some duplication for the reset function, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] latest CVS compile error
Eric, With the latest CVS changes I getting a compile error: Making all in Main make[2]: Entering directory `/home/curt/projects/FlightGear-0.9/source/src/Main' source='globals.cxx' object='globals.o' libtool=no \ depfile='.deps/globals.Po' tmpdepfile='.deps/globals.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X11R6/include -DPKGLIBDIR=\/usr/local/lib/FlightGear\ -Wall -O2 -D_REENTRANT -c -o globals.o `test -f globals.cxx || echo './'`globals.cxx /usr/local/include/simgear/structure/callback.hxx: In member function `void SGFunctionCallbackFun::operator()() [with Fun = SGSubsystem*]': fg_io.hxx:60: instantiated from here /usr/local/include/simgear/structure/callback.hxx:76: error: call to non-function `SGFunctionCallbackSGSubsystem*::f_' make[2]: *** [globals.o] Error 1 Any ideas? Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] keyboard mappings and Short Ref doc
Jim Wilson [EMAIL PROTECTED] wrote: Martin Spott [EMAIL PROTECTED] said: Nope. I have to repeat myself here - people simply don't listen what I'm talking about! Users with a German keyboard _have_ to use these keys. We definitely can't use Shift-2 to select the second engine on a C310, we have to use @ (AltGr-q). This means Q is the only 'correct' identification for the key you need to press here. I refuse to deal with different keyboard layouts in the manual - this has to be solved in the software. Ah ok. That's a problem for another release. Oh, i'd vote for fixing this _before_ the next release because this problem is already known for quite some time, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: keyboard mappings and Short Ref doc
Lee Elliott [EMAIL PROTECTED] wrote: On Wednesday 24 September 2003 11:52, Martin Spott wrote: Misc keyboard controls CTRL + B Speedbrake. Still does not work on the YF-23. While testing I found an interesting effect. Usually I'm running FG with: YASim doesn't support speedbrakes or have a speedbrake control [...] Aaaah, so it would probably worth adding before the release ? Most of the aircraft that profit noticeably from a speed brake run with YASim, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] latest CVS compile error
Curtis L. Olson wrote: Eric, With the latest CVS changes I getting a compile error: Making all in Main make[2]: Entering directory `/home/curt/projects/FlightGear-0.9/source/src/Main' source='globals.cxx' object='globals.o' libtool=no \ depfile='.deps/globals.Po' tmpdepfile='.deps/globals.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X11R6/include -DPKGLIBDIR=\/usr/local/lib/FlightGear\ -Wall -O2 -D_REENTRANT -c -o globals.o `test -f globals.cxx || echo './'`globals.cxx /usr/local/include/simgear/structure/callback.hxx: In member function `void SGFunctionCallbackFun::operator()() [with Fun = SGSubsystem*]': fg_io.hxx:60: instantiated from here /usr/local/include/simgear/structure/callback.hxx:76: error: call to non-function `SGFunctionCallbackSGSubsystem*::f_' make[2]: *** [globals.o] Error 1 Any ideas? It looks like tge compiler is mizing up two function calls with different parameters because one is defined with the template. I'll see if I can fix this. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear door sequencing
--- Frederic BOUVIER [EMAIL PROTECTED] wrote: David Culp wrote: Wow Fred! It's been a while since I tried the A320. That's a fantastic model, and the gear door sequencing looks great. Thanks, It is still missing the speedbrakes, slat and reverse. BTW, as a non native english speaker, I need some clarifications on terminology. Am I correct when I say : Slat are in front of the wing, Yes. Speedbrakes are on the top of the wing ( the extrados ? ) and can be used flying, The panels on top of the wing are usually called spoilers but they can function as speedbrakes. Speedbrakes can, in general, be located anywhere on the aircraft. Though those mounted on the fuselage are usually on top (F-15) or somewhere aft of the wing (F-16). Reverse are small doors on the engine nacelle that open once the plane is landed and try to stop before the end of the runway. Yes. Thrust reversers force some or all of the airflow out of the engine in the forward direction and slow down the aircraft. Note that depending on the design, the actual mechanisms involved can be quite large. Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] latest CVS compile error
Erik Hofman wrote: Curtis L. Olson wrote: Erik, With the latest CVS changes I getting a compile error: Any ideas? It looks like the compiler is mixing up two function calls with different parameters because one is defined with the template. This should be fixed now. Unfortunately this required a change in globals.hxx and an almost complete rebuild of FlightGear. This was something I desperately tried to avoid but to no avail :-( Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] OT latex2html??
Hi, due to the size of the current flight school (pdf=5.6MB), I would like to change it to HTML. I tried to use latex2html, but was more or less disappointed by the result (same with pdf2html). Any suggestions for a 1:1 converter or a different format to PDF or HTML? TIA, Carsten ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OT latex2html??
Carsten due to the size of the current flight school (pdf=5.6MB), I would like to change it to HTML. I tried to use latex2html, but was more or less disappointed by the result (same with pdf2html). Any suggestions for a 1:1 converter or a different format to PDF or HTML? Don't Adobe's accessibility tools for PDF include an HTML converter (or renderer)? Mally --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.520 / Virus Database: 318 - Release Date: 18/09/03 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OT latex2html??
To answer my own question: Don't Adobe's accessibility tools for PDF include an HTML converter (or renderer)? http://www.adobe.com/products/acrobat/access_onlinetools.html This seems to be an online service only. I don't know if that's any use to you. Mally --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.520 / Virus Database: 318 - Release Date: 18/09/03 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OT latex2html??
On Wed, Sep 24, 2003 at 09:24:14PM +0200, Carsten Höfer wrote: due to the size of the current flight school (pdf=5.6MB), I would like to change it to HTML. I tried to use latex2html, but was more or less disappointed by the result (same with pdf2html). I had many problems with latex2html, too, but with a little configuration it can yield good results. An example is a documentation I had to write: http://ftp.intevation.de/great-er/sciparam/manual/sciparam-manual.html You can download the source for it in http://intevation.de/cgi-bin/viewcvs-greater.cgi/sciparam/doc/ Especially the file .latex2html-init has to be tweaked to give useful results. Thomas -- Email: [EMAIL PROTECTED] (at work: [EMAIL PROTECTED]) http://jtah.de/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] OT latex2html??
Carsten Höfer writes: Hi, due to the size of the current flight school (pdf=5.6MB), I would like to change it to HTML. I tried to use latex2html, but was more or less disappointed by the result (same with pdf2html). Any suggestions for a 1:1 converter or a different format to PDF or HTML? If you have the time and patience, do a one-time conversion from LaTeX to Docbook SGML or XML. Every Linux distro that I know of has tools to produce decent HTML, PDF, and even ASCII from Docbook (it's the standard format for Linux documentation). All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT] PalmOS/GPS Moving Map?
Wendell Turner writes: Does anyone know of a simple PalmOS low-res moving map program, I use the cumulus program http://cumulus.kflog.org/ on my Zaurus. It looks very interesting, but unfortunately, doesn't run under Palm OS. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] re: [Flightgear-cvslogs] CVS: source/src/Scenery tileentry.cxx, 1.28, 1.29 tileentry.hxx, 1.8, 1.9 tilemgr.cxx, 1.24, 1.25
Curtis L. Olson writes (in a CVS log entry): VASI/PAPI lights are generally always on. I remember reading somewhere that they are typically turned off in very low visibility when a precision approach is in use, unless explicitly requested by the pilot -- unfortunately, I cannot locate the source. Also, the red/white VASI coloring has never worked right. This is also a step towards fixing that problem. I will look forward to that. I land at night with VASIS/PAPI quite often in real life, and would like to be able to practice with FlightGear. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] [OT] PalmOS/GPS Moving Map?
Google( palm moving map) Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Wireeframe and Flat Shaded Display
Norman Vine wrote: Erik Hofman writes: This functionality has been removed about three months ago. It is no longer possible to use the scenery without textures. If there was some discussion as to dropping this basic support could someone pont me to it please. OK the last discussion I see about this is on Tue Jun 24 10:19:05 CDT 2003 http://baron.me.umn.edu/pipermail/flightgear-devel/2003-June/018316.html The wireframe mode got broke somewhere along the way, but I fixed it recently. I haven't tried lately to see if it's broke again, but last I checked it did work. It can be useful for debugging your models/terrain because it will show you the exact triangle layout ... I am still searching for where it was decided that this useful functionality was to be removed Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] MATLAB/Simulink
Good evening, Is there anyone on this list who has linked FlightGear or Microsoft FlightSim to Simulink block diagrams? Any advice or suggestions? Nickolas HeinMorgantown WV - Original Message - From: Norman Vine To: FlightGear developers discussions Sent: Wednesday, September 24, 2003 7:31 PM Subject: RE: [Flightgear-devel] Wireeframe and Flat Shaded Display Norman Vine wrote: Erik Hofman writes: This functionality has been removed about three months ago. It is no longer possible to use the scenery without textures. If there was some discussion as to dropping this basic support could someone pont me to it please.OK the last discussion I see about this is onTue Jun 24 10:19:05 CDT 2003 http://baron.me.umn.edu/pipermail/flightgear-devel/2003-June/018316.html"""The wireframe mode got broke somewhere along the way, but I fixed itrecently. I haven't tried lately to see if it's broke again, but lastI checked it did work. It can be useful for debugging yourmodels/terrain because it will show you the exact triangle layout ..."""I am still searching for where it was decided that this useful functionalitywas to be removedNorman___Flightgear-devel mailing list[EMAIL PROTECTED]http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] [OT] PalmOS/GPS Moving Map?
David Megginson writes: Does anyone know of a simple PalmOS low-res moving map program, that just shows coastlines, lakes, rivers, towns and cities (as points), and possibly a couple of major highways? Even lower-res than vmap0 would be fine. http://www.gpsinformation.org/dale/Palm/pilotgps.htm HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] MATLAB/Simulink
I'm not sure if this is helpful at all, but have a look here (read carefully): http://www.u-dynamics.com/aerosim/default.htm Jon -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of NickSent: Wednesday, September 24, 2003 6:53 PMTo: FlightGear developers discussionsSubject: [Flightgear-devel] MATLAB/Simulink Good evening, Is there anyone on this list who has linked FlightGear or Microsoft FlightSim to Simulink block diagrams? Any advice or suggestions? Nickolas HeinMorgantown WV - Original Message - From: Norman Vine To: FlightGear developers discussions Sent: Wednesday, September 24, 2003 7:31 PM Subject: RE: [Flightgear-devel] Wireeframe and Flat Shaded Display Norman Vine wrote: Erik Hofman writes: This functionality has been removed about three months ago. It is no longer possible to use the scenery without textures. If there was some discussion as to dropping this basic support could someone pont me to it please.OK the last discussion I see about this is onTue Jun 24 10:19:05 CDT 2003 http://baron.me.umn.edu/pipermail/flightgear-devel/2003-June/018316.html"""The wireframe mode got broke somewhere along the way, but I fixed itrecently. I haven't tried lately to see if it's broke again, but lastI checked it did work. It can be useful for debugging yourmodels/terrain because it will show you the exact triangle layout ..."""I am still searching for where it was decided that this useful functionalitywas to be removedNorman___Flightgear-devel mailing list[EMAIL PROTECTED]http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MATLAB/Simulink
Jon, As it happens I was looking at the forum list for that product when your mail arrived. I've posted my request there. I have talked to Marius in the past and may use his Aerosim blockset for linking to FG and MSFS. I'm hoping he's also included X-Plane because it looks so darn useful. Nickolas HeinMorgantown WV - Original Message - From: Jon Berndt To: FlightGear developers discussions Sent: Wednesday, September 24, 2003 10:39 PM Subject: RE: [Flightgear-devel] MATLAB/Simulink I'm not sure if this is helpful at all, but have a look here (read carefully): http://www.u-dynamics.com/aerosim/default.htm Jon -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of NickSent: Wednesday, September 24, 2003 6:53 PMTo: FlightGear developers discussionsSubject: [Flightgear-devel] MATLAB/Simulink Good evening, Is there anyone on this list who has linked FlightGear or Microsoft FlightSim to Simulink block diagrams? Any advice or suggestions? Nickolas HeinMorgantown WV - Original Message - From: Norman Vine To: FlightGear developers discussions Sent: Wednesday, September 24, 2003 7:31 PM Subject: RE: [Flightgear-devel] Wireeframe and Flat Shaded Display Norman Vine wrote: Erik Hofman writes: This functionality has been removed about three months ago. It is no longer possible to use the scenery without textures. If there was some discussion as to dropping this basic support could someone pont me to it please.OK the last discussion I see about this is onTue Jun 24 10:19:05 CDT 2003 http://baron.me.umn.edu/pipermail/flightgear-devel/2003-June/018316.html"""The wireframe mode got broke somewhere along the way, but I fixed itrecently. I haven't tried lately to see if it's broke again, but lastI checked it did work. It can be useful for debugging yourmodels/terrain because it will show you the exact triangle layout ..."""I am still searching for where it was decided that this useful functionalitywas to be removedNorman___Flightgear-devel mailing list[EMAIL PROTECTED]http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___Flightgear-devel mailing list[EMAIL PROTECTED]http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Wireeframe and Flat Shaded Display
Norman Vine [EMAIL PROTECTED] said: Norman Vine wrote: Erik Hofman writes: This functionality has been removed about three months ago. It is no longer possible to use the scenery without textures. If there was some discussion as to dropping this basic support could someone pont me to it please. OK the last discussion I see about this is on Tue Jun 24 10:19:05 CDT 2003 http://baron.me.umn.edu/pipermail/flightgear-devel/2003-June/018316.html The wireframe mode got broke somewhere along the way, but I fixed it recently. I haven't tried lately to see if it's broke again, but last I checked it did work. It can be useful for debugging your models/terrain because it will show you the exact triangle layout ... I am still searching for where it was decided that this useful functionality was to be removed Wireframe mode works, it's the turning the textures on and off that no longer works. Maybe we should remap F9 to switch wireframe on and off? Do we need to be able to render geometry without the textures? As far as shading is concerned, the scenery is always flat shaded and the models are always smooth shaded. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
