Here's an update for cvs/head (there were some changes made
to fg_init.cxx in the meantime):
http://members.aon.at/mfranz/fg_init.diff [5.9 kB]
Doesn't look, though, as if there's much interest.
m.
-
Take Surveys. Earn
On Thursday 05 April 2007 01:40, Gabor Toth wrote:
Hi,
I've got the hint on the IRC channel from Jester to use OSG revision 6398
to avoid this error. It worked for me.
Regards,
Gabor
Thanks! That worked fine.
I tried the patch from the users list first, but while it got past
On 4/5/07, Toth Gabor wrote:
On Thursday 05 April 2007 04:34, Csaba Halász wrote:
On 4/5/07, Gabor Toth wrote:
Hi,
I've found a funny rendering bug seen on the following pictures:
http://fgfs.i-net.hu/downloads/fgfs-screen-054.jpg
Hi Curt,
Thanx for the quick answer, the details from my first mail about this issue
are:
Config: AMD Athlon64 X2 4200, Geforce 6600 (Asus)
OS: Fedore Core 5
Kernel: 2.6.20-1.2307.fc5smp
nVidia driver version: 1.0-9755
OSG revision: 6398
SimGear, FlightGear version: CVS
Oops, you are right, that information was all in your original message, just
not in the quoted versions later. Sorry about that. It really looks like
it might be some sort of osg bug (or possibly our usage of osg?) I've seen
a similar issue using open flight models in our commercial driving
* Curtis Olson -- Thursday 05 April 2007:
It really looks like it might be some sort of osg bug (or possibly
our usage of osg?)
Yes. I can confirm the bug, even for KSFO:
http://members.aon.at/mfranz/osg-rendering.jpg [20.0 kB]
So far I could only reproduce if I banked an aircraft
* Melchior FRANZ -- Thursday 05 April 2007:
http://members.aon.at/mfranz/osg-rendering.jpg [20.0 kB]
So far I could only reproduce if I banked an aircraft quickly.
BTW: it seemed as if *all* textures on the airport rotated/sheared,
even the grass texture. Your opengl state theory seems
* Melchior FRANZ -- Thursday 05 April 2007:
BTW: it seemed as if *all* textures on the airport rotated/sheared,
even the grass texture. Your opengl state theory seems plausible
to me.
And another detail might be interesting: Gabor saw it on the 747,
and I saw it on the bo105. Both aircraft use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Melchior FRANZ wrote:
* Curtis Olson -- Thursday 05 April 2007:
It really looks like it might be some sort of osg bug (or possibly
our usage of osg?)
Yes. I can confirm the bug, even for KSFO:
http://members.aon.at/mfranz/osg-rendering.jpg
Roy Vegard Ovesen writes:
I tried the patch from the users list first, but while it got past
model_panel.cxx I gor similar errors on Main/renderer.cxx.
there are two patches i posted. you need to apply both.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
|
On Thursday 05 April 2007 20:20:26 sydsandy wrote:
Also if I look in certain directions everything goes white , and I can
see the 'invisible' panel area defined in the animation file for hotspot
and 2 d instrument arrangements it seems to appear if the center of
the transparent polygon
* Melchior FRANZ -- Tuesday 03 April 2007:
Any comments?
Nope. Accepted by overwhelming lack of responses. You've been
warned. Later reclamations can not be accepted, sorry. :-P
m.
-
Take Surveys. Earn Cash. Influence the
Hi all,
if anyone remembers , what was the purpose of the serviceable
property ?
Was it meant as an on/off switch , instrument fault , or just instrument
state ?
The reason I'm asking is I have redone the Aerostar electrical system ,
so that one can create a battery / alternator with
Hello!
Nick had some trouble with the tacan on the lightning, so I had a peek at it.
Worked for me all right. However, the instrument needle works as if it
were a fixed compass card indicator, which it isn't. So there should
be an additional rotation applied to adjust for the a/c heading. Patch
On 4/6/07, sydsandy [EMAIL PROTECTED] wrote:
Hi all,
if anyone remembers , what was the purpose of the serviceable
property ?
Was it meant as an on/off switch , instrument fault , or just instrument
state ?
I can't remember because I am fairly new to flightgear. But I'd say it
should be
Reported by AnMaster on IRC ;)
Inserting and deleting waypoints not at the end of the route messes up
leg distances.
Beefed up the test prog a little, see patch #1.
Result (have cut out the irrelevant part):
Route dump: Init
#0 Start (0, 0) @0 dist: 0
#1 1 (0, 1) @0 dist: 1
I can't remember because I am fairly new to flightgear. But I'd say it
should be an instrument fault.
Thats what I assumed too ...
In the C++ sources under Instrumentation, quite a few implementations
(counted 14) check for proper power.
not bad, out of 31 , i guess :)
SO , should
17 matches
Mail list logo
