Raimund hat folgendes zum Q3 PR gefunden:
Hallo habe folgendes gefunden.
Invalid CD Key – This has been a problem since the 1.25 patch, although I believe it was fixed in 1.27. Nevertheless, if you are having it, the fix is to write-protect your CD key. The file is called q3key and is located in your baseq3 directory. First run Quake 3, re-enter the correct value for the CD key, and then exit without doing anything else. Make sure it is right before you take the next step! Then mark the file q3key as „read-only“ in Windows Explorer (File | Properties menu), or use the DOS command „attrib +r q3key“. When you next run Quake 3 you will get error messages in the console about not being able to write your CD key, but everything will still work, and you won´t lose it anymore. (the key, that is If you still get the „Invalid CD Key“ message you probably entered it wrong. You will have to undo the read-only attribute before you can correct it.
Missing Textures – Some people have had a problem with textures being replaced by a grey color with white cross-hatching on it. Normally this would mean a missing texture, but in this case it is a shader error. Shaders are code that tells Quake 3 how to render a texture, and many user made pak files come with custom shaders. Map files, skin and model files, even custom HUDs can all have custom shaders in them. Since shaders are also used in the Quake 3 menus, this error may even be responsible for the problem that some people have had with getting a blank screen when they start up. The problem is due to an incorrect shader file in one or more of your custom pak files. Quake 3 used to allow for some errors in shader code, but for the new patch the shader code was optimized to increase speed, and one of the unfortunate side effects is that now the syntax is stricter. Therefore some shaders that weren´t written correctly used to work fine anyway, but now they don´t. What really sucks is that an incorrect shader apparently messes up the parser in the engine, so that a bad shader in a file that you are not even currently using can still cause problems for every shader that was read after that. Like it or not, the only current fix is to move all of your custom pak files out of the baseq3 directory, and then move them back in one at a time until you find the one (or more) causing the problem. You will then have to get an updated version of that file before you will be able to use it with version 1.27. Check the pak author´s web site for updates. You did save the readme file that came with it didn´t you?
Sound Problems – I have not been able to reproduce this problem so I can´t answer this for sure, but I do know this: A problem with trap calls for looping sounds cropped up in the source that Id released to mod authors. Any mod author that has the code already also has access to Id´s NDA Mod Developer´s forum, where the fix is documented. If your sound problem is also occuring in the base game, we may have to wait for a fix from Id.
Mouse Wheel Problems – To the best of my knowledge this problem has only occured with Logitech mice. Go to the Logitech website, and get the latest mouse drivers AND Mouseware version 9.0 AND the „Mouse Registry File for Gamers“ and install them all in that order. This worked for me.
Mouse Sensitivity Problems – Your mouse sensitivity and acceleration settings are now a product of both the settings in Quake 3 and the settings in the Windows Control Panel. Start by turning off mouse acceleration and turning down mouse sensitivity in both, then adjust from there.
Demos Don´t Play Back – Demos are just a recording of server packets. When the server protocol changes, so does the demo format. Id changed the server protocol for version 1.27 in order to discourage cheating, so none of your old demos are going to work anymore. Also, two of the new demos that come with the patch are looking for Team Arena resources that just aren´t there (faux pas, Id!). You can however run the new deathmatch demo that comes with the patch, which is called „demo127“. This demo was recorded on „The Campgrounds“, which is a large map, so you should expect your frame rates with this demo to be somewhat less than they were with the old „demo001“. This is not due to the patch, it´s just the nature of the demo. If anything, it probably gives a more realistic number than the old one.
S3 Texture Compression – Id decided to change the name of the variable used to control texture compression, and it now defaults to off. If you were using texture compression, you should either turn it back on in the menu, or edit your config file and look for the new variable named „r_ext_compressed_textures“. If you weren´t using texture compression due to the infamous GeForce texture compression bug, you might want to try turning it back on now, because word has it that Id has worked around the bug.
I hope this helps everyone.
cu Raimund