On Mon, 2005-06-06 at 19:44, Josh Babcock wrote:
Well, take a look at what I put in, no wires, though I could do that
with about zero trouble if people think it would add to the model.
Personally I don't think it would add much though.
Agreed.
Also I think the bar
I put in there is pretty
On Tue, 7 Jun 2005 11:54:20 +1000, Mostyn wrote in message
[EMAIL PROTECTED]:
* Melchior FRANZ -- Monday 06 June 2005 09:16:
I *HATE* competition! Please, make it go away! ... Fortunately, one
could almost say that I have a *tiny* head start. So, don't panic
... panic? Whaahh ...
Okay,
I have just rebuild the last cvs release, and, may be i am wrong
after crash, the aircraft is again in normal startup situation, we have
not time to see place and position of crash.
Is it new? if yes how can we disable that new function.
--
Gerard
Gerard ROBIN wrote:
after crash, the aircraft is again in normal startup situation, we have
not time to see place and position of crash.
Is it new? if yes how can we disable that new function.
I saw the same effect last week, although I was under the impression
that this depends on the
Le mardi 07 juin 2005 13:39 +0200, Gerard ROBIN a crit :
I have just rebuild the last cvs release, and, may be i am wrong
after crash, the aircraft is again in normal startup situation, we have
not time to see place and position of crash.
Is it new? if yes how can we disable that new
I believe you are seeing the results of a new capability that Dave Culp added
to JSBSim
recently.
Jon
Gerard ROBIN wrote:
after crash, the aircraft is again in normal startup situation, we have
not time to see place and position of crash.
Is it new? if yes how can we disable that new
Le mardi 07 juin 2005 07:11 -0500, Jon Berndt a crit :
I believe you are seeing the results of a new capability that Dave Culp added
to JSBSim
recently.
Jon
Gerard ROBIN wrote:
after crash, the aircraft is again in normal startup situation, we have
not time to see place and
After RESET, and if using FDM JSBSim:
FG duplicate a new FDM JSBSim,
we can see it in Browser Property , /fdm/jsbsim (origine), /fdm/jsbsim1
(new 1 first reset), /fdm/jsbsim2 (new 2 second reset) and so on.
We had the same error in FG-9.8
The consequence is, after reset we cannot use JSB
Jon Berndt wrote:
Gerard ROBIN wrote:
after crash, the aircraft is again in normal startup situation, we have
not time to see place and position of crash.
Is it new? if yes how can we disable that new function.
I saw the same effect last week, although I was under the impression
that
Le mardi 07 juin 2005 12:50 +, Martin Spott a crit :
Jon Berndt wrote:
Gerard ROBIN wrote:
after crash, the aircraft is again in normal startup situation, we have
not time to see place and position of crash.
Is it new? if yes how can we disable that new function.
I saw the
Drew wrote:
Is there a reliable way to determine the terrain height below the
aircraft that is independent of the view being used?
Subtract the AGL altitude from the MSL altitude? I'm pretty sure both
of these are available in the property tree.
Andy
I will tell you the most FGFS incredible history:
I have discovered a conflict between main Airports and the Nvidia
graphic card 6600GT. I cannot explain what and why.
Does anybody can help me to understand ?
With the last Nvidia driver (7664) that graphic card perform fgfs at a
70 fps speed
Thanks for the suggestion...I just tried it, but the
/position/altitude-agl-ft property doesn't seem to be working. It's
always zero.
Perhaps the FDM needs to set this, in which case, how would the FDM
model know what the terrain height is?
On 6/7/05, Andy Ross [EMAIL PROTECTED] wrote:
Drew
Drew wrote:
Perhaps the FDM needs to set this, in which case, how would the FDM
model know what the terrain height is?
Yes, the FDM needs to set this, and it knows it because it needs it to
compute the gear forces. I know support is there in YASim; if you are
using a YASim model and this isn't
Gerard ROBIN wrote:
I have tested, after deleting airports objects (tower, beacon,
windsock,..) and after deleting textures, no change. Theses are not the
explanation, what else ?
Probably the runway and approach lighting. You might want to run with
--disable-enhanced-lighting
Erik
Gerard ROBIN wrote:
I will tell you the most FGFS incredible history:
I have discovered a conflict between main Airports and the Nvidia
graphic card 6600GT. I cannot explain what and why.
Does anybody can help me to understand ?
With the last Nvidia driver (7664) that graphic card perform
Le mercredi 08 juin 2005 06:06 +1000, Geoff Reidy a crit :
Gerard ROBIN wrote:
I will tell you the most FGFS incredible history:
I have discovered a conflict between main Airports and the Nvidia
graphic card 6600GT. I cannot explain what and why.
Does anybody can help me to
I'm not using a YASim model...it's a net-fdm interface...I'm only
using FlightGear as a scenery generator. Anyway, I just looked at the
YASim code, and it uses environment/ground-elev-m to derive the
height above terrain, which means it will also fail using tower view.
On 6/7/05, Andy Ross
I also have an nvidia card, though an older one, and when I go from Enhanced
Runway Lights (as low as 3 fps) to no Enhanced Runway Lights, it jumps to 40
fps. Any connection?
- Original Message -
From: Gerard ROBIN [EMAIL PROTECTED]
To: FlightGear developers discussions
Le mardi 07 juin 2005 22:34 +0200, Gerard ROBIN a crit :
Le mercredi 08 juin 2005 06:06 +1000, Geoff Reidy a crit :
Gerard ROBIN wrote:
I will tell you the most FGFS incredible history:
I have discovered a conflict between main Airports and the Nvidia
graphic card 6600GT. I
Gerard ROBIN wrote:
could you check if theses properties working.
It has not any effect on my side
I continu to get light.
controls
lighting
taxi-light type=boolfalse/taxi-light
landing-lights type=boolfalse/landing-lights
nav-lights type=boolfalse/nav-lights
beacon
Hi,
I have been playing with flight gear and right now I noticed that we are at
version 0.9.8
1) I am using FGFS Version 0.9.4, I noticed that the Airport Data file
extensions changed to tgz, does the data can be used on the version 0.9.4.
2) I am looking for the module that takes care of
On Tuesday 07 Jun 2005 23:16, [EMAIL PROTECTED] wrote:
1) I am using FGFS Version 0.9.4, I noticed that the Airport Data file
extensions changed to tgz, does the data can be used on the version 0.9.4.
Have you any reason not to upgrade? There's been a fair amount of improvement
since 0.9.4
Drew wrote:
I'm not using a YASim model...it's a net-fdm interface...I'm only
using FlightGear as a scenery generator. Anyway, I just looked at
the YASim code, and it uses environment/ground-elev-m to derive
the height above terrain, which means it will also fail using tower
view.
Er, no.
On Tue, 7 Jun 2005 11:19:02 -0700, Drew wrote in message
[EMAIL PROTECTED]:
Is there a reliable way to determine the terrain height below the
aircraft that is independent of the view being used? I've tried the
property /environment/ground-elevation-m, but when I use tower view,
it returns
Le mardi 07 juin 2005 17:07 -0400, [EMAIL PROTECTED] a crit :
I also have an nvidia card, though an older one, and when I go from Enhanced
Runway Lights (as low as 3 fps) to no Enhanced Runway Lights, it jumps to 40
fps. Any connection?
As far as i understand the preference.xml content,
On Tue, 7 Jun 2005 23:55:33 +0100, AJ wrote in message
[EMAIL PROTECTED]:
On Tuesday 07 Jun 2005 23:16, [EMAIL PROTECTED] wrote:
1) I am using FGFS Version 0.9.4, I noticed that the Airport Data
file extensions changed to tgz, does the data can be used on the
version 0.9.4.
Have you
Le mercredi 08 juin 2005 01:45 +0200, Gerard ROBIN a crit :
Le mardi 07 juin 2005 17:07 -0400, [EMAIL PROTECTED] a crit :
I also have an nvidia card, though an older one, and when I go from
Enhanced
Runway Lights (as low as 3 fps) to no Enhanced Runway Lights, it jumps to
40
fps.
Le mardi 07 juin 2005 23:55 +0100, AJ MacLeod (email lists) a crit :
On Tuesday 07 Jun 2005 23:16, [EMAIL PROTECTED] wrote:
1) I am using FGFS Version 0.9.4, I noticed that the Airport Data file
extensions changed to tgz, does the data can be used on the version 0.9.4.
Have you any
Is there a way to tell YASim to add or subtract some drag? I want to add
some drag to the superfort when the bomb doors open. They were supposed
to really wreck the airflow, though not as bad as the lg which doubled
the drag!
Josh
___
Flightgear-devel
Josh Babcock wrote:
Is there a way to tell YASim to add or subtract some drag? I
want to add some drag to the superfort when the bomb doors
open. They were supposed to really wreck the airflow, though
not as bad as the lg which doubled the drag!
Well, right now you could model them as landing
If I start putting weekly updates to the superfort on my website, will
someone volunteer to commit them? I'm planning on just uploading it from
a cron job which can send the lucky contestant e-mail reminders if desired.
Josh
___
Flightgear-devel
Josh Babcock wrote:
I don't think the LG thing will work, they have to be extended
independently of the LG.
Just tie a different property to the EXTEND input on the gear.
Nothing in YASim is hardcoded; all user inputs are configurable.
Speedbrakes would be great, though I would request that
I believe you are seeing the results of a new capability that Dave Culp
added to JSBSim recently.
Aaah, I sense something: This might be a means to automagically
re-incarnate crashed AI aircraft :-)
Actually I added the reset-after-crash to my OV-10 sim because it will be used
by the
Dave Culp wrote:
I believe you are seeing the results of a new capability that Dave Culp
added to JSBSim recently.
Aaah, I sense something: This might be a means to automagically
re-incarnate crashed AI aircraft :-)
Actually I added the reset-after-crash to my OV-10 sim because it will be
It could easily check another property and then decide whether to use
the old behavior or automatically reset. That property could have a
user-friendly setting in preferences.xml, and everyone else could change
it locally.
Yep, that would be best solution. I'll see if I can get to that
36 matches
Mail list logo
