Re: [Flightgear-devel] About the bug 385
Am 04.03.2012 00:09, schrieb jean pellotier: BTW, whitch OSG version do i have to use? last devel version is ok? Any version that reproduces the issue for you. If it still occurs with OSG trunk, then that's also interesting. If it wasn't, well, then you have a solution ;-). But I already have a suspicion on a timing/sequence issue inside FG itself, so OSG probably won't matter. 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
Re: [Flightgear-devel] About the bug 385
Am 03.03.2012 03:28, schrieb Robert: 2012/3/2 ThorstenB bre...@gmail.com mailto:bre...@gmail.com 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. Thorsten, this bug is also present on Linux (in my case), and I think I have read in the google bug-reports that OSX is affected, too. Never heard anyone reporting the issue for Linux. Indeed, there was a related bug for Mac (#356), but that was reported to be fixed with OSG 3.0.1, only leaving an ugly effect (whatever that is). Anyway, anyone reproducing the issue and capable of compiling FG 2.7.0/Git could help by providing the terminal output when running a debug patch, see #385, comment 41 for details: http://code.google.com/p/flightgear-bugs/issues/detail?id=385#c41 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
Re: [Flightgear-devel] About the bug 385
Le 03/03/2012 23:12, ThorstenB a écrit : Am 03.03.2012 03:28, schrieb Robert: 2012/3/2 ThorstenBbre...@gmail.commailto:bre...@gmail.com 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. Thorsten, this bug is also present on Linux (in my case), and I think I have read in the google bug-reports that OSX is affected, too. Never heard anyone reporting the issue for Linux. Indeed, there was a related bug for Mac (#356), but that was reported to be fixed with OSG 3.0.1, only leaving an ugly effect (whatever that is). Anyway, anyone reproducing the issue and capable of compiling FG 2.7.0/Git could help by providing the terminal output when running a debug patch, see #385, comment 41 for details: http://code.google.com/p/flightgear-bugs/issues/detail?id=385#c41 cheers, Thorsten Hi, thanks for the patch, as I am on linux and affected by the bug (and the one complaining the most), I guess i will try it, BTW, whitch OSG version do i have to use? last devel version is ok? cheers 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/3/2 ThorstenB bre...@gmail.com 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. Thorsten, this bug is also present on Linux (in my case), and I think I have read in the google bug-reports that OSX is affected, too. cheers, Robert -- 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
[Flightgear-devel] About the bug 385
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
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