profile
viewpoint

mastercomfig/team-comtress-2 544

Team Fortress 2, but with a lot of fixes, QoL improvements and performance optimizations!

roninopf/tf2basehud 30

Team Fortress 2's original/basic HUD. Use this to customize your own.

Yttrium-tYcLief/Scrotter 17

A VB.NET application for placing screenshots into frames of various mobile devices, with a vast library of phones and tablets across multiple platforms.

Yttrium-tYcLief/yayahud 14

Yet Another Yahud

Yttrium-tYcLief/CompVMInstaller 11

Installer for yttrium's Competitive TF2 Viewmodels.

takram/takyahud 10

Updated version of a more classic yahud

Yttrium-tYcLief/CompetitiveViewmodels 4

A set of competitive (hidden) viewmodels for TF2

Yttrium-tYcLief/RUUE01HD 3

Animal Crossing: City Folk HD Project

Yttrium-tYcLief/guides 2

A /g/uide for ricing phones

Yttrium-tYcLief/appchan-x 0

The most comprehensive, feature filled 4chan userscript.

issue commentmastercomfig/team-comtress-2

Auto delete custom gameserver files by exiting tf2

You want to re-download 400mb of meme files every time you connect to a custom server?

BensonMaDude

comment created time in an hour

issue closedmastercomfig/team-comtress-2

Demos recorded on TC2 0.0.16 cannot be played back on stock TF2, but a demo recorded on 0.0.9 works

Describe the bug Demos made in TC2 0.0.16 cannot be played back on TF2. However, a demo recorded on 0.0.9~0.0.10 works.

How you encountered the issue I recorded a demo on TC2 0.0.16 and tried playing it back on a stock download of TF2

Additional Information I've tried recording demos on TC2 with different contents, and tried playing them back on stock TF2 and on the pre_jungleinferno_demos beta branch; The demos used for testing were:

  • dustbowl_no_bots.dem (just spectating with no bots playing)
  • dustbowl_no_action.dem (server full of bots but no action, that is, no fire, no shooting and no gibs. the whole demo was recorded during the setup time)
  • dustbowl_action.dem (a section of a normal bot versus bot)
  • upward_no_bots.dem
  • upward_no_action.dem
  • upward_action

here are the demos: demos.zip

All of the demos were met with the same behavior on stock TF2, the game attempts to load the demo, then quits to the main menu, showing errors in the console: console_stock.log

Same goes for the beta branch, but the game instead crashes with this warning: image There are also different errors in the console: console_pre_jungleinferno_demos_branch.log

however, a demo made by @fiend#3938 on the discord around version 0.0.9 or 0.0.10 does play normally on stock tf2 and on the beta branch. Here it is: dustbowlbench.zip

I think it is important to retain demo compatibility so we can demonstrate the increase in performance in a controlled test, and demos are the best way to do that.

Desktop (please complete the following information):

  • Team Comtress version (don't say latest, say the actual version): 0.0.16
  • Custom content (if any): none (I've made sure to delete every custom config or content, even steam's cloud backup)
  • DX level: default (no launch options)
  • Launch options: none except for -condebug so I can have the log
  • Operating system (OS): Microsoft Windows 10 Pro N 10.0.18363 Build 18363
  • Graphics card (GPU): NVIDIA GeForce GTX 1660 SUPER
  • Graphics driver version: 26.21.14.4587
  • Processor (CPU): AMD Ryzen 5 3600 6-Core Processor, 3593 Mhz, 6 Core(s), 12 Logical Processor(s)
  • TC2 on HDD or SSD: HDD
  • Memory (RAM) size in MB or GB: 16GB

closed time in 11 hours

Kenajcrap

push eventmastercomfig/team-comtress-2

Yttrium tYcLief

commit sha c0c9f376c2c0e7a94c6c863c446856d79b9a63c0

partially revert 1037853 to fix demo loading

view details

push time in 12 hours

issue commentmastercomfig/team-comtress-2

CEngineTraceClient::GetWorldCollideable Assertion Failed

Might be fixed with the threading fixes coming to 0.0.18.

SizzlingCalamari

comment created time in 14 hours

issue closedmastercomfig/team-comtress-2

Mat_phong 0

Mat_phong 0 broke a lot of MVM textures and I'd really love to finally see them fixed in normal casual servers. I don't really know a lot about TF2 code so sorry if there isn't a huge notepad file here. I'd really love to finally get this fixed tho.

23413223112332121232132312321323123123123

Also posted a link to a mod that fixes it (only in servers that allow it) to see if this will help in any way. https://gamebanana.com/skins/138140

closed time in 19 hours

PaPaSoulzune

issue commentmastercomfig/team-comtress-2

Mat_phong 0

This is an asset problem and not a game code problem, so is out-of-scope, unfortunately. However, you did report it at agrastiOs/Ultimate-TF2-Visual-Fix-Pack#17 , which is the proper place for this kind of report.

PaPaSoulzune

comment created time in 19 hours

issue commentmastercomfig/team-comtress-2

SourceTV 32bit eye angles

Sometimes I see issues crop up in Source that make me roll my eyes... like, of course that's a problem.

iBoonie

comment created time in 19 hours

issue commentmastercomfig/team-comtress-2

Stuck in ground after spawn or trimping

This happened to me in CSGO a few times. Turns out people can still shoot you.

It's a client graphics problem; your hitbox still renders properly on the server.

Melonenyoshi

comment created time in 19 hours

issue closedmastercomfig/team-comtress-2

1. A feature that allows you to disable hats and other cosmetic particles 2. Medals having their own slots

Description

  1. Have the option to disable seeing hats based on what slot they are on. There are currently 3 slots for cosmetics. Lets say I want to keep on one hat. I just turn off #2, #3 slots and leave #1 on. Second option would be disabling weapon skins, hat paints and particle effects from unusuals, killstreak and cosmetics (Eks: Shellmet's and Soldier's Stogie's smoke effect). It would be nice to reduce smoke from soldiers rockets.

  2. Medals feels rather more and more insignificant and yet new competitive ones are added nearly every second month. A slot 3 slot similar for cosmetics dedicated for medals would really be great. Also there should be an option to disable them too.

All this could be placed in to advanced options. This is inspired by Funke's youtube video: "What Team Fortress 2 NEEDS"

Checklist

<!-- You do not have to answer "yes" to all of these to suggest an idea -->

  • [ ] None of the open or closed issues document this idea.
  • [ ] This is a new idea, not a bug.
  • [yes ] This idea does not seriously affect game balance.
  • [ ] This idea is for the code of the game, not for textures, sounds, or other resources.
  • [ ] This is not an idea for new game content (e.g. new weapons, maps, sounds).
  • [yes ] This is obviously an improvement, not something that people commonly disagree on.

<!-- You do not have to answer "yes" to any of these, this is just additional context -->

  • [ ] This idea has been implemented in vanilla TF2.
  • [ ] There is proof that this idea is well liked (e.g. a history of use of a similar mod in a competitive league).
  • [ yes] This idea has been implemented in a mod. <!-- Insert link -->
  • [ ] This feature has existed in the vanilla game but was removed.
  • [ ] This idea is for internal procedures or tooling (e.g. improving the build process, supporting new systems).

Screenshots

<!-- Add screenshots to help explain your idea -->

Alternatives

<!-- Alternative implementations of this idea --> 1.

closed time in 19 hours

BensonMaDude

issue commentmastercomfig/team-comtress-2

1. A feature that allows you to disable hats and other cosmetic particles 2. Medals having their own slots

First off, please only file one feature request/bug per issue report.

Have the option to disable seeing hats based on what slot they are on. There are currently 3 slots for cosmetics. Lets say I want to keep on one hat. I just turn off #2, #3 slots and leave #1 on.

As far as I'm aware, slot information is not actually provided to the client, but is also irrelevant as you can equip any cosmetic in any slot. Do you really just want to hide items based on their equip slot, I.E. what region they actually attach to (permit hats, but not pants, etc)?

Second option would be disabling weapon skins

This is already implemented in TC2.

hat paints and particle effects from unusuals, killstreak and cosmetics (Eks: Shellmet's and Soldier's Stogie's smoke effect)

This would likely not happen for consistency reasons. It's important to make all clients render the same thing, within reason.

It would be nice to reduce smoke from soldiers rockets.

This is literally a balance concern and is out-of-scope.

Medals feels rather more and more insignificant and yet new competitive ones are added nearly every second month. A slot 3 slot similar for cosmetics dedicated for medals would really be great. Also there should be an option to disable them too.

This is an item schema issue, not just a game client one, and it also requires major UI work, so is therefore out-of-scope.

It's important to remember that Team Comtress 2 is not a new vision for the game going forward - it is literally only focused on bugfixing and performance, with minor QoL additions that are not controversial.

BensonMaDude

comment created time in 19 hours

issue commentmastercomfig/team-comtress-2

Display Strange / Stat Clock Kill Count on HUD (like CS:GO)

I assume by this you mean implement it in VGUI but leave HUD devs to put it directly into the UI? or just making something like a convar?

The former. We don't touch game assets, including HUD files, so we couldn't actually implement it in the in-game HUD, but we could expose variables that HUD devs could use in labels, a la killstreaks. If this project got picked up by Valve, then obviously we could go ahead and implement it in the default HUD as well, but that second part is currently out-of-scope.

AzureAzel

comment created time in 2 days

issue commentmastercomfig/team-comtress-2

Chat/Menu will become unclickable or closable, can result in getting stuck in MOTD

I think TC2 just straight-up needs more playtesting to spot this, but if it happens now in vanilla than it exists in TC2 (unless it's a regression).

Considering the vast number of UI changes that happened in Jungle Inferno, it is not at all impossible for this to be an issue that only arose after TC2, hence my question.

Jarfeh

comment created time in 2 days

issue commentmastercomfig/team-comtress-2

Add version_comtress command

Whatever you think is the best way to approach it, I have no problems. I just want to make sure we discern build versions from release versions.

micwoj92

comment created time in 3 days

issue commentmastercomfig/team-comtress-2

Add version_comtress command

Any implementation of this should also, ideally:

  1. Modify start_tf2.bat to include +version_comtress or whatever command is eventually used
  2. Include "dev" versus "release" variables, so that version_comtress only reports an actual release number if it's the public release build, built by Mastercoms, and just reports "debug" and a build timestamp otherwise
  3. Implement this string as a variable that can be pulled by UI elements on the main menu, so that we can add a version indicator to the custom HUD
micwoj92

comment created time in 3 days

issue commentmastercomfig/team-comtress-2

Add a Comtress version indicator

I'll expand #33 to cover this as well.

GoodOldJack12

comment created time in 3 days

issue commentmastercomfig/team-comtress-2

Display Strange / Stat Clock Kill Count on HUD (like CS:GO)

We could definitely make this available in code, but an actual UI implementation would be out-of-scope, at least for now.

AzureAzel

comment created time in 3 days

issue closedmastercomfig/team-comtress-2

Add a Comtress version indicator

Description

There should be a way to identify which released version of the patch is currently installed. This should, in my opinion, be done with a simple text file in the root TF2 directory. Optionally a small text in the main menu.

This is useful to verify if a bug report isn't from an older version by accident.

Checklist

<!-- You do not have to answer "yes" to all of these to suggest an idea -->

  • [x] None of the open or closed issues document this idea.
  • [x] This is a new idea, not a bug.
  • [x] This idea does not seriously affect game balance.
  • [ ] This idea is for the code of the game, not for textures, sounds, or other resources.
  • [x] This is not an idea for new game content (e.g. new weapons, maps, sounds).
  • [x] This is obviously an improvement, not something that people commonly disagree on.

<!-- You do not have to answer "yes" to any of these, this is just additional context -->

  • [ ] This idea has been implemented in vanilla TF2.
  • [ ] There is proof that this idea is well liked (e.g. a history of use of a similar mod in a competitive league).
  • [ ] This idea has been implemented in a mod. <!-- Insert link -->
  • [ ] This feature has existed in the vanilla game but was removed.
  • [x] This idea is for internal procedures or tooling (e.g. improving the build process, supporting new systems).

Screenshots

<!-- Add screenshots to help explain your idea --> N/A

Alternatives

<!-- Alternative implementations of this idea --> N/A

closed time in 3 days

GoodOldJack12

issue commentmastercomfig/team-comtress-2

Add a Comtress version indicator

Duplicate of #33

GoodOldJack12

comment created time in 3 days

pull request commentmastercomfig/team-comtress-2

Add support for F13-F24 buttons

Agreed, this PR is not ready for merging yet, I simply posted it in the hopes that someone could help troubleshoot since my knowledge is super limited.

Totally fine! Was just making sure that stance is firm so nobody else merges it either.

treacherousfiend

comment created time in 3 days

issue commentmastercomfig/team-comtress-2

Windows Defender automatically quarantines tier0.dll

I'll look into improving documentation tomorrow.

woow101

comment created time in 3 days

issue closedmastercomfig/team-comtress-2

Disable auto-balance towards the end of a round.

Description

The auto-balance system should be coded in such a way that makes it disable towards the end of a match. The cut off point for this can be debated, but in casual as it currently stands you can be auto-balanced in overtime. No matter your score, no matter how much you contributed to the team.

It's so blatantly broken to the point the announcer can call "Victory" and play the victory music whilst the player is in humiliation because they got auto-balanced in the last possible second. The purpose of a late auto-balance serves no function anyway, as the majority of the time the end of the round results in a team scramble anyway.

It seems this idea has already been posted in the Official TF2 GitHub. The feature existed but was later removed for unknown reasons. https://github.com/ValveSoftware/Source-1-Games/issues/2602

Feb 2008: Changed team autobalance code to not balance the teams when the active round timer shows less than 60 seconds. https://wiki.teamfortress.com/wiki/February_28,_2008_Patch

I think personally it should be more than 60 seconds, but that's just me.

Checklist

<!-- You do not have to answer "yes" to all of these to suggest an idea -->

  • [x] None of the open or closed issues document this idea.
  • [x] This is a new idea, not a bug.
  • [ ] This idea does not seriously affect game balance.
  • [x] This idea is for the code of the game, not for textures, sounds, or other resources.
  • [x] This is not an idea for new game content (e.g. new weapons, maps, sounds).
  • [x] This is obviously an improvement, not something that people commonly disagree on.

<!-- You do not have to answer "yes" to any of these, this is just additional context -->

  • [X] This idea has been implemented in vanilla TF2.
  • [x] There is proof that this idea is well liked (e.g. a history of use of a similar mod in a competitive league).
  • [ ] This idea has been implemented in a mod. <!-- Insert link -->
  • [x] This feature has existed in the vanilla game but was removed.
  • [ ] This idea is for internal procedures or tooling (e.g. improving the build process, supporting new systems).

Screenshots / Video

https://www.youtube.com/watch?v=Bc7j0mrbKvc&ab_channel=Alibi

closed time in 3 days

AgentAlibi

issue commentmastercomfig/team-comtress-2

Disable auto-balance towards the end of a round.

This idea is definitely too far outside of the current project scope, at least for now.

I'll tag it with revisit in case we expand later.

AgentAlibi

comment created time in 3 days

pull request commentmastercomfig/team-comtress-2

Create FUNDING.yml

Good idea, but since this affects her directly, I'll let @mastercoms approve/merge it.

Margen67

comment created time in 3 days

pull request commentmastercomfig/team-comtress-2

Add support for F13-F24 buttons

Currently the F13-F24 buttons only work when the console is open, suggestions to fix this would be very nice

This definitely needs to be addressed before I'd feel comfortable merging this.

treacherousfiend

comment created time in 3 days

issue closedmastercomfig/team-comtress-2

Overly Shiny Ham Shank

Description

<!-- A clear and concise description of what the bug is --> the porkrind on the ham shank is polished-aluminium shiny

Checklist

<!-- You do not have to answer "yes" to all of these to open an issue -->

  • [x] None of the open or closed issues document this problem.
  • [x] This is a bug, not a new idea.
  • [x] This is objectively a bug, and not something that people commonly disagree on.
  • [idk ngl] This bug is in the code of the game, not in the textures, sounds, or other resources.
  • [ ] This issue occurs on the latest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [x] This issue occurs with DirectX level 100.
  • [x] This issue occurs on the latest Team Comtress release, or the master branch.
  • [huds and killsounds only] This issue occurs when using no custom content.
  • [x] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options.
  • [x] This issue occurs when using a listen server (using the map command ingame).
  • [ ] This issue occurs when using a dedicated server.
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process).

Reproduction

<!-- The steps to recreate the bug. Bugs that cannot be recreated are extremely unlikely to receive a fix -->

  1. buy ham shank
  2. equip hand shank
  3. ???
  4. profit

Screenshots

<!-- Add screenshots to help explain your problem --> https://drive.google.com/file/d/1xT_1jFyEsE3XVsTJtYb7NqLFZohBN5oN/view?usp=sharing

Setup Details

  • Server or client: <!-- Did you observe this issue from the game client, or by running a dedicated server? -->client
  • Operating system: <!-- Specify a version e.g. Windows 10, Mac OS X Catalina, or uname -rv output -->windows 10 enterprise
  • Team Comtress version: <!-- Release version number or commit id -->0.0.17
  • Custom content: <!-- Any 3rd-party content, including config files -->tf2hudplus, premium upgrade hud for machine attacks, optivex sounds, consistent kill icons
  • Launch options: <!-- If not using start_tf2.bat, specify a list of options --> <!-- For graphics-related issues: -->
  • Graphics driver: <!-- Specify a version. This is especially important on Linux -->radeon adrenalin 20.8.3
  • DirectX level: <!-- This will be different if you set dxlevel in vanilla TF2 -->100

Performance Details

<!-- Fill this out for performance-related issues -->

  • GPU model: <!-- Example: NVIDIA GTX 2070 Super -->
  • CPU model: <!-- Example: AMD RYZEN 3600X -->
  • RAM amount: <!-- Example: 32GB -->
  • TF2 installed on: <!-- HDD or SSD. Leave empty if not yet tested with vanilla TF2 -->
  • TC2 installed on: <!-- HDD or SSD -->
  • TC2 installation method: <!-- Basic or Advanced (if you do not know what this means, put Basic) -->

closed time in 4 days

InfernoSuperNova

issue commentmastercomfig/team-comtress-2

Overly Shiny Ham Shank

You likely have leftover config data. Try re-reading the installation instructions in the readme; we updated it today with better instructions regarding Steam Cloud.

InfernoSuperNova

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Overly Shiny Ham Shank

its a launch option that just makes TF2 remove the current config file and make a new default one

Not entirely accurate. It basically ignores your config for that session. It won't overwrite anything in it, but it also won't read anything from it.

It's a way to ensure that if you have lingering config data, like from a graphics config you used on live TF2 that got copied from Steam Cloud Sync, it's completely ignored.

InfernoSuperNova

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Overly Shiny Ham Shank

I'm asking you to try using -default to see if it fixes it.

InfernoSuperNova

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Overly Shiny Ham Shank

Does this bug occur if you start the game with the -default launch option?

InfernoSuperNova

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Overly Shiny Ham Shank

Are you using a graphics config?

InfernoSuperNova

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Windows Defender automatically quarantines tier0.dll

this sort of thing has been discussed in discord repeatedly; it's most likely just a heuristic detection, because it sees a modified version of a file that differs from the one that 99% of users have, so it flags it as suspicious and its default behavior towards suspicious files is to call them malicious. This is a common problem in the development world, and unfortunately there's not much we can do about it besides submit the file to Microsoft so that it gets certified as clean and doesn't get flagged again, which we've already done, but they're being awfully slow about it.

I'm going to leave this issue open so others can see it and not make duplicate issues, at least until we hear back from MS.

woow101

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Bots getting stuck in comp maps

As a collaborator I can view your raw comment. The only content you put inside of comment brackets was "Play any comp map with a bot", from what I can see.

Regardless, I didn't close this because of submission issues, just because the bug, while definitely being problematic, is 100% out of scope currently.

MysticTutor

comment created time in 4 days

pull request commentmastercomfig/team-comtress-2

Re-enable special robot headshot/backstab animations

They were implemented and simply disabled for some reason. I'm going to see about stress-testing these, in case there's an actual valid reason for them to have been disabled.

Thestickman391

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Dynamic shadows sometimes show on the wrong side of walls

Yeah no, this is definitely a bugfix and within scope, but is going to require a lot of effort to fix.

henke37

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Use steam audio for sound system like CSGO does

TF2 used a steam-based system until 2016, when it switched to CELT. CELT is also used in both Dota 2 and CSGO, to this date, as far as I'm aware.

CSGO enabled things like positional audio, but I don't think those fit TF2 really.

FriskTheFallenHuman

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

set $raytracesphere to 0 on any eye_refract material

Can anyone document what this shader actually does (looks like), exactly where it's used, and how much of a performance hit it provides?

Xephobia

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Add support for more mouse buttons

Implementing Mouse6-Mouse9 as well as F13-F24 would be ideal, for the full range of macro capability.

henriquecm

comment created time in 4 days

pull request commentmastercomfig/team-comtress-2

Disable zombie souls for sentry busters

I'm normally opposed to hacky solutions but honestly this one seems fine to me.

Thestickman391

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Loading window covers top dual list on Mac

This is a bug, not an enhancement. I've updated your description to fit the proper bug template. Please fill it out with further information before we can address this.

MysticTutor

comment created time in 4 days

issue closedmastercomfig/team-comtress-2

Vote on class of bot in comp

Description

<!----> If a team in competitive is give a bot the team should be able to vote on what class that bot should be.

Checklist

<!-- You do not have to answer "yes" to all of these to suggest an idea -->

  • [x] None of the open or closed issues document this idea.
  • [x] This is a new idea, not a bug.
  • [x] This idea does not seriously affect game balance.
  • [x] This idea is for the code of the game, not for textures, sounds, or other resources.
  • [ ] This is not an idea for new game content (e.g. new weapons, maps, sounds).
  • [x] This is obviously an improvement, not something that people commonly disagree on.

<!-- You do not have to answer "yes" to any of these, this is just additional context -->

  • [ ] This idea has been implemented in vanilla TF2.
  • [ ] There is proof that this idea is well liked (e.g. a history of use of a similar mod in a competitive league).
  • [ ] This idea has been implemented in a mod. <!-- Insert link -->
  • [ ] This feature has existed in the vanilla game but was removed.
  • [ ] This idea is for internal procedures or tooling (e.g. improving the build process, supporting new systems).

Screenshots

<!-- Add screenshots to help explain your idea -->

Alternatives

<!-- Alternative implementations of this idea --> 1.

closed time in 4 days

MysticTutor

issue commentmastercomfig/team-comtress-2

Vote on class of bot in comp

There is competitive, as it was introduced in Meet Your Match, but the competitive code received a major overhaul in Blue Moon, and this is likely out of scope anyway.

It's a neat feature request but not really the kind of thing this project is focused on. May revisit in the future, though, if our scope expands.

MysticTutor

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Re-enable Soldier vs Demoman domination lines

This might fall outside of scope, I'd wait to hear from @mastercoms before we go further.

joshuadinada

comment created time in 4 days

issue closedmastercomfig/team-comtress-2

Current Installation instructions do not take into account possible issues with Steam Cloud Sync

Description

If you have Cloud Sync enabled and follow the current instructions, the original TF2 config.cfg that got deleted during the installation will be restored in TC2 when it is first launched, which, depending on the user's TF2 config, may cause crashes or other weird problems, and also will make troubleshooting harder since the user would not be wrong to affirm with 100% certainty he deleted his config.cfg like instructed. This leads to even worse problems if the user does turn cloud sync off before launching TC2 for the first time but turns it back on later on, which would either update TF2's config.cfg or TC2's config.cfg depending on in which order he plays the different versions after cloud sync is turned back on, leading to a lot of confusion and aggravation if an unaware player loses his TF2 config "because of TC2" (not actually tc2's fault) The short term solution would be to include instructions to disable cloud sync and keep it disabled while they have TC2 "installed". But I feel like this is the kind of instruction that will get ignored (because they think they know better) or be forgotten by users after a while.

Checklist

<!-- You do not have to answer "yes" to all of these to suggest an idea -->

  • [x] None of the open or closed issues document this idea.

Alternatives

<!-- Alternative implementations of this idea -->

  1. Finding a way to check if cloud sync is enabled for TF2 and preventing TC2 from launching if it is
  2. Finding a way to disable cloud sync entirely for TC2 but keep it enabled when launching TF2

NOTE: My initial theory (that was shared by some others on discord) was that TC2 had cloud sync disabled but for some reason it was enabled only on the first launch, I tested many scenarios and that doesn't seem to be the case. TC2 follows TF2's cloud configuration and behavior normally. I can expand on that if it is pertinent to do so.

closed time in 4 days

Kenajcrap

issue closedmastercomfig/team-comtress-2

Add warning about being careful to not delete tf\custom\tc2 during instalation

Description

<!-- A clear and concise description of what the idea is --> There were at least 2 players that I know of this week that had problems with the basic installation because they tried to launch TC2 while keeping their customization in tf\custom\ then when that didn't work, deleted the whole custom folder without noticing that pastinggame_clean.zip had put a new folder there. While the installation instructions are completely correct and very clear, never giving the impression you should do things in the reverse order, there will always be people trying stupid stuff and its important to account for that.

Checklist

<!-- You do not have to answer "yes" to all of these to suggest an idea -->

  • [x] None of the open or closed issues document this idea.

Alternatives

<!-- Alternative implementations of this idea -->

  1. Renaming tf\custom\tc2 something more noticeable
  2. Adding a check for it in start_tf2.bat

closed time in 4 days

Kenajcrap

issue commentmastercomfig/team-comtress-2

Being backstabbed as a Sniper with crit resistance with the razorback multiplies your current health by 200%

Sometimes this game amazes me.

Keep in mind backstabs do 200% of the total current health in damage; somewhere in the resistance calculation, the number is becoming negative, and then being blown way out of proportion thanks to the 200% scale. More info about this is on the wiki. We'll need to find out where the resistance causes this to go negative.

Thestickman391

comment created time in 4 days

push eventmastercomfig/team-comtress-2

Kenajcrap

commit sha d59d9330abe229efa6bc9193092421146201067d

Basic Installation Instrucions Improvements: warning about custom/tc2 and instructions to disable steam sync (#302) * warning about custom/tc2 and Steam Sync * fix punctuation Co-authored-by: BuildTools <unconfigured@null.spigotmc.org>

view details

push time in 4 days

PR merged mastercomfig/team-comtress-2

Basic Installation Instrucions Improvements: warning about custom/tc2 and instructions to disable steam sync documentation

Related Issue

<!-- Number of the issue where this bug was filed --> #295 and #296

Implementation

<!-- A clear and concise description of what the changes are --> The warning was added as a note and disabling steam sync as an extra step

Checklist

<!-- You do not have to answer "yes" to all of these to open a pull request -->

  • [x] This PR targets the master branch.
  • [x] This change has been filed as an issue.
  • [x] No other PRs address this.
  • [x] This PR is as minimal as possible.
  • [x] This PR does not introduce any regressions.

Caveats

<!-- Any caveats and side effects of this PR --> While the warning should stay, the extra step is a short term arrangement to prevent confusion while a better way of handling the problem is created. Please, discuss long term options like the ones mentioned in the open issues

Alternatives

<!-- Alternatives that were considered --> alternatives are cited in #295 and #296

+4 -2

0 comment

1 changed file

Kenajcrap

pr closed time in 4 days

issue closedmastercomfig/team-comtress-2

Bug with recording

When you try to record on a tf2 server (all servers even custom) You will not be able to record so you would have to use a different software. <!-- You do not have to answer "yes" to all of these to open an issue -->

  • [ ] None of the open or closed issues document this problem.
  • [ yes] This is a bug, not a new idea.
  • [ ] This is objectively a bug, and not something that people commonly disagree on.
  • [ ] This bug is in the code of the game, not in the textures, sounds, or other resources.
  • [ yes] This issue occurs on the latest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [ ] This issue occurs with DirectX level 100.
  • [ ] This issue occurs on the latest Team Comtress release, or the master branch.
  • [yes ] This issue occurs when using no custom content.
  • [ ] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options.
  • [ ] This issue occurs when using a listen server (using the map command ingame).
  • [ ] This issue occurs when using a dedicated server.
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process).

closed time in 4 days

daze725

issue commentmastercomfig/team-comtress-2

Bug with recording

He likely means recording a demo, in which case this is a duplicate of #191.

I'm going to close this as a duplicate; if this isn't a duplicate, it can be reopened once a better description is given.

daze725

comment created time in 4 days

pull request commentmastercomfig/team-comtress-2

Set tf_forced_holiday based on EventPopfile

I see nothing wrong with this addition as long as it's tested before being merged.

Thestickman391

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Quick FrameView Performace Comparison

Agree with the close. further discussion should take place on discord

Kenajcrap

comment created time in 4 days

issue commentmastercomfig/team-comtress-2

Cancel reloading while taunting

It's a weird behavior to be sure, but not really an exploit or anything. Doesn't give you an advantage over other players.

As for whether it should be changed (to disable reloading during taunting), it's a very gray area. I honestly don't have an opinion one way or the other on it, and generally we don't do changes just for the sake of doing them. I'm gunna leave this up to @mastercoms.

joshuadinada

comment created time in 5 days

issue closedmastercomfig/team-comtress-2

Bots getting stuck in comp maps

Description

<!-- There are a number of spot in the different competitive maps where the bots get stuck. Like in the second spawn of Granary, the shutter in Badwater, the red spawn on snakewater, etc. etc.

All the comp maps should be reworked so bots do not get stuck anywhere. -->

Checklist

<!-- You do not have to answer "yes" to all of these to open an issue -->

  • [x] None of the open or closed issues document this problem.
  • [x] This is a bug, not a new idea.
  • [x] This is objectively a bug, and not something that people commonly disagree on.
  • [ ] This bug is in the code of the game, not in the textures, sounds, or other resources.
  • [x] This issue occurs on the latest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [ ] This issue occurs with DirectX level 100.
  • [ ] This issue occurs on the latest Team Comtress release, or the master branch.
  • [x] This issue occurs when using no custom content.
  • [ ] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options.
  • [ ] This issue occurs when using a listen server (using the map command ingame).
  • [ ] This issue occurs when using a dedicated server.
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process).

Reproduction

<!-- Play any comp map with a bot --> 1.

Screenshots

<!-- Add screenshots to help explain your problem -->

Setup Details

  • Server or client: <!-- Did you observe this issue from the game client, or by running a dedicated server? -->
  • Operating system: <!-- Specify a version e.g. Windows 10, Mac OS X Catalina, or uname -rv output -->
  • Team Comtress version: <!-- Release version number or commit id -->
  • Custom content: <!-- Any 3rd-party content, including config files -->
  • Launch options: <!-- If not using start_tf2.bat, specify a list of options --> <!-- For graphics-related issues: -->
  • Graphics driver: <!-- Specify a version. This is especially important on Linux -->
  • DirectX level: <!-- This will be different if you set dxlevel in vanilla TF2 -->

Performance Details

<!-- Fill this out for performance-related issues -->

  • GPU model: <!-- Example: NVIDIA GTX 2070 Super -->
  • CPU model: <!-- Example: AMD RYZEN 3600X -->
  • RAM amount: <!-- Example: 32GB -->
  • TF2 installed on: <!-- HDD or SSD -->
  • TC2 installed on: <!-- HDD or SSD. Leave empty if not tested with TC2 -->
  • TC2 installation method: <!-- Basic or Advanced (if you do not know what this means, put Basic) -->

closed time in 6 days

MysticTutor

issue commentmastercomfig/team-comtress-2

Bots getting stuck in comp maps

map issues are definitely out of scope unless it's a problem with the actual AI system, but this sounds like navmeshes, yeah.

MysticTutor

comment created time in 6 days

issue closedmastercomfig/team-comtress-2

Pressing "N" while ingame causes severe rendering problems.

Description

Whenever I press "N", which according to my keyboard settings, is bound to "Take Steam Abuse Screenshot" severe rendering glitches occur. Both with the 3D geometry, and the UI.

Checklist

<!-- You do not have to answer "yes" to all of these to open an issue -->

  • [x] None of the open or closed issues document this problem.
  • [x] This is a bug, not a new idea.
  • [x] This is objectively a bug, and not something that people commonly disagree on.
  • [x] This bug is in the code of the game, not in the textures, sounds, or other resources.
  • [ ] This issue occurs on the latest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [ ] This issue occurs with DirectX level 100.
  • [x] This issue occurs on the latest Team Comtress release, or the master branch.
  • [x] This issue occurs when using no custom content.
  • [x] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options.
  • [x] This issue occurs when using a listen server (using the map command ingame).
  • [ ] This issue occurs when using a dedicated server.
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process).

Reproduction

  1. Enter 2Fort (I used map ctf_2fort)
  2. Press "N".

Note: If this doesn't happen for you, check that your keybinding for "N" is the same as mine "Take Steam Abuse Screenshot".

Screenshots

Image

Setup Details

  • Server or client: Client
  • Operating system: Windows 10
  • Team Comtress version: a360bec
  • Custom content: None
  • Launch options: Just tf2.bat <!-- For graphics-related issues: -->
  • Graphics driver: Nvidia 446.14
  • DirectX level: 98

Performance Details

  • GPU model: NVIDIA GTX 2070 Super
  • CPU model: Intel Core i7-4790k
  • RAM amount: 16GB
  • TF2 installed on:
  • TC2 installed on: Hybrid
  • TC2 installation method: Advanced

closed time in 6 days

Zionner

issue commentmastercomfig/team-comtress-2

Pressing "N" while ingame causes severe rendering problems.

Duplicate of #246.

Zionner

comment created time in 6 days

pull request commentmastercomfig/team-comtress-2

Fix ubercharge canteen running out cancelling Mmmpf taunt uber

I feel like this is so messy it might introduce a bunch of other bugs. Can anyone test it?

Thestickman391

comment created time in 7 days

CommitCommentEvent

issue closedmastercomfig/team-comtress-2

Change icon of hl2.exe

Is your feature request related to a problem? Please describe. I'm always frustrated when I look at TC2 executable and it looks like half life

Describe the solution you'd like Change default icon to some variation of mastercomfig logo

Describe alternatives you've considered Change default icon to mastercomfig logo

Additional context I know i can just change in windows, I'm just lazy.

closed time in 7 days

micwoj92

issue commentmastercomfig/team-comtress-2

Change icon of hl2.exe

We aren't going to be changing the executable icon, but I heavily appreciate the SVG logo, and I'm sure we'll find a use for it.

micwoj92

comment created time in 7 days

issue closedmastercomfig/team-comtress-2

Mount via gameinfo.txt to prevent copying 28 gb game

Is your feature request related to a problem? Please describe. Mounting would be great because copying an entire 28GB game is not nice

Describe the solution you'd like Posibility to mount tf2 games files for team comtress 2

Describe alternatives you've considered i have copied the gameinfo.txt from the tffolder of my tf2 install and copyed it on the tf folder of team comtress 2, i modyfied it so anything pointing to a tf2 vpk file would point to a vpk file of my tf2 install, hoewer it did nothing when trying to launch with start_tf2.bat or hl2.exe

closed time in 7 days

Xephobia

issue commentmastercomfig/team-comtress-2

Mount via gameinfo.txt to prevent copying 28 gb game

We might revisit this in the future, but for now we're going to stick with duplicate game files, for ease of development and debugging.

Xephobia

comment created time in 7 days

issue closedmastercomfig/team-comtress-2

Fire glitch

Sometimes some pyro weapons can shoot through walls.

closed time in 7 days

eggeggy1

issue commentmastercomfig/team-comtress-2

Fire glitch

Resubmit using the proper template.

eggeggy1

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

Heavy hit box

Resubmit using the proper template.

eggeggy1

comment created time in 7 days

issue closedmastercomfig/team-comtress-2

Heavy hit box

If your body is near the heavy as a spy you can phase inside it and you cant backstab them.

closed time in 7 days

eggeggy1

issue openedmastercomfig/team-comtress-2

[MVM] Firing Speed upgrades not working properly on automatic weapons

Description

Minigun upgrades in MvM are not what they should be. Thought to be fixed in 279a541 (0.0.7), but is not actually fixed as of 0.0.17. However, 279a541 did apparently modify the overall DPS numbers. Most notably, Firing Speed 2 seems to do nothing, both pre and post 279a541.

Live TF2:

Heavy Stock Minigun:
0 firing speed: 124 DPS (100% total; this should be 100%) 115
1 firing speed: 144 DPS (116% total; this should be 110%) 133
2 firing speed: 144 DPS (116% total; this should be 120%) 133
3 firing speed: 172 DPS (139% total; this should be 130%) 160
4 firing speed: 208 DPS (168% total; this should be 140%) 200

TC2 0.0.17:

Heavy Stock Minigun:
0 firing speed: 115 DPS
1 firing speed: 133 DPS
2 firing speed: 133 DPS
3 firing speed: 160 DPS
4 firing speed: 200 DPS

This bug also affects the Syringe Gun (and various other automatic weapons).

Syringe gun:
0 firing speed: 104 DPS
1 firing speed: 122 DPS
2 firing speed: 122 DPS
3 firing speed: 146 DPS
4 firing speed: 182 DPS 

Checklist

<!-- You do not have to answer "yes" to all of these to open an issue -->

  • [x] None of the open or closed issues document this problem.
  • [x] This is a bug, not a new idea.
  • [x] This is objectively a bug, and not something that people commonly disagree on.
  • [x] This bug is in the code of the game, not in the textures, sounds, or other resources.
  • [x] This issue occurs on the latest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [x] This issue occurs with DirectX level 100.
  • [x] This issue occurs on the latest Team Comtress release, or the master branch.
  • [x] This issue occurs when using no custom content.
  • [x] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options.
  • [x] This issue occurs when using a listen server (using the map command ingame).
  • [x] This issue occurs when using a dedicated server.
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process).

Reproduction

  1. Shoot a tank, measure with tf_damagemeter 1.

Setup Details

  • Server or client: 0.0.17
  • Operating system: Windows 10
  • Team Comtress version: 0.0.17
  • Custom content: none
  • Launch options: start_tf2.bat
  • Graphics driver: 452.06 WHQL
  • DirectX level: 9.0

Performance Details

<!-- Fill this out for performance-related issues -->

  • GPU model: GTX 1080
  • CPU model: i7 5930k
  • RAM amount: 32GB
  • TF2 installed on: SSD
  • TC2 installed on: SSD
  • TC2 installation method: Advanced

created time in 7 days

issue commentmastercomfig/team-comtress-2

[MVM] Huntsman bugs

Can confirm ingame. Also affects Rescue Ranger and Crusader's Crossbow. Doesn't happen when walking backwards.

DrCactusTF2

comment created time in 7 days

issue closedmastercomfig/team-comtress-2

Unable to call for help/medic

Description

<!-- A clear and concise description of what the bug is --> Ingame, if you press the button to call MEDIC!, nothing will happend. I tried binding it to diffrent keys with no result. I also tried adding a medic bot to my team, yet still nothing happend.

Checklist

<!-- You do not have to answer "yes" to all of these to open an issue -->

  • [x] None of the open or closed issues document this problem.
  • [x] This is a bug, not a new idea.
  • [x] This is objectively a bug, and not something that people commonly disagree on.
  • [x] This bug is in the code of the game, not in the textures, sounds, or other resources.
  • [ ] This issue occurs on the latest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [ ] This issue occurs with DirectX level 100.
  • [x] This issue occurs on the latest Team Comtress release, or the master branch.
  • [x] This issue occurs when using no custom content.
  • [x] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options.
  • [x] This issue occurs when using a listen server (using the map command ingame).
  • [ ] This issue occurs when using a dedicated server.
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process).

Reproduction

<!-- The steps to recreate the bug. Bugs that cannot be recreated are extremely unlikely to receive a fix -->

  1. Go in a match and press "e"

Setup Details

  • Server or client: <!-- Did you observe this issue from the game client, or by running a dedicated server? --> Client.
  • Operating system: <!-- Specify a version e.g. Windows 10, Mac OS X Catalina, or uname -rv output --> Windows 10
  • Team Comtress version: <!-- Release version number or commit id --> 0.0.17
  • Custom content: <!-- Any 3rd-party content, including config files --> None.
  • Launch options: <!-- If not using start_tf2.bat, specify a list of options --> None.
  • DirectX level: <!-- This will be different if you set dxlevel in vanilla TF2 --> 90

closed time in 7 days

joshuadinada

push eventmastercomfig/team-comtress-2

Yttrium tYcLief

commit sha e2baa097b50a180bc67e0a38ce24e9695d259a4f

update new readme to fix newline issues

view details

push time in 7 days

push eventmastercomfig/team-comtress-2

Yttrium tYcLief

commit sha 43a27c54c4144fca859227d9040bc6504390c2bf

Update README to better describe the project (#154)

view details

push time in 7 days

PR merged mastercomfig/team-comtress-2

Update README to better describe the project documentation rfc

Definitely open to critique here.

+62 -94

21 comments

1 changed file

Yttrium-tYcLief

pr closed time in 7 days

pull request commentmastercomfig/team-comtress-2

Update README to better describe the project

I'm going to go ahead any push this forward. We can revise it later if need be, but I think it's in a pretty good state now.

Yttrium-tYcLief

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

Unable to call for help/medic

fixed over discord, was related to persistent config files from live tf2 installation

for users experiencing this: run the game with -default, then type host_writeconfig ingame, then close the game and delete any tf/cfg/autoexec.cfg you might have.

joshuadinada

comment created time in 7 days

issue openedmastercomfig/team-comtress-2

Medigun (and Kritzkrieg) heal sounds not working

Description

Self-explanatory. #212 does not seem to have fixed this problem.

Checklist

<!-- You do not have to answer "yes" to all of these to open an issue -->

  • [x] None of the open or closed issues document this problem.
  • [x] This is a bug, not a new idea.
  • [x] This is objectively a bug, and not something that people commonly disagree on.
  • [x] This bug is in the code of the game, not in the textures, sounds, or other resources.
  • [ ] This issue occurs on the latest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [x] This issue occurs with DirectX level 100.
  • [x] This issue occurs on the latest Team Comtress release, or the master branch.
  • [x] This issue occurs when using no custom content.
  • [x] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options.
  • [x] This issue occurs when using a listen server (using the map command ingame).
  • [x] This issue occurs when using a dedicated server.
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process).

Reproduction

  1. heal a target lmao

Setup Details

  • Server or client: 0.0.17
  • Operating system: Windows 10
  • Team Comtress version: 0.0.17
  • Custom content: none
  • Launch options: start_tf2.bat
  • Graphics driver: 452.06 WHQL
  • DirectX level: 9.0

Performance Details

<!-- Fill this out for performance-related issues -->

  • GPU model: GTX 1080
  • CPU model: i7 5930k
  • RAM amount: 32GB
  • TF2 installed on: SSD
  • TC2 installed on: SSD
  • TC2 installation method: Advanced

created time in 7 days

issue commentmastercomfig/team-comtress-2

[MVM] Mphhh ubercharge canceling

This is sort of an unintentional design flaw due to how conditions work in TF2. I've discussed this on a similar issue somewhere, can't find it right now, but essentially conditions don't have their timers reset when being re-applied. You can't have multiple overlapping conditions; a real uber being applied to an mmph'ing pyro will overwrite their original mmph uber with the real one, and then the uber will run out when the uber would normally run out, which means you can simply flash a pyro to completely cancel out their uber invulnerability.

joshuadinada

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

[TC2] Giant Robots are using human body sizes

I don't think I understand this issue. What is the intended behavior?

Giants have scaled-up bodies, but normal sized heads. They don't use separate models; they simply use the original models with a scale factor (of like 3x) applied to their root bone, and then a scale on bip_head to bring it back down to normal size. My guess is we somehow broke that in TC2.

DrCactusTF2

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

[MVM] Huntsman bugs

Damage is improperly rounded

Have you confirmed this in TC2? We've fixed numerous damage rounding errors, and have mostly fixed all of the MvM issues relating to it (especially the minigun).

or fire them while ubered

Is this really as blatant as it sounds? An ubered Sniper's arrows will not penetrate, regardless of upgrades?

DrCactusTF2

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

Resizing causes game crash.

No worries, glad you got it sorted.

joshuadinada

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

Sapper bug and class selection animation

There has been a fix made for the choppy class animations by ficool2: https://steamcommunity.com/sharedfiles/filedetails/?id=2153744818

While this is a separate issue from the sapper one, and should be in its own issue, I'll briefly address it.

Looking at the description of that submission, it seems there are 4 key issues. I won't bother repeating them all here, but issue 1 has to do with the HUD elements themselves, which we are intentionally staying away from with this project. Issue 2 (sound) is a legitimate game code issue that we could address. Issue 3 is an animation issue with game assets, which we don't touch. Issue 4 is likely a code issue, but may or may not get fixed by Valve, and there unfortunately isn't enough information in that short description to tell us what's going on there.

condor00fr

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

Resizing causes game crash.

By "resize" do you mean change the game resolution, or literally clicking and dragging on the window?

joshuadinada

comment created time in 7 days

push eventYttrium-tYcLief/team-comtress-2

Yttrium tYcLief

commit sha b6de296065a14917917743801bd16a798fddfc82

issue report wording tweak

view details

push time in 7 days

pull request commentmastercomfig/team-comtress-2

Fixed README.md to tell people to build with C++17

We're actually in the process of redoing the readme.md, and it won't include build instructions directly in the readme anymore. Instead it will point to a wiki page for build instructions. I've gone ahead and added your changes to said wiki page.

For the record, the C++17 change was implemented in 0.0.17, so it is a fairly new thing.

higgy999

comment created time in 7 days

GollumEvent

issue commentmastercomfig/team-comtress-2

Screenshots not functioning proprely

hl2_2020-09-19_11-00-45

haha okay yeah that's a problem

joshuadinada

comment created time in 7 days

pull request commentmastercomfig/team-comtress-2

Re-enable func_monitors and fix point_camera rendering

I would love if we could get a map with this entity so that we can confirm this PR actually fully implements it, before we go ahead and merge it. Would that be possible?

FriskTheFallenHuman

comment created time in 7 days

push eventmastercomfig/team-comtress-2

Margen67

commit sha c9e0ea3fadd9d6fd6f6b14c531cee85e6d7e5015

Fix typos in issue templates

view details

Yttrium tYcLief

commit sha e840a6ce3cf3ec89181ce4fd2e5f982d2d73044d

Merge pull request #232 from Margen67/typo_fixes Fix typo in issue templates

view details

push time in 7 days

PR merged mastercomfig/team-comtress-2

Fix typo in issue templates documentation
+2 -2

0 comment

2 changed files

Margen67

pr closed time in 7 days

pull request commentmastercomfig/team-comtress-2

Revert sv_restrict_aspect_ratio_fov back to 1

While not explicitly mentioned in the commit description, this was explicitly highlighted in the patchnotes for 0.0.6, so I think it was intentional:

sv_restrict_aspect_ratio_fov 2 by default, so that players cannot gain an advantage with ultrawide displays

This is, as such, not a regression.

We can certainly have a discussion regarding if it should be changed back, but it's definitely not unintentional.

Margen67

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

[Feature Request] Regex filter for console output

Would need to hear from devs on how much this would affect performance.

LavaDesu

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

Disguises don't play their respective fall damage sound even if uncloaked

Is this an intentional design choice?

Margen67

comment created time in 7 days

issue commentmastercomfig/team-comtress-2

Spapper bug and class selection animation

besides it woudn't hurt to see em back

That's irrelevant. If this was a design change/choice, and not a bug, it's outside of scope for this project.

I'll wait to hear back from someone more knowledgeable on whether this is a bug or not before closing it.

condor00fr

comment created time in 7 days

issue closedmastercomfig/team-comtress-2

Screenshot bug

Ingame, if you press F7 or whatever button is binded to "Take Steam Abuse screenshot", the game becomes unplayable, with many visual bugs, leaving you with the only option to restart the game. This also happends if you take a normal screeshot. Here is demonstration of the bug: https://youtu.be/mAL8SRU1kNg

closed time in 7 days

joshuadinada

issue commentmastercomfig/team-comtress-2

Screenshot bug

We need far more info than this. Please fill out the New Issue template rather than deleting it.

joshuadinada

comment created time in 7 days

issue closedmastercomfig/team-comtress-2

"Find a Game" HUD element limitation/bug

Description

<!-- A clear and concise description of what the bug is --> Another bug found in custom HUDs due to limitations in the Engine. I'm not sure how exactly this could be worked over, but I'm sure something in the internal code is preventing HUD devs from extending this menu just a tad bit more to cover the bottom sliver. If not, please do correct me and close this (I'm looking at you, Yttrium.) This bug causes a missing sliver of shading at the bottom whilst in the "Find a Game" menu, which occurs in all custom HUDs, however, this might be a client bug that renders this impossible to fix in the current state by modifying HUD files. This bug is shown in the screenshot below. I've seen it in all custom HUDs, besides those (like Toonhud) that have a banner at the bottom to disguise this issue that HUD developers face, however, this is just a bandaid fix.

((This is my first issue here so please don't get mad at me if I did something dumb. Just give me constructive criticism.))

Checklist

<!-- You do not have to answer "yes" to all of these to open an issue -->

  • [x] None of the open or closed issues document this problem.
  • [x] This is a bug, not a new idea.
  • [x] This is objectively a bug, and not something that people commonly disagree on.
  • [x] This bug is in the code of the game, not in the textures, sounds, or other resources. (Probably, I'm not a HUD dev, as I feel like this would be fixed already if it were possible to do without modifying the game itself. Some HUDs cover this up by having a banner at the bottom with options such as Advanced Options on it.)
  • [x] This issue occurs on the lastest vanilla TF2 update.
  • [ ] This issue is listed on the Source 1 official bugtracker.
  • [x] This issue occurs with DirectX level 100.
  • [ ] This issue occurs on the latest Team Comtress release, or the master branch. (N/A)
  • [ ] This issue occurs when using no custom content. (N/A, seems like a custom HUD issue, possibly a HUD dev limitation.)
  • [ ] This issue occurs when using start_tf2.bat (or start_server.bat) with no custom launch options. (N/A)
  • [ ] This issue occurs when using a listen server (using the map command ingame). (N/A)
  • [ ] This issue occurs when using a dedicated server. (N/A)
  • [ ] This bug is in the internal procedures or tooling (e.g. the build process). (N/A)

Reproduction

<!-- The steps to recreate the bug. Bugs that cannot be recreated are extremely unlikely to receive a fix -->

  1. Use a custom HUD
  2. Open up the "Find a Game" drawer
  3. Witness the missing sliver of shading at the bottom of the screen (shown in screenshot)

Screenshots

<!-- Add screenshots to help explain your problem --> Screenshot_20200919_012422

Setup Details

  • Server or client: Client
  • Operating system: Windows, MacOS, Linux, Toaster
  • Team Comtress version: N/A
  • Custom content: Rayshud (This also applies to other huds), no explosion particles, reduced particles, Mastercomfig Low
  • Launch options: -novid -nojoy -nosteamcontroller -nohltv -particles 1 -nostartupsound -gl_amd_pinned_memory -gl_enablesamplerobjects <!-- For graphics-related issues: -->
  • Graphics driver: N/A, HUD issue unrelated to graphics drivers (whether it be NVidia, AMD, Intel, etc)
  • DirectX level: N/A, on Linux

Performance Details

N/A

closed time in 7 days

RicochetYT
more