Gamma and brightness settings does not work if I use my Nvidia GPU, but they do work with the Intel HD one.

[IronPig]

Moving the gamma and the brightness sliders does not do anything if I have set the Nvidia GPU in Nvidia X Server Settings, but they work with the Intel HD GPU. This is very annoying since I think the Intel HD GPU is a lot slower than the Nvidia one so I mostly use later, but if I want to play The Dark Mod (and I want to see the level (the default brightness and gamma is very dark)) I have to switch to the Intel HD GPU. What should I do to make the brightness and the gamma changeable with the Nvidia GPU.

 

I am using Ubuntu 16.04, GeForce 820M/PCIe/SSE2(I guess).

 

[duzenko]

Sounds like a driver bug to me

[IronPig]

And how can I fix that?

[Bikerdude]

Is the driver you have installed atm the latest for that intel GPU?

[teh_saccade]

The newer nvidia drivers are pulling colour profiles, gamma, brightness, etc... from the OS (your desktop settings) and overriding some game and application settings.
Especially those using older game engines, using older directx, glide, opengl, older shader models etc....

Skipped frames, messed up draw distances, hard lights and shadows.

(newer games look great, though...)

You may notice a difference if you switch any affected game between windowed mode and fullscreen mode (alt+enter or menu)..

If there is a some difference between the gamma, brightness and colour between windowed (application profile) and fullscreen (desktop profile) then one workaround is to run in windowed mode and simply strip the border.(metacity / fluxbox --replace), but since you are using ubuntu this will strip all borders from all windows...

The other option is to force the settings for the whole machine, using the nvidia software, to ensure the colour range - more important, the colour profile (ICC) - is correct [for your monitor] and is set to full.
Also calibrate monitor, probably have to use gnome colour manager (gnome-settings-daemon) / xiccd also.

Many older games have had this issue lately (not ones from the 90's, however...) - if you were using windows, it would be easier to fix. Windowed mode and border-stripper does the trick.

You might try to roll back to driver 23.21.13.8813 (388.13, not 388.31 or whatever it is now).

 

Or force the game to change its brightness and gamma settings by editing the config files (set to read-only to prevent over-write).


Don't forget there is likely a brightness function for your display for fine tuning.


Unfortunately - games from the dx9ish era are starting to show many issues with graphics, physics and scripting as more and more Call of Duty / Assassin's Creed / Tom Clancy's: Shovelware is released and OS and hardware drivers focus on superficialities such as FPS and realistic, open-world. free-roam, VR, cinematic boob-bounce physx more than supporting enjoyable game-play - because that's what gaming is now: Tits bouncing at 4k, 120FPS, displayed on a TV (that likely max's 30FPS).

I believe the TDM team have recently discovered why some games are capped at 30-32/60FPS for physics sake, while trying to squeeze more FPS out of a 59.94hz display on a laptop with an intel on-board graphics card...

Incidentally - The Hobbit was filmed at 48FPS and some people complained it was too lifelike and broke their suspension of disbelief:
https://www.facebook.com/notes/peter-jackson/48-frames-per-second/10150222861171558
Most movies are 30FPS.


Anyway - try setting the brightness and gamma using the config files in the TDM directory - trial and error ought to do it. The GUI isn't playing nice with the nvidia drivers.

Progress.

[teh_saccade]

TL:DR - change the gamma and brightness in the config files, found in your TDM directory, if the sliders are not working..

[lowenz]

820M? Mobile GPU on a mobile system?

[lowenz]

 

Unfortunately - games from the dx9ish era are starting to show many issues with graphics, physics and scripting as more and more Call of Duty / Assassin's Creed / Tom Clancy's: Shovelware is released and OS and hardware drivers focus on superficialities such as FPS and realistic, open-world. free-roam, VR, cinematic boob-bounce physx more than supporting enjoyable game-play - because that's what gaming is now: Tits bouncing at 4k, 120FPS, displayed on a TV (that likely max's 30FPS).

DX9 code but using Shader Model 1.1/1.4 (DX8).

For old DX1->8 titles the solution is dgVoodoo2 http://dege.freeweb.hu/dgVoodoo2/dgVoodoo2.html

 

Join us to help the development/testing! http://www.vogons.org/viewforum.php?f=59

Edited January 30, 2018 by lowenz

[teh_saccade]

Did consider the gog or guru3d sweetfx community fixers, but unfortunately the guy is using ubunteww - idk if this would work without a windows vm, in which case - why use ubuntu on a lower-spec machine to run slow win vmware instead of simply use separate windows installation or win with linux vmware..?

820M is the "mobile" version, discrete gpu for laptops and notebooks (nvidia for desktop, amd for notebook, imo), yes.
Maybe 3-4 years old now. Think an over/hotclocked version of one of the 500M series. Is ok for older applications if locked to max performance.

Can't hackintosh it, as there's no way to use discrete gpu on hackintosh laptop.

Linux is not what i'd consider a gaming platform (except for playstation, kinda...).
Most "linux games" are simply run using Wine packaged, to make up for not having windows.

https://www.theverge.com/circuitbreaker/2017/1/26/14402028/wine-2-0-update-windows-apps-linux-mac-not-an-emulator

Perhaps there would be some way to work with guru3d or voodoo because of this. Idk. Not tainting Kali or Mint with games to find out.
Would be easier to get a win xp or win 7 iso and install that as primary os.

Never understood the rationale behind using ubuntu, other than too cheap to buy and/or too moral to pirate mainstream OS.

Edited January 31, 2018 by teh_saccade

[duzenko]

2.07 should have shader-level gamma control if you can wait till then

[teh_saccade]

Interestingly, I found a strange fix for my older DX games not displaying colours / brightness / gamma correctly in fullscreen...

I installed STALKER - Lost Alpha: Director's Edition (remake of STALKER: Shadow of Cherobyl) and actually bothered to go through with all the redist. crap.
http://www.moddb.com/mods/lost-alpha

(sound's a bit messed up in places, few bugs - but it's a nice remake if you like the 2007 budget bin feel for a 2003 game. Still not as good as Call of Pripyat [w/Complete mod], but fun enough).

After the DX installation packaged, seems some older games are "fixed"...

TDM looks the same as it did before now...

(it was either that or BSOD on NTFS.sys followed by a win10 update - I don't believe it was a BSOD... it was deferring the update for so long. I never asked for this.)

No idea what has changed.