hello?

Still can't after three more months :(

weird, after last nights windows update(or maybe arma's update, I don't notice updates on steam that much) it now displays a crash error

Problem signature:

Problem Event Name:	APPCRASH
Application Name:	arma3.exe
Application Version:	1.32.127.785
Application Timestamp:	543e7ada
Fault Module Name:	eamapps\common\Arma 3\arma3.exe!CreateFX
Fault Module Version:	6.3.9600.17278
Fault Module Timestamp:	53eeb4a3
Exception Code:	c0000139
Exception Offset:	00098f05
OS Version:	6.3.9600.2.0.0.256.4
Locale ID:	1033
Additional Information 1:	1abe
Additional Information 2:	1abee00edb3fc1158f9ad6f44f0f6be8
Additional Information 3:	1abe
Additional Information 4:	1abee00edb3fc1158f9ad6f44f0f6be8

Hello, I've included a screenshot of what came up on my 'xapo*' search, and it included mostly the files you've mentioned. both set of files appear in both the system32 and the sysWOW64 folders

I tried running with the -nosound parameter and it still displays the same error message.

Thanks for the reply!

Still can't fix it, please help

i still can't play the game

Hi, pls try running the game with '-nosound' command line parameter. Also, try searching the windows directory for 'xapo*' and post the results here, you should probably see something like:

c:\Windows\System32\XAPOFX1_0.dll
c:\Windows\System32\XAPOFX1_1.dll
c:\Windows\System32\XAPOFX1_2.dll
c:\Windows\System32\XAPOFX1_3.dll
c:\Windows\System32\XAPOFX1_4.dll
c:\Windows\System32\XAPOFX1_5.dll

anyone?

Changed, thank you.

In all my attempts to find seat locations, the only known way is to work with global units with moveindriver.. ect. But its incredibly brute force, takes up network usage in MP, takes up needless amounts of resources, and made me cringe when I coded it. Basically, the brute force method does not work locally. The only real way of resolving this is by giving out the commands as doctorsheep said, or forcing BIS and the community to add the selection position names in config.

It seems to me like requesting it as a config issue would result in more work having to be done to add the memory points AND any models created by the community not having those points would be useless to me AND memory points added to the config are optional.

The "proxy:" locations are exactly what I'm looking for, they are guaranteed to exist, I just need a way to access them. Whether it be through selectionPosition or a command that just pulls all of the locations into an array like this ticket.

https://dl.dropboxusercontent.com/u/1132210/Screenshot%202014-10-23%2009.24.18.png

Ok, as you wish, I am unresolving this.

I think this is more of a config issue, as we do have the means to retreve this informatin whenever alvailable. Would you like to make another ticket regarding config problem?

Killzone Kid, the only vehicles with memory points corresponding roughly to actual seat locations are the FFV enabled ones (added only after the FFV stage). All other vehicles lack per seat memory points and use general memory points like a single "pos cargo" for cargo seats.

The command is selectionPosition, the problem is the absense of actual selections for the seats.

On further testing, selectionPosition can be used to retrieve memory point positions just fine. Those could be found in config

MH-9

heli selectionPosition "pos driver";
heli selectionPosition "pos codriver";
heli selectionPosition "pos cargo lf";
heli selectionPosition "pos cargo l";
heli selectionPosition "pos cargo lr";
heli selectionPosition "pos cargo rf";
heli selectionPosition "pos cargo r";
heli selectionPosition "pos cargo rr";

Going to resolve this.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

It seems you are either running a smaller resolution than the minimum launcher size (891x690px) or you have your DPI set above the recommended 96dpi, making the launcher bigger (and all other elements as well).

Temporary fix: move your taskbar to a side.

Future fix: we have redesigned the launcher, making it a bit more flat, resizeable and also removed those buttons. These should solve your issue. Check the dev-branch.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Thanks for the feedback! Marking as resolved.

It has been confirmed that the reason for this is a 200MB limit on Steam Workshop - please close thread as 'no bug', thanks!

@DarkDruid ,problem is fixed,i didnt verify the game integrity,sorry for inconvenience

Cheers.

I only experienced the same issue with the development build hence why i asked.

Hi, I am not able to reproduce this issue. Are you still able to reproduce it? Do you use any mods? Thanks

@Shields ,i didnt mention that i am on the arma 3 dev build,i am on the stable build,and everyday i check dev changelog

Sure you don't have the development build of arma 3?

Looks like the game is using single precision found the problem on a duplicate 0018538

Yeah, the engine should really bump the precision on the numbers used in scripts and do a conversion if this gets translated to the graphic environment.

I got the same problem.

dmp: http://puu.sh/dnRHU/d0f20ae057.rpt

• This is the only file i got.

Thanks for the help!

Hey, are there not any other files? I'm talking about bidmp and mdmp, which are crucial for analyzing crashes. Thanks.

upload a crashdump so they can fix ur problem
Hello,
Thank you for reporting the issue.
We need crash dump files from this folder for solve your problem.
C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package please?
When the archive is smaller than 5000k, you can attach it here. When it is bigger, please use some free sharing service and post link here.

How to find correct crashdump file:
Try to make the crash happen
Look into crashdump folder
Upload crashdump with latest date in name (crashdump is rpt + bidmp + mdmp file with same name). Please try to provide as many crashdumps as possible, it helps us investigating the problem in a big way.

Thank you.
copied

Dumps have been found and Uploaded. Thank you for the help.

when i start A2/A3 its minimize .. i can hear the shots are firing but i cant open up the screen

Hello,

thank you for your report and files. It seems that your problem is that DirectX crashes. This may be from various reasons, such as outdated DirectX, outdated drivers, overclocked CPU or GPU [by manufacturer or user] and many more.

Sadly, there is nothing that can be done from our side. I linked this problem to bug number #0000579, where you can read useful tips in comments. Also, please check out the forums page for another useful tips:
http://forums.bistudio.com/showthread.php?147598-Endless-DXGI_ERROR_DEVICE_REMOVED-Crashes

Sorry for the inconvenience, have a nice day.

This has been fixed by the new stamina system.

Agree /fixed.

related to http://feedback.arma3.com/view.php?id=22100

In a infantry simulator game, this should be number 1 to fix,and this is repored since year, since version 1.32 (we have 1.52 now). Thats only my opinion.

This is not my experience, AI definitely seek more cover in Combat mode en they scan better for enemies, for instance behind them. They will also move with me (as their leader), even if it's a bit on the slow side.

But this ticket is not about that, it is about longer range covering of ground, say 500m for instance. The ai will get a bit stuck in aiming down the sights while moving which is not appropriate in that situation.

I just discovered that the problem has something to do with moving in formation. As long as they're in formation, they run with rifle low, with the occasional peeking through the scope, very good. When they are behind, they get a bit confused and start raising rifle a lot or constantly, then they get tired and slow and get even more behind which results in very slow progress.

With the way the AI reacts when in Aware and Combat, there is fundamentally no difference in the two modes. They basically become too afraid to move, even with max courage.

This should now be fixed in the dev branch. Thank you for helping us improve the game!

Related to:

0013494: AI knows about all units of the same side in the direction it is facing (within spotting distance)
http://feedback.arma3.com/view.php?id=13494

0013493: AI is alerted immediately when a unit it knowsabout is killed
http://feedback.arma3.com/view.php?id=13493

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Hello,
from the crashdumps it is clear that your game crashes because of corrupted memory allocator in Windows. There is unfortunately nothing which can be done by us. I'd suggest repairing/reinstalling your system.
Sorry for inconveniences, have a nice day.

Anything I can do more to speed things up???