If you used nQuake to install your Quake setup, those models are not yet validated by the version of the client you have. To get rid of this problem, remove g_models.pak from your Quake dir.
ezQuake is a client. nQuake is a package. nQuake contains ezQuake plus some add-ons. The ezQuake installation will install only minimum required files to play the game (presuming you already have pak1.pak from the Quake game). The nQuake installation will install ezQuake, better graphics, pro-gaming config files, bot helpers, crosshairs and many others.
If you are not sure, get nQuake
Yes, everything works in both Windows 7 and Vista. You might need to run it with administrator privileges and turn of Data Execution Prevention (DEP), especially the software rendering version.
In ezQuake, we have tried hard to make commands and variables intuitive so it's easy to locate. However, if you can't find the command for something, we have made the cvarlist
command which lists commands related to an item. For example, if you are looking for a command related to the mouse, type cvarlist *mouse*
(stars are needed).
Yes and no. First of all we recommend using sv_forcenqprogs 1
(available since version 2.0). Then most mods become playable (it prevents the client from loading qw(sp)progs.dat). However there are known issues e.g. in the Dissolution of Eternity mod (second episode crashes).
We recommend using other clients for playing Single player games, especially with mods. For example Fitzquake or DarkPlaces.
Try setting "threaded optimization: off" in video card drivers.
Change cl_physfps_spectator to 0. Note: player view movement will not be as smooth since then.
You've hit the limitation of the QuakeWorld protocol. You need to clear values of some variables that are sent to the server. For example type setinfo pmodel ""
or setinfo emodel ""
or setinfo b_switch ""
or setinfo w_switch ""
. To see full list of variables you can try to make empty, type localinfo
.
Make sure following files/directories have lower-case names: quake/id1, quake/id1/pak0.pak, quake/id1/pak1.pak
Try using different display frequency and resolution. Use e.g. "+set vid_displayfrequency 60 -width 640
" as a command line options. If everything fails try "-current
" as a command line option.
There are several things that can cause this:
This has been fixed in ezQuake versions 1.8.2 and 1.9 and higher. If you are using an old ezquake, try the following: type scr_conalpha 0
in the console. Use 16bit color depth (-bpp 16 command line option in older builds.)
Try changing client priority by sys_highpriority -1
or 0
or 1
.
By default in build 1754 the var mvd_autohud
is set to 1. Which means a special cfg is loaded when you play a demo. To get rid of this behaviour completly, do the following: disconnect; cfg_load your config; mvd_autohud 0; cfg_save your_config
Most of the problems starts with wrong files placement before the installation of the client. Check the Clean Quake Install section in the Installation chapter.
If you use laptop and your screen refresh rate is locked to 60 Hz, your FPS might get also locked to 60 FPS.
In that case use -dibonly command line option.
This is caused by some out-dated unofficial Quake installation packs. To get rid of such errors you have to remove opengl.dll and glide.dll from your Quake directory.
You need to download mgl_redist.zip and unzip it into your Quake root (c:\quake\)
Sure. Ask your question at ezQuake IRC channel or visit The Support page or ask other users on the forum.
Last update: 08.07.2011 20:12 UTC
ezQDocs