I am rather surprised that this has not been addressed. It's clearly a bug. If you run the sample mission it would be obvious. It worked fine in A2, broken by A3. There are a number of other speech related bugs too, such as "say" command not working with lip files, which I believe otherse have already reported.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Jan 1 2017
Dec 31 2016
Also, I just attempted to run my Arma 3 in compatibility mode and an error came up. Here are the details:
Package ID: PCWDiagnostic
Path: C:\WINDOWS\Diagnostics\Index\PCWDiagnostic.xml
Error Code: 0x80070002
Source: Engine
User: DESKTOP-FB87KV4
Context: Restricted
Browsing through the files, my files are different from "System" and on. I have "System.Management.Automation". If that's the correct file, then I have the "v4.0_3.0.0.031bf3856ad364e35" file, then all I have in that file is an application extension called: "System.Management.Automation.dll". C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.031bf3856ad364e35
Maybe my version is different, as I have "v4.0_3.0.0.0...", and my system needs update?
Here's the "System.Management.Automation" file if you need it:
I remember posting an issue similar to this a long time ago too bad it got removed. I am glad someone else is still trying to fight this
Can anyone confirm? I had some issues launching 64 where it was launching 32 instead but i think i confirmed 64 was running and tackir enabled.
Actually not sure if its just me, but it's been working!
Would be nice to play with x64, but without trackir...nope.
Hello,
according to the report its an entirely different file "System.Management.Automation.dll", not "System.dll".
Are you sure that you've send a report for the correct file?
finally, I found the solution. The problem was the windows 7 x32 .now with windows 7 x64 Arma 3 works . thank you so much @Jawsh
@Mr.Epic, attach the troubleshooting report to the feedback tracker. If the report file will not upload directly to the feedback tracker then try uploading it to a free file sharing service such as Dropbox, Microsoft OneDrive, Google Drive, Mega.nz, and so forth, and then link to the report file.
It would appear this may have morphed into an internal application failure that does not "throw" any exception. I run two 24/7 Arma servers (Altis and Tanoa) that both intermittently fail as of the latest 1.66 patch.
email me
Thanks for getting to me so quickly. I have done those steps and now it is redownloading missing files from Arma. Thanks so much from the feedback. @Jawsh
@stax94, I am not able to download the report file. Could you please try attaching (drag and drop) the file to the feedback tracker or upload the file to a more reputable file sharing service? Some examples include: Dropbox, Microsoft OneDrive, Google Drive, and Mega.nz.
@Sebbo, a few questions for you.
This problem is still happening... it is weird you spend so much to update the game but don't fix something that is a big glaring problem that affects every moment in the game. I emailed Roderick from SIMUL and he said the problem was fixed on their version, but it will require BIS to update it on the game's version. This was in mid 2015, and I reported the problem then, but in almost 2 years since then, it has never been fixed.
Dec 30 2016
im good now, thnx alot.
Has anyone found anything yet?
It looks like in 1.66 this bug is solved. Tested it today with a friend again and I was able to lock onto the Laser designator and the missile tracked the laser too.
Hello SirBoston,
I'm sorry for the delay, I didn't forgot about you, but rather run out of options that can be easily done.
Just noticed that setting v-sync ingame disables Crimson framerate target control, if this might be related.
Hello xnooztv,
it seems that you've libraries from two different versions of Launcher combined in one folder, and that is causing the crash. If the verification of the game cache doesn't help, please manually delete the folder D:\Program Files (x86)\Steam\steamapps\common\Arma 3\Launcher\fr-FR\ . This will fix the crash, but also it will remove French localization; to re-download it you have to run the verification of the game cache again.
Hello blackxpade,
the logs says that Launcher can't start because it can't load the file D:\Steam\steamapps\common\Arma 3\Launcher\log4net.dll.
Did you tried to verify the integrity of the game cache as Jawsh suggested? It should force Steam to re-download any corrupted or missing file. If the issue will persist after that and the file exists in the directory (as written above), please try to delete the file and verify the game cache again to force the re-download.
@blackxpade, attach files by dragging and dropping them rather than pasting a wall of text.
@Wyattcox35, try the below possible solutions one-by-one:
@lordcomp, are you able to join other game servers such as official servers? Are you able to play single player missions?
@xnooztv, attach files by dragging and dropping them rather than pasting a wall of text.
Dec 29 2016
@Jawsh
hello sir:-
- im able to play altis life without getting kicked.
- the battle royale is the only mode i play on, which the game crash as soom as i click on a server, i dont get a chance to enter.
- as you requested i removed all the launch option, such as -nolog , etc.
- 0xC00000095 STATUS_INTEGER_DIVIDE_BY_ZERO isnt available on the possible solution given above.
- https://www.dropbox.com/s/y1o25znobhkkelg/ArmaReport_Log_20161229T175646_LENOVO.zip?dl=0
-https://www.dropbox.com/s/sbe7wvx2iwzlqlh/ArmaReport_Log_20161229T192539_LENOVO.zip?dl=0
-now im getting kicked with message like picture >>>> not found. OR battle eye not responding.
i played Arma 3 before , but the problem that i didn't play it from 6 months. perhaps because of the new update ??!!
for the graphic card i have 2 :
1- Intel (R) HD graphics 4000
2- AMD Radeon HD 8730m
<Processor>Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz (4 CPUs), ~2.4GHz</Processor>
<CardName>Intel(R) HD Graphics 3000</CardName>
thank you for the answer . i did what you told me and the problem persists.
so here the link of the report
https://drive.google.com/open?id=0BygRYN9iAGGTam5DWExaemdDT2c
@tbongo, try the below possible solutions one-by-one:
I'm fairly hopeful my issue has been resolved, not sure about the rest of our community.
Won't really know until we get back to our regular arma schedule as some of the files I've uploaded belong to others in our community.
thank buddy it's very helpful
that post is for dayz not for arma 3 dev build
@twintailsfox, this issue has already been reported: T121937. Please search before submitting a new issue.
I could find a better place to put and now i leave this for the admins of these forums to spread this help to other but do warn them not to delete the files as once this is fixed they should re-enter the files to their folder as these could be essential to playing the tanoa map.
So take your mac and go to finder. Navigate your way to library then open application support. Find the steam folder and go to steam apps and from there to common. Find the arma 3 folder and open it. Scroll down to Expansion and open it then open addons. Now find all files in the folder that contain the word vegetation as this is the problem file. Now move all these files to your desktop and leave them there. Go back to steam and play arma 3. You may open it and load in or it may say Bad version 72 in tanoabuka p3d file. Do the same steps to get to the expansions folder and addons folder as described before. But this time move all files containing the word tanoabuka to the desktop. Now your arma 3 should run fine. This worked for me and let me know if it works for you.
So for those of you with my same problem you may get his error message: Bad Version 72 in p3d file: a3\vegetation_f_exp\clutter\grass\c_grassbunch_hi.p3d.
Well instead of having to re download content to switch to legacy branch try this.
I have figured out a better way to fix my problem and i believe it could help others
Hello? It's still not working and I've tried it again and again.
Added information of getObjectTextures from an instance of the bug. Note, bug does not happen globally for all clients, only for some, inconsistently.
@Hazard27, try the below possible solutions one-by-one: