Comments - ZJ-B312

Well the G28 rifle is derived from the HK417, maybe it can be a HK417 replacer as well.

Yes it has - I recently figured out that to launch the menu requires holding F (interact), I'd been pressing F all this time and thus was unable to do anything except turn my lamp on and off. Now I can refuel and retrieve the lamp into inventory as intended.

I haven't used the others but from the description, it sounds as though you are supposed to top up fuel for the lamps. Though i can't seem to figure out how to do it.

Thanks for the reply, on further inspection, I think it may be w_usp_match_up.ltx or w_usp45_up.ltx; for the HS2000 w_glock_up.ltx, these are from JSRS 5.0. What should I look out for inside these?

Apart from that I only have the DLTX modpack affecting the upgrade tree, but I already loaded the respective PPP patches.

Ah yes i remembered, after you reach a certain rank a bunch of "private messages" will show up in your pda advertising this tracking function, that's when you know you unlocked it

Hi, it seems that the USP45 Tactical is unable to mount its silencer if accidentally upgraded with the Silencer Affinity upgrade, in comparison, the HS2000 is still able to do so despite being upgraded with Silencer Affinity.

Of course, it doesn't really make sense that either of these should still have the silencer upgrade in the upgrade tree since they can fit a silencer right out of the box. Could I suggest the upgrade paths be changed to something else? Thanks.

You have to press 0 (next firing mode) button while in PDA

In your main file, a 2nd gamedata folder containing the same dltx config seems to be mistakenly placed in gamedata\textures\wm\ when its not supposed to be there.

Edit: sorry, found another comment further up pointing out the same thing

Many thanks for this, helpful for those who don't use BaS because in the original upload the Gauss rifle icons and description go missing. I hope the author can implement this as another option in the fomod installer.

When running weapon reanimation mods that contains aoldri's "Universal Animation Scripts" dependencies, I got this CTD when trying to type out my target's name into the pda tracking that this addon provides:

Expression: <no expression>
Function: CScriptEngine::lua_pcall_failed
File: ..\xrServerEntities\script_engine.cpp
Line: 206
Description: fatal error
Arguments: LUA error: ...rary/stalker
anomaly\gamedata\scripts\ads_reloads.script:7: attempt to index local 'casted_wpn' (a nil value)
stack trace:

The solution is to download the latest 23 Jul 2023 commit on the github for ads_reloads.script, which fixes this issue, just an FYI.

Thank you, much appreciated!

Do you think you can make an optional file for Duty? (or guide me how to name the config file - since the parameter inside is the same 2 lines) Since in loner playthrough you are almost never friendly with mil, mercs or monolith.

How do I refuel gas lamps that have run of fuel? Also is it possible to retrieve a placed lamp back into inventory?

Thanks!

Hi I would like to ask about the script conflicts with your VSSK mod. While all other scripts are just exact duplicates of each other, when I checked on WinMerge there are differences in wpn_sway_enabled.script. Is the VSSK one supposed to override the SVU version in terms of load order? Thanks!

On the VSSK mod,
ln4:
valid_wpns = {
wpn_svu = true,
wpn_svu_alt = true,
wpn_svu_nimble = true,
wpn_vssk = true
}

ln44:
--news_manager.send_tip(db.actor, "APPLY SWAY")
ln56:
--news_manager.send_tip(db.actor, "REMOVE SWAY")

On the SVU mod,
ln4:
valid_wpns = {
wpn_svu = true,
wpn_svu_alt = true
}

ln42:
--news_manager.send_tip(db.actor, "APPLY SVU SWAY")
ln54:
--news_manager.send_tip(db.actor, "REMOVE SVU SWAY")

Hi, I'm somewhat confused by the Modded Exes portion (step 5) where you mentioned your exes having the same combined edits as MrDemonized combined Modded Exes, but his bin folder includes non-DX11 executables and there is files in the db and gamedata folder as well in his zip archive which I presume is needed for stuff to work.

Do I extract his archive to my game folder first and afterwards override the DX11 executables with yours? (I'm using his 1.5.1 modded exes which he no longer supports so I assume your DX11 exes is more up to date?)

Thanks! I'll try it out

Hi, will there be issues affecting a current save from swapping out an an old (2021) version of HD models to the current one via MO2? I know you did mention that missing models may cause crashes but I'm not too sure if there are these sort of differences with regards to the old version...or can I just use the MEGA patch that you linked and load it after the old version?

I used the original Death Animations mod with Anomaly 1.5.1 no problem, but that's probably because I started it with a new game. Do you think switching it midgame to this one updated for 1.5.1 would have any effect or would it be redundant?

Check out the fix for the HK417 acog its in the new optional files. Although you only get a illuminated reticle when you have light behind your character.

Sure thing, it could be useful for some who made the mistake of buying the bugged HK417 lmao

Btw, do you know how I can make ACOG crosshair addons compatible with your G36 variants?

This 1drv.ms is my personal edit(to fix HK417 issues) of the recently released Anomaly 3D Reticles Moddb.com . However this causes the reticle to look butchered like this: Ibb.co when none of the files look like that. Similarly, using the unedited version of the crosshair addon causes only a chevron to appear Imgbb.com

I've asked around on discord and it appears that 3D scope reticles apparently aren't controlled by weapon config files.

The RCO versions of the ACOG used by Marines/Army have the additional horizontal stadia markings. The vanilla ACOG probably represents the civvy version that only has vertical BDC markings.

I had a look at Tacticool scopes Moddb.com and realised he only uses 1 single crosshair file which is intriguing.

Thus, I merged the crosshairs and duplicated it as setka_new and setka_new_2 for the shoker_addons folder. The inverted versions were merged and duplicated as _crosshair and crosshair_dot for the wpn_addon_scopes_acog_new folder. 1drv.ms

The results are:
"Normal" rifles do not experience transparency problems and the ACOG is illuminated regardless of light.

HK417 now has a working reticle that illuminates red only when you have light source behind you.

Modded G36 variants possess only the vertical portion of the reticle markings that cuts off at the 500m marking. It looks weird but still usable I guess.
Ibb.co

HK417 is a blacklisted gun apparently just like the Steyr AUG A3, reddit sources say you have to type wpn_hk417 in the debug menu to spawn it - it doesn't appear by default. The one I had I somehow bought it off Freedom trader Skinflint.

I think the problem with "special guns" needing to use the crosshair files is that they are already using them in some form - which is why half the reticle is appearing - but possibly incorrectly or differently from vanilla Anomaly. And I have no clue where those files that control the use of the crosshair are found.

Ok, I've just been testing them, but the same problems are occurring.

HK417
Ibb.co Vanilla ACOG, missing chevron
Ibb.co Your ACOG, illuminated but missing chevron

M4 carbine(both with your addon)
Ibb.co Working as Intended
Ibb.co Same rifle and scope, but viewing different objects under different lighting leads to loss of the BDC illumination, but not chevron.

I've also tested it on the G36 variants I added with the G36 Pack addon:
G36K
Ibb.co Vanilla ACOG reticle
Ibb.co Your ACOG reticle

G36L "Nimble"
Ibb.co Vanilla ACOG reticle
Ibb.co Your ACOG reticle

So therefore my questions are:
1) It seems for both the HK417 and G36, only one combination of the acog files are being used, either addons_acog_setka_new + wpn_addon_scope_acog_crosshair only (causing no chevron aimpoint) or addons_acog_setka_new_2 + wpn_addon_scope_acog_crosshair_dot (causing lack of BDC markings). I cannot find the file which control the use of this either, it certainly doesn't seem to be inside the weapon's ltx file.

2)In the case of the M4 (and other "normal" rifles like HK416, SCAR-H, etc etc) it works perfectly, until when viewed from certain angles/lighting the BDC illumination fades off whereas the chevron remains as red. Not as bad a problem as the 1st, but is this expected to happen?

Thanks for your help

I'm using DX11 and facing the same thing so no, that is likely not the issue

bruh if this isn't even compatible with RC versions then it is definitely not gonna work on 1.5.1. Get his 1.5.1-compatible stuff here: Moddb.com

Thanks I'll give it a try

Usually the HK417 ACOG reticles are messed up in someway, in vanilla Anomaly for e.g. the aiming chevron is completely missing. According to the OP i guess the same problem is manifesting.