I don't see a problem with that solution. Using SRV records like that could work as some kind of shitty matchmaker if you follow the weight and priority parts of the SRV record, but if that is not intended then it's user error. But I'd imagine the main usage would be hosted solutions where multiple servers share the same IP as described by Jaffa, or like @HeroGamers games describes having something like mycommunity.org point to server4.coolgameservers.net, port 23456, both of which wouldn't be degraded by saving the last resolved host/port.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Apr 4 2025
Scratch some part of that.
I can use the same connectToServer hack also for the direct connect UI.
So you have to specifically enter domain and port 0 (or manually empty it (it will be default filled with 2302)) in direct connect.
Then it will try to resolve the port via SRV record, if that fails it falls back to 2302 (same as would've happened before if you left it empty or entered 0 manually)
Apr 3 2025
Apr 2 2025
Running my test missions again seems like it was, or at least it's switching the target a lot faster so this can be closed now @dedmen
Apr 1 2025
This seems to have been done in 2.14
get/setOpticsMode
If wrong, ping me.
In T184219#2782959, @dedmen wrote:What are you doing that 2048 arguments are not enough??
What are you doing that 2048 arguments are not enough??
In T154359#2782908, @dedmen wrote:Use getAttackTarget instead. If that is wrong then ping me.
Use getAttackTarget instead. If that is wrong then ping me.
Revision: 152762
_entity removeAllMagazinesTurret _turretPath
Mar 31 2025
Can confirm there is a similar issue on ArmA Reforger regarding Round Start:
https://feedback.bistudio.com/T190471
Mar 30 2025
right rearview mirror bug not replicated on the current build
since we are actively playing with the Escape and Liberation community the above situation hasn't happened to us yet, we would have noticed it for sure.. on the current build I can't replicate the problem
the problem was not replicated on the current build even after ten attempts
the Mi-17 lacked countermeasures
Mar 29 2025
can't repro
fixed in the hotfix (rev 12692)
Mar 28 2025
confirmed. Cannot find any event handler that works with "switch to group member"
I had some time to test. I observe that the following work:
Mar 27 2025
Steam Beta Client was bugged for a while and caused crashes. Valve already fixed it.
Yeah well "cpu: Pentium(R) Dual-Core CPU E6300 @ 2.80GHz"
Too old CPU (That one is from 2009). That code that used the unsupported instruction was removed on profiling branch, but different code was added that uses the same instruction.
Your CPU is just too old, I'm surprised it can run windows 10.
We will not fix that.
Please. Stop openiing new tickets for the same thing.
You are getting an error message, it tells you why its crashing.
secExt_x64.dll That comes from the @Rocket Life modpack. Ask them. It failed trying to get your hard drives serial numbers.
Wiki documentation was wrong. Because https://feedback.bistudio.com/T178348 was not resolved until today. It'll be a thing in 2.20
2.20
??????
MarkerDeleted eventhandler only has two parameters, a string and a bool.
There is no _deleter. Not a bug.
Something is wrong with your Arma, there are lots of non-game files in the game folder. D3DCompiler, d3dx9, binkw, X3DAudio, xactengine?
Please delete all files (not folders!) in your game directory, then verify game files in steam to clean it up.
Does it still not work? Then https://community.bistudio.com/wiki/Arma_3:_Unusual_Process_Exit#0xC000007B_-_STATUS_INVALID_IMAGE_FORMAT (It currently links the wrong c++ 2013, it should be c++2022 now)
I need the crash report files: https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/
Don't believe what a spam bot is saying, it cannot be graphics card, the error is CPU side. It might be your CPU is too old though.
22:05:02 DX11 error : buffer Map failed : DXGI_ERROR_DEVICE_REMOVED
22:05:02 DX11 - device removed - reason: DXGI_ERROR_DEVICE_RESET
Something is very wrong with that trace file.
The game failed to capture properly, it should not only contain extDB entries.
And no it doesn't seem to be a extDB issue, all the extDB scopes are very short, its just that everything inbetween is somehow missing.
Maybe the normal captureFrame log file shows better info, and its just the trace file that's bad?
"deleteParentWhenTriggered" has a default value of true
"explodeParentWhenTriggered" has a default value of false
Mar 26 2025
happens without cba; some quick notes from testing