@dedmen
I think the real question here is:
Group B Alpha 1-2 sees 11e1a0100# 482246: fridge_01_f.p3d delta 4.000000 now at 4.000000
Group B Alpha 1-2 sees 11e140b80# 482251: bandage_f.p3d delta 4.000000 now at 4.000000
Group B Alpha 1-2 sees 11e140100# 482252: radio.p3d delta 4.000000 now at 4.000000
Group R Charlie 4-6 sees 14bf36b00# 476558: dummyitem.p3d delta 0.018084 now at 0.091254
So I noticed that this crash occurs due to Arma saving some stuff that it shouldn't.
Maybe because I store displays into global variables, and it tries to deserialize those global vars.
Ah yes. So not a bug then.
I'll add it as a note to the wiki.
Oh that's a much better idea! Thank you!
Seems like a manifestation of the FOV issue. The FOV is broken in Arma, thus you see incorrect LODs, or objects disappearing at certain viewing angles.
To the devs:
Doing this seems like a good solution to me:
Use the shortcuts[] property to show the keybinds next to commanding menu items, but also add the assigned keys from shortcutsAction to this array.
E.g. in RscMenuMove we have:
shortcuts[] = {2};
shortcutsAction = "CommandingMenu1";if the user is using Numpad1 for "CommandingMenu1", you just add it next to the shortcuts[] array before creating the menu (in this example, shortcuts[] = {2, 79}; should be used before creating the menu).
I have tested this with custom commanding menus and it works perfectly fine.
@BIS_fnc_KK
I think what they mean is the roadway LOD on top of the ladder, which allows you to stand on an invisible "floor".
Freeze dump:
Here are two videos that demonstrate the problem:
Graphics card driver is up to date!
What you mentioned is not a vanilla feature. You can't go prone with the launcher in your hands in the base game. So blame the mod you're using (possibly ACE)
The only thing I could reproduce was the player standing up when he's prone, and switches from No Weapon to the Launcher.
The hunchback bug also occurs with civilians. These are spawned in the mission by either 1) civilian module or 2) with createAgent. Very little scripting otherwise, just a couple of event handlers (killed, firedNear) attached to the civilian unit.
The mission ran for several days and each new mission area spawned "hunchback" civilians like the screenshot. All other Blufor and Opfor units behaved normally, only the civilians were broken. That continued until I rebooted the server and the issue disappeared.
If it's run in an init field, then this is a local argument, since it will definitely run wherever the unit is local.
It'll also run where the unit is not local, which might lead to problems (or maybe it just has no effect; idk)
It works just fine.
First of all, the command takes local args
Second of all, you're not supposed to use it in init fields
I just realized you can do this with the ASLToAGL command. This can be closed.
