Description

Allows you to track compatible upgrade kits, parts, attachments, repair tools and ammo for selected weapons and/or armour. Compatible items will be highlighted while the item is tracked.

Preview
track compatible items
Post comment Comments
NewbieRus
NewbieRus - - 714 comments

ЗДРАВСТВУЙ АВТОР. отличный аддон. не могли бы вы добавить отслеживание частей для оружия и костюмов? например: щелкнул правой кнопкой по пистолету ПМ = и будут подсвечены части, из которых он состоит. То же самое с костюмами. А то бывает разбираешькакие-то костюмы и не знаешь - какая деталь пригодится в будущем.

Reply Good karma Bad karma-3 votes
ElCaz4dor
ElCaz4dor - - 193 comments

Kind of want to start making written notes for components required and upgrades required, but then I come across this mod and the other mod that shows which component is used for crafting which item.

Reply Good karma Bad karma+3 votes
Wiz3rd
Wiz3rd - - 32 comments

Another BANGER QoL mod from you, good job!

I love seeing stuff like this. No ********, just useful stuff.

10/10

Reply Good karma Bad karma+5 votes
Markuzkiller
Markuzkiller - - 342 comments

To clarify things, I need to MANUALLY sets the tracking right?
It isn't automatic at the moment of equipping the weapon/armor piece?

I already have a mod that does that, but I cannot upload it here since it's not mine, and I use only for myself.

The mod a have does all these automatically at the moment of equipping the items, however it only works for weapons and don't work on upgrades.

But honestly, I don't even use upgrades to begin with

Still amazing mod!!

Reply Good karma Bad karma+3 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Yep, you need to manually select an item to be tracked using its right-click menu.

Reply Good karma+2 votes
billlcarr
billlcarr - - 272 comments

Fantastic QOL mod!

I noticed in the log, there's TONS of repetitions of this-

~ ------------------------------------------------------------------------
~ STACK TRACEBACK:

g:/games/stalker - anomaly\gamedata\scripts\_g.script (line: 1701) in function 'SYS_GetParam'
... d1sp_track_compatible_items.script (line: 644) in function 'base_highlight'
... rax_persistent_highlight.script (line: 51) in function 'Highlight'
... ui_inventory.script (line: 2046) in function 'UnHighlight_All'
... ui_inventory.script (line: 3851) in function <... ui_inventory.script:3793>
~ ------------------------------------------------------------------------
!ERROR SYS_GetParam(0, nil, parent_section) | What's missing?

No crash, and everything seems to function perfectly, but the log is filled with these stack tracebacks (I'm assuming one for every time I open my inventory)

Reply Good karma Bad karma+3 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Thanks for this.

I've fixed this issue in the latest release.

Reply Good karma+3 votes
billlcarr
billlcarr - - 272 comments

Awesome, thanks!

Reply Good karma Bad karma+3 votes
billlcarr
billlcarr - - 272 comments

Wow, and an MCM too! I really like your "keep ammo highlighted" mod, but this right here is peak QOL!

Reply Good karma Bad karma+3 votes
billlcarr
billlcarr - - 272 comments

Found a minor bug. When I track attachments for the VEPR 12, it highlights all the correct ones, but it also highlights the GP-25 grenade launcher.

Reply Good karma Bad karma+3 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Hi again

I've had a look into this (and written a detailed explanation of why this happens below), but my tldr answer is that I probably can't fix this.

If anyone more knowledgeable on anomaly modding reads this and knows a solution, please correct me.

For an explanation, the issue is that some guns in anomaly have grenade launchers configured in their ltx definitions, but then disable them with grenade_launcher_status = 0. I don't know why this is the case. The VEPR 12 falls into this category. The same applies to silencers and scopes. For some guns this makes sense as you need to buy the under-barrel attachment as an upgrade (but the VEPR 12 doesn't have this)

Normally in anomaly when you hover over an item, it knows to highlight attachments because it calls the function weapon_grenadelauncher_status() on the object instance in your inventory, which checks both the ltx definitions *and* whether the gun instance has an attachment upgrade brought.

The issue is that this mod tracks on the name rather than an object instance. This is what allows the trackers to persist without the original item. I cannot call this function without an object instance.

If I change the addon to require grenade_launcher_status = 2 in the ltx definition (meaning it supports grenade launchers) it will then break highlighting possible attachments for weapons like the AKMN (with or without the under-barrel upgrade brought) as the default ltx definition has the status as disabled (0).

I think the better solution is to leave the logic as-is so that everything is highlighted as expected, with some invalid highlights sometimes, as opposed to some guns not working with the tracker at all.

Reply Good karma+3 votes
billlcarr
billlcarr - - 272 comments

Thanks for the explanation. Not a problem at all, I just thought I'd mention it, but I figured it was something like this. Keep up the great work, your add-ons are fantastic.

Reply Good karma Bad karma+3 votes
дедушка_Ли
дедушка_Ли - - 176 comments

Hello.
I offer you, as well as everyone else, as a temporary solution, translation of mod settings in MSM-menu into Russian for version 0.0.4.
I.postimg.cc
Drive.google.com

Здравствуйте.
Предлагаю вам, так же как и всем желающим, как временное решение, перевод настроек мода в МСМ-меню на русский язык для версии 0.0.4.
I.postimg.cc
Drive.google.com

Reply Good karma Bad karma+3 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Hi, and thanks for providing this.

I've include those localization strings in the latest release.

I've also added localization support for the right-click menu item text, and added some (crude) google translate localization for them.

Reply Good karma+2 votes
дедушка_Ли
дедушка_Ли - - 176 comments

Hello, author.
After installing version 0.0.5, when I right click on a weapon, I have a crash:
I.postimg.cc
I connect version 0.0.4 - everything is fine, but there are still untranslated items:
I.postimg.cc.
Thanks in advance for the answer!

p.s. I also offer translation into Russian for version 0.0.5:
Drive.google.com

Здравствуйте, автор.
После установки версии 0.0.5, когда нажимаю правой кнопкой мышки на оружии, у меня происходит вылет:
I.postimg.cc
Подключаю версию 0.0.4 - все нормально, только остаются непереведенные пункты:
I.postimg.cc.
Заранее спасибо за ответ!

p.s. Так же предлагаю перевод на русский язык для версии 0.0.5:
Drive.google.com

Reply Good karma Bad karma+2 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Hi, I've been unable to replicate this crash on my end.

To help me diagnose this could you do the following:

Firstly, could you try a fresh install of the addon. If using MO2 just right click and remove it. If you manually installed it, could you delete any files under your anomaly installs /gamedata/scripts folder that contain the words 'd1sp_track_compatible'

Once uninstalled, try installing version 0.0.5 again.

If you still get this crash could you provide me the following:

(1) The name of the item causing the crash
(2) The last 10-15 lines of your games log file. This is located under /{your anomaly install folder}/appdata/logs and will be called 'xray_{windows username}.log'
(3) The lines in your script file causing the issue. Open '/gamedata/scripts/d1sp_track_compatible_items_mcm.script' (or d1sp_track_compatible_items.script if using the non-configurable version) and either screenshot or copy the code around line 186.


Reply Good karma+2 votes
дедушка_Ли
дедушка_Ли - - 176 comments

1. Tried reinstalling your addon - the same crash, under the same conditions.
2. "(1) The name of the item causing the crash" - this I do not understand.
3. Screenshot of the last lines in the log file:
I.postimg.cc
4. Screenshot of the script "d1sp_track_compatible_items_mcm" (line 186), on the right version 0.0.5, on the left version 0.0.4:
I.postimg.cc

p.s. I'm sending you the log file itself just in case.
Drive.google.com

Thank you again for your reply!

Reply Good karma Bad karma+2 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

I think there might be some conflict here caused by installing both versions of the addon.

In the addon zip file there are two root folders

- 01 Basic
Contains 'd1sp_track_compatible_items.script'
This is used if you don't want to configure highlight colours

- 02 Basic with MCM support
Contains 'd1sp_track_compatible_items_mcm.script'
This is used if you want to use MCM for configuration

Each root folder above then also contains the localization files

'01 Basic' and '02 Basic with MCM support' are mutually exclusive (install only one)

The error in your log file is being raised in the script 'd1sp_track_compatible_items.script' while the notepad++ diff you provided is of d1sp_track_compatible_items_mcm.script.

Could you please look in your anomaly installs gamedata/scripts folder and confirm that you only have **one** of the following

- d1sp_track_compatible_items.script
- d1sp_track_compatible_items_mcm.script

I'm assuming you want to use MCM to configure the highlight colours so you'll want to be using '02 Basic with MCM support' which would be the script 'd1sp_track_compatible_items_mcm.script'

If you are using mod organizer 2, you could open the 'data' tab in the launcher, and navigate to gamedata/scripts to confirm you only have one of these scripts.

Again if using MO2, it may also be useful, if you haven't already, to disable all other addons except this one, and see if the crash still occurs.

Reply Good karma+2 votes
дедушка_Ли
дедушка_Ли - - 176 comments

Dear Author!
Thank you for pointing out where to find my mistake!
As it happens, it's all a matter of inattention: by searching for the file "d1sp_track_compatible_items.script" in my build, it turned out that I did not disable the previous version 0.0.2!
And for some reason, versions 0.0.2 and 0.0.4 did not give any crashes....
Installed version 0.0.5, everything is fine:
I.postimg.cc

Thank you very much again and sorry for wasting my time!

Reply Good karma Bad karma+2 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

No problem - happy to help.

Reply Good karma+2 votes
SniperHellscream
SniperHellscream - - 981 comments

Hello friend, I am using your mod together with this mod: Github.com (Outfit Repair Overhaul) and I get this error when I try to see the description of the Proto-Exo

! [LUA] 13 : [Lua] ...y files/anomaly - 1.5.2\gamedata\scripts\utils_ui.script(2177) : Update
! [LUA] 14 : [Lua] ...les/anomaly - 1.5.2\gamedata\scripts\ui_inventory.script(3570) :
! [SCRIPT ERROR]: ...les/anomaly - 1.5.2\gamedata\scripts\arti_outfits.script:456: bad argument #1 to 'pairs' (table expected, got nil)

FATAL ERROR

[error]Expression : <no expression>
[error]Function : CScriptEngine::lua_pcall_failed
[error]File : C:\anomaly_src\xray-monolith\src\xrServerEntities\script_engine.cpp
[error]Line : 206
[error]Description : fatal error
[error]Arguments : LUA error: ...les/anomaly - 1.5.2\gamedata\scripts\arti_outfits.script:456: bad argument #1 to 'pairs' (table expected, got nil)

stack trace:

Reply Good karma Bad karma+2 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Hi

I can't see any reference to this addon in those logs. Looking at the source code from that github link you provided, it appears the issue you are seeing is caused by the 'Outfit Repair Overhaul' addon when it tries to call "to_infobox", passing a potentially <nil> value into 'pairs'

To confirm which addon is causing this issue you could disable all addons other than this one (if you are using MO2) and then try to replicate that issue by hovering over the Proto-Exo.

Just to be safe I've added a <nil> check in a similar line within this mod when it calls to get compatible repair kits.

Reply Good karma+3 votes
SniperHellscream
SniperHellscream - - 981 comments

Hello friend, OK, I did exactly what you told me, and I was doing several tests in MO2. I did a full clean install and found that (Track Compatible Items) by itself works perfectly. and along with (Outfit Repair Overhaul) they also work perfectly, on a clean install with just these 2 mods enabled.
But I realized that the error only occurs when activating WPO Github.com from the same author.
This error only occurs when using the 3 mods simultaneously, if they are used separately there is no problem, for example (Track Compatible Items + WPO) or (Track Compatible Items + OPO) there are no errors. When combining the 3 together the game gives an error (Track Compatible Items + OPO + WPO).

Reply Good karma Bad karma+2 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Hi again

Could you try the latest version of this addon and see if it fixes your issue.

I was able to replicate your issue by installing both of those addons + this one. While this addon doesn't actually change anything around armour/guns for some reason using a certain internal function caused that crash. No idea why.

Reply Good karma+3 votes
SniperHellscream
SniperHellscream - - 981 comments

Exactly, your mod is not the cause of the problem, but for some strange reason the error occurs when combining the 3 mods, it's strange, thank you very much for your response, i update to the latest version shortly and I'll see how everything works

Reply Good karma Bad karma+2 votes
SniperHellscream
SniperHellscream - - 981 comments

Thank you very much friend, the last update solved it, thanks for helping me with my problem, now it works excellent, great job! 10/10. My best wishes for you!!

PS: I have created a Spanish translation for your mod, since it is my native language, in case you are interested in adding it to your mod, so your content will reach more people, greetings!!

Spanish Location:
Mega.nz

Reply Good karma Bad karma+2 votes
d1sasterpiece Author
d1sasterpiece - - 19 comments

Good to hear its working

And thanks for the localization files - I've added them to the latest release

Reply Good karma+2 votes
Guest
Guest - - 689,988 comments

eexxon

Reply Good karma Bad karma-1 votes
Post a comment

Your comment will be anonymous unless you join the community. Or sign in with your social account: