![is opengl 4.4 still good is opengl 4.4 still good](https://news-cdn.softpedia.com/images/news2/AMD-Catalyst-14-4-Driver-for-Linux-Brings-OpenGL-4-4-Support-a-Year-after-NVIDIA-439735-2.jpg)
Graphics Card: GeForce GTX 560 Ti/PCIe/SSE2, with 1024 MB of memory
#Is opengl 4.4 still good windows 7#
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
![is opengl 4.4 still good is opengl 4.4 still good](https://top10.netflix.com/images/big_numbers/6.png)
When I go to a less busy region the memory usage immediately goes lower.ĬPU: Intel® Core i7-2600K CPU 3.40GHz (3411.19 MHz) lots of objects and lots of textures) the region is the more memory is used by the viewer.
#Is opengl 4.4 still good plus#
from 400 MB to 1005 MB - OS plus Firestorm 4.6.5 (64 bit) viewer running.98 MB - no programs running, just the OS running.And as you said too, video memory is used also to store other data besides the textures.įor GPU memory usage this is what I typically observe in my system: The viewer can and will exceed that cap when it needs to. And it is what Linden Lab calls a soft cap. That's true, as you said in your other post, the max 512 MB is reserved just for the textures. I`ve read somewhere that that is a "soft cap", whatever that means, but I checked what my card was doing a while ago and it peaked at 1010mb memory with just sl running on firestorm. If you haven't gone deeper into fine-tuning other advanced viewer settings that also impact performance, I'd suggest doing so first. in fact, it occurs to me that it may end up having the opposite effect, since less available VRAM would mean having to manage textures in and out of your graphic card's memory more often, which is an additional task the viewer would have to do usually, changing these VRAM settings is done only to prevent texture overload (the viewer quitting or crashing because of too many of them) or “texture trashing” issues, which is damn near an ongoing bug some people have been suffering otherwise, asking the most of your graphics card, rather than capping it, is usually the best strategy to get the most framerates, I think. I also see that you're doing all this to try and get better framerates, but I'm not convinced that capping your max. After changing its value, it's just a question of relogging to make sure it'll be in effect. In this case, for example, if you type just “TextureMemory” (remember, no spaces), only the settings containing that will appear, including the one you want, which is “RenderTextureMemoryMultiple”. Go to the Advanced menu, find the “Debug Settings” option and, on opening it, type in the search box at least part of the name of the setting you're looking for. Sorry for bothering you this long, but where's that setting? I'm with the latest firestormĪll the better, since it's also the one I use.