pls detele this

This does not seem to occur in multiplayer, however; the reticle is accurate to the little static crosshair both when shooting the ground and locking on to an air target.

it happens everywhere. Tried on different maps (Vanilla ones). You only need to reach zero km/h after you started the plane. Then a parking brake gets applied which can only be released by pressing the digital thrust increase key.

I'm getting the same crash, except the message is generic 'Arma III has stopped working', no error code in the pop up. I had logs off, I've turned them back on to hopefully capture what's happening.

Ulairi has it right it's those items that you used to be able to right click and drag to change the size and now you can't do that

Being that this has only changed as a result of the Jets DLC, the common thought here is that it's the preferable way to fly a jet. As anyone that has flown a chopper in the last 3 years can tell you, this new camera for choppers is complete garbage. There should be either a way to toggle the option on or off, or just revert the old camera back for just choppers. It's hard to comprehend how this was missed? Has anyone from BI ever tried to do a fast extraction before, cos you cant do it now. Takes me longer to land a chopper now than it does to get drunk.. Common BI, lets fix this.

I've using AIO-RUNTIME for fixed C++ . And Arma3 start well ....

Another one.This one occurred while I was tabbed into the game doing some testing. Didn't crash my driver completely this time so I didn't have to hard reset. Error at the bottom of the rpt looks the same though.

Based on testing done 5 minutes ago, the approximate view distances for different PiP settings are as follows:
Low: 300m
Medium: 400m
High: 600m
Very High: 1000m
Ultra: 1500m

Can confirm.

Please fix this even with head tracker it sucks. This should be a high priority. Nobody landed a heli during testing? How could this be missed? Why wasn't it addressed before release? How about that unfinished half-assed carrier. WTF BI?

Second time today. Happened shortly after I alt-tabbed out of the game in the eden editor. I had turned down some of my graphics settings to see if perhaps that would help.

That solved the problem, the ticket can now be closed.

do you by any chance have a video of such issue?

Duplicate of T124853

Fix in progress, thanks.

Attached in original post.
Thanks

We will fix this in the next update. Thank you.

Another crash, this one killed my display driver completely so the screen input ended and I had to hard reset my computer.

Completely agree, has made the flying of helicopters pretty much impossible for me. Hate it.

In T124853#1605396, @razazel wrote:

Hello,

thank you for the feedback.

Could you please specify what are you unable to resize exactly?

thank you for the feedback.

Did you try Stable version? Does it happen everytime or only in some spcific situations? (e.g. happens in a custom mission but in editor - VR it does not)

Duplicate of T83081

On the video. I put four UAVs. Cameras sent to one object.
The distance from the UAV to the object is different. I could see in the PIP window, the same object, in different image quality.
https://youtu.be/RYMq7Kucazk
There is a drop in FPS when the PIP camera window is active. But the fall of FPS is the same everywhere. It does not depend what kind of picture quality I see in PIP. The fog does not reduce the fall of FPS and the absence of fog does not increase the FPS drop. I do not understand why you can not remove fog from the PIP window? Make the range of visibility in the PIP window equal to the overall visibility in the game.

https://feedback.bistudio.com/T83081

confirmed. works fine now

I have to agree it's 10/10 for Jets but for Heli's is not great.

Issue still present

In T124835#1605315, @Gnashes wrote:

If BI ever decided to explore a method for "multiple admins having access to debug", a compromise for security could be done via some method similar to the following:

enableDebugConsole = 4; // available to all admins identified in server.cfg admins[]

This would essentially allow server owners to either allow only logged in admins to access debug and many admins use the #login command(eDC=1), or to allow access to the debug console for all whitelisted admins who may also login with the #login command(eDC=4).

A thought, at any rate.

Gnashes has a good idea please fix this or implement a workaround for us so we are able to have more than one admin with the access to the console. Please do not ignore this BI thank you.

If BI ever decided to explore a method for "multiple admins having access to debug", a compromise for security could be done via some method similar to the following:

I also get stuck with the Hunter:

I can confirm the symlink fixed it on CentOS 7.

Here is mine:

There was security flaw in debug console that allowed to launch it without any permission with relatively short code. This has now been removed. Leaving this flaw would have been far worse for everyone running public servers than a little inconvenience for a few people that exploited this flaw for own benefit.

Should be like this.

Agreed change it back its absolute rubbish.

Placing backpack inside other backpack, entering arsenal, backpack inside disappearing.

I don't really know but i notice that the back of aircraft carrier (the one a little bit down where you can put a turret) is correctly calculating hitbox.
Btw when i put an object in zeus on the aircraft carrier, he's leaning, he isn't flat.

I've started to encounter this crash after the 1.70 jets update. So far it's fairly inconsistent and I've only produced it during development work for ACE - seems to happen while I'm alt tabbed out of arma working in my text editor. Has happened while idle in eden, while idle in game, while idle at the pause menu. Seemingly always when I'm tabbed out though.

+1 Pretty much everyone on Olympus is upset about the new 3rd person heli camera and wants it to be reverted to the old one.