Just putting this out there. Have found quite a few issues about this but nothing that brought up the laptop/nvidia/integrated/optimus. Then again I could be wrong...there are like a million of them.
This bug will be the death of me (and has been on several occasions by the time I am done with alt+tab, ctrl+enter, or ctrl+alt+del to get my screen back). I have an nvidia card. GTX560M. With all the newest drivers from nvidia. Having a laptop I also have an integrated card built in (No disable option in the BIOS). I have changed all the settings to only use the nvidia card (universally and specifically to the MWO exe's). Nothing seems to make the bug vanish.
I looked over what the Nvidia optimus technology does. It will always (I mean that, ask NVidia, it's a power saving 'feature') use the integrated card until it needs more GPU power then *seamlessly* *cough* adds in the processing of the NVidia card. It would make sense that its swap is when the 'colors' come up. Ususally either during an AS splatcat or getting wailed on by 5000 lasers makes my screen go all trippy. Make sense to anyone else for the timing?
Only manufacturer (Mine is a Toshiba) versions of windows have optimus integrated / forced in.If you do a wipe and just install windows (Not your recovery disc, just plain old windows (7pro, x64 for me)) it seems to remove the integrated / forced optimus configuration. Then you can disable the integrated graphics in windows and only use the NVidia. Across the web this appears to have helped a great deal of laptop using people on various games.
Anyone have any input for this? Tried it and it worked? Tried and didn't work? realistically I shouldn't have to flatline my system just to play a game. If it works I am considering it tho.
1
Kaliedoscope Bug - Optimus
Started by BahamutSin, Apr 10 2013 10:51 AM
1 reply to this topic
#2
-
-
- 1,132 posts
Member
Posted 10 April 2013 - 11:13 AM
http://mwomercs.com/...84#entry2178984
This bug has been identified and addressed, the fix is currently in test and looking good so far. We are beyond the window for hotfixes at this point so it will be included in the next patch.-Matthew Craig
Quote
This bug has been identified and addressed, the fix is currently in test and looking good so far. We are beyond the window for hotfixes at this point so it will be included in the next patch.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
