here I upload shader framework that supports shaders from VP1.0 to GLSL and
have runway lights calculated in vertex shader and uses point sprites
http://fgfs.narod.ru/glsl.tar.gz
Tested on Nvidia Geforce5950 and linux 6629 drivers
must compiled with -DGL_GLEXT_PROTOTYPES key in C++ section of makefile
Now I start integrate FBO extension in Harald clouds code to make
render-to-texture more efficiently

----- Original Message -----
From: "Gerard Robin" <[EMAIL PROTECTED]>
To: "FlightGear developers discussions" <flightgear-devel@flightgear.org>
Sent: Tuesday, June 21, 2005 3:43 PM
Subject: Re: [Flightgear-devel] Lights was: Shadows


> Le mardi 21 juin 2005 à 11:34 +0400, Roman Grigoriev a écrit :
> > to Harald JOHNSEN:
> > spot lights in fgfs I had 3 years ago. they worked on vertex program and
> > registercombiners but everyone afraid of vertex programs and
multitexturing
> > You can see some screens here http://fgfs.narod.ru
> > But I work on it and now I have runway lights, landing lights, relief
> > mapping , DXT compression and another cool stuff that work on fragment
and
> > vertex program
> > But fgfs community refuse to use it :(
> > to sad to hear it :((
> > but I have framework to use shaders from VP1.0 to GLSL in fgfs
> > but you have some influence in fgfs community so I think you can do what
I
> > haven't done yet - have flightgear looks better by using some modern
stuff.
> > we can discuss about shaders with you
> > feel free to mail me
> > Thanx in advance
> > Bye
>
>
> Hello Roman, have you any patch which could be applied on fg-9.8
> I guess, it could be a great pleasure to test it.
>
> thank
>
> >
> --
> Gerard
>
>
> _______________________________________________
> 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

Reply via email to