Gijs de Rooy wrote:
> I just pushed a fix
Thanks, looks much better now.
> https://gitorious.org/fg/fgdata/commit/3b92fc9bc0705be6516161fc50781d800d6680c2
As a side note, I'd like to point out that my case wasn't about
overriding "custom" shader settings (as alleged in the comment in
"gui.nas")
Martin,
I just pushed a fix (thanks to Emilian for some great feedback!):
https://gitorious.org/fg/fgdata/commit/3b92fc9bc0705be6516161fc50781d800d6680c2
Use --prop:/sim/rendering/shaders/quality-level=-1 to enable the custom
settings in the Shader Options dialog.
Apart from that the quality-
Hi Martin,
> Actually this slider doesn't override anything, instead it's being
> overridden by the defaults.
It does override the custom settings, whenever the slider is touched. But just
setting
the property via commandline (or anything other than the dialog) was something
I
didn't think o
Martin Spott wrote:
> As far as I can tell there's still a functional gap in the current
> implementation of shader control. When I start FlightGear with:
>
> --prop:/sim/rendering/shaders/quality-level=0
>
> (that's what is controlled by the slider, correct ?) then I still
> get the full
> Martin wrote:
>
> Disabling the shaders requires moving the slider forth and back at
> runtime in order to take effect - that's inconsistent, I'd say ;-)
Ah, good catch. Didn't think of that :P
Will commit a fix this evening, if no-one beats me to it.
Thanks!
Gijs
Gijs de Rooy wrote:
> Next to that there are some typos/faults in current Git with respect to
> shader-properties, so it is possible
> that some shaders are accidentally still enabled. I'm preparing a commit that
> fixes quite some bugs, hope
> to push it today. But you can already test it via
On 12 December 2011 16:48, Gijs de Rooy wrote:
> could it be thre trees? They are now no-longer dependant of the
> Shader/Quality-vs-Performance setting...
This is another way to set FPS limit to about 2 ;-) But it was off
when I was testing.
> to push it today. But you can already test it via
>
Hi,
> The recent shader options revamp seems to put me in the "4 fps" mode even
> though I set everything to minimal.
could it be thre trees? They are now no-longer dependant of the
Shader/Quality-vs-Performance setting...
Next to that there are some typos/faults in current Git with respect t
> I was talking about this on irc before as well. I am testing stuff on
> an older macbook running Ubuntu, and with fg 2.4 I could set the
> "enable shaders" master switch in rendering options to off, and
> without 3d clouds I got about 25fps, which was ok for testing panels
> and developing gauge
9 matches
Mail list logo
