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
> > themselve
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 a
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
___
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
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 te
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
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 ne
> -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
> 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, r
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
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.htm
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
__
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
13 matches
Mail list logo
