[FIXED]
The problem seems to be HUD related, and can be "fixed" with a workaround described in #6 by turbochad69. It involves joining with a normal resolution, joining a map and then changing to a lower res with mat_setvideomode. You can also use a lower aspect ratio if you have a height of 640, like in 640x450. The actual solution is probably designing a custom HUD with the conflicting element(s) removed, but that'd take a lot of trial and error and probably result in a bad hud.
----
I wanted to have a lower resolution than 640x480 because I'm horribly bottlenecked by my iGPU and to allow a higher refresh rate for my CRT. However, when I start the game with such a resolution and try to load a map, after the loading screen, it crashes after showing a frame of the 'welcome' text and the map rendered in the background. The main menu works with the intended resolution and I can click whatever I want.
I'm using the -small launch option to allow me to use lower than 640x480 resolutions and mastercomfig with the low preset. I've tried:
- Searching online for anything similar.
- Changing HUDs (flame, m0rehud, yahud, default, etc).
- Verifying the game files.
- Changing mastercomfig to the medium and very-low preset (that disables chat, killfeed, etc).
- Different resolutions (560x412, 576x436 and 624x472).
- Changing to dxlevel 90 or 80.
- Removing all launch options except the necessary ones.
Any pointers to what is going wrong would be appreciated.
[b][FIXED][/b]
The problem seems to be HUD related, and can be "fixed" with a workaround described in #6 by turbochad69. It involves joining with a normal resolution, joining a map and then changing to a lower res with mat_setvideomode. You can also use a lower aspect ratio if you have a height of 640, like in 640x450. The actual solution is probably designing a custom HUD with the conflicting element(s) removed, but that'd take a lot of trial and error and probably result in a bad hud.
----
I wanted to have a lower resolution than 640x480 because I'm horribly bottlenecked by my iGPU and to allow a higher refresh rate for my CRT. However, when I start the game with such a resolution and try to load a map, after the loading screen, it crashes after showing a frame of the 'welcome' text and the map rendered in the background. The main menu works with the intended resolution and I can click whatever I want.
I'm using the -small launch option to allow me to use lower than 640x480 resolutions and mastercomfig with the low preset. I've tried:
- Searching online for anything similar.
- Changing HUDs (flame, m0rehud, yahud, default, etc).
- Verifying the game files.
- Changing mastercomfig to the medium and very-low preset (that disables chat, killfeed, etc).
- Different resolutions (560x412, 576x436 and 624x472).
- Changing to dxlevel 90 or 80.
- Removing all launch options except the necessary ones.
Any pointers to what is going wrong would be appreciated.
propaI'm using the -small launch option
aiera-small launch option
not sure how to help sorry but cmon aiera at least read the post first
[quote=propa]I'm using the -small launch option[/quote]
[quote=aiera]-small launch option[/quote]
not sure how to help sorry but cmon aiera at least read the post first
The issue with the -small command is that it only works on select direct x levels, so you will need to play around with -dxlevel 80 and then work upwards if it doesn't work. Also, the -small command can be overwritten by other gpu related commands and should be placed at both the start and end of launch options.
If it's still crashing try changing your native desktop resolution and using windowed borderless mode.
The issue with the -small command is that it only works on select direct x levels, so you will need to play around with -dxlevel 80 and then work upwards if it doesn't work. Also, the -small command can be overwritten by other gpu related commands and should be placed at both the start and end of launch options.
If it's still crashing try changing your native desktop resolution and using windowed borderless mode.
TheRealWeinerThe issue with the -small command is that it only works on select direct x levels, so you will need to play around with -dxlevel 80 and then work upwards if it doesn't work. Also, the -small command can be overwritten by other gpu related commands and should be placed at both the start and end of launch options.
If it's still crashing try changing your native desktop resolution and using windowed borderless mode.
I'm not sure if you understood well my problem (my bad, probably didn't make it clear enough), but the -small launch option and therefore resolution itself works. The main menu shows and I can click whatever I want. It's only when I try to load a map, and after it finishes loading, that it crashes. I'm changing my native resolution from Windows and letting TF2 auto scale. Also, windowed borderless mode (probably) comes with an input latency problem.
I've tried both dxlevel 80 and 90, as I said, both leading to crashes. After reading your post, I tried to start up a map with only the -small (both at the start and end) and -console options, thinking -small may have a connection to the crash, but to no avail. Still a crash.
I've edited my original post to show this.
[quote=TheRealWeiner]The issue with the -small command is that it only works on select direct x levels, so you will need to play around with -dxlevel 80 and then work upwards if it doesn't work. Also, the -small command can be overwritten by other gpu related commands and should be placed at both the start and end of launch options.
If it's still crashing try changing your native desktop resolution and using windowed borderless mode.[/quote]
I'm not sure if you understood well my problem (my bad, probably didn't make it clear enough), but the -small launch option and therefore resolution itself works. The main menu shows and I can click whatever I want. It's only when I try to load a map, and after it finishes loading, that it crashes. I'm changing my native resolution from Windows and letting TF2 auto scale. Also, windowed borderless mode (probably) comes with an input latency problem.
I've tried both dxlevel 80 and 90, as I said, both leading to crashes. After reading your post, I tried to start up a map with only the -small (both at the start and end) and -console options, thinking -small may have a connection to the crash, but to no avail. Still a crash.
I've edited my original post to show this.
Seems to crash due to some divide by zero when you have the width narrower than 640, I don't know how to fix it but I was able to reproduce the problem if that helps. You can put the height lower than 480 fine, so maybe that works for you (eg. 640x360 or something)
It's definitely a hud-related / hud-adjacent problem, for example if you do cl_drawhud 0 it doesn't crash. It also seems like you can get around the crashes by launching in a normal resolution, joining a map first, and then changing to your small resolution with mat_setvideomode or something, seemingly no crashes after that even when loading a new map or doing hud_reloadscheme. More of a workaround than a solution though. I wasn't able to narrow down what specific part of the hud (if any) is to blame during the short while I spent looking at it.
Seems to crash due to some divide by zero when you have the width narrower than 640, I don't know how to fix it but I was able to reproduce the problem if that helps. You can put the height lower than 480 fine, so maybe that works for you (eg. 640x360 or something)
It's definitely a hud-related / hud-adjacent problem, for example if you do cl_drawhud 0 it doesn't crash. It also seems like you can get around the crashes by launching in a normal resolution, joining a map first, and then changing to your small resolution with mat_setvideomode or something, seemingly no crashes after that even when loading a new map or doing hud_reloadscheme. More of a workaround than a solution though. I wasn't able to narrow down what specific part of the hud (if any) is to blame during the short while I spent looking at it.
turbochad69Seems to crash due to some divide by zero when you have the width narrower than 640, I don't know how to fix it but I was able to reproduce the problem if that helps. You can put the height lower than 480 fine, so maybe that works for you (eg. 640x360 or something)
It's definitely a hud-related / hud-adjacent problem, for example if you do cl_drawhud 0 it doesn't crash. It also seems like you can get around the crashes by launching in a normal resolution, joining a map first, and then changing to your small resolution with mat_setvideomode or something, seemingly no crashes after that even when loading a new map or doing hud_reloadscheme. More of a workaround than a solution though. I wasn't able to narrow down what specific part of the hud (if any) is to blame during the short while I spent looking at it.
Thank you so much! Everything you've said worked in my case. Your "workaround" works especially, and it's not too much of a bother. Seeing as the hud and resolution functions with that method though, I think it isn't totally a hud related problem. Maybe it's an (unfixable) bug within the game that occurs at the first map load with such resolutions.
In regards to using a height lower than 480, while the game doesn't crash like that, it feels quite weird. I could definitely get used to it however. I'll see if I can try anything tomorrow, and if nothing helps, I'll mark the issue as solved. Thanks again.
[quote=turbochad69]Seems to crash due to some divide by zero when you have the width narrower than 640, I don't know how to fix it but I was able to reproduce the problem if that helps. You can put the height lower than 480 fine, so maybe that works for you (eg. 640x360 or something)
It's definitely a hud-related / hud-adjacent problem, for example if you do cl_drawhud 0 it doesn't crash. It also seems like you can get around the crashes by launching in a normal resolution, joining a map first, and then changing to your small resolution with mat_setvideomode or something, seemingly no crashes after that even when loading a new map or doing hud_reloadscheme. More of a workaround than a solution though. I wasn't able to narrow down what specific part of the hud (if any) is to blame during the short while I spent looking at it.[/quote]
Thank you so much! Everything you've said worked in my case. Your "workaround" works especially, and it's not too much of a bother. Seeing as the hud and resolution functions with that method though, I think it isn't totally a hud related problem. Maybe it's an (unfixable) bug within the game that occurs at the first map load with such resolutions.
In regards to using a height lower than 480, while the game doesn't crash like that, it feels quite weird. I could definitely get used to it however. I'll see if I can try anything tomorrow, and if nothing helps, I'll mark the issue as solved. Thanks again.
OFCOURSE YOURE FROM aregentia nothing works there and maybe get a job instead of playing tf2 but even then you cannt afford the gpu because its so shit country with low gdp and wages sorry bro
OFCOURSE YOURE FROM aregentia nothing works there and maybe get a job instead of playing tf2 but even then you cannt afford the gpu because its so shit country with low gdp and wages sorry bro
TheBabaBossOFCOURSE YOURE FROM aregentia nothing works there and maybe get a job instead of playing tf2 but even then you cannt afford the gpu because its so shit country with low gdp and wages sorry bro
argentina #1
[quote=TheBabaBoss]OFCOURSE YOURE FROM aregentia nothing works there and maybe get a job instead of playing tf2 but even then you cannt afford the gpu because its so shit country with low gdp and wages sorry bro[/quote]
argentina #1