Recluse

OK I got all the files in now, and it is working fine. Sorry for the bother!!!! Color me embarrassed!

Indeed Radio1 brings up the menu. (and comms work fine with the Carriers and Airfields) To complicate matters, there may be something messed up in my install. I posted here and on the discord that there is missing information on the STRS-->AG MDI which doesn't seem related to any installed mods as it seems to work OK with the previous version. I have downloaded and re-installed the mod several times and it remains the same. FYI, this is the RAR file I used to install the files: EDIT: OOPS... might be MY ERROR. I double checked and it seems I might have missed some of the files in the COCKPIT folder... Let me install them and double check before you waste your time on my oversight!! VNAO_T45 radio2+fixes.rar

Thank you for the reply!! Indeed, using the mapped Key command or the HOTAS binding for COMM2 did NOTHING. Didn't bring up the menu at all. I put in your files as they were, but here is the relevant section in case something got messed up: Here are the bindings I set: Originally I did not have a key command, but I added it just in case. The HOTAS switch responds in the Key Binding screen, just not getting any menu in game. null

It seems to me that the T-45C doesn't like more than one carrier of ANY kind even if different units with different TACANS: 1) I had some old missions with both a SuperCarrier (CVN-71 - TCN 71) and the Stennis (CVN-74- TCN 74). When I added Goshawks, I couldn't get the TACAN to work AT ALL. EDIT: I realized that this mission was using the AIRBOSS script, so TACAN was set there NOT in the Mission Editor. Maybe this is the problem HERE.... 2) I created a mission from scratch with ONE SuperCarrier (CVN-73 - TCN 73). TACAN worked like a charm. 3) I added another SuperCarrier to that mission, (CVN-71 - TCN 71). TACAN worked for the original 73 but NOT for the added 71 (TACAN SET in MISSION EDITOR. NO AIRBOSS SCRIPT) I didn't try DELETING one carrier from the older missions...but I will. Note: I installed the files from @deeleyer from the DISCORD site which have the TACAN fix as well as the other fixes. As an aside, I still could not get COMM2 to work even when mapping a key command in addition to the HOTAS command in the bindings.

Thanks @Rudel_chw. My problem is that my MFD doesn't show the SINGLE selection or the RPPL button. Thinking it is some incompatibility with another mod, or something odd with the install. Will troubleshoot and see what I can find. EDIT: ODD! When I reinstall the previous version, I see the RPPL button label and the ROCKET: SINGLE legend in the MFD null

Extract the Folder VNAO_T45 into your YOURNAME\Saved Games\DCS\Mods\Aircraft folder. NOTE your folder might be called something different (e.g. DCS_open beta) or something. If you have never installed any mods before, you MIGHT have to create the Mods\Aircraft folders under the Saved Games\DCS_whatever folder

Finally getting some hands on time with this. Going through @Rudel_chw's training missions. Quick question if I may: - in the CCIP bombing training, it is mentioned that by default a single bomb is dropped with each pickle and one of the PB is shown on the left MFD and is referred to as the RPL setting, but there is no legend on the button. I mention this because by default, it seems that if I hold down my pickle button it keeps dropping bombs as long as it is held down. In fact, it is pretty hard to JUST release one. Wondering if there is a way to fix this so only 1 (or a selected RPL qty) drops. Might be my stick, but I can say that I used this button for every other module and it works as expected. - For the RPL qty, again I cannot see how to set this. The QTY buttons don't SEEM to do anything, but I may not have found the elusive RPL setting. Thanks!!! EDIT: I am thinking maybe there is interference from some other mod causing issues. I looked at an OLDER video (PRE-1.2) but I can clearly see the RPPL legend on the button which is also in @Rudel_chw's video from the 1.2 tutorial.

@Coldemps In case you missed the videos above on the Redk0d clickable mod: It is quite old and has not been worked on for some time, but it still works. https://github.com/RedK0d/CLICKABLE-FC3 (1.1.1e latest) There is a later version, actually 1.15 (which I use) https://redk0d.gumroad.com/l/fvkodo More information and some installation help can be found on the Discord https://discord.gg/vmb6JtZ3 It provides partially clickable cockpits for FC3 aircraft. It still works, though it is a little more difficult to get working with the F-15C which requires a different installation method. Works well "out of the box" with the other aircraft. Not all the clickable switches are Animated, but it definitely does add to the enjoyment/immersion of FC3 aircraft (IMHO)

Took the DAP for a ride with Hellfires. Had a CTLD AUTOLASE JTAC on 1688. Got about a 50% hit rate. I was assuming a max range of 8 km like the Apache, but I had to get a bit closer. Thought it was like LOAL, so for some shots I didn't have the reticle close to the target. Worked a bit better when the Reticle was closer to where the target was. Any tips on range and aimpoint for best results? Thanks!!

Err. maybe I was mistaken here. Don't remember the numbers, but it DOES look like it is starting from a later point. Slow download made the time look the same as it did originally. As an aside, I tried to EDIT my original message, but all of a sudden I do not seem to be able to edit any forum posts. I get a red "Required" at the top, but no indication of WHAT is required.

Hmmm that wasn't my experience. It did not register what had already been downloaded and unpacked. It started from scratch again (and crashed again). Too many MiG-29 lovers out there

Ugh.. server crashed or was too busy about 75% of the way through the update...starting over

LOL!! I was just coming here to ask about this!! Sad to lose my daytime AN/AVS-7 HUD, but I guess I will survive

Sounds great, but do I read correctly that there will be no more HUD (AN/AVS-7) without NVG's??

Hi, @Bartek16194 Just started to play with this. I have a mission with High Scattered 2 (Cloud Base 8202 feet) and otherwise perfect conditions, with 0800 start but I keep getting the Case 3 recovery due to "Cloud base <1000 ft or <5 NM visibility). Did something change in DCS that makes the weather extraction seem off, or did I forget a setting in the CRT.lua? Default DCS logic always gives Case 1 for these conditions. Pretty sure I have the latest version. GitHub says 2.2 but the script still says 2.1. Date of files is 21-MAR-2025