#Blitz resets League of Legends graphical settings to medium preset

22 messages · Page 1 of 1 (latest)

keen ether
#

I just noticed that the Blitz application will reset my League of Legends graphical settings back to medium on each game round.
It also removes the FPS cap in the process, resulting in glitching (like Champ teleportation) due to too high FPS.

This means, that I have to re-set my FPS cap EACH GAME (!), otherwise the game will be unplayable.

This problem only occurs, while Blitz is running. Quitting Blitz will let me keep my graphical settings for future matches.

Running the Troubleshooter application and applying all fixes did nothing regarding solving this problem.

Windows 10 22H2 (Build 19045.2965)
Blitz 2.1.38
League of Legends Game Version 13.10.5098402+branch.releases-13-10.code.public.content.release
League of Legends Client Version 13.10.510.5878

umbral edge
#

Why do you think it’s blitz?

#

I don’t think blitz has access to leagues settings?

keen ether
#

Literally quitting Blitz solves the issue.

If Blitz is not running, the settings get saved correctly.
If Blitz is running, the settings get reset each game.

I don't know why. But that's how it is.

What I did:

  1. Start Blitz
  2. Start a custom game
  3. Settings are set to medium
  4. Set settings to very high and set FPS cap
  5. Exit game
  6. Start new custom game
  7. Settings are automatically set to medium again.
  8. Exit game
  9. Quit Blitz
  10. Start custom game
  11. Game settings are still set to medium
  12. Set game settings back to very high with FPS cap
  13. Exit game
  14. Start new custom game
  15. Graphic settings are still at very high and FPS cap is still set
umbral edge
autumn goblet
#

@trail needle

trail needle
#

Thanks, sorry about this Rico, we'll look into it.

Ku could you help me get logs for this, not sure if they'll help but maybe.

autumn goblet
#

@keen ether when possible, can you click the ingame feedback button, and write a small description regarding the issue, we'll be taking care of it :)

keen ether
#

I'm attaching the Blitz logs as well here.

I quit Blitz, emptied the logfile, started a custom game and set my graphics settings to very high.
Then I exited the game, started Blitz again and entered another new custom game (where the settings were set back to medium).

So this log should be as "clean" as possible while still containing any information regarding the issue.

📎 app.log
autumn goblet
keen ether
autumn goblet
#

Cheers, will forward to devs

stuck estuary
#

A temporary fix that worked for me, was to make the files game.cfg and PersistedSettings.json read-only.

They are found wherever you installed League. Usually in your C drive. C:\Riot Games\League of Legends\Config

Went into a custom game, let the bug happen. Fix my settings, go out of the game. Locate the files, turn on read-only. Start a new custom game, settings should be the same as before.

Somehow, afterwards, you can turn read-only off again and the settings won't default.

umbral edge
#

Strange

errant fog
stuck estuary
#

I turned it off quite literally right after to test if it would revert.
But you can essentially just keep it read-only, unless you make changes to ingame settings quite often.

autumn goblet
#

@errant fog @stuck estuary would both of you be able to also click the Send Feedback button so we can make an investigation case out of it

stuck estuary
keen ether
errant fog
autumn goblet
#

ty ty