If I am understanding you correctly, you want to get access to various
variables within flightgear. Isn't the Property Tree via telnet or http
something that might work for you? Should be easy to access it from a web
service even. Or define a generic protocol, the wiki had an example how to
make
Happy new year!
Vivian,
On Friday, December 30, 2011 10:48:40 Vivian Meazza wrote:
The hangs are caused by mipmap generation on the fly by OSG?
The hangs are caused by mipmap generation by the driver which happens on forst
use of a texture.
The old texture files are static and I would
Hi,
On Friday, December 30, 2011 11:11:39 Frederic Bouvier wrote:
* If it's just the mipmaps. May be we can precompute the mipmaps using
the cpu in the database loader thread. This would help all textures not
only the ones that could be converted. May be this is the most generic
Hi Erik,
On Friday, December 30, 2011 11:39:37 Erik Hofman wrote:
On Fri, 2011-12-30 at 10:42 +0100, Mathias Fröhlich wrote:
* If it's just the mipmaps. May be we can precompute the mipmaps using
the cpu in the database loader thread. This would help all textures not
only the ones that
Hi,
On Friday, December 30, 2011 11:45:21 Frederic Bouvier wrote:
The problem I have to solve currently is how to feed the G-Buffer
to the Effect system because the textures used to store it are
camera-dependent (in a multi screen context) but the pass (which
is a stateset) is built once for
An (incomplete) list of issues I have observed in flying various aircraft
recently - maybe some of them can be fixed by maintainers before the
release:
* Vostok-1 is currenty a no-show - it crashes before doing anything, the
log seems to point to a property as the cause. I guess it *may* be a
Hi Mathias,
De: Mathias Fröhlich
On Friday, December 30, 2011 11:45:21 Frederic Bouvier wrote:
The problem I have to solve currently is how to feed the G-Buffer
to the Effect system because the textures used to store it are
camera-dependent (in a multi screen context) but the pass
Hi Pete, Geoff,
Now my script work perfectly.
When I remove all 21 | tee -a $LOGFILE and I replace it by a simple
$LOGFILE I see many less information in terminal when script is running. It's
very annoying to haven't information about step in terminal...
For example, when the script
On 2012-01-01 16.40, Clément de l'Hamaide wrote:
When I remove all 21 | tee -a $LOGFILE and I replace it by a
simple $LOGFILE I see many less information in terminal when
script is running. It's very annoying to haven't information about
step in terminal... For example, when the script
On Sun, 2012-01-01 at 16:40 +0100, Clément de l'Hamaide wrote:
Hi Pete, Geoff,
Now my script work perfectly.
Hi Clément,
Glad to hear it is all now working fine...
Sorry my explanation was not clear...
1. I assume, like Francesco's script, and mine,
you have the command in the early
On 2012-01-01 20.17, Geoff McLane wrote:
But in doing this, as you point out, there is NO OUTPUT
to the console...
Except as Jari pointed out, you can start the script
as a background process, and use a repeated tail
command to view the end of the LOG in a console...
Or even start the
How about this at the top of the script (in tried yet)
$0 2$1 |tee $logfile
Rediredt all script output and tee in background. Exit status should still stop
the build and out put should be on screen as well as in the log file
Sent from Samsung tabletGeoff McLane ubu...@geoffair.info
On Sun, 1 Jan 2012, thorsten.i.r...@jyu.fi wrote:
An (incomplete) list of issues I have observed in flying various aircraft
recently - maybe some of them can be fixed by maintainers before the
release:
* Vostok-1 is currenty a no-show - it crashes before doing anything, the
log seems to
* dhc6: Nice to see more details in the cockpit. Just, how the hell do I
switch all the warning signs off? After starting the engines, the whole
warning panel lit up (which I know from some other aircraft as a test
mode), but the lights never went out. Plane was flying fine though.
I dont see
On Fri, 30 Dec 2011 11:13:43 -0800 (PST), Gene wrote in message
alpine.lfd.2.00.1112301112510.6...@grumble.deltasoft.com:
On Fri, 30 Dec 2011, Mathias Fröhlich wrote:
blobs?
We could try to decompress the blobs? --- No, patent
infringement!!!
I call shennanigans. There's no way a
FG seems not to be the only project which has problems with multi GB git
repos. The Linux kernel and Android are in the same league and they have
experiences of their own.
This might be an interesting read:
https://plus.google.com/112413860260589530492/posts/EJCsVq6o1vF
Stefan
16 matches
Mail list logo
