Comments - MadcatMayhem

Yeah ssfx_wetness_multiplier shows up. Ive got a habit of triple checking everything. Currently on Update 11 EXEs with NO shader scopes. But I might try Shader Scopes later on.

Oooh you really should mention that in the main description. Also I checked and ssfx_wetness_multiplier shows up for me.

Im guessing I have to edit the .h files to configure SSS, for now, right?

Hey Asci, very nice mod but I think its not loading for me. Also need clarification after scouring all the comments on this addon page. I have the mod order as ES-->Beef's NVG-->SSS. This is what I configured the addons as:

-ES: PBR version and corrected cubemaps
-Beef's NVG addon with the patch only for ES/no SSR
-SSS: Main File, Patch for ES & Beef's NVG, all the screen space shader stuff.

Im using Update 11's EXE, the NO shader scope. I had a weird issue regarding Update 10's EXE but thats not the problem now. Im not seeing any console commands show up that SSS has. I can post more info later on.

Apparently cyberdemons can fight each other and are damaged by their own rockets too.

So I've been coming back to Doom and have been using Beaut Doom 7.16. I noticed a couple of bugs. Was tweaking eyecandy settings to preserve framerate on massive horde battles.

Beautiful Doom settings seem to be saved into the actual game save. I have to load that save, configure it again, and then overwrite the save for Beaut Doom settings to apply.

Projectiles settings dont seem to apply to cyberdemon and arachnotron projectiles either.

Hey Grok. I noticed you removed all of bmblbx's Dynamic mods again. I have all his addons but three of his upscaled texture packs on google drive. The 4k pda, skybox, and somehow I found the upscaled world texture pack. I could try to make some room on my google drive and add all of the upscaled texture packs if you want.

Its really pathetic bmblbx just took all his toys and ran home like a bitch.

Hello sganon. I currently am running several overhauls such as WPO, TO, Grok's Craft Repair Overhaul, OPO, and Mad Mags (in that order in MO2).

"trade_presets.ltx" is missing the following at the bottom. I'm going to keep an eye on Anomaly to see if I get anymore crashes. Appreciate your's and all the other modders work.

[craft_repair_overhaul]
armor_repair_fa = 0.5, 0.5
helmet_repair_kit = 0.5, 0.5
toolkit_p = 0.5, 0.5
toolkit_s = 0.5, 0.5
toolkit_r5 = 0.5, 0.5
toolkit_r7 = 0.5, 0.5
light_repair_kit = 0.5, 0.5
medium_repair_kit = 0.5, 0.5
heavy_repair_kit = 0.5, 0.5
exo_repair_kit = 0.5, 0.5
sewing_thread = 0.5, 0.5
heavy_sewing_thread = 0.5, 0.5

Actually nevermind. We need GZDoom or Zdoom much newer than the last stable releases. Grab them from here.
Devbuilds.drdteam.org

This is a brilliant idea for a mod thats LONG overdue for the old-school shooters. Problem is it's giving an error at launch no matter what mods, iwad, and engine I'm using. Pretty sure Im using the latest GZdoom and Zdoom.

No worries man. I'm able to hold out for next version of ZoA. :D

Is there any way to disable SSAO in this mod? Its killing my video card at the moment

Edit: Woops, nevermind.

Guys, this mod is great. Its very playable in it's current state, and I'm very glad to use the magazine system now since it's much more responsive now.

But combat is unbearable. The NPCs are a bunch of tanked-up crackshots, meanwhile I'm a soldier with pea shooters and paper armor. It's incredibly one-sided at the moment.

I finally am to play this mod with no troubles. But as of this moment one issue drives me nuts. All the enemies are bullet sponges and I take two pistol rounds to die. Armor and weapon are irrevelant. I am sure I have ZoA 1.07, with latest patch and hotfix. Any ideas?

Ive been playing with 1.0004 for several hours now and it seems to be fine. I even see the warning on the main menu to downgrade when I was at 1.0006.

Should I patch up to 1.0005 again? Seems pretty stable now.

Just need a slight clarification. I've read in the changelog that ZoA now runs on 1.0006. Does it matter if its the U.S. or Worldwide patch?

Yeah this is weird then, it could be cpu then as I have a core 2 quad at 3ghz. I'd like to move the shaders and textures folders out of the gamedata folder but I get crashes to desktop.

Nope still using the older MP 2013. I turned prefetch back on and the pauses are noticibly shorter, but just barely.

It's weird because I've got 8gb of ram and the video card is a GTX 560 2gb. Also stalker runs on the SSD so loading times are MUCH faster, even with prefetch. The only thing regarding more ram usage was just being on 1.0005 and verifying XR_3DA with Large Address Aware. Should I try some other modified .exe or .dll?

Hey bordegunner

Cheers for your tinkering of OL mod. Been a few years for me.

I've got two annoyances, one I remember from years ago the second is recent. The A-Life repopulates the same, if not worse, from OL 2.2. I know its open A-Life, but is it always this bad?

The REAL annoyance I get are these seconds-long pauses when I get to certain parts of levels. Ive got plenty of PC horsepower to run stalker with crazy eye candy mods, but these pauses are getting ridiculous.

Is it shaders, texture size, prefetch off? XR_3DA.exe has been checked by Large Address Aware. Maybe its because theres 3gb worth of textures?

Uh dude, wouldn't that compress the messed up HUD and menus further? Totally forgot to mention I'm on an old LCD screen. I can turn off resolution scaling but I'd rather not.

Sorry if I spammed, been trying to post while logged-in.

Alright, thanks to a few pointers from people like MeekX I managed to narrow down my issue with ZoA and NS DMX. Once texture is at 50% or "texture_lod 2", the game doesn't BSOD anymore. At 75% or 100% texture detail slider (texture_load 1 and 0, respectively), the game will BSOD. This is also at stock CPU overclock, so that's out of the equation.

My only problem now is a corrupted HUD. Actually there is no HUD intended in ZoA, right? I think my resolution might be too small. The inventory, conversation, and trading interface are all screwed up and missing elements. I'm stuck on a native resolution of 1280x1024 (5:4). Would that have anything to do with it?

I'll try to post a log, if I can get past the blue screens. No worries though, I can wait it out for a patch.

Yes, fire mode indicator and boxed ammo. Those two are badly-needed. Some HUD elements are neccessary for feedback. Playing with ACE mod for Arma2, you do a mag check, then recieve either a message or mag icon that gives you a hint of the ammo count in a magazine. Mag check could work in stalker. Reload animation, maybe a magazine symbol thats color coded.

Oh god yes with the boxed ammo. You could crash the game by dropping 100 rounds of 9mm due to the physics on 100 boxes of ammo haha.

No worries on the prefetch typo. I'm stuck on an old lcd so my native res is 1280x1024. I use EVGA Precision to give me info like memory usage, but the game cant load with ZoA. I'll check the video memory usage on MP2013 though.

Hey Meekx, when you type -prefetch, do you actually mean "prefetch"?

Regarding overclock, I went back down to stock CPU clock, but the video card is stock OC. It also has 2gb vram, so I doubt it would've been filled up that quickly.

Did some more testing but with vanilla and RAM-enhanced EXEs. Tested ZoA and NS DMX 1.3.5 and both give me the same kind of BSODs at new game creation. I'm also beginning to suspect save game corruption, as I CTD when loading them. Reinstalled SoC and installed 1.0004 patch to be sure, but no change.

Played some SoC MP 2013 but forgot to go to 1.0005 patch. Still ran stable for few hours until a CTD. So it might be nvidia drivers, or the engine messing with RAM?