I cannot repro this on the latest build (tested on hosted and dedicated), could have been fixed indirectly because of other improvements done to the game, please retest
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Advanced Search
Feb 9 2022
Feb 8 2022
should be fixed in 148730
Feb 3 2022
Try lb or lnb type commands with toolbox
Feb 2 2022
Should be fixed in 148703
should be fixed in 148703
should be fixed in 148703
Feb 1 2022
[] spawn { disableSerialization; _CT_TREE = findDisplay 46 ctrlCreate ["RscTreeMulti", -1]; _CT_TREE ctrlSetPosition [0,0,0.3,1]; _CT_TREE ctrlCommit 0; _CT_TREE tvAdd [[],"Parent_A"]; _CT_TREE tvAdd [[0],"Child_A"]; _CT_TREE tvAdd [[0],"Child_B"]; _CT_TREE tvAdd [[0],"Child_C"]; _CT_TREE tvExpand [0]; sleep 1; for "_i" from 0 to 2 do { hint format ["Selecting Child %1",_i]; _CT_TREE tvSetSelected [[0, _i],true]; sleep 1; }; sleep 1; hint "DESELECT ALL"; _CT_TREE tvSetCurSel [-1]; };
use tvSetSelected and RscTreeMulti
Added in 2.02 tvIsSelected, tvSelection, tvSetSelected
Should be changed with the next data update
Jan 31 2022
Added "arsenalPreOpen" which fires before arsenal display is created (next data update)
Could be config related
should be fixed in 148107
rev 148701 opening map, changing seat or abandoning car should result in steering autocentering @ceeeb please check
Jan 17 2022
rev 148671 changes reverted to the original state. After careful consideration, the issue is now a "won't fix"
Jan 12 2022
Jan 7 2022
For the mouse input, the mouse must be moving at the moment the map opens
Jan 6 2022
Am I right to understand the issue here is more about wheels keep turning after keyboard input started and player opens map? So would making wheels start turning towards center be enough? Mouse/analog steering doesn't have this problem in my tests, wheels stay where you left them, only keyboard turning seems to continue to extreme.
Jan 4 2022
OK, the changes should be active with the next dev or one after next
I'm sorry, I understand where you are coming from, but the reality of the situation is, I can relatively safely change that cursor elevation. The rest will require thorough investigation and risk assessment, and we do not have resources for that. So it is either cursor change only or leave it as it was for years.
Just to clarify, the real issue is that cursor value displayed on the map is real altitude and not fake altitude and you want cursor to display fake altitude as well, is this all what this ticket is about? Because this could be tweaked, but only this
As I tried to explain to you, and as stated on the scripting page, current map elevation offset shows fake altitude for mountain peaks, that’s all. When in 3den mode the altitude delivered by cursor is real altitude, artillery computer shows real altitude, HUD elements show real altitude. elevationOffset is half baked feature that only brings inconsistency to the map visualisation and the actual values. There is no good solution but a complete revamp of altitude system to take elevation offset into account across the engine. Unfortunately at this stage of Arma 3 development this might not be possible.
Thanks for reporting. After some investigation, the elevationOffset feature seems to affect the altitude figures displayed on the map, and nothing else. It is unfortunate that Livonia is using it, because the altitude figures on the map do not correspond to the true altitude in game. Therefore we created a script command setElevationOffset https://community.bistudio.com/wiki/setElevationOffset that you could use to reset this offset to 0, available with rev. 148610
Jan 1 2022
Rev 148609 alt syntax https://community.bistudio.com/wiki/reload
does RPT say something like "Invalid path (only relative paths supported):.... ?
Dec 31 2021
Should be fixed in 148607
Dec 29 2021
is the limit hardcoded in the function or the engine?
Dec 28 2021
Should be fixed in rev. 148606
in new year for sure
Ok, now firemode also persists on weapon swap (Revision: 148605) please test thoroughly
Dec 27 2021
could be due to buggy graphics driver, have you upgraded recently?
Dec 26 2021
The fix has been applied internaly thank you for reporting
should be fixed in 148604
Rev 148603, customCenter param https://community.bistudio.com/wiki/setVelocityTransformation
You can use inPolygon https://community.bistudio.com/wiki/inPolygon as trigger condition. We wont be altering triggers in the near future.
Dec 25 2021
Dec 24 2021
Should be on dev
Dec 19 2021
Dec 17 2021
Also need exact repro steps
could try allowFleeing https://community.bistudio.com/wiki/allowFleeing
Dec 16 2021
Have you tried https://community.bistudio.com/wiki/allowCrewInImmobile ?
Dec 14 2021
Cannot repro the problem. Try to verify files. Also wait for the next dev just to be sure.
The fact that you can create display over dialog is wrong but it breaks backward compatibility if changed. The correct way is for dialog to appear on top of display, and it will be possible with alt syntax https://community.bistudio.com/wiki/createDialog
Should be fixed in 148602
Rev 148602 changes reverted in favour of alternative syntax https://community.bistudio.com/wiki/createDialog. Use createDialog ["MyDialog", true]; to make sure it is visible during briefing
Dec 8 2021
Was it not crashing in 2014?
If you wish to prevent map from opening, you can do this with ease already https://community.bistudio.com/wiki/openMap
Dec 4 2021
Not sure what the first video shows, but second issue is legit
Dec 3 2021
Nov 29 2021
Subscribed to 3200 mods.
O_o
Nov 28 2021
Nov 27 2021
should be fixed in 148571