Hi there,

In T124112#1601926, @razazel wrote:

Hello,

new RC is out, would you mind trying it in there?

Thats a windows thing.

Bump.

Can also recreate since the x64 patch went live:

Cpt Rogers did you test the RC Branch?

I have been having the same issue with my rig.

i have the same problem with ASUS Strix 7.1
if i change the sound device while ARMA3 is running the game souds mute and im forced to reboot the game to get thee sounds back
very annoying during long missions

Related to T76306

Just retested an no crash this time until after an than believe it was out of memory error, maybe related, maybe not.

Even after re-launch of the plane you need to first deploy the hook and then undeploy it!

Still present with Dev Version: 1.71,141530

Dev Version: 1.71,141530

Thanks a lot!

Oh it works with latest DEV Branch :D Consider that as fixed.

In T124667#1601780, @oukej wrote:

The HUD should already have it displayed ;)

I am seeing this as well, in version 1.68.141.205.

corrected in 3 may dev build, please close

I can confirm as of the 1.70 RC the issue is still there. Minor but it is a distraction since it makes it hard to see the deck with the HUD overlay blocking.
http://i.imgur.com/LwuOCW5.png

new RC is out, would you mind trying it in there?

Thanks, we will check this as soon as we can.

Getting the same issues stated above

+1
This is the main difficulty for scripting something consistent with Arma's engine.
Commands are not endless command. I mean. You are waiting for some evident result but many commands are struggling against the engine.
In a "perfect world", Arma's engine should work as is until a script runs a command acting on unit's behavior. At this time, this command should overrides the engines until another parameter or a cancel command.
The list of "disapppointing" commands is not exhaustive but consider:

Hello Ketrab, so now you get more info from me. I have Arma V-1.68.141205 Vanilla no Mods. In 1st Person there are no shadows of NVG with Helmet, Cap or other headgear it makes no difference also i testet various variants. In 3rd Person shadows are visible. My graphic settings are all on ultra. The next one, there are no muzzleflash on KatibaGL only. The KatibaGL has muzzleflash in 1st Person but not in 3dr Person in freelook. Unit with KatbaGL not self played has muzzlflash.

Fixed in DEV 1.71.141501

I thought Oukej said it would only be 8km? To be clear, I don't mind it being 10, it's just a mismatch between the display and the observed detection range. Can't actually lock so it's not that big a deal.

The HUD should already have it displayed ;)

Oh ok. Now it works normally, don't know why but thank's for your help.

@oukej Yeah scripted like in Arma 2 :D But it would be still great to have such keybind because atm we also don't have an addAction for that so there is no way we could fold and unfold the wing without writing an addAction ourselves.
And for the tailhook is pretty hard to hope to catch the addAction for it while landing because I would conzentrate more on the correct angle of approach instead of trying to find a Tailhook down action in the list.

The Render distance ist specified in the Mission.

macOS Sierra version 10.12.4

Agreed, I find it hard to believe that these Air Superiority fighters can bleed airspeed in a hard turn to the point they are well below flying speed.

I found out that the 750 m only appear on 1 single server, but the rendering distance could'nt be changed

Hey! Thanks for the report!

not sure, but could it maybe be because the enemy jet has the active radar on?

Yes Yes! This should really be implemented. Would be much easier and I wouldn't need to get my hands of the Throttle or Stick in order to launch from the carrier. Also the Tailhook Up/Down would be great as using an action in such danger situation is pretty much unacceptable (atleast for me) as trying to hit the action is pretty difficult when focusing on the landing.

at least 3 and 4 are retracting as of 05/02/2017. 1 and 2 are not working #T124670

3 and 4 are retracting as of 05/02/2017. Only 1 and 2 are not operational. #T124670

seems fixed as of 05/02/2017.

Come to think of it, could be related to the Shikra, since I had a crash with it last week too...