Comments - Sikkpin

I do have some interaction shader replacements for ETQW but I've never done any of the post effects for it. It already has a pretty good bloom solution and even though the color balancing is nothing more than simple tinting, it does the job just fine. If you want to improve the post process visuals of ETQW, you can create custom atmosphere parameters for the maps. This probably won't work for online play but it'll work for solo/private matches.

Open console (~ or CTRL+~) and type: pm_thirdperson 1

Then hit ENTER.

You can't change the hud on the fly as it's loaded at spawn and saved in the save file, so which hud to use is loaded from there when loading a save. Yes, it would be possible to modify the behavior to allow changing it mid-game, but you can;t do it with the current code. Sorry.

Without getting too technical, the absence of the player model in the mirror/camera renders is an unfortunate side effect from have to do a specific render pass in order to get a depth buffer to be used for things like dof, ssao, etc.

I've tried to resolve this but it doesn't seem possible with just the game code. Having soft shadows on allows the player model to draw in mirror renders but there's, of course, a significant performance hit.

Since having CatAI off is causing problems for you, you can try one of the following: 1) install an older driver and see if disabling CatAI still crashes or 2) leave CatAI enabled with your current driver but rename the Doom3.exe to something else, like "Doom 3.exe" (note the space).

Let me know it that helps you at all.

"wrong game DLL API version" means you're not patched to the latest version, which is 1.3.1. Here's a link to the patch you need:

Ftp.idsoftware.com

Did you follow the instructions in the readme? There's no reason for it to crash unless you are doing something wrong and a new version won't help this as the as the installation will be exactly the same.

How exactly are you installing it and trying to run it?

I don't know. I've never used Desura, never saw a reason too. My suggestion would be to download it manually and follow the instructions in the readme.

I still don't understand how Desura can possibly work with mods that have specific requirements on how to install and/or run said mod. Just seems to me like another unnecessary piece of software taking up resources. I imagine that it has advertisements in it as well.

Yes. Only a dll comes with the mod. The source is there, though, so you can build a .so file (or .dylib if you're on a Mac) if you have the means.

And if you do have the means (or anyone else, for that matter), I'd appreciate a copy of the file so I can include it in the package.

It seems there's a slight problem with this the update. All of the "test.vfp" shaders (the various parallax shaders) in the "glprogs" folder are bugged. So if anyone was using one of these shaders and getting a black screen when HDR was enabled, that's why.

You can get a tiny 28kb patch containing the fully working shaders here:

Sikkpin.fileave.com

Sorry about the inconvenience.

You need to turn CatAI OFF. Do a search for how it can be done with the latest drivers. And the first person body is just a hack and unsupported.

I changed all weapons to fire their projectiles from the barrel as opposed to the center of the view. Some weapons already had this set, like the rocket launcher, but most others didn't. To change this back, open the weapons respective def file (for instance: "weapon_pistol.def") and look for this: "launchFromBarrel" and set it to "0". The def files are located in the "def" folder in the "pak_modfiles.pk4" file.

Strange that you'd need to do something like that, but that's good to know. Steam seams to ruin a lot of older games when it comes to mod compatibility. Shame.

Hmmm, I'd say set the file to "read only" but I doubt that would do anything. Try renaming the "Doom3.exe" to "darkathena.exe". I've heard this can help.

If you haven't touched the CCC and it's still at their default settings then CatAI is ON. In older drvers, CatAI is on by default and with newer drivers, you can't even turn it off through the control panel. Look a few posts down for how you can manually turn CatAI off and then get back to me if the problem still persists.

Also, don't force AA/AF through the CCC. Let Doom 3 handle those things.

Fix what? How can I fix a problem that I don't have and therefore don't know the cause? Remember, I don't have the engine source, just the game code like everyone else. I can do nothing about hardware incompatibilities. Plus, as I stated below, the shaders used are not hardware specific so there are no "hardware incompatibilities" with this mod.

My guess is that the problem is from one of these things: Improper installation, mixing other mods with this one, or not turning off CatAI. Turning off CatAI has to be done, regardless. I posted below a way to do it with current drivers.

CatA.I. needs to be turned off. Performance is not the same as off. I know the new drivers don't allow you to turn it off through the CCC but you can still turn it off by editing the "Profiles.xml" file. Another user here posted this:

from farhad24:

heres what AMD users should do to make it work
go to
C:\Users\"your name"\AppData\Local\ATI\ACE
open profile
edit this line
Property name="CatalystAI" value="Enable" />
to this
Property name="CatalystAI" value="Disable" />
thats over save and quit

If it's still not working correctly after that, do me a favor and upload some screenshots for me to look at (your CCC settings are good, by the way). Also, everything else is working okay, right?

All of the shaders are written in ARB so there's no "incompatibility" when it comes to Ati hardware. I have an Ati card, by the way.

Now, since every effect you listed uses an encoded depth render, I'm going to take a guess and say you are forcing AA and/or AF through your driver. If you are, turn those things off (or app controlled) as they also get applied to the depth render which, since it's encoded, cause pixels to have incorrect depth and, therefore, screwing up any effects that use it.

And sun shafts won't work unless you are in a large enough area with an unobstructed sky box. The large areas in the monorail map can work to test it out.

I don't have the steam version so I can't say for sure but try downloading the 1.3.1 patch ( Ftp.idsoftware.com ), take the exe from that (the installer can be opened with 7-zip - 7-zip.org), rename it, and stick it in your Doom 3 dir. Id games don't need to be "installed" to run so, my guess is, if you use the original exe it should run without steam.

CatAI needs to be turned off. If you can't turn it off through the control panel, you can either use a third-party program like ATI Tray Tools or rename "Doom3.exe" to something like "Doom 3.exe" (note the space).

Let me know if either of these things help.

"wrong game DLL API version" means the version of the dll and the exe don't match. The game needs to be patched to 1.31. To check the version, run the game without the mod and open the console. The version number is on the right. Also, when you get the error window, scroll up to the top, it'll tell you what version you're running. It should read: 1.3.1.1304

Third person cvars listed below.

pm_thirdPerson - enables third person view

pm_thirdPersonRange - camera distance from player in 3rd person

pm_thirdPersonHeight - height of camera from normal view height in 3rd person

pm_thirdPersonAngle - direction of camera from player in 3rd person in degrees (0 = behind player, 180 = in front)

pm_thirdPersonOffest - camera offest from player in 3rd person (-n = left, +n = right)

These variables are not saved to your "DoomConfig.cfg" so you'll need to put them in an "autoexec.cfg" to have them apply every time you play.