so i changed my config from the comanglia toaster config to another config, and for some reason the sides of my screen are glitchy as fuck. in the options it still says my native resolution is 1920 x 1080. i believe the toaster config had something to do with the change in resolution, and now i am using another config, it's glitched
PLEASE HELP :(
https://steamuserimages-a.akamaihd.net/ugc/832451764370128308/7B1338D23CFE6626A5717803C122B3C19F698610/
so i changed my config from the comanglia toaster config to another config, and for some reason the sides of my screen are glitchy as fuck. in the options it still says my native resolution is 1920 x 1080. i believe the toaster config had something to do with the change in resolution, and now i am using another config, it's glitched
PLEASE HELP :(
https://steamuserimages-a.akamaihd.net/ugc/832451764370128308/7B1338D23CFE6626A5717803C122B3C19F698610/
effective. Power
لُلُصّبُلُلصّبُررً ॣ ॣh ॣ ॣ 冗
effective. Power
لُلُصّبُلُلصّبُررً ॣ ॣh ॣ ॣ 冗
campereffective. Power
لُلُصّبُلُلصّبُررً ॣ ॣh ॣ ॣ 冗
my pc is not an apple product god damnit
[quote=camper]effective. Power
لُلُصّبُلُلصّبُررً ॣ ॣh ॣ ॣ 冗[/quote]
my pc is not an apple product god damnit
gotta see the positives, atleast now the hud stuff isnt covering the gameplay :)
gotta see the positives, atleast now the hud stuff isnt covering the gameplay :)
DuMmTmgotta see the positives, atleast now the hud stuff isnt covering the gameplay :)
gotta see the negatives, i have to learn where the "middle of the screen" is
[quote=DuMmTm]gotta see the positives, atleast now the hud stuff isnt covering the gameplay :)[/quote]
gotta see the negatives, i have to learn where the "middle of the screen" is
at least now you got a great frame rate
at least now you got a great frame rate
tl;dr mat_viewportupscale 1, needs to be in the autoexec
the config is using the command "mat_viewportscale <number less than 1>" to decrease the rendered resolution, while keeping the display at 1080p
the viewportupscale command will take this lower-resolution, and, basically, up-scale it!
mat_viewportupscale 0
http://i.imgur.com/JS3fktL.jpg
mat_viewportupscale 1
http://i.imgur.com/kraHGtN.jpg
tl;dr mat_viewportupscale 1, needs to be in the autoexec
the config is using the command "mat_viewportscale <number less than 1>" to decrease the rendered resolution, while keeping the display at 1080p
the viewportupscale command will take this lower-resolution, and, basically, up-scale it!
mat_viewportupscale 0
[img]http://i.imgur.com/JS3fktL.jpg[/img]
mat_viewportupscale 1
[img]http://i.imgur.com/kraHGtN.jpg[/img]
Does this mean your main menu is always open behind your game? If so does closing console do anything?
Does this mean your main menu is always open behind your game? If so does closing console do anything?
damneasyDoes this mean your main menu is always open behind your game? If so does closing console do anything?
it probably is always open, thinking of valve.
inb4 hud that removes menu
[quote=damneasy]Does this mean your main menu is always open behind your game? If so does closing console do anything?[/quote]
it probably is always open, thinking of valve.
inb4 hud that removes menu
r1cetl;dr mat_viewportupscale 1, needs to be in the autoexec
the config is using the command "mat_viewportscale <number less than 1>" to decrease the rendered resolution, while keeping the display at 1080p
the viewportupscale command will take this lower-resolution, and, basically, up-scale it!
mat_viewportupscale 0
http://i.imgur.com/JS3fktL.jpg
mat_viewportupscale 1
http://i.imgur.com/kraHGtN.jpg
this helped ty
[quote=r1ce]tl;dr mat_viewportupscale 1, needs to be in the autoexec
the config is using the command "mat_viewportscale <number less than 1>" to decrease the rendered resolution, while keeping the display at 1080p
the viewportupscale command will take this lower-resolution, and, basically, up-scale it!
mat_viewportupscale 0
[img]http://i.imgur.com/JS3fktL.jpg[/img]
mat_viewportupscale 1
[img]http://i.imgur.com/kraHGtN.jpg[/img][/quote]
this helped ty
r1ceit probably is always open, thinking of valve.
inb4 hud that removes menu
not a source expert but if you open the VGUI tree it does seem to imply that this is true
you can see for yourself with vgui_drawtree so I'm sure someone with better engine knowledge can make sense of it
[quote=r1ce]
it probably is always open, thinking of valve.
inb4 hud that removes menu[/quote]
not a source expert but if you open the VGUI tree it does seem to imply that this is true
you can see for yourself with vgui_drawtree so I'm sure someone with better engine knowledge can make sense of it
how did this happen?
no really someone who knows explain pls
how did this happen?
no really someone who knows explain pls
Spuhow did this happen?
no really someone who knows explain pls
mat_viewportscale says what percentage of the screen the viewport (the view into the 3d world you see) should be sized to. This is always true, but it's mat_viewportupscale that determines how it's drawn to the screen.
mat_viewportupscale 0 says "the viewport only takes up half the screen, well let's just leave the rest blank and forget about it." This is what OP's problem was, he had it set to this.
mat_viewportupscale 1 says "the viewport only takes up half the screen, so let's resize it to fill the rest of the screen" This is what a lot of people complain about with comanglia's toaster cfg, that it makes everything look really blurred.
r1ce does a pretty good job of explaining it.
Mouldr1ceit probably is always open, thinking of valve.
inb4 hud that removes menu
not a source expert but if you open the VGUI tree it does seem to imply that this is true
you can see for yourself with vgui_drawtree so I'm sure someone with better engine knowledge can make sense of it
vgui_drawtree actually seems to suggest the opposite for me. Opening vgui_drawtree outside of the mainmenu shows extremely different components than inside the mainmenu. Though the "show hidden" option crashes tf2 for me and that might reveal something more, I can't say.
What's happening is that the engine is not prepared to redraw parts of the screen that aren't covered by anything, because normally it always should and it'd just make everything laggier if it had to check every time. Even though the mainmenu isn't actually enabled, it's still visible just because nothing actually replaces it and tells the engine to cover it up. If you have something you can drag over the screen (like the vgui_drawtree window) it can end up covering the whole screen, even though there's still only the one instance of it.
Basically, don't go removing your mainmenu hoping it'll help fps, because it probably won't (and if it does, valve fucked up something way weirder than always having the mainmenu enabled).
[quote=Spu]how did this happen?
no really someone who knows explain pls[/quote]
mat_viewportscale says what percentage of the screen the viewport (the view into the 3d world you see) should be sized to. This is always true, but it's mat_viewportupscale that determines how it's drawn to the screen.
mat_viewportupscale 0 says "the viewport only takes up half the screen, well let's just leave the rest blank and forget about it." This is what OP's problem was, he had it set to this.
mat_viewportupscale 1 says "the viewport only takes up half the screen, so let's resize it to fill the rest of the screen" This is what a lot of people complain about with comanglia's toaster cfg, that it makes everything look really blurred.
r1ce does a pretty good job of explaining it.[quote=Mould][quote=r1ce]
it probably is always open, thinking of valve.
inb4 hud that removes menu[/quote]
not a source expert but if you open the VGUI tree it does seem to imply that this is true
you can see for yourself with vgui_drawtree so I'm sure someone with better engine knowledge can make sense of it[/quote]
vgui_drawtree actually seems to suggest the opposite for me. Opening vgui_drawtree outside of the mainmenu shows extremely different components than inside the mainmenu. Though the "show hidden" option crashes tf2 for me and that might reveal something more, I can't say.
What's happening is that the engine is not prepared to redraw parts of the screen that aren't covered by anything, because normally it always should and it'd just make everything laggier if it had to check every time. Even though the mainmenu isn't actually enabled, it's still visible just because nothing actually replaces it and tells the engine to cover it up. If you have something you can drag over the screen (like the vgui_drawtree window) it can end up covering the whole screen, even though there's still only the one instance of it.
Basically, don't go removing your mainmenu hoping it'll help fps, because it probably won't (and if it does, valve fucked up something way weirder than always having the mainmenu enabled).