[Flightgear-devel] About the bug 385

2012-03-01 Thread jean pellotier
Hi,

  happy ati user :)  I'm affected from quite some time by the bug 385:

http://code.google.com/p/flightgear-bugs/issues/detail?can=2start=0num=100q=colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestonegroupby=sort=id=385#makechanges

It appear in my setup that adding a radar section in the 
intrumentation.xml (or any name called by the instrumentation field in 
the -set.xml file) solve the bug, for all the planes tested (b1900d, 
bo105, iar80, super constellation etc...)

   radar
 namewxradar/name
 number0/number
   /radar

- is there some clue why the radar can have such an impact?

- is it possible to add the radar section to the aircrafts in the base 
package affected by the bug, or do we have to buy nvidia again?

jano

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] About the bug 385

2012-03-01 Thread ThorstenB
On 02.03.2012 00:29, jean pellotier wrote:
 http://code.google.com/p/flightgear-bugs/issues/detail?can=2start=0num=100q=colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestonegroupby=sort=id=385#makechanges

 It appear in my setup that adding a radar section in the
 intrumentation.xml (or any name called by theinstrumentation  field in
 the -set.xml file) solve the bug, for all the planes tested (b1900d,
 bo105, iar80, super constellation etc...)

 radar
   namewxradar/name
   number0/number
 /radar

 - is there some clue why the radar can have such an impact?

 - is it possible to add the radar section to the aircrafts in the base
 package affected by the bug, or do we have to buy nvidia again?

See my comments at bug #385:
For some people, removing the instrumentation section from aircraft 
fixes the issue (or renaming it, which is effectively the same). 
Otherwise, adding even more stuff to the section, such as the radar also 
seems to help.

This could be a timing issue, since people seeing the issue obviously 
need to speed up or slow down the phase of initial aircraft loading.

We already know that FG doesn't receive a Window resize event when the 
issue happens. But we don't know why this only happens with the ATI, 
only with their driver versions 11.5 and above, and only on Windows.

One hope is that using a newer OSG library might fix the issue. The 
latest OSG release is still 3.0.1, but there have been a number of fixes 
to OSG, including the modules handling GraphicsWindows since. So, it'd 
be interesting if someone seeing the issue tested FG the latest OSG 
trunk version.

If this doesn't help, then it really takes someone using a debugger and 
investigate what's happening to the resize event. In any case, randomly 
adding or removing stuff to aircraft files isn't a solution. Of course, 
it's ok for anyone to change things locally as a work-around, but 
nothing acceptable for FG in general.

cheers,
Thorsten

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel