https://clips.twitch.tv/RichExquisiteConsoleChocolateRain
e: s'd
Account Details | |
---|---|
SteamID64 | 76561198088600319 |
SteamID3 | [U:1:128334591] |
SteamID32 | STEAM_0:1:64167295 |
Country | France |
Signed Up | August 4, 2014 |
Last Posted | January 9, 2021 at 8:19 PM |
Posts | 173 (0.1 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
you could try adding the "-console" launch option so the console is always opened when you launch the game
McCantsI'm Really, really sorry for necroing this topic.
But I'm trying to set custom sizes for the crosshairs
What variables do I have to add, or change in the weapon files?
Thanks in advance for helping
Just use the cl_crosshair_scale command in your various class configs to adjust every crosshair to its desired size
springrolls That is... really weird. Just to make sure, the problem fixes itself when you delete the vpk? And is it all offline maps or just a few? Maybe try verifying your game files to see if there's anything weird happening?
very weird indeed, the new vpk was the only thing that had changed and I therefore thought it caused the crashes but now that I launch the game everything work flawlessly, even with offline maps; thks for the tips anyway
Been experiencing crashes everytime I launch an offline map although it seems to work flawlessly on any online server with the new "Stock headsfeet" version, not sure what might be causing that or if I'm the only one in that case
creeprootFixed an issue where values computed from server bounded ConVars could be incorrect on the client and therefore possibly exploitable
this is the only thing in the update notes that could point to anything but i have no clue about the implications
https://www.teamfortress.tv/56919/tf2-update-for-8-21-20
its all explained here
mastercomsRemove -dxlevel 91 -full -w 1920 -h 1080
So you recommend setting the resolution through the game and let it remember it every launch ?
+ how useful is the dxlevel launch option versus setting it in an autoexec with mat_dxlevel 91 or are they different ?
raduOut of that list, I think I had -nouserclip -softparticlesdefaultoff, if you determine that the issue is not from the headsfeet vpk I would try and remove "disable_d3d9_hacks" and "cl_clean_texture" (besides the 2 I mentioned at the beginning of the sentence) since I don't see how the other ones would cause this.
After testing, sadly, removing all my vpks did not fix it, neither did removing a lot of launch options - I'm down to this :
-dxlevel 91 -full -w 1920 -h 1080 -freq 144 -console -novid -nojoy -nosteamcontroller -nohltv -particles 1 -nostartupsound
kordyansorry for jacking the thread, what's that?
Hogosakialso sorry about derailing the thread but what are -noff, -nouserclip, -usetcp -disable_d3d9_hacks, -NoQueuedPacketThread?
Alright so my launch options are all from a mix between comanglia's config and mastercoms' recommandations - newer and often better explained. So since I forgot what each of them actually do, I'd recommend going over mastercoms' config or asking her directly (lots of it is also explained here but you'd have to find the right pages and the thread is very long.
e: on mastercoms' website, there's a launch options dedicated sections https://docs.mastercomfig.com/en/latest/customization/launch_options/ So for instance, you have
-nouserclip : uses software clipping instead of hardware user clip planes, FPS increase or decrease depends on your CPU+GPU and graphics API
yerbwhen i used a lot of vpks this would happen, are u using any?
Depends on how you define "a lot" but yes good catch bc I think this is only happening since I updated my headsfeet vpk to the newest 7.3.20 version (I use 5 vpks), I'll test that later.
raduI also had this issue, for me it was from some more uncommon launch options, I would try removing those first.
Do you know which ones specifically may cause the issue ? I tryed removing some of them bc they were either seemingly useless or outdated. I currently have this :
-dxlevel 91 -novid -full -w 1920 -h 1080 -console -nojoy -noff -nohltv -nouserclip -softparticlesdefaultoff -reuse -usetcp -nostartupsound -primarysound -snoforceformat -nosteamcontroller -disable_d3d9_hacks -NoQueuedPacketThread +cl_clean_texture
hey,
so a couple days ago when launching TF2, I noticed that every ALT +TAB I did resulted in a seemingly random chance of getting a weird contrasty image when I tabbed back in tf2 (instead of my usual bright TF2 - I use mat_monitorgamma 1.6 aka the brightest for better visibility). To fix the issue, I have to tab out then back into the game a random number of times before the colors get back to normal. Using the latest nvidia drivers and windows update, everything is up to date and my monitor doesnt have auto brightness or anything like that. I tryed to record screeshots to showcase the issue and have a way to compare but the various programms I tried to capture footage (screenshots or video) never represent what I actually see. So I only have this which is an accurate representation of that annoying constrasty look I'm getting. I'm sure everyone knows that a bright tf2 never looks anything like that.
Any ideas on how to fix it ?
Anyone knows how to make the killfeed look like this please ? Using m0rehud and try to tweak it through the "HudDeathNotice" in HudLayout.res but could only make it either normal or completly blank ...
Hypnotize
You absolutly nailed it, working flawlessly now (with the Shift + 1-9 quick class loadout selection too). Ty so much ! :)