From the Hardcore Side
There are people who play Quake, and then there are people
who live and breathe it. In the first part of "From the
Hardcore Side", a new semi-regular feature at PQ, Pappy-R
brings all his hardcore gaming experience to you and talks
about what's going on in the hardcore scene today.
This week's edition is going to tackle some issues people have been having with the new v1.27g Point Release for Quake III. I don't think I'll ever get used to the mail I get when id Software patches a game. When Q3 v1.25 and then v1.25y came out I got a ton of mail saying the new physics sucked and that any change would kill either "pro" gaming or certain individuals love for the game. I got at least just as many mails this time when the physics changes were dumped and there was little or no difference between v1.17 and v1.27.
| An example of a shader problem.
To all those people who mail me and thank me for making such a great game (yes they do), I didn't make the game, I'm just a big fan like you. To all those that mail and curse me for changing the game with patches (yup, this happens as well), I didn't make the game, I'm just a fan but maybe not like you. Now let's jump in and see if we can't help some players.
The recent Quake III v1.27g Point Release has fixed some things in the game, added some features to make the base game compatible with the new Team Arena mission pack and altered other areas. For a full list, always read the Readme.txt that places itself in the Quake III base directory. One thing that always surprizes me is that people do not read the "readme" files. This is quite clear by the "demos won't play" mail I've gotten and the posts on message boards. It clearly states in the new readme that this is a known issue. Here's the blurb ripped right from the text.
- Launching demos from the user interface does not work. To play a demo back, go to the console and type "demo demofilename" without the quotes. This is a bug that cropped up when we changed the extension for demos so they include the protocol number so demos show up properly in menus. This will be addressed in a later patch.
Demos from other game versions will not play in v1.27 due to not being compatible. This is a known issue since the v1.25 strain of patches.
The other two major issues I've gotten mail on are mouse sensitivity going through the roof after installing the new patch, and that textures are messed up. The pic here is from our buddy Steve who claims that Quake III now has "holodeck" features (heheh, he made my day with that analogy). Both of these problems are indeed caused after installing the v1.27 patch, but are not really flaws in the patch as much as fixes and tweaks that cause problems to some users. I asked Robert Duffy at id Software about these issues and here's what he had to say to help explain and fix the problems for affected users.
Pappy: I have mail from people getting bad or missing texutres in levels. They don't say whether these are in regular Q3 levels or 3rd party and I have yet to see the problem myself. Can you offer some info?
Robert: This is due to bad shader files. Basically the shader parsing is more strict and requires valid shader definitions ( matching braces, no invalid keywords etc. ) This allows us to find them much faster and helped speed up level loads etc. The way to fix this is to start removing NON-id pak files until the problem goes away OR you can clean install from CD, then apply the 1.27 patch and the add back in mod content as needed.
Pappy: I have a few odd claims that the patch messes up mouse settings making the mouse far too sensitive once the patch is installed.
Robert: We fixed the mouse wheel bug by properly initializing direct input. This appears to have caused the mouse acceleration settings from windows to show up in the game. You can fix this by either turning OFF mouse acceleration in windows or by adjusting the m_pitch, and sensitivity values until your mouse feels right. We have only had this reported on a few mice.
As usual, I hope this helps some people out there and I'd like to thank Robert for taking the time to offer some help here. After writing this piece I noticed that Haqsau's Lab has also posted some info on v1.27 issues, so hit that as well. Keep those mails coming and I'll be doing more gameplay issues next time for you all.
CYA out there!