Re: [Flightgear-devel] 2.10.1

2013-05-09 Thread Renk Thorsten
The downside is that I think it would require adding an if() test to the vertex shader, something I've been avoiding due to (unfounded?) concerns about performance. General advice that I can find is that GLSL is designed as a linear program: conditionals and loops are best avoided:

[Flightgear-devel] Tree images for texturing

2013-05-09 Thread Renk Thorsten
I have a series of tree photographs if anyone is interested in creating new tree textures. The images are 1200x1600 JPEG, taken on an overcast day in diffuse light, outlining the trees against the bright sky, isolated as good as possible against the background. I've experimented with

Re: [Flightgear-devel] Check your IOrules!

2013-05-09 Thread grtuxhangar team
Thomas, May i know which part of fgdata is involved, since with my own systems, for weeks i can't use the entire original fgdata GIT without crashing. .Please tell me what these messages are used for ? Thank ahmad On 9 May 2013 02:17, Thomas Geymayer tom...@gmail.com wrote: 2013/5/9

Re: [Flightgear-devel] Check your IOrules!

2013-05-09 Thread Thomas Geymayer
Am 2013-05-09 13:19, schrieb grtuxhangar team: Thomas, May i know which part of fgdata is involved, since with my own systems, for weeks i can't use the entire original fgdata GIT without crashing. Just two small changes to Nasal/io.nas and Nasal/props.nas:

[Flightgear-devel] Réf.: Re: 2.10.1

2013-05-09 Thread Olivier
It even does it with a simple fgfs --show-aircraft... It's been there for quite a while now, nearly one year afair. -- Le mer. 8 mai 2013 14:57 HAE, Gijs de Rooy a écrit : Hi Stuart, Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm I

Re: [Flightgear-devel] Check your IOrules!

2013-05-09 Thread grtuxhangar team
Thomas, Thank. Won't it be better to have such messages with _WARN instead of _ALERT ? since we are collecting a lot of others not useful annoying messages -Enabling ATI viewport hack - DDS texture warning Which oblige the user to build some customized program to avoid it. ahmad On 9 May

[Flightgear-devel] Syncing sim time

2013-05-09 Thread castle . 64
Hi, Thanks to Jan Comans I've been able to sync the 3D clouds across three instances of fgfs running on a multi-core machine. This, in turn, provides for some very respectable frame rates of 40 to 50 fps per core with a three projector system with older generation Nvidia boards ( GT430 and

Re: [Flightgear-devel] Syncing sim time

2013-05-09 Thread Arnt Karlsen
On Thu, 9 May 2013 14:57:21 + (UTC), castle...@comcast.net wrote in message 142462582.1782424.1368111441180.javamail.r...@sz0139a.emeryville.ca.mail.comcast.net: Hi, Thanks to Jan Comans I've been able to sync the 3D clouds across three instances of fgfs running on a multi-core machine.

Re: [Flightgear-devel] 2.10.1

2013-05-09 Thread Gijs de Rooy
Hi Toshi, According Fred's comment in http://code.google.com/p/flightgear-bugs/issues/detail?id=1027#c9 those messages are output by fgrun reading the file: $fgdata/Aircraft/C130/kc130-yasim-cnf.xml thanks for the pointer! This is now fixed in fgdata. Cheers, Gijs

Re: [Flightgear-devel] Syncing sim time

2013-05-09 Thread Stuart Buchanan
Hi Jack, On Thu, May 9, 2013 at 3:57 PM, Jack wrote: Thanks to Jan Comans I've been able to sync the 3D clouds across three instances of fgfs running on a multi-core machine. This, in turn, provides for some very respectable frame rates of 40 to 50 fps per core with a three projector