@Astaroth, it's a DayZ ticket. Please, transfer it.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Dec 4 2019
@Astaroth, it's a DayZ ticket. Please, Transfer it.
@Astaroth, it's not valid anymore. Ticket can be closed.
As it was user's fault with configuration of monitors in Windows.
@Astaroth it's not valid anymore. Ticket can be closed.
It had nothing to do with ArmA, but was a problem of too low voltage of GPUs that was responsible for the errors.
I had same problem with my GTX 580 back then and increasing its voltage solved the problem.
@Astaroth, it's fixed. Ticket can be closed.
@Astaroth, I've checked it - it's fixed. Ticket can be closed.
@Astaroth it's not a bug. Ticket can be closed.
Since always in ArmA, using right mouse button to zoom in optics was working as max zoom only and only if you keep pressing the RMB.
To keep optics zoom and to be able to keep it at a certain level (not max), - and + of num pad have to be used.
Same applies to all Armas, not only A3.
@Astaroth, it's fixed. Ticket can be closed.
Dec 3 2019
@Astaroth, it's fixed. Ticket can be closed.
@Astaroth, please, close the ticket, since too old and no details were provided.
@Astaroth, it's fixed. Ticket can be closed.
I've checked this on our server with several players inside of inventory of dead soldier and me deleting it, using deleteVehicle cursorTarget and no crash for any of the players.
The inventory was simply closed for them.
@Astaroth not valid anymore. Ticket can be closed.
@Astaroth it's fixed. Ticket can be closed.
@Astaroth it's not valid anymore. Tocket can be closed.
No GameSpy browser anymore for ArmA 3.
@Astaroth it's fixed. Ticket can be close.
@Astaroth it's fixed. Ticket can be closed.
@Astaroth it's fixed. Ticket can be closed.
@Astaroth, I've checked it - it's fixed. Ticket can be closed.
@Astaroth , ticket can be closed.
One simply must not forget to set the text editor to UTF-8 encoding.
When UTF-8 encoding is set for the text editor, there is no problem, since ArmA supports UTF-8.
@Astaroth, it's resolved. Ticket can be closed.
@Astaroth I've checked it - it's fixed. Ticket can be closed.
@Astaroth, not reproduceable anymore. Tocket can be closed.
@Astaroth, I've checked it - it's fixed in the way that weapons are now removed from hands of players and players have hands on their knees (see screenshot).
https://i.imgur.com/2ecYpqg.jpg
Ticket can be closed.
@Astaroth, I've checked it - it's fixed in the way that weapons are now removed from hands of players and players have hands on their knees. Ticket can be closed.
@Astaroth, I've checked it - it's fixed. Ticket can be closed.
@Astaroth I've checked it - it's fixed. Ticket can be closed.
@Astaroth it's fixed. See screenshot.
https://i.imgur.com/4Jd4Tm2.jpg
Ticket can be closed.
@Astaroth it's fixed. See dedmen's comment. Ticket can be closed.
Dec 2 2019
Up
I have a fix ready and already tested for this.
Integration into game TBD.
this is causing my graphics card to go down and it's only an Arma 3 issue
Dec 1 2019
should be fixed in next dev
We have no reproduction of the crash on game load here. Can you try loading it without mods to see if it works, and then gradually enable mods to see when it stops functioning.
Nov 30 2019
Nov 29 2019
Congratulations on finding some old relic that haven't been used for 10 years. Yeah it is not functional.
Nov 28 2019
Nov 27 2019
Note to file :
Type: Public
Build: Stable
Version: 1.96.146114
OK, thanks for your reply. Doesn't answer any of my questions, but if the report is awaiting a full evaluation from internal personnel, then I guess the wait is anybodies guess. I will continue my POC (proof of concept) using EH's and see how it goes. I assume from your reply though, that CT_TREE is not fully functional for multiselect in the current version and watch this space. Cheers
This means that the report is filed in internal system about missing functionality i.e. inability to get multiple selected items, that’s all.
@BIS_fnc_KK Appreciated the Acknowledged status, but what does that actually mean for this case?
Issue still reproduced :(
Nov 26 2019
I did some digging into this and found that the decal color is influenced by the tree's MCA texture. Unfortunately this means to change this it requires a rework of all trees, which at this point will not be done.
This needed to be addressed on BI's side, which it did for the Enoch terrain (Enoch -> "Livonia).
I looked into this and the control strips are already marked to be excluded from AI traffic. It would appear that this setting has no effect.
Unfortunately nothing can be done about this.
Nov 25 2019
A combat mode of a unit depends on a combat of the group the unit is in, so in order to get combat mode of the unit you can get the combat mode of the current group the unit is in. When you move unit to another group, the unit behaviour is set by the new group, this is why combat mode you set on temp group won’t affect the unit in the new group. In short, "combatMode unit" does what you want already, returns combat mode the unit is subject to currently. I hope I made it clearer.
In T146675#1985180, @BIS_fnc_KK wrote:This is the intended behaviour. See orange note box at https://community.bistudio.com/wiki/lineIntersectsSurfaces
In T146461#1985203, @BIS_fnc_KK wrote:The command sets combat mode for a group, not individual AI units.
https://community.bistudio.com/wiki/combatMode
Nov 24 2019
It is what it is. If you would like to have unified return for every command make sure you clear inventory when entity dies, for example:
The command sets combat mode for a group, not individual AI units.
https://community.bistudio.com/wiki/combatMode
This is the intended behaviour. See orange note box at https://community.bistudio.com/wiki/lineIntersectsSurfaces
Nov 23 2019
Nov 21 2019
2019... still having this issue... can you please, please address this? add a delay to it or something, please...
Nov 20 2019
Hello, wanted to ask if you have already recognized something?
hey, first of all thank you very much for your reply.
Hello, please try to go through the steps described here
Hello, would you mind to provide some repro steps to achieve this error message?
I see, your first comment mentioning it's happening in both SP and MP confused me. It could have helped as so far we have reports only from MP that we are not able to reproduce ourselves :(
Can someone please take a look at this?