Apparently not...
And I
know from experience, and because I worked for the past 11 years on the viewer code and came to intimately know it, that such high LOD settings got negative (and counterintuitive) effects.
If you push camera settings in the same unreasonable way, I'm not surprised you need to compensate them...
I too have 32Gb RAM, but even then I certainly won't use that setting (it can fill up the RAM in a matter of minutes or even a few dozens of seconds, depending on the sim), especially since it got zero visual impact on actually visible objects (for which the texture LOD is already maxed out, even with that setting off).
Not sure why you mention this here: it's unrelated. As for me not implementing some things, it's my choice. I simply don't need these things and won't loose time implementing them, debugging them, maintaining them. If you want them implemented, then simply provide a working (bug-free) patch of your own brew.
Correction:
entirely for my own use !
No use for me = no motivation to spend time on it = no work done. The equation is pretty straightforward to understand, right ? I develop and maintain this viewer
alone and did it for the past 11 years, on my sparse free time; choices have to be done and I am and will always be the one and only to do them ! Period.
I wrote "should probably", not "shall" neither "will", but if you insist, I will do it, just to teach you a lesson...
What matter most for me are stability and performances. Any thing that might harm those gets eradicated.