Vettefan

Works well for me in 2.7.3 with the T-45 v1.0.1

Yes, they are since 1.01 (current release). You may also want to check the release notes on the first page of this topic.

appreciated!

Hi @Pieterras, Thanks for your detailled reply to my question and also pushing me to into the right direction. You are appreciated! Cheers!

Great find! - I also found that file as one of my references during my research but I was missing the scores-requirements in that file (that's also what triggered my question initially). Source (page 11): One could assume that e.g. 10 arrested landings, all with a "Cut"-grade would be enough be qualified, as the plane was technically "landed" on the carrier. This is why I was / am also after real-life references. Cheers Edit: Typos corrected

Thanks, @Nozzle! Appreciate your great explanation and insight. Cheers

Hello, This is a bit of a nerdy question. I am tracking my progress in carrier landings and I would like to know whether my scores would actually meet any official requirements to be CQ'ed "in real life". Unfortunaltely, I could not find any solid information in any NATOPS manual on the carrier qualification scoring details... Is there anyone (maybe a real CQ'ed pilot) out here who happens to know the following in particular, or anyone who has some guideline on hand, covering the following: the minimum scores to be met in terms of passes and boarding rate? Are there night-flights included and are they counted differently in any way? - if yes, how? Would the CQ score for initial qualification and also permanent qualification in the squadron be an average of a certain amount of passes (how many passes in average? Long story short: Is there anything like "past x passes of score y and boarding rate z" to be carrier (re-)qualified? Many thanks in advance!

Hi @Flappie. Thanks for looking into this matter! After a couple repairs and checks, I I just went the hard way and re-mapped my (most important) key-binds from scratch. It seems to work now. Cheers!

In the last patch (1.01) the team updated the keybinds. Please check my screenshot below how I see it in the options now. I hope this helps. Cheers. Update: I was really pleased to see the update for keybinds, as for business travel reasons I have to sometimes use an Xbox controller setup...

Minor thing I noticed: All my flights are recorded as night-flights in the logbook (I actually flew 95% day and 5% night so far but day-flights shows 0). Not a big deal for me but maybe a topic to be investigated for one of the next updates in future.

Stellar job! Thank you so much for this great update. I am really, really happy about these improvements. Cheers!

it is indeed so much fun! Devs did a fantastic job!!

This is something that was addressed a couple times ago on the previous pages, as many guys here would like to see this feature (me included for the reason you mentioned). It was addressed to the devs so let's stay tuned.

Same here: SP only (so far), no SRS installed and all works well.

I did have the same issue (as quite some other persons here also seem to have) and posted my very own solution approach to this issue a couple pages earlier: Norton AntiVirus defined the VNAOT45FM.dll as malware and constantly quarantined it. I set this file as an exception, re-installed the mod, and now I can enter the cockpit without any issues! Also, you may want to check to have the right plane selected: it shows "Hawk" in your screenshot. Good luck!

Still, as requested already a couple times above, I would really encourage the devs to consider the implementation of the usual key bindings (eg. Num+ / Num-) for throttle control as well.

But a new one: Does anyone know whether I can control the engine throttle up / down via the keyboard (Num+ / Num-)? (I cannot yet find an option in the settings, just an "axis control") - I have to currently use my keyboard as my HOTAS needs replacement... Cheers

Had the same issue before: Check that the VNAOT45FM.dll is not quarantined by your virus scanner! - setting an exception in the virus scanner and restoring the .dll from quarantine solved it for me! Good luck!

@MadMaxter: PROBLEM SOLVED: Norton AntiVirus defined the VNAOT45FM.dll as malware and constantly quarantined it. I set this file as an exception and now I can enter the cockpit without any issues! Looking so much forward to testing the bird later! Cheers!

Thanks, MadMaxter. I checked but I somehow always seem to be locked out from the cockpit. I only get an external view and an AI pilot takes full control. I cannot get in either front or back seat at all but seem to be an outside spectator of the flight. This is in the quick start mission as well as in a mission I create by myself (screenshots attached from ME). Appreciate any hints in the right direction!

I seem only to be able to watch the aircraft, but I cannot take control over it... The mod is installed in the right location... (...\Saved Games\DCS.openbeta\Mods\aircraft\VNAO_T45) I also performed a repair of my open beta. Any good ideas? Thanks in advance!

So happy it is released! Great job, guys!! Well done!

Hi, I cannot contact the AWACS (E-2) via the comms.-menu. I am tuned on the correct frequency (can see the status change messages from AWACS) and can see the menu entry active, but the "F7" key does not work to open the menu to see the sub-menus (Other comms.-menu options work fine, navigating with the "F"-keys). Still, mouse-clicking the desired menu item(s) and the sub-menus (for AWACS / Overlord1-1) does work and I get the requested replies from the AWACS. Situation: DCS 2.7 Plane: F-14B (issue re-produced in the F/A-18) Engines running and still parked on Supercarrier Persian Gulf map AWACS: E-2 Thanks for any advise and / or looking into this matter.

Thanks, mate! - that was the missing piece for me! Cheers!

Yes, but I am not able to select my "standard" carrier frequency 127,500 in the radio. Checked that also later in the Mission Editor as a pre-set frequency for the A-4 and it returned an "invalid frequency" error (but only for the A-4E! - my Tomcat and Hornet still allow for 127,500...). When I now set my carrier frequency to e.g. 300,000 and do the same as a pre-set frequency in the plane, it works all fine and I can communicate with the carrier!