Completely agree with both of the comments above. There is very little incentive for server owners and admins to carry on hosting. Server costs are huge and a VIP system (as in other games) is absolutely essential.
Recent Activity
Today
And it's still not fixed in 12th December update.
damn it. that explains some of the WTF moments i've had in the game over the last few months where i thought to myself “how the hell does the opponent see me”. too bad, too bad...
First Person Perspective(1PP) should the normal case, not the exception in a military simulator.
I completely agree with this request and want to emphasize its importance for server admins and communities alike. The introduction of the queue system is a welcome improvement, but the lack of VIP queue functionality creates significant challenges for server management and sustainability.
The day is saved!! Excellent choice to implement controller presets AND also have the legacy preset be available!
Kudos!
Crash log from another client who tried to connect to a server and suddenly crashed, will keep crashing until teleported through CF tools or other RCON tool. Server just wiped recently.
MELHOREM ISSO LOGO
Check the key bindings, there are some changes, so maybe that's the cause. For me it works exactly as previously.
The sqf error is not duplicated, but summarized with the "x repetitions" - the context message is duplicated.
ok nvm. too much effort to be worth it. thanks for checking!
sorting by count is done.
in cases of
This crash was only present on profiling branch for a very short time.
Correct, we do not support cloud saves. And we do not plan to change that.
The default user profile name, is the username of the account playing the game. If the username stays the same, every new profile will have the same name.
This happens when joining a server, and the mission download fails.
So you are joining into a mission, while you don't even have the mission file.
This was already fixed, the server must've been running the pre-hotfix A3 version.
That error is directly forwarded from Steam.
Why steam says it, I don't know either.
So basically, it tells the HC to turn it on locally, and print into its own console.
This is a problem in case you want to script something that relies on CfgGroups, you will need to make exceptions for factions which have it set up differently.
Ihre Organisation hat diese App unter Verwendung von Device Guard blockiert.
And why is this a problem or a bug?
Illegal instruction. Your CPU seems to be quite old.
The bug has been fixed on the performance profiling branch https://community.bistudio.com/wiki/Arma_3:_Steam_Branches, it will be quite a while until the fix makes it to the main branch.
Resolved for 1.2.1.169
https://community.bistudio.com/wiki/setObjectScale
Scaling is not supported. Bugs like this will not be fixed.
I can see you were pirating our DLCs. If you want support with the game, you better not pirate it.
The game now uses Visual c++ redistributable 2022, not 2013 anymore.
You have 2022 installed, but only the x86 version, the game by default uses the x64 version, which seems like you have not installed.
What is a jamming tower?
What is a "MED pod"?
What are naval scooters?
Which base?
What tank are you talking about? What active protection? This sounds like some mod, which is not anything we would deal with.
What sectors?
What mission are you talking about?
What mission?
Are you talking about some server?
If it doesn't seem like a bug, why are you reporting it in a bug ticket then?
This video gives a better idea of this issue, recorded on version 1.2.1.169. My fps is around 30 or so
Hello shoolhanyarok.
Currently there is an issue with nvidia app, please use nvidia geforce experience instead.
Regards,
Geez
it also seems to stop at a specific point in the loading right before u load the server
Hello.
Server IP 95.156.224.202.11000
Hello SignofTerror.
Please use the ingame report feature.
Regards,
Geez
Hello MikeSpike2001.
Please try the following:
Nothing you can do from your end unfortunately. This has to be fixed on our side.
Resolved for 1.27
Please tell me what I need to do? What exactly causes such problems?
Hello again.
The issue has been confirmed internally and is being worked on.