MSI Afterburner breaking the Optimus fix doesn't seem to come any sooner

Well... I think the MSI Afterburner breaking the Optimus fix doesn't seem to be coming any sooner for people who install drivers later than 399.24.

I was looking in the Guru3D forum and found this.

Check this out.

https://forums.guru3d.com/threads/m...tes-nvidia-optimus-switching-graphics.423182/

 

That makes it sound like there's no intention of fixing it or it's logistically difficult at least.

 

Does this cause performance issues in game or is the purely battery related when not gaming?

 

Sounds the same to me.

Now quitting the MSI Afterburner or set the iGPU to be the primary GPU when on battery become the only options

It will only affect the battery life as Optimus can't work correctly with the dGPU constantly awake caused by MSI Afterburner.

 

Also makes me think that it's not a universal thing, it's not having that problem on my own machine that I can see, but that's the only machine I have access to with optimus, the one I mostly use AB on has no integrated graphics to switch to.

 

Wow, Unwinder himself showed up in the end of that post. Looks like we will have to wait until he figures it out.

 

So far on the GS65 I'm still seeing this problem with 416.81 (Even Clean version), dGPU consumes around 6.8~7.5W every 2 seconds for 2 seconds long, I've HWINFO64 set to 500ms for the monitoring frequency and launch AB to see this symptom. AB set to use Integrated in both NVIDIA Panel and Windows setup already.

Using 1803 (OS build:17134.376)

Which leaves the idle wattage to stay around 17W~19W on Battery when doing nothing.

So now I'm forced to quit AB and use HWINFO64 for monitoring purpose and nVIDIA Inspector to OC the dGPU on Startup.

Yep the author really said that, I think it'll probably take a while or it is probably never going to be fixed.

 

He needs HW to do the testing and validation, that's why MSI sponsored/employed him to work on MSI AB exclusively. MSI AB is Desktop Platform project but not Notebook Platform so this is probably the reason why.

 

Will probably have to keep that way until official notebook support is added (if it is, considering Unwinder's comments)

 

Good thing that HWINFO64 works well with RTSS

Except not being able to play with the FV curve line, the combo is actually golden.

Edit: Sometimes the nVIDIA Inspector fails to set the clock, but it is fixed after I set it to Windows 7 compatibility mode also increase the delay of the task to 1 minute.

 

Haven't tried that but I might since AB is giving me some unrelated trouble on my desktop.