Re: [Flightgear-devel] wish list for next release
On November 1, 2005 12:43 pm, Andy Ross wrote: Erik Hofman wrote: Ampere K. Hardraade wrote: A texcopy function that allows one to copy one part of the texture to another would be useful. Although it would be doable, one problem with this is that the textures themselves are stored in video memory so updating them isn't as easy as it sounds. And the APIs are complicated. Traditional (1.1) OpenGL can only do this to and from the framebuffer, not between textures. What I meant was copying one part of the texture to another part of the same texture. Sorry for the confusion. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Ampere K. Hardraade wrote: A texcopy function that allows one to copy one part of the texture to another would be useful. Although it would be doable, one problem with this is that the textures themselves are stored in video memory so updating them isn't as easy as it sounds. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Erik Hofman wrote: Ampere K. Hardraade wrote: A texcopy function that allows one to copy one part of the texture to another would be useful. Although it would be doable, one problem with this is that the textures themselves are stored in video memory so updating them isn't as easy as it sounds. And the APIs are complicated. Traditional (1.1) OpenGL can only do this to and from the framebuffer, not between textures. The last time I looked at this problem, about 2 years ago, there were a bunch of extensions being proposed that would represent all memory areas on the graphics card (vertex buffers, textures, framebuffers, depthbuffers, etc...) with a unified API that was tentatively called the uberbuffer. I'm not sure what happened to this, or what the status is of driver support on modern cards. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
On October 30, 2005 04:23 am, Erik Hofman wrote: This can be done now by using the texture animations; texrotate and textranslate See FlightGear/data/Docs/model-howto.html for more information. Erik A texcopy function that allows one to copy one part of the texture to another would be useful. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Dave Culp wrote: 2) Texture cropping for 2D panels so that Attitude Indicator ladders stay in bounds. This can be done now by using the texture animations; texrotate and textranslate See FlightGear/data/Docs/model-howto.html for more information. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
On Sunday 30 October 2005 03:23 am, Erik Hofman wrote: Dave Culp wrote: 2) Texture cropping for 2D panels so that Attitude Indicator ladders stay in bounds. This can be done now by using the texture animations; texrotate and textranslate See FlightGear/data/Docs/model-howto.html for more information. This works for 2D panels? The document only mentions animations for 3D models. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Dave Culp wrote: On Sunday 30 October 2005 03:23 am, Erik Hofman wrote: This can be done now by using the texture animations; texrotate and textranslate This works for 2D panels? The document only mentions animations for 3D models. Ow, that I'm not sure of. I guess it would be better to backport this code to support 2D panels also then. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Ow, that I'm not sure of. I guess it would be better to backport this code to support 2D panels also then. The only thing lacking in the 2D code now is the ability rotate, translate, and *then* crop a texture. Maybe it would be required that the texture be drawn to a context in memory, rotated, translated, and then cropped and drawn to the screen? It's unlikely that I'll be learning OpenGL in the next few years, so it would be *really* great if someone could look into this issue. This would finally make the 2D panel code complete. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] wish list for next release
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dave Culp
Sent: Sunday, October 30, 2005 7:55 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] wish list for next release
Ow, that I'm not sure of.
I guess it would be better to backport this code to support 2D panels
also then.
The only thing lacking in the 2D code now is the ability rotate, translate,
and *then* crop a texture. Maybe it would be required that the texture be
drawn to a context in memory, rotated, translated, and then cropped and drawn
to the screen?
It's unlikely that I'll be learning OpenGL in the next few years, so it would
be *really* great if someone could look into this issue. This would finally
make the 2D panel code complete.
I am not really up to speed with the Panels but ...
FG_SRC / cockpit / panel.hxx
/**
* A transformation for a layer.
*/
class FGPanelTransformation : public SGConditional
{
public:
enum Type {
XSHIFT,
YSHIFT,
ROTATION
};
FGPanelTransformation ();
virtual ~FGPanelTransformation ();
Type type;
const SGPropertyNode * node;
float min;
float max;
bool has_mod;
float mod;
float factor;
float offset;
SGInterpTable * table;
};
seems to have what you need
Maybe it just needs to be exposed better
Norman
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Norman Vine wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dave Culp
Sent: Sunday, October 30, 2005 7:55 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] wish list for next release
Ow, that I'm not sure of.
I guess it would be better to backport this code to support 2D panels
also then.
The only thing lacking in the 2D code now is the ability rotate, translate,
and *then* crop a texture. Maybe it would be required that the texture be
drawn to a context in memory, rotated, translated, and then cropped and drawn
to the screen?
It's unlikely that I'll be learning OpenGL in the next few years, so it would
be *really* great if someone could look into this issue. This would finally
make the 2D panel code complete.
I am not really up to speed with the Panels but ...
FG_SRC / cockpit / panel.hxx
/**
* A transformation for a layer.
*/
class FGPanelTransformation : public SGConditional
{
public:
enum Type {
XSHIFT,
YSHIFT,
ROTATION
};
FGPanelTransformation ();
virtual ~FGPanelTransformation ();
Type type;
const SGPropertyNode * node;
float min;
float max;
bool has_mod;
float mod;
float factor;
float offset;
SGInterpTable * table;
};
seems to have what you need
Maybe it just needs to be exposed better
Norman
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Slightly off-topic. Is anyone working on or thinking about improving the
ability to do MFDs and glass cockpit type displays? Someday it would be
really nice to have an easy way to display text on a screen, have a
plugin generate an image to display on a screen (like a moving map) or
have a touchscreen where the hotspots can change on the fly. Maybe just
have a plugin system that passed screen touches and properties in one
direction and an image in the other.
Josh
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Josh Babcock wrote: Slightly off-topic. Is anyone working on or thinking about improving the ability to do MFDs and glass cockpit type displays? Someday it would be really nice to have an easy way to display text on a screen You could write your text in a texture and then use that as a regular instrument texture. If you are displaying some interessant texts then it can even be a generic reuseable text source. , have a plugin generate an image to display on a screen (like a moving map) not sure what you are talking about or have a touchscreen where the hotspots can change on the fly. Isn't this called panel hotposts ? Maybe just have a plugin system that passed screen touches and properties in one direction and an image in the other. Josh Like 2D instruments with hotspots and conditional layers ? Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] wish list for next release
Harald JOHNSEN wrote: Josh Babcock wrote: Slightly off-topic. Is anyone working on or thinking about improving the ability to do MFDs and glass cockpit type displays? Someday it would be really nice to have an easy way to display text on a screen You could write your text in a texture and then use that as a regular instrument texture. If you are displaying some interessant texts then it can even be a generic reuseable text source. I was thinking of something a little more flexible. Piecing text together from individual letters is extremely tedious. , have a plugin generate an image to display on a screen (like a moving map) not sure what you are talking about Imagine being able to display Atlas-like output in an instrument in FG. Similarly someone could write code that could display a weather map, or terrain avoidance maps, or maybe some systems management stuff like the glass-cockpit heavy metal planes have. A plugin API would not have to do much, but would enable someone who can do a little coding to do some neat stuff. or have a touchscreen where the hotspots can change on the fly. Isn't this called panel hotposts ? No, panel hotspots are static. It would be nice to have something that can change as things move on the display or the display changes modes. I started thinking about this because I'm building a super-secret model that has panels that can move. It would be pretty silly to move the panel away and still have the hotspots hovering in mid-air. Maybe just have a plugin system that passed screen touches and properties in one direction and an image in the other. Josh Like 2D instruments with hotspots and conditional layers ? Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] wish list for next release
Is it time to establish a wish list for the next release (or did I miss it?). Maybe this should be called a things to wrap up list, if it's too late for a wish list. BTW, I looked for a wish list at the flightgear.org website and found a goals page, which is a similar thing as a wish list, but this page looks pretty out-dated. Here are my wishes: 1) Oliver's multiplayer 2) Texture cropping for 2D panels so that Attitude Indicator ladders stay in bounds. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
