Dev Build 1.83.144553 the issue seems to have been fixed. Can you please confirm it?
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Mar 22 2018
Have you already tried the possible solutions listed here?
You do realize that you are binding the same control to 2 different things and expecting it to work separately, right?
Hmm tested it and they seem ok. PCML locks as always, the only reason the Nyx and Titan wouldn't lock is that the target couldn't be detected by the IR trackers that both have. Will have a look at it further.
Aaah sorry my bad.
Tested it again. It seems that this issue is fixed in our internal build, will have to wait for the next Dev Branch and test it again if the issue persists.
Vitdom,
I did try to verify game content through Steam, nothing got detected. I re-installed arma 3, nothing changed. I've checked for pc updates and made sure Arma 3 is up to date. Is there a specific update I should check? I never overclocked my pc, I had built the pc myself. I used to be able to play Arma 3 without any problems, the last time I played Arma 3 was like 3 or 4 years ago on the current pc with the current pc parts. I have just tried a couple different MPs, it would load the game, I would select what team to be on and click start, got the error. The first MP I tried, I would walk a few feet and get the error. The second MP I tried, I spawned beside a heli, got in it, started the engine and got the error; it did like a small lag then the error popped up.
the mission should be in the additional information part, either way here it is again https://www.dropbox.com/s/kvelqqakewzn5j4/bis_pip_error.VR.rar
Mar 21 2018
Here is a video demonstrating the problem. I took my hand off the mouse (so that I didn't accidentally change the direction that the player was facing), pressed the key to go prone, pressed the key to deploy the bipod and then held Alternate to look at different angles. Clearly the player is hovering in the air, supported only by the bipod.
Hey, thanks for the report! The compass/veh.radar has been removed as a part of sensor overhaul. You can get the heading information directly from diegetic elements or from the info panels (GPS panel, Radar display) - those can be displayed by left or right square bracket [ ].
The AT Nyx,
The Titan short
and the PCML
I think some kind of player controlled setting would work.
Thank you for the report, we will have a look at it.
Thank you for the report. We are aware of the issue, however this was done for performance reasons. The game was more unplayable with overdraw distances knocking the FPS down as much as 10. This was introduced as a way to combat that, we are aware it is not perfect. Perhaps some tweaks may happen in the future though can't promis anything.
I have tested it in your attached mission and I was not able to reproduce the issue. Could you please provide a video of the issue so that I might figure out what I am doing differently?
Thank you for the report. Could you please upload the mission you used for the test?
In T127981#1671229, @Vitdom wrote:Were you presented with any error message when Arma 3 crashed?
Did you verify game files through Steam?
Were you presented with any error message when Arma 3 crashed?
Did you verify game files through Steam?
Same goes for AcinPknlMwlkSrasWrflDb
Still reproducible as of 1.80.
No addons!
CPU: E3-1230 v2
Graphics card: Nvidia GTX 1060 6GB
RAM: DDR3 12GB
Hello (I'm late at the party),
my comment was valid when posted and was concerning Arma 2. It seems this behaviour changed in Arma 3, I then invite you to add your note.
My comment was about an observed behaviour at the time and is obviously not the official word for it ;-)
Did you try and verify game content through Steam? Were any files redownloaded?
Make sure you are using the latest drivers. How much is your system overclocked? Does it also happen in MP?
In T127950#1671011, @Wulf wrote:It is really odd haven't noticed anything like this, nor can I trugger it.
Mar 20 2018
I remember there was information about the repair and it seems that it really works but I will check it again in the RC and DEV versions.
It seems fine now. Thanks!
Sorry for late reply
I'm also having minor texture flickering in the Varsuk
AMD Firepro W7000 4gb
Wulf u running AMD or Nvidia?
This should be fixed. Can you please confirm this?
Which launchers did you test?
Hello,
As you can see in the video, the mission size is 21,8Mb.
There are only Altis Life needed mods on the server : @extDB3 and @life_server // No clientside mod
I did the ticket for this problem too.
T126258
But there is a ticket of 2013
The problem is reproduced on any riflescope where there is a smooth change of zoom. On the riflescope where there is a step-by-step change of zoom, the problem isn't reproduced.
Should the issue resurface, please let us know.
I seems to me there is no more problem since windows or nvidia last update (I can't say).
Thank you for the report, we will have a look at it.
@Lex That's the exact same issue I'm having.
Both of them are alright and intended.
Here you go. Notice how the rounds zeroed at 2600 m impact much closer than the rounds zeroed at 2400 m.
Talked with the designers and they don't know of this controller. Could you please send us screenshots of the option menu in Arma 3 as well as settings of the controller from Windows? We want to confirm how many Axis you have.
It seems that this was fixed in the process.
Could you please add a screenshot or a video of the issue that would be very helpful.
I tested this in our Dev branch and I am unable to reproduce this issue. The view never locks in the zoom. Could you please test this in the Dev branch if the issue persists? If it does then please make a video, I need to see how exactly you are triggering it.
Thank you for the report, we are aware of the issue. We will see what can be done about this.
Thank you for the report, we are aware of the issue and working on a fix.
Instead of a Hard-Restart of the system, try hitting WinKey+Tab and create a new Desktop to kill the Arma3.exe process.
Yes, thank you. This undocumented behavior lead to confusion from my side. After talking with @reyhard this was cleared up.
How big is the mission? Are you using any other mods?
This should be fixed in the next proper update. You can test it on Dev branch.
It is really odd haven't noticed anything like this, nor can I trugger it.
Ok, we will have a look at it.
@ckappslive Please create separate ticket for this issue, you might think you have the same problem when in reality the reason behind it might be completely different.
I have the same problem "Bad Module Info"
In T127950#1670920, @Wulf wrote:Hello.
Does this happen on a specific map or location? Because I am not able to reproduce this issue.
Mar 19 2018
Tested and still present in today RC, v1.83.144509
it happened in the devBranch before the RC as well as in the RC, I need to re d/l the current devBranch to check.
@Vitdom I actually discovered it via using the Ares plugin for Zeus. It seems to occur in virtual garage no matter how you called it
Sorry, All works
Thank you for the report. We are aware of the issue and working on a fix.
It could have been the MSI Afterburner, Arma 3 is known to have bad experiences with afterburners as they cause more issues than benefits.
Oh, you are right in the RC release the problem is fixed.
Probably due to the PhysX update.
That's nice.
So i just checked the Tank DLC dev branch. Seems to be a little different but still the same issue.
So what is wrong with this issue report that nobody replies or assigns.
It has been about a half year without any significant change to this bug... and i know
i'm not the only one having it.
Ok, thank you for the information. We will have a look at it.
Yes, it would help a lot to know if this issue occurs regurlarly. We would be very grateful.