Gasalon

What works for me is to get the nose wheel on the ground asap. Otherwise the same thing you described happened to me all the time. Whether or not this realistic I don’t know.

In the hornet I always caged it to get an accurate vertical position. You had a 2nd marker at the actual position which I used to determine drift and I hoped it would be the same here. At very high crosswinds the marker it is outside the HUD if you don’t cage it and you can’t get accurate readings neither horizontal nor vertical which makes the landings harder for me. Thanks for the clarification though I guess I’ll wait until it works then

Not sure if it is a bug or my own stupidity, but I can’t cage or uncage the velocity vector on the HUD which makes high crosswind landings a real pain. According to the manual the left multifunction button on the throttle should do that, but doesn’t work for me. Keybindings are correct… does anyone else have this issue?

I noticed that several keybinds are not working allthough correctly assigned (tested both HOTAS and keyboard) Its not a full list but these are the one's I remember: Pilot Seat: Nav FLIR knob and selector switch; WSO Seat: MIC Switch; PODS Switch; ICS Switch With the mouse I can click all of them and they work. Does anyone else have this issue?

Much appreciated

I did not say that the campaign should force users to cold start, my “yep” was just confirming the posts before that were asking for such an option. I have bought all Hornet Campaigns so far (didn’t like Rising Squall for the same reason). Cold Start is an integral part of a mission for me and a deal breaker if such an option is not offered.

Yep Hot Start only makes this a definite “do not buy” thingy for me

Does anyone know what the 3 switches below the IFEI that control tape recordings are called in the key binding list? I can’t find them

For me the crash is somehow related to using external cameras. Twice it crashed immediately after using F2 view and cycling through air targets. On the third time when I did not use external views it worked perfectly

Here you go (files are too big for the forum) Single Player TLAMs working Dedicated Server TLAMs not working

Hi everyone, I have a weird issue with Combined Arms and Liberation Syria, not sure who is to blame. When flying the mission normally on my computer I can control all units on the F10 map and engage with them. When playing the same mission on my dedicated server (single player, 2nd Computer in LAN) I can control everything and engage with all units except with ships... Whenever I select attack target and click on the map the crosshair just disappears and nothing happens. Tanks fire normally using the same procedure. In Single player TLAMs are launched correctly. I tried both from in cockpit and as battleground Commander, same result... Does anyone have an idea what's going on here?

Didn't save the track file unfortunately. The mission file is too big to upload it here, but here is a link: https://easyupload.io/2zp4o1 It's Mission 8 from the free Oil in the Water Campaign But the "Ground Repair" should fix any of that shouldn't it? The pitch ladder issue should have been gone.

Hi all, My F/A-18 showed very weird behaviour yesterday and I wanted to get your opinion if this could have been a random failure (option is turned on) or if it is a bug. After egressing from a bombing run my HUD suddenly completely froze. DDIs were responsive except for the button to go the menu. That one was also unresponsive as was the UFC. I did not take any damage from enemy fire during the run in and no warning lights or error messages appeared anywhere. I climbed to A35 and switched off both engines then did a windmill restart after the generators went out. When power was back on everything remained unresponsive except for the HUD. It was working again but the flight path indicator position on the pitch ladder was wrong. When it was at the horizon line I still had like +500 positive climb. I diverted to a large airfield and managed to land the jet safely then taxied to the parking area and completely shut the aircraft down. I selected request repair from Ground Crew menu and once complete restarted the jet. When doing INS alignment I obviously had no STD HDG option but the alignment was really quick (like 60 seconds quick) before OK appeared and I pushed to IFA. After take off every system was working normally again except for the mismatch of Flight path indicator and HUD pitch ladder. What are your thoughts on this? Random System failure or bug? Regards Gasalon