On 30 Sep 2011, at 19:52, Michael Robson wrote:
Essentially what I am looking to do is create some instruments of my own with
some detailed generation of graphical entities that are being continually
updated. I am therefore assuming that a 'dynamic texture' is the way to go
with this.
makes use of already existing code in Flightgear.
Chase Zakharov for a better description of what is happening.
Alan
-Original Message-
From: James Turner
Sent: Saturday, October 01, 2011 9:40 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Query about groundradar
James, this sounds very interesting. I will check out the code this weekend
if I get time and have a look through. I am pretty sure that this is the way
I need to go to implement my instument!
Alan, that instrument looks interesting. I may be able to use the technique
for a 'layer' on my display.
: [Flightgear-devel] Query about groundradar Instrument module
To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net
Date: Saturday, October 1, 2011, 11:07 AM
Another way is to use the ZKV1000 instrument. See
http://wiki.flightgear.org/FlightGear_Newsletter_October_2010. It is so
From: Michael Sgier
Sent: Saturday, October 01, 2011 3:43 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Query about groundradar Instrument module
Any ideas/help on what to do? In GIT the Honda and DA20 are black/off?
Thanks
Michael
I
From: Robbo
Sent: Saturday, October 01, 2011 10:57 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Query about groundradar Instrument module
Alan, that instrument looks interesting. I may be able to use the technique for
a 'layer' on my display. Is it essentially
-twin.org.uk wrote:
*From:* Robbo robbo_b...@hotmail.com
*Sent:* Saturday, October 01, 2011 10:57 AM
*To:* FlightGear developers
discussionsflightgear-devel@lists.sourceforge.net
*Subject:* Re: [Flightgear-devel] Query about groundradar Instrument
module
Alan, that instrument looks interesting. I
Hi,
Thanks for your replies with regards to this subject.
It is all starting to make some sense now. If I understand correctly then, the
C++ module generates an in-memory texture that the xml files reference for
displaying within the OSG tree. This texture is being continually re-generated
On Thu, Sep 29, 2011 at 10:32 PM, Robbo robbo_b...@hotmail.com wrote:
Hi,
Essentially, there is a 'texture' declared as follows:
static const char* default_texture_name =
Aircraft/Instruments/Textures/od_groundradar.rgb;
FGTextureManager::addTexture(texture_name, getTexture());
Now all is
Robbo,
I just went through the process of adding this texture to the A380
after reading the source code, for when you are taxiing around an
airport.
The output texture file is in essence a virtual file. So the texture
is created in memory and given a path reference (it's never actually
On Thursday 29 September 2011 14:32:54 Robbo wrote:
Hi,
I am trying to familiarise myself with Flightgear's source code so that I
may try and contribute. I am currently looking at the 'groundradar'
instrument module and there is something within that is causing me some
confusion.
11 matches
Mail list logo
