Yeah not really sure. Stumbled upon a fix for the ALiVE end though which is good. I've also put some feelers out to see if it's a feature or a bug. Like you say, it's looking more like a bug given that it's not consistent across all rhs vehicles.

Haha no worries, I've got a list of all the vehicles which cause the issue now so we're good.

For anyone else reading this, here's the list of vehicles from RHS and Project OPFOR that will cause this error:

["RHS_AH64D","RHS_AH64D_GS","RHS_AH64D_CS","RHS_AH64D_AA","RHS_AH64D_noradar","RHS_AH64D_noradar_GS","RHS_AH64D_noradar_CS","RHS_AH64D_noradar_AA","RHS_AH64D_wd","RHS_AH64D_wd_GS","RHS_AH64D_wd_CS","RHS_AH64D_wd_AA","RHS_AH64D_noradar_wd","RHS_AH64D_noradar_wd_GS","RHS_AH64D_noradar_wd_CS","RHS_AH64D_noradar_wd_AA","RHS_AH64DGrey","RHS_AH1Z","RHS_AH1Z_GS","RHS_AH1Z_CS","RHS_AH1Z_wd","RHS_AH1Z_wd_GS","RHS_AH1Z_wd_CS","rhsusf_m1025_w_m2","rhsusf_m1025_d_m2","rhsusf_m1025_w_s_m2","rhsusf_m1025_d_s_m2","rhsusf_m1025_w_mk19","rhsusf_m1025_d_Mk19","rhsusf_m1025_w_s_Mk19","rhsusf_m1025_d_s_Mk19","rhssaf_m1025_olive_m2","LOP_AA_M1025_W_M2","LOP_AA_M1025_W_Mk19","LOP_IA_M1025_W_M2","LOP_IA_M1025_W_Mk19","LOP_PESH_M1025_W_M2","LOP_PESH_M1025_W_Mk19","LOP_PESH_IND_M1025_W_M2","LOP_PESH_IND_M1025_W_Mk19","LOP_ISTS_M1025_W_M2","LOP_ISTS_M1025_W_Mk19","LOP_ISTS_OPF_M1025_W_M2","LOP_ISTS_OPF_M1025_W_Mk19","LOP_IRAN_AH1Z_WD","LOP_IRAN_AH1Z_GS","LOP_IRAN_AH1Z_CS"]

No worries! Not sure if it's worth chasing down all instances of this or if two will do. If you need any more examples devs, let me know.

We have a bug report.

Okay... it's also the RHSUSF armed M1025 that cause this issue - both desert and woodland. Unarmed don't seem to be a problem.

I think I've found (at least) two culprits, and they are LOP_PESH_M1025_W_M2 and LOP_PESH_M1025_W_Mk19. Can't find any vehicles that do this for LOP_AM yet though.

@HeroesandvillainsOS  are you using Peshmerga?

Thanks dude! No worries though, I'll try to get a repro together with as few variables as possible. Stumbled on this while I was testing another script so it might take a little while for me too.

That said, I'm not sure whether the error is a config error by project opfor (most likely) or an error caused by ALiVE not reading certain configs correctly.

Yup, definitely alive. The error is in alive\addons\sys_profile\fnc_profileSimulator.sqf.

Alright, still present with LOP_PESH and LOP_ISTS. The index reference is about an index of hitpoints for a profile (presumably a vehicle), rather than map index. I'm fairly sure it's an issue with one of the project opfor factions (not all - LOP_AFR and a few others don't have this).