I thought setParticleParams (and drop) would only take a p3d as input. I searched through many pbos but can't find a snow p3d or way of using the above "a3\data_f\snowflake4_ca.paa" texture in a particle script. Excuse me taking up your time.

Thread of this in Discord Feedback tracker: https://discord.com/channels/105462288051380224/1310192027534753802

No I meant the performance branch of the game. Anyway the crash should've been fixed by now so if you're still getting the crash, wait for a dev to analyze your crash files and respond.

In T186575#2706623, @Leopard20 wrote:

If you're using the perf branch, wait for the update or switch to stable.

It should work with setParticleParams, why, it doesnt? or you mean 3d particle?

It is just a variable stored on player that the function returns, I will get rid of it

You need to confirm if PIP has been disabled

1. place unit, exec player forceAddUniform 'U_B_CombatUniform_mcam'
2. exec [player, "BI"] call BIS_fnc_setUnitInsignia;
3. exec player forceAddUniform 'U_B_CombatUniform_mcam_vest'
4. exec [player] call BIS_fnc_getUnitInsignia;

result - insignia class name was return although no picture on clan selection

Yes I saw you updated the biki thanks a lot KK. Quick question - is there a particleshape equivalent to the texture "a3\data_f\snowflake4_ca.paa" that can be used in setParticleParams?

Bit of an update to this; Running Stable? Build 152405 (Will test with v12 prof later), with 30 people on the server and monitoring Outbound with #monitor 0.1 with client.

Переустановка игры не помогла, такая же ошибка.

repro please

With lastest dev update insignia will not be lost after take off and putting on again for same uniform object.
But if unit put on new(other class name) uniform BIS_fnc_setUnitInsignia will return false and no imagine will show

This change seems affect to issue T161323, can't reproduce on the latest dev update

input validation is more strict now. would need some != "" checks now

If you're using the perf branch, wait for the update or switch to stable.

I've just noticed a new graphics driver 566.14 from 12NOV. I have 566.03. Maybe that is the cause of the issues ??

Fixed 2.20

So sad, still an unusable control with script controls...

Official Arma Discord, #perf_prof_branch channel:
https://discord.com/invite/arma

In T185482#2701071, @kju-PvPscene wrote:

You may want to ask on the arma discord as reminder if your update was missed

types from last week

F13, F14, and F15 now work, F16~F24 still work as keybinds, but display as "UNEXPECTED_KEY_ID"
Found that this is almost certainly related to missing DIK keycodes
These I believe are the missing DIK code and scancode lines, from "\a3\ui_f\hpp\definedikcodes.inc"
Reference I found for DIK codes: https://community.bistudio.com/wiki/DIK_KeyCodes

agreed. especially for large terrains is seriously hampers the ability to navigate or plan as you have to zoom in a lot.

rev 152421

Sorry for the ambiguous repro steps and wrong code, I believe my intention was originally to use _this instead of this but I didn't catch the error because it currently doesn't work either way.

Will this ever be a possibility? Recently went into the Editor and was reminded of this difference. It would make the in-game map look substantially better than it does currently.

Aren't both 1st and 3rd person views not using the same models? (Or maybe, does a model file contain both a 1st/3rd person models?)

logEntities has class name and position (but no vehVarName either)

deleteVehicle has received a local check and should be fixed.
If there is a repro, I need a repro to see whats happening

I've updated documentation yesterday

Oh I see the mistake.