Skip to content

Latest commit

 

History

History
112 lines (83 loc) · 5.59 KB

FAQ.md

File metadata and controls

112 lines (83 loc) · 5.59 KB
Raw

FAQ

Q: NeoDefaults changes a setting I don't like. Can I replace it?

A: Yes. See Customizing NeoDefaults for an explanation on customizing the configuration.

 

Q: I change a setting in the game, but it always goes away the next time I launch TF2. Why?

A: neodefaults.cfg is run every time TF2 starts up. Therefore, if you change something that neodefaults.cfg modifies, it just will be set again the next time you launch TF2. See Customizing NeoDefaults for an explanation on how to make sure your setting is not overridden.

 

Q: Why is there a custom.cfg? Can't I edit the neodefaults.cfg config file directly?

A: The short answer is no. The neodefaults.cfg file is a read-only file.

The much longer answer is that this was done on purpose with future releases in mind. If there are new versions of NeoDefaults in the future, and someone runs the program again, the newer NeoDefaults will need a way to easily replace an old neodefaults.cfg file. In most practical situations, NeoDefaults would just be able to delete the old neodefaults.cfg and replace it with a new one.

However, if a user manually changed parts of neodefaults.cfg to their own tastes, this complicates things. It won't be easy to figure out which settings were added by the user and which ones should be replaced. And if custom settings have been added, they should never be overwritten.

To solve this problem, a custom.cfg file is provided, where custom settings may be stored. This guarantees that neodefaults.cfg will only ever contain changes made by NeoDefaults, so NeoDefaults can safely delete the old file and replace it with an updated version. The file is set to read-only to make it obvious that it should remain unmodified.

 

Q: Where can I learn more about customizing TF2 with scripts/config files?

A: woolen has a great video where he explains his personal customizations that can help give you a good idea of how config files work and what kind of settings you might want.

 

Q: Why does NeoDefaults set cl_interp to 0.0303 instead of 0?

A: TF2 sets the default value for cl_interp (AKA "lerp"), at 0.1, or 100 ms. According to the the Valve Developer Wiki, this value was tuned for the Source engine during the era of dial-up modems (!), so it should absolutely be lowered. It's insane that the default value for this variable hasn't been changed by the TF2 dev team in over a decade.

Many players set their cl_interp to 0, and this is even recommended by wiki. However, since this project is geared towards newer players, it's often the case that such players won't have the most reliable internet connections, so they can benefit from having a little bit of lerp. NeoDefaults sets this value to 0.0303 in order to strike a balance between lowering it and making the experience slightly more playable for those with unideal network connections. It's worth mentioning that this value is still ideal for players with stable connections that heavily use hitscan weapons, so using 0.0303 should not be considered a detriment.

 

Q: Why doesn't NeoDefaults enable/disable (insert setting here)?

A: NeoDefaults is designed to be a short list of very cherry-picked customizations, and only includes what is considered essential. If you think there's a critical setting missing, open an issue on GitHub so that it may be considered in a future release of the installer.

 

Q: I got a warning that said "Tried to modify autoexec.cfg and failed". What happened?

A: The autoexec.cfg file is checked by TF2 every time the game starts up. In order for NeoDefaults to run on startup, this file must indicate that we want the neodefaults.cfg file to run. This error is not expected to happen, but in case it did, here are some steps you can take to fix this:

  1. Open the cfg folder located at <your TF2 install path>/tf/cfg.
  2. If you use mastercomfig, open the "user" folder. If you don't know what this is, you likely don't have it installed, so ignore this step.
  3. Find the "autoexec.cfg" file, and open it using a text editor like Notepad.
  4. Add the following lines to the bottom of the file: 
    //--------Added by the NeoDefaults Installer--------//
exec NeoDefaults/neodefaults
//--------------------------------------------------//
    This tells autoexec.cfg to run the neodefaults.cfg file located in cfg/NeoDefaults.
  5. Save the file, and launch TF2. When TF2 has launched, hit the ~ character to open the console.
  6. There will be a bunch of text written there, but among all of it, you should see the following message: 
    -------------------------------------------------------------------------
------------------ NEODEFAULTS (version number) LOADED ------------------
-------------------------------------------------------------------------
    If you see this message, then you've fixed the autoexec file successfully. If not, something went wrong. Consider opening an issue on GitHub for additional help.

 

Q: I installed the hitsound through the Advanced Install, but I don't hear it in-game.

A: There's an in-game setting that turns hitsounds on and off, and it is off by default. neodefaults.cfg enables this for you, but it's likely that you opted out of the config install. To fix this, open the Advanced Options menu in TF2 and enable the "Play a hit sound" setting.