This page will tell you how to comfortably upgrade from older to new versions of ezQuake. To know how to upgrade from FuhQuake, visit the Installation manual page.
Also don't forget to check the FAQ
Upgrading to 2.1
Q: my crosshair is blurred!
A: /gl_texturemode2d gl_nearest
Upgrading from 1.8 to 1.9
Q: There are several things on the screen that weren't there before, I want to turn them all off!
A: Type /legacyquake command into the console. It will disable most of the new features that display something new on the screen and it will also tell you how to turn them back on later.
Some users didn't follow the recommendation from "Upgrading from 1754 to 1.8" chapter and they are still using command-line to configure their client. We want to emphasize here again, that using command-line options is deprecated and unnecessary. It can cause you troubles with mouse input, video configuration, proper config loading and many others. Read below on how to remove the need for command-line options.
Upgrading from 1754 to 1.8
-
The way how the client loads and saves it's configuration has been changed in many aspects. This is our recommendation how to save your configuration now:
- Load the client and load your configuration.
- Go to Options menu, select the Config tab and hit "Save". Before you do that you may wish to decide where you want to have your configuration saved - in your quake/ezquake dir or in your system profile dir - recommended (e.g. in Windows that's My Documents/ezQuake). If you change this in future, you will have to manualy delete config.cfg from the old location.
- If you have your own various default.cfg, config.cfg and autoexec.cfg files to auto-load your configuration on start-up, remove them. If you used command-line option +cfg_load myconfig, remove it.
Now your configuration will be auto-loaded on client startup from the config.cfg file and you should not need any command-line options anymore.
- The r_fastsky setting now works even if you are using custom skybox texture; use r_fastsky 0 if you are missing your custom sky look
- Screen settings in GL version are now done via config. Go to the Options menu, video tab, set the screen settings you like and save your config
- As you might have already noticed, you do not need any command-line options. Typically you should be able to completely erase your command line. Look for variable equivalents. Video related settings are all available through the menu, -dinput is represented by in_mouse 2, -m_smooth by in_m_smooth 1, etc.
- In this build, the menu will pop up once starting ezQuake. If you'd like ezQuake to go directly to console like old times, set cl_onload variable to "
console". You need to use the recommended way to load and save configuration (see above) for this to have any effect.
Upgrading from 1517 to 1754
- Independent physics feature is now enabled by default. Follow the link for more info. If you want to disable them, use this command-line option when running ezQuake:
-noindphys
- If your graphics card settings say that vertical synchronization should be application controled, you will have vertical synchronization turned on on startup. To prevent this, you have to explicitly mention:
vid_vsync 0.0
either in your config or in the console or put +vid_vsync 0 in your command line. (Note: Due to some other circumstances you have to use exactly 0.0 in your config, just vid_vsync 0 might get ignored in some occasions).
- If you have vid_displayfrequency 75 in your config, your display frequency will now really get switched to 75 when you load your config. To prevent this, type new value of your desired vid_displayfrequency and save your config.
- Head Up Display defaults have been changed. If you have noticed different frags and teamfrags placement, try this:
frags extra_spec_info 0
teamfrags extra_spec_info 0
If you noticed some odd clocks or frag counter on your screen, use:
hide democlock
hide gameclock
hide teamfrags
To make sure your HUD configuration is exactly the same as in previous version of ezQuake, use the Keeping exact old settings guide from below.
- For MultiView Demos (MVD) we do automatically load custom Head Up Display (HUD) configuration from now on. To disable this behavior, use:
mvd_autohud 0
- Behavior of mp3_volume has been changed. If you had custom scripts for increasing and decreasing your media player volume, those won't work anymore. To increase or decrease your media player volume from within the client, use following commands:
mp3_volume +0.1
mp3_volume -0.1
This has been changed to avoid media player volume problems when loading your config.
- You can make your commandline more friendly by changing following option:
+set vid_displayfrequency X into -freq X (both ways still do work but also don't forget save your vid_displayfrequency into the config - see above)
Also you can throw away "+set cl_independentphysics 1" because it's on by default now.
- cl_nolerp default value has been changed to 0
For full description of what has been changed see the changelog
Upgrading to 1517
- You might get fullbright textures on walls in this build. That's because we have fixed r_fullbright behavior and you have set variable to 1 in belief it has something to do with fullbright skins. To get rid of this behavior, just use:
r_fullbright 0
Keeping exact old settings
As we are modernizing the client, by upgrading to new versions long time users might face two situations they would like to avoid. New feature they do not want which is turned on by default and an old feature but with different default value.
New features
As mentioned in "Upgrading from 1.8 to 1.9", by using /legacyquake command you are able to turn off some new modern graphics features that were not present in older versions of the client.
You can also supply an argument to this command so that only new features from specific version are turned off. So for example when upgrading from version 1.9 to version 2.0 you can use legacyquake 2.0 and new graphic features that were added in version 2.0 will be turned off.
New default values
As we are modernizing default settings to meet current gaming standards, these changes might affect your configuration if you used default settings before.
To make sure existing settings don't change between versions, save your full config also with default values. To do this, before you use the cfg_save command, type this into the console:
cfg_save_unchanged 1
After this just save your config with
cfg_save
Now you can install new version of ezQuake and load your full config in it using the cfg_load command.
Last update: 10.04.2011 14:14 UTC
ezQDocs
