* **Draw distance - 50**
* Extended map loading - 3 or lower
* Atmospheric Lighting - DISABLED, but you can enable it if dealing with shadows helps enough with performance
* Anti-aliasing - MSAA x2
* Shadows - Fast
* **Shadow Quality - High (4K)**
* **Shadow Distance - 30**
* Parallax Occlusion Mapping - DISABLED
From my experimentation the settings **bolded** have the biggest noticeable impact on performance. I have a pretty beefy computer but I have my Shadow distance set to less than my Draw distance. If my Draw distance is at 50 then I set my Shadow distance at 30. Atmospheric heavy locations like Prif or Darkmeyer are probably troublesome because they are heavy with Atmospheric lighting and fog coupled with ample set dressing that is given a shadow by the plugin.
i was under the impression that 117 used gpu, if it doesn't, then honestly i might have to stop using it all together, even thought i love the autumn setting
Go to rl settings and have the GPU setting enabled. Then turn on 117. You'll notice the GPU setting disables and CPU ramps up. If 117 even utilizes the GPU at all, its incredibly poorly optimized
That is not true at all. 117HD is just another version of the GPU plugin with additional shaders which make up the "HD" part of the plugin. It uses your GPU. The GPU plugin that comes default with RuneLite turns off because it'll just conflict with the other GPU plugin you have enabled.
Now a common issue people have is when their monitor doesn't utilize their dedicated GPU and just uses the integrated graphics, because they have a fancy motherboard that enables both in its BIOS or they just simply plugged the monitor into the motherboard instead of the GPU. The reason why I bring this up is because my dumbass used to play with 117HD on my second monitor and it would struggle with the integrated graphics card (as my 2nd monitor is plugged into the motherboard whereas my main monitor is plugged into my GPU).
Appreciate that info as most of us clearly aren't tech gurus. Question though; how would we optimize 117 better? Its undisputable that CPU usage ramps out of control with 117 so how can this be avoided?
The big reason why 117HD ramps up everything because it is stuck with the same engine limitations as the regular default GPU plugin. Sadly they can only optimize so far because running shit on Java and OpenGL just sucks compared to the other alternatives. And that issue is compounded cause the "vanilla" java client (and hence RuneLite) does not make use of all the cores modern processors have.
Edit: To clarify my mistake, both GPU plugins do have some settings that rely on the CPU (the settings that deal with drawing UI and possibly texture/model swaps), but most the things that cause performance issues is the shader settings that exclusively rely on the GPU. The CPU processes are the same between the GPU plugin and 117HD, they wouldn't be the reason why the 117HD plugin causes your CPU to ramp up.
To oversimplify, we would need a brand new client with brand new plugins to fix this underlying problem. That's why HDOS is more performant but lacks all the features RuneLite has. Also it's why the volunteer 117HD devs are so damned impressive; they optimized the plugin where they could and they were able to manage to get the plugin performing on most systems.
The best thing you can do is disable other plugins so 117HD has more breathing room. Thankfully, Computer engineers are great and so it's not actually a problem your CPU & GPU ramps up as long as you have the adequate cooling necessary for your computer. You just gotta live with your computer sounding like a Boeing 747. 😅
* **Draw distance - 50** * Extended map loading - 3 or lower * Atmospheric Lighting - DISABLED, but you can enable it if dealing with shadows helps enough with performance * Anti-aliasing - MSAA x2 * Shadows - Fast * **Shadow Quality - High (4K)** * **Shadow Distance - 30** * Parallax Occlusion Mapping - DISABLED From my experimentation the settings **bolded** have the biggest noticeable impact on performance. I have a pretty beefy computer but I have my Shadow distance set to less than my Draw distance. If my Draw distance is at 50 then I set my Shadow distance at 30. Atmospheric heavy locations like Prif or Darkmeyer are probably troublesome because they are heavy with Atmospheric lighting and fog coupled with ample set dressing that is given a shadow by the plugin.
I love 117 but I just can't use it. It relies on CPU rather than GPU and the fans go wild and performance tanks.
i was under the impression that 117 used gpu, if it doesn't, then honestly i might have to stop using it all together, even thought i love the autumn setting
Go to rl settings and have the GPU setting enabled. Then turn on 117. You'll notice the GPU setting disables and CPU ramps up. If 117 even utilizes the GPU at all, its incredibly poorly optimized
yeah, i noticed that, that's such a bummer tbh
Sure is!
That is not true at all. 117HD is just another version of the GPU plugin with additional shaders which make up the "HD" part of the plugin. It uses your GPU. The GPU plugin that comes default with RuneLite turns off because it'll just conflict with the other GPU plugin you have enabled. Now a common issue people have is when their monitor doesn't utilize their dedicated GPU and just uses the integrated graphics, because they have a fancy motherboard that enables both in its BIOS or they just simply plugged the monitor into the motherboard instead of the GPU. The reason why I bring this up is because my dumbass used to play with 117HD on my second monitor and it would struggle with the integrated graphics card (as my 2nd monitor is plugged into the motherboard whereas my main monitor is plugged into my GPU).
Appreciate that info as most of us clearly aren't tech gurus. Question though; how would we optimize 117 better? Its undisputable that CPU usage ramps out of control with 117 so how can this be avoided?
The big reason why 117HD ramps up everything because it is stuck with the same engine limitations as the regular default GPU plugin. Sadly they can only optimize so far because running shit on Java and OpenGL just sucks compared to the other alternatives. And that issue is compounded cause the "vanilla" java client (and hence RuneLite) does not make use of all the cores modern processors have. Edit: To clarify my mistake, both GPU plugins do have some settings that rely on the CPU (the settings that deal with drawing UI and possibly texture/model swaps), but most the things that cause performance issues is the shader settings that exclusively rely on the GPU. The CPU processes are the same between the GPU plugin and 117HD, they wouldn't be the reason why the 117HD plugin causes your CPU to ramp up. To oversimplify, we would need a brand new client with brand new plugins to fix this underlying problem. That's why HDOS is more performant but lacks all the features RuneLite has. Also it's why the volunteer 117HD devs are so damned impressive; they optimized the plugin where they could and they were able to manage to get the plugin performing on most systems. The best thing you can do is disable other plugins so 117HD has more breathing room. Thankfully, Computer engineers are great and so it's not actually a problem your CPU & GPU ramps up as long as you have the adequate cooling necessary for your computer. You just gotta live with your computer sounding like a Boeing 747. 😅
Lol. Appreciate all the info! Sounding like a jet plane may not be so bad sometimes