Amarok_73

Yeah, I've learned this lesson already long time ago, that any serious testing have to be done in fully controllable environment, where influence of secondary factors is minimized.

Same here, In F-18 I am operating only from the sea, so on the multiplayer mission where I was struggling with this issue I've had not to mess with Anti-Skid, but then I observed on Your track, that You did it, what remind me, that when starting in the air, this is one of necessary steps.

But indeed it means that full flaps is one of requirements for hands free landing?

FINALLY! I made it, this time I verified that Anti Skid is off, but most important difference from my previous attempts was using full flaps not the half...

Yes, I am "spamming" with CPL when ACL RDY/ Mode 1 appears, but every time i press CPL it causes message "Auto Pilot" to appear... When flying on Tacan, he have no problem to keep on it.

Indeed... track is then here. ACLS problem.trk

Both, usually I fly the multiplayer, but just now I've decided to prepare clean mission and try it in single. Effect the same. Here's the track for anyone patient enough. And yes - I know, I've botched a little the procedure regarding the altitude and speed keeping, but it's like sixth CASE 3 landing today and I am quite tired already... test ACLS.miz

For both replies answer is yes - I do that, just forgot to mention as it is so automatic, but Mode 1 on display answers it anyway. And yes, I am trying to fly according to real procedures, so I am using the ATC at the first landing attempt, then in the case of bolter, I am going into the manual control. Anyway, it seems, that I do everything in order, inferring from lack of such replies, I assume there's no any bug pending related to this subject, so... I need to check in details my moves. Thank You for the information @Zodiacc and @Q3ark!

I'd like to ask what can be the reason, that I am unable to go fully automatic down to the deck when riding the ACLS. the ALS is set, Mode 1 is visible on it, tadpole is on HUD, the FPM is in line with it, I am trying to CPL autopilot to P/R, and nothing happens... What did I forgot about?

We have removed all the mods (I suppose), and the only thing modded we're using is the custom skin. May it be the source of the problem? Could You point me please, to the lines from log file referring to the mods? I'll try to investigate it from this side...

And some more crash logs... dcs.log-20221003-185023.zipdcs.log-20221003-184941.zip

Friend of mine is encountering regular crash that is related to F14-Avionics.dll, but only when we both are flying this plane (me on RIO position). This is VERY annoying, because practically every take-off have to end this way. This seems to happen always in situations when we engage enemies, and there is a lot of commotion around us. I wonder if the line "0x0000000001D4BD5D (DCS): AmdPowerXpressRequestHighPerformance + 0xED7D59" can be any hint in this situation. Here's the package of couple of his Crash reports. dcs.log-20220906-172829.zip dcs.log-20220803-185244.zip dcs.log-20220629-204950.zip dcs.log-20220616-114344.zip dcs.log-20220918-203147.zip dcs.log-20220929-201733.zip dcs.log-20221002-135751.zip dcs.log-20221002-134632.zip

After the recent (?) patch, PERFormance page seems to be not working.

Hello, As in the subject title, the extremely high or low pressure setting for Apache is not possible, while this can be set from the Mission Editor. Ah64 high and low preessure setting issue.trk

I've reported it already in other thread. To be able to get into the "Underlay" menu You have to deselect the TADS with T6 button, then click VIS. That way the menu will become persistent.

Another minor issue implemented in last patch is related to VIS button. Both the IHADSS and VIS issues can be observed on attached track. IHADSS behaviour is shown as is correct before the live CP/G joins the cockpit, and how it works after join. server-20220922-210054.trk

Here it is. I've added little wind to see if it causes turning the heli upwind, but it seems that this is not that case. Yaw issues.trk The HOTAS I am using is Logitech G940.

I understand, but current behavior is far from what I'd expect in situation, when the SCAS is disconnected by pedal input. I have just got into stable hover (as a side note, it's pretty easy after recent patch), no foot input at all, and then suddenly _very_ sharp right rudder appears, causing almost unstoppable turn. I have not had the controls helper on the screen, so I can't tell now if there was visible input on yaw axle, or it was still in the position set for the hover. Speaking about controls helper, I've also noticed, that now the collective inputs are very quivering.

So far, two major issues found: 1. In stable hover, SAS(?) suddenly causes strong rotation in yaw axis to the right. 2. IHADSS mode is bouncing when switching, when up, then it goes through transision mode to the cruise, when switching to the back, it skips through hover to the bob-up mode. It happens only when live CP/G is present.

Another quite annoying issue with CP/G and his gun is that he's not using the LMC.

@Micr0 Indeed, at 40 kts the deck pitching is satisfactory. But then for the rest of planes, especially the ones that have to land cross wind, ESPECIALLY F-16s and for helicopters such conditions are quite harsh not to say impossible. Pity that there's no separate parameter like "Sea state" that would make it possible to tune down the wind a bit, keeping the waves high.

I've set 13 kts for wind at ground, then for carrier traveling upwind 25 kts, and pitching is barely noticeable to none. LSO's display shows up to 0.1 on both axles. null

Hello @Fuzzel, I really like Your part of job done for F-18. Is there any chance for update, so Bingo settings will work again? And perhaps You could add the option for bullseye waypoint as it is in F-16 module of DCS-DTC?

Still hoping for the correction of this annoying bug. The best time of the day for flying is ruined by this issue...

Please, please, pleaseeeee...?