> Actually, it would be nice if RenderVolumeLODfactor could either
> persist from one version to the next (instead of getting reset with everey
> new version installation), or be set based on GPU detection.
> I imagine the default of 1.125 is based on "class 0" (intel integrated
>graphics)
> but a
On Sun, 22 Aug 2010 15:26:06 -0700, leliel
wrote:
> On Sun, Aug 22, 2010 at 7:48 AM, Trilo Byte
> wrote:
>> Actually, it would be nice if RenderVolumeLODfactor could either
>> persist from one version to the next (instead of getting reset with
>> everey
>> new version installation), or be set ba
On Sun, Aug 22, 2010 at 3:32 PM, Trilo Byte wrote:
>> That's because you're running into RenderMaxNodeSize.
>
> Thanks, will take a look into that
Be careful with that setting. RenderMaxNodeSize specifies the maximum
amount of vertex data an object can use in kilobytes, the default on
class 2 and
> The default for class 1 and up is 2.0.
I've been on machines meeting/exceeding class 1 for nearly 2 years.
Every single viewer update (at least on Mac OS) *still* reverts to 1.125
>> On a side note, I've found that setting above 6.0 can have unexpected and
>> unwanted results, most notably 'd
On Sun, Aug 22, 2010 at 7:48 AM, Trilo Byte wrote:
> Actually, it would be nice if RenderVolumeLODfactor could either
> persist from one version to the next (instead of getting reset with everey
> new version installation), or be set based on GPU detection.
Put it in the settings_per_account.xml
Actually, it would be nice if RenderVolumeLODfactor could either
persist from one version to the next (instead of getting reset with everey
new version installation), or be set based on GPU detection.
I imagine the default of 1.125 is based on "class 0" (intel integrated graphics)
but anybody usin
