On Freitag 02 Dezember 2005 12:48, Melchior FRANZ wrote:
* Mathias Fröhlich -- Friday 02 December 2005 07:35:
float
XDR_decode_float ( const xdr_data_t f_Val )
{
union {
float f;
xdr_data_t x;
} tmp;
tmp.x = XDR_decode_int32 (f_Val);
return tmp.f;
* Melchior FRANZ -- Friday 02 December 2005 18:44:
I will present a patch after that which restores the
original, pre-ObjectsTerrain behavior.
Committed.
If FG_SCENERY=A:B and both dirs contain a Terrain/ and Objects/
subdir, then FGGlobals::set_fg_scenery() will expanded this to a
list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Melchior FRANZ schrieb:
If FG_SCENERY=A:B and both dirs contain a Terrain/ and Objects/
does the seperator have to be a double colon :?
Or, more precisely, is it a ; under Windos? A double colon would cause
real trouble under Windos... (imagine
* Christian Mayer -- Saturday 03 December 2005 12:35:
Melchior FRANZ schrieb:
If FG_SCENERY=A:B and both dirs contain a Terrain/ and Objects/
does the seperator have to be a double colon :?
Or, more precisely, is it a ; under Windos? A double colon would cause
real trouble under Windos...
Melchior FRANZ wrote:
* Melchior FRANZ -- Friday 02 December 2005 18:44:
I will present a patch after that which restores the
original, pre-ObjectsTerrain behavior.
Committed.
If FG_SCENERY=A:B and both dirs contain a Terrain/ and Objects/
subdir, then FGGlobals::set_fg_scenery()
I've just tried out the c310 @KSFO, current metar conditions.
The Yasim one develops 38PSI of manifold pressure, ~2700RPM
at props and throttle full forward on the ground, brakes applied.
The JSBsim gives a (more realistic-?) 29PSI. No surprise the ground
roll at the Yasim one's is much shorter.
I've just tried out the c310 @KSFO, current metar conditions.
The Yasim one develops 38PSI of manifold pressure, ~2700RPM
at props and throttle full forward on the ground, brakes applied.
The JSBsim gives a (more realistic-?) 29PSI. No surprise the ground
roll at the Yasim one's is much
* Harald JOHNSEN -- Saturday 03 December 2005 13:12:
Now the question are :
I guess this is mostly answered in my reply to Christian. People
seem to be unaware of the FG_SCENERY path list. This is not a new
feature. It exists since at least two years (or something). Only
the behavior changed a
On Saturday 03 December 2005 01:26 am, Vassilii Khachaturov wrote:
2) when I hit the F3 to generate the above snapshot, I got an unusual
attitude, from which it was very difficult to recover
Are you flying using the mouse?
Affirmative.
When you hit F3 the cursor is slewed to the
If this is just flipping the sign why not just grep and fix all the aircraft in
CVS that specify incidence? I guess I don't understand the ritual. Maybe
there was more to this change that I'm just not aware of?
Best,
Jim
___
Flightgear-devel
Jim Wilson wrote:
If this is just flipping the sign why not just grep and fix all the aircraft in
CVS that specify incidence? I guess I don't understand the ritual. Maybe
there was more to this change that I'm just not aware of?
Most modelers (if not all) were unaware of this problem. Some
On Sat, 3 Dec 2005, Erik Hofman wrote:
Jim Wilson wrote:
If this is just flipping the sign why not just grep and fix all the
aircraft in CVS that specify incidence? I guess I don't understand the
ritual. Maybe there was more to this change that I'm just not aware of?
Most modelers (if not
2) when I hit the F3 to generate the above snapshot, I got an unusual
attitude, from which it was very difficult to recover
Are you flying using the mouse?
Affirmative.
When you hit F3 the cursor is slewed to the bottom left corner of the
screen. If you are using the mouse
Jim Wilson wrote:
If this is just flipping the sign why not just grep and fix all the aircraft in
CVS that specify incidence? I guess I don't understand the ritual. Maybe
there was more to this change that I'm just not aware of?
The big issue is that developers were actually specifying
Jim Wilwon wrote:
If this is just flipping the sign why not just grep and fix all
the aircraft in CVS that specify incidence?
The files in CVS (most of them -- the ones that weren't pre-fixed
for the 0.9.9 release) specify incidence as documented, not as it
was actually implemented in code. So
* Melchior FRANZ -- Saturday 03 December 2005 16:45:
+union {
+float f;
+int i;
+} v;
Umm ... but is sizeof(float)==sizeof(int) on all supported
platforms? It's not on Atari ST, for example (IIRC). :-/
m.
___
Melchior FRANZ wrote:
Now the question is: should fgfs work around a broken gcc release,
when there's hope that the next version will be fixed? Or is it not
a bug,
Strictly, it's not a bug. Within a single function, it is not legal
to have two pointers of different types pointing to the same
Melchior FRANZ wrote:
Umm ... but is sizeof(float)==sizeof(int) on all supported
platforms? It's not on Atari ST, for example (IIRC). :-/
Really? I honestly thought all 68k platforms used a 32 bit int to
match the register width. Certainly all 68k gcc variants do (gcc
can't support a 16 bit
Joacim Persson wrote:
I've discovered a difference between how fgfs calls the yasim solver, and
how the yasim binary (aka yasim-test) does it. I have a -yasim.xml which
doesn't pass yasim(-test) but which fgfs accepts... ?:-P
So what is the difference? Number of iterations?
That sounds like
On Samstag 03 Dezember 2005 16:45, Melchior FRANZ wrote:
It turned indeed out to be yet another one of these ugly aliasing
bugs with gcc 4.0.2 ([1] *AND* [2]!). In fastmath.hxx apparently
reinterpret_cast doesn't work appropriately. Could explain why Alex'
clean patch didn't work. Now the
On Samstag 03 Dezember 2005 17:17, Mathias Fröhlich wrote:
You are citing the standard yourselves often enough that I believe that you
can read that.
Sorry, Melchior.
I sometimes do not see that I might be insulting.
That was not my intention!
Greetings
Mathias
--
Mathias Fröhlich,
--- Harald JOHNSEN wrote:
Now the question are :
- where must I put the objects I download from fgdb on my disk
- where can I put some other objects I want to add
- and finaly the only important question : what do my FG_scenary
env var must look like ?
Have a look at the Getting Started
From: Erik Hofman
Jim Wilson wrote:
If this is just flipping the sign why not just grep and fix all the
aircraft in CVS that specify incidence? I guess I don't
understand the ritual. Maybe there was more to this change that I'm just not
aware of?
Most modelers (if not all) were
From: Andy Ross
unintended consequences. The old files were tuned for a broken
implementation, and may need some re-tuning for the fixed one.
Ah ok. I thought it was just an inverted sign on the configuration input.
Best,
Jim
___
On Sat, 3 Dec 2005, Andy Ross wrote:
That sounds like a bug. They are intended to produce identical
behavior. Is it possible you have a yasim binary build from a
different version of the code than your fgfs?
My first thought too.
The file I used was the AN-225-yasim.xml with the only
On December 2, 2005 09:33 am, Josh Babcock wrote:
Perhaps it would be easy to write a null autopilot. Put that in the base
package, and anyone who wants no autopilot in their aircraft could
select that. I know nothing of autopilots though.
Josh
How about disabling avionic functions by
On November 30, 2005 12:25 pm, Melchior FRANZ wrote:
Could be added to the list of admitted features for 1.0, next
to landing lights ... :-)
m.
Just so people don't pull their hair out trying to come up with a solution to
the landing lights:
27 matches
Mail list logo
