McGridles Posted December 30, 2015 Share Posted December 30, 2015 1. http://steamcommunity.com/app/346110/discussions/0/594820656447032287/#c530649887215947947 2. http://steamcommunity.com/app/346110/discussions/0/523890681407965271/#c535150948595647419 http://steamcommunity.com/app/346110/discussions/0/523890681407965271/#c535150948595663682 3.https://www.reddit.com/r/playark/comments/3vba1z/how_to_automatically_perform_rbloomquality_0_and/ For much time the community has been pressing tab and typing in 'r.bloomquality 0' and 'r.lightshafts 0' because of the blinding glare in the game which hurt peoples eyes when playing at night. If you are dyslexic you are in for some trouble. There is yet no GUI in game to remedy such a widely used feature which would make for a simple solution. There is no permanent fix and this is currently the only way. I seek for an answer from an official developer if editing the .ini to remove bloomquality and lightshafts is allowed. Keep in mind that these commands are already being used by everybody. Link to comment Share on other sites More sharing options...
Perrin Aybara Posted December 30, 2015 Share Posted December 30, 2015 What does Dyslexia have to do with any of this? Link to comment Share on other sites More sharing options...
Jen Posted December 30, 2015 Share Posted December 30, 2015 Here are some things you can edit to hopefully disable these settings permanetly. Quote Go to folder "\ARK\Engine\Config\" open file "BaseScalabilty.ini" in Notepad++ and modify ALL of the "PostProcessQuality" sections to Change Bloom and Add Lightshaft settings accordingly. Change "r.BloomQuality=2" to "r.BloomQuality=0" Add "r.lightshafts=0" Now these 2 settings will be Off when you start the game and whenever you change graphics in game they will stay off. Quote Folder location: \Steam\steamapps\common\ARK\ShooterGame\Saved\Config\WindowsNoEditor\ Add this anywhere in Engine.ini [SystemSettings] r.DefaultFeature.Bloom=False r.BloomQuality=0 r.LightShafts=0 Add this to Scalability.ini [TextureQuality@1] r.Streaming.PoolSize=1350 [PostProcessQuality@0] r.BloomQuality=0 r.LightShafts=0 r.LightShaftQuality=0 r.LensFlareQuality=0 [PostProcessQuality@1] r.BloomQuality=0 r.LightShafts=0 r.LightShaftQuality=0 r.LensFlareQuality=0 [PostProcessQuality@2] r.BloomQuality=0 r.LightShafts=0 r.LightShaftQuality=0 r.LensFlareQuality=0 [PostProcessQuality@3] r.BloomQuality=0 r.LightShafts=0 r.LightShaftQuality=0 r.LensFlareQuality=0 Link to comment Share on other sites More sharing options...
McGridles Posted December 31, 2015 Author Share Posted December 31, 2015 18 hours ago, Jen said: Here are some things you can edit to hopefully disable these settings permanetly. So it is allowed and will not result in a ban? Link to comment Share on other sites More sharing options...
killasap0 Posted December 31, 2015 Share Posted December 31, 2015 52 minutes ago, McGridles said: So it is allowed and will not result in a ban? I'm PRETTY SURE that's what he's saying since he posted ALL of those OPTIONS..... LOL Link to comment Share on other sites More sharing options...
McGridles Posted December 31, 2015 Author Share Posted December 31, 2015 43 minutes ago, killasap0 said: I'm PRETTY SURE that's what he's saying since he posted ALL of those OPTIONS..... LOL I was just trying to get a direct response. I was pretty sure it was not a bannable offense but people on my server seem to think it is. This would provide them verification of that. Link to comment Share on other sites More sharing options...
Drathek Posted January 4, 2016 Share Posted January 4, 2016 On 12/31/2015 at 11:30 AM, McGridles said: I was just trying to get a direct response. I was pretty sure it was not a bannable offense but people on my server seem to think it is. This would provide them verification of that. VAC is not going to ban you for modifying a setting that the developers have allowed to be configured, nor are you going to be finding a GM enforcing players to use a certain config when playing. In the situation where we may have missed locking down a setting that gives an unfair advantage over other players, then by all means make a thread and discuss it so it can be reviewed. Link to comment Share on other sites More sharing options...
rpicardi1 Posted January 4, 2016 Share Posted January 4, 2016 Currently, bloom can be extremely blinding in the snow on slopes. Link to comment Share on other sites More sharing options...
Toni Posted January 4, 2016 Share Posted January 4, 2016 2 hours ago, Drathek said: VAC is not going to ban you for modifying a setting that the developers have allowed to be configured, nor are you going to be finding a GM enforcing players to use a certain config when playing. In the situation where we may have missed locking down a setting that gives an unfair advantage over other players, then by all means make a thread and discuss it so it can be reviewed. Drathek, please change the default settings for this 2 parameters to 0. Why you should do that? --> Try to build a metal house, put an omni-lamp in this house... and see what happens. Thats the reason why most people do not like it. We do not want to get glared in our own houses Another solution for that: Remove the bloom effects on metal parts Link to comment Share on other sites More sharing options...
BigHead Posted January 4, 2016 Share Posted January 4, 2016 This is why we need a command prompt on xbox..... Link to comment Share on other sites More sharing options...
McGridles Posted January 5, 2016 Author Share Posted January 5, 2016 On 1/4/2016 at 4:52 AM, Drathek said: VAC is not going to ban you for modifying a setting that the developers have allowed to be configured, nor are you going to be finding a GM enforcing players to use a certain config when playing. In the situation where we may have missed locking down a setting that gives an unfair advantage over other players, then by all means make a thread and discuss it so it can be reviewed. That is all I needed to hear. Thank you for the input. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.