https://imgur.com/a/1aL51iD
I was in vacation for 2 weeks and since I came back I've had this bug occuring everytime, it was working perfectly fine before that despite my mumble version being a little bit old (I have version 1.4.287).
I know that by using the command "-nod3d9ex " in launch options the bug can be fixed but it makes my game lagging and alt-tabbing very long, also causing crashes sometimes.
Any ideas on how to fix this bug without using the launch options command ?
https://imgur.com/a/1aL51iD
I was in vacation for 2 weeks and since I came back I've had this bug occuring everytime, it was working perfectly fine before that despite my mumble version being a little bit old (I have version 1.4.287).
I know that by using the command "-nod3d9ex " in launch options the bug can be fixed but it makes my game lagging and alt-tabbing very long, also causing crashes sometimes.
Any ideas on how to fix this bug without using the launch options command ?
Do you notice your game flashing black when you are loading into the main menu? Do you alt-tab while your game is loading in? Try not alt-tabbing.
From my knowledge, there's three main causes to this:
I) Your game starts at a different DirectX level and loads in a different one when the game fully loads in
II) Your game switches resolution when loading in.
III) You have conflicting graphics settings in your config versus VPK modules in your custom folder.
I) If you haven't refreshed in a while, I would get a new graphics config. Firstly, in any of these steps; make sure to check your autoexec.cfg (if you have one) or config.cfg. If you use Mastercomfig, double check that you followed the instructions for using an autoexec properly because it's different. You can try putting the DirectX level in your launch options:
-dxlevel 90 (or 80 / 81 if you use them instead).
You might need to put it in your config.cfg as well.
II) You can try the same above with resolution. I've had this issue when I used to frequently switch them back and forth. Just changing your resolution or aspect ratio can break the overlay. This problem is even more pronounced for Discord. Ideally, you use your native resolution and aspect ratio of your monitor. The command for your launch options is:
-w # -h #
Ex. -w 1920 -h 1080
III) Check that your config.cfg and autoexec.cfg don't have extra commands that effect your graphics settings that you've put in.
If none of these work you should also run Mumble and Steam in administrator mode to see if it persists. You can also put -safe in your launch options to launch the game in safe mode and see if it yet again, still happens.
Do you notice your game flashing black when you are loading into the main menu? Do you alt-tab while your game is loading in? Try not alt-tabbing.
From my knowledge, there's three main causes to this:
I) Your game starts at a different DirectX level and loads in a different one when the game fully loads in
II) Your game switches resolution when loading in.
III) You have conflicting graphics settings in your config versus VPK modules in your custom folder.
I) If you haven't refreshed in a while, I would get a [url=https://comfig.app/]new graphics config.[/url] Firstly, in any of these steps; make sure to check your autoexec.cfg (if you have one) or config.cfg. If you use Mastercomfig, double check that you followed the instructions for using an autoexec properly because it's different. You can try putting the DirectX level in your launch options:
[i]-dxlevel 90 [/i](or 80 / 81 if you use them instead).
You might need to put it in your config.cfg as well.
II) You can try the same above with resolution. I've had this issue when I used to frequently switch them back and forth. Just changing your resolution or aspect ratio can break the overlay. This problem is even more pronounced for Discord. Ideally, you use your native resolution and aspect ratio of your monitor. The command for your launch options is:
[i]-w # -h #[/i]
Ex. -w 1920 -h 1080
III) Check that your config.cfg and autoexec.cfg don't have extra commands that effect your graphics settings that you've put in.
If none of these work you should also run Mumble and Steam in administrator mode to see if it persists. You can also put -safe in your launch options to launch the game in safe mode and see if it yet again, still happens.
Thanks a lot for your awnser, it helped me fixing the issue!
I tried one by one each steps and nothing worked for me but the step 3 really stuck to my mind and I decided to change the whole cfg/custom folders and use someone else's.
The new folders made the overlay worked and when I switched back to my own files it was working perfectly aswell.
I really think there is a proper solution to find, imo it's about launching the game without any cfg/custom files to "reset" the overlay and what's causing issue with it, then putting back your files without changing a thing and it might works.
edit : I have been told (by zen) that if you have "-dxlevel X" set in your launch options it might cause that issue, also "mat_antialias" set to 1 could be responsible for that issue so try to set it to 0.
Thanks a lot for your awnser, it helped me fixing the issue!
I tried one by one each steps and nothing worked for me but the step 3 really stuck to my mind and I decided to change the whole cfg/custom folders and use someone else's.
The new folders made the overlay worked and when I switched back to my own files it was working perfectly aswell.
I really think there is a proper solution to find, imo it's about launching the game without any cfg/custom files to "reset" the overlay and what's causing issue with it, then putting back your files without changing a thing and it might works.
edit : I have been told (by zen) that if you have "-dxlevel X" set in your launch options it might cause that issue, also "mat_antialias" set to 1 could be responsible for that issue so try to set it to 0.