> On 4 Apr 2012, at 17:00, Frederic Bouvier wrote: > > > Thank you James, > > > > Can you push that to gitorious ? > > Done. > > Looking at the language docs, 'varying' in a fragment shader really > is a synonym for 'in', and hence, it makes sense (to me) that > assignment to an input is disallowed. > > But I'm curious, if *no one* else saw this issue, how tolerant most > drivers are. So far I have the impression my drivers (that's Ati / > Apple) are: > > - strict about the language compared to nVidia (or fglrx? or Ati > Windows?) > - have lower limits than other people's hardware / platforms > - aren't very up to date! (in terms of supported GLSL version) > > Taken together, this does *not* make me happy - but so long as we can > find a solution to each problem....
It was part of a "fix" I pushed late yesterday night. My NVidia driver didn't protest though. Thank you for finding this and for the debugging help. Regards, -Fred ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
