User Details
- User Since
- Oct 16 2017, 5:21 PM (380 w, 5 d)
- Roles
- Administrator
Fri, Jan 24
Wed, Jan 22
Did you try verifying game files via Steam?
Jan 1 2025
Dec 31 2024
Are you using the perf/profiling branch?
Dec 30 2024
Yes this is also due to an unsupported instruction by your CPU. Nonetheless, I'm sure Dedmen will look at it once he's back from vacation.
Dec 28 2024
It seems that you have a program (or virus) on your computer that's interfering with input.
Does the issue happen in other games?
What are your PC specs?
Your CPU is too old, and due to a recent change the game crashes on your CPU.
The issue has been fixed on the performance/profiling branch. So switch to that until v2.20 stable is released:
https://community.bistudio.com/wiki/Arma_3:_Steam_Branches
Dec 26 2024
Please don't report mission/mod issues here. They have their own Steam Workshop page.
Old Man is not a campaign. It's a scenario.
Dec 24 2024
I was playing tutorial.
So you mean you were already in the game?
This is a launcher crash. Even if it crashes mid-game it shouldn't affect the game.
Dec 22 2024
Dec 21 2024
It is a known problem with old CPUs, such as Core2 Duo. The issue has been fixed in performance branches. Unfortunately the fix has not made it to the stable branch yet.
So for now, switch to the performance branch, as I explained in my previous comment.
Dec 17 2024
Post the details text file on your Desktop which the error has mentioned.
Dec 15 2024
What is your CPU model? The error is due to an unsupported instruction by your CPU.
Try running the performance/profiling branch of the game.
Read this page for more details on how to switch branches:
https://community.bistudio.com/wiki/Arma_3:_Steam_Branches
Dec 12 2024
If your PC crashes in other games too, why do you report it here? It means it has nothing to do with this game.
Dec 11 2024
IDK. Just wait for Dedmen to analyze your crash file.
Dec 9 2024
By the way, have you verified your game files yet? Here's how to do that:
No problem. If you have something to post, post it here.
I guess you'll have to wait for Dedmen to analyze your crash files then.
Can you also try the performance branch? Maybe the issue is already fixed there.
In case you don't know how to use it:
https://community.bistudio.com/wiki/Arma_3:_Steam_Branches
TL;DR:
- Right click on Arma 3 in Steam
- Select Properties
- Go to Betas
- If you don't see the performance branch in the drop down, use the code CautionSpecialProfilingAndTestingBranchArma3 to get access.
- Select the performance/profiling branch in the drop down and wait for Steam to download the exe (it's less than 100 MB).
Dec 8 2024
Instead of trying those things, remove these parameters and try again:
-cpuCount=12 -exThreads=7 -malloc=system
the cpuCount and exThreads are especially bad.
Dec 6 2024
Your file.io files were deleted.
Can you upload the rpt here? Not on another site?
Nov 30 2024
It's a OneDrive error. It says Cloud File Provider is not running. You must sign in to your OneDrive account and sync your files.
Google "OneDrive Cloud File Provider is not running" for more info.
Nov 26 2024
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.
Nov 20 2024
If you're using the perf branch, wait for the update or switch to stable.
Nov 19 2024
Official Arma Discord, #perf_prof_branch channel:
https://discord.com/invite/arma
Nov 14 2024
If v4 fails to install, try versions 4.5+ because they should be backward compatible with v4
Nov 13 2024
Install the latest .NET Framework.
Nov 8 2024
Switch to the stable branch until a fix is released on the performance branch.
Oct 23 2024
Oct 20 2024
Looks like this is a bug in the simulation of "ThingX". The object is "stopped" after 5 seconds, because the game forgets to mark it as "moved". (it keeps getting moved and immediately stopped in the same frame...)
A simpler example:
ABCDEF = "Land_Football_01_F" createvehicle getPosATL player; ABCDEF setVelocity [0,0,100]; TimeCreated = time; TimeStopped = nil; onEachFrame { systemChat str [velocity ABCDEF#2, velocityModelSpace ABCDEF#2]; if (velocity ABCDEF#2 == 0) then { if (isNil "TimeStopped") then {TimeStopped = time}; systemChat str (TimeStopped-TimeCreated); }; }
Does this mean the developers are using a new compiler or new compiler flags starting with v2.18?
Oct 19 2024
It appears this is due to a POPCNT instruction
F3 0F B8 C0 = popcnt eax,eax
Oct 13 2024
The issue is reportedly fixed on the profiling branch. For now use the profiling branch on both the server and clients until a hotfix is released.
See the #perf_prof_branch channel on Arma Platform Discord server for more info.
Oct 9 2024
The error is from the next line:
_dirToEnd = (abs _dirToFront / _dirToFront) - _dirToFront;
Sep 26 2024
not sure if I should open a new task due to the OS change
You can edit your task (I already did it for you)
Sep 24 2024
Paste the exact error, or upload the RPT file. Read this:
https://community.bistudio.com/wiki/Crash_Files
If you're referring to the launcher error, you're probably missing .NET Framework.
Sep 17 2024
Sep 16 2024
If you have "massive logs" it's probably because you have a bad or broken mod. (it still depends what you mean by massive)
Sep 5 2024
Sep 3 2024
Sep 1 2024
Jun 10 2024
Actually nvm, wiki says ligthAttachObject is not suitable for use on moving objects.
Jun 3 2024
Using findIf is even faster. Another implementation is:
params ["_array", "_value", ["_column", 0]]; private _valueArray = [_value]; private _column = [_column, 1]; _array findIf {_x select _column isEqualTo _valueArray };
May 26 2024
This is not related to the game itself. It's related to Geforce Now not supporting ACE3's extensions.
there's nothing on the internet about it.
May 16 2024
May 11 2024
Sorry, closed it by mistake 😅
Apr 24 2024
Apr 19 2024
Normal is fine too:
Apr 17 2024
It's not broken. You're using an old version of the game. As the wiki says, the command will be available in A3 v2.18. (you can also try it in the dev branch right now)
Apr 10 2024
Should be fixed yes. Please try the latest dev branch update and report back.
Mar 4 2024
Feb 26 2024
Should be fixed with the next dev branch update
Feb 2 2024
They are local.
Jan 29 2024
Looks like removing all action "preprocessings" was a bit too much and it breaks some actions. I'll have to go case by case