Gideon312

Super nice mission so far. I love the idea of the (spawnable) JTAC (on Bagram) to insert where the action is. Wander where to drop him though? Not sure where the action is, whenever you spawn them via F10!

Hey everyone, I recently came across a reference to the AN/AWB-3(V) Monitor Control in the F/A-18C, but I can’t seem to find much information about it. - Where can I find this system in the cockpit? - What does it do, and how is it used in the Hornet? - Is it implemented in DCS, or is it just a real-life system that isn’t modeled yet? Any insights would be greatly appreciated! Thanks in advance!

Absolutely incredible, thanks. I tried the first version in NTTR, but was not pleased with the green outcome. So this is great……

Thanks for your reply, at least I could make the AI flight turn with 30 degs of bank. Not able to get his speed down to 250.

Tried this script as a do file: local unitName = "YourAIPlaneName" -- Replace with the AI unit's name local unit = Unit.getByName(unitName) if unit then unit:getController():setTask({ id = 'Orbit', params = { altitude = 5000, -- Replace with desired altitude (feet) speed = 250, -- Airspeed in knots pattern = 'Circle', bank = 30, -- Bank angle in degrees } }) end Still same result……

Hi everyone, I’m working on setting up an AI flight in the Mission Editor and need some help with getting the bank angle right. Here’s what I’ve done so far: • I’ve added an AI jet (an F/A-18) to the mission with a single waypoint. • I’ve added an Advanced Waypoint Action to make the jet orbit at that waypoint. • I’ve managed to get the airspeed close to 250 knots, which works fine. The issue is with the bank angle during the orbit. Instead of holding a 30-degree bank angle, the AI is flying with a bank angle ranging from 45 to 50 degrees. Does anyone know how to limit or adjust the bank angle for AI aircraft in orbit? Is there a specific setting, workaround, or perhaps a script that can help enforce the desired 30-degree bank angle? Any advice would be greatly appreciated! Thanks in advance!

Changed it to radioMainMenu and it worked. Thanks again.

Subject: Help Needed with Nested Radio Menu - “Fog Control” Issue Hi all, I’m struggling to add a nested radio menu for “Fog Control” under a main menu called “Mission Main Menu,” which itself is within another menu named “RW Training.” Despite using "attachTo:" as specified, I can’t get the “Fog Control” option to appear in the correct submenu. (RW Training --> Mission Main Menu --> Fog Control) I’ve double-checked all the naming conventions for typos, but everything seems correct. Unfortunately, the menu still doesn’t work as expected, and I get the following error (screenshot attached). Has anyone experienced a similar issue or knows what might be causing this? Any help or guidance would be greatly appreciated! Thanks in advance! NTTR_TRAINING_HELO_DML_v1.0.miz

Thanks for your quick reply, and yes it did resolve the issue

Need Help with DML Fogger - New to DML Hi everyone, I’m completely new to DML, and unfortunately, my first attempts at using it have been unsuccessful so far. I’m trying to implement the Fogger module in a mission on the NTTR map. I’ve looked at the example mission and tried to replicate the setup by copying the trigger zones and the “do script” entries in the trigger section of the Mission Editor. I’ve also copied over the weather settings from the example mission (fog enabled, manual settings, etc.). When I start the mission, the F10 radio menu appears, and I can select one of the options, but nothing happens—the fog doesn’t change. I’ve double-checked for any possible typos in my attributes but couldn’t find anything wrong. Does anyone have any idea what might be going wrong? All help is greatly appreciated! Thanks in advance! NTTR_HELO_DML_v1.0.miz

Thanks for the quick reply! You’re absolutely right that I might be overcomplicating things by treating the racetrack like an IFR holding pattern. I’ll give the SA page approach a try and focus more on maintaining situational awareness rather than precise system setups. Using the CRS line with E as the reference point is a great suggestion—I hadn’t thought of simplifying it that way. It’s a lot less work and still gets the job done effectively. I appreciate the feedback, and I’ll definitely check out your sig! Always looking to fly with like-minded Hornet pilots. Thanks again for the advice!

Hi everyone, I’ve been practicing keyhole CAS procedures in the F/A-18C Hornet and need some advice on improving efficiency, especially when setting up a racetrack pattern around a designated Point A. Here’s my specific scenario: • Point A is located 5 NM north of point E (I.e. centerpoint of the keyhole). • I need to establish a west-east racetrack centered on Point A. • The racetrack is 4 NM long (2 NM west of Point A, 2 NM east of Point A). • I have no problem creating an offset waypoint for Point A, but I’m looking for suggestions on how to quickly set up the racetrack and ensure I’m flying it at the correct distance while keeping my sensors on target.

Awesome job, unfortunately the new update with fog makes it unplayable because of the fog. Hopefully it's an easy fix for you.

Tried it on a dedicated server, but the server crashed. Does one have to set it up as an own server?

Hello everyone, I’m having an issue with static objects in DCS and wondered if anyone else has encountered this. In a mission we’ve created, the static objects (like vehicles) show up fine on the Fire Control Radar (FCR) of the AH-64 Apache in Single Player. However, when I load the exact same mission in Multiplayer, these static objects disappear from the radar. This makes it challenging to locate targets and complete the mission effectively. Does anyone know if this is a known bug, or if there’s a setting or workaround to make static objects visible on the FCR in Multiplayer as well? Any help would be greatly appreciated! Thanks in advance! Hello everyone, I’m having an issue with static objects in DCS and wondered if anyone else has encountered this. In a mission I created, the static objects (like vehicles and buildings) show up fine on the Fire Control Radar (FCR) of the AH-64 Apache in Single Player. However, when I load the exact same mission in Multiplayer, these static objects disappear from the radar. This makes it challenging to locate targets and complete the mission effectively. Does anyone know if this is a known bug, or if there’s a setting or workaround to make static objects visible on the FCR in Multiplayer as well? Any help would be greatly appreciated! Thanks in advance!

One of the best missions I’ve ever flown. After the last update, the Homebase has changed, among other things, making takeoff and landing after the mission nearly impossible. Will this fantastic mission be updated again?

Interesting post on Reddit by mbucchia: His suggestion is to uninstall OpenXR toolkit, a piece of software which isn’t maintained in the last two years.

Update: Thanks to everyone for the tips! I’ve applied them and disabled the “force IPD” setting, which has made VR usable again. However, I’m still not convinced if the performance has improved significantly.

Hello everyone, Since the latest DCS update on September 30th, I've been facing poor framerate and performance with my Pimax Crystal VR headset. I read that the issue might be related to the additional OpenXR toolkit and Quadview, which supposedly needed to be uninstalled, as DCS now has built-in support for foveated rendering. After discovering that this wasn't the issue, I reinstalled everything. Additionally, I manually updated the Pimax Play software to the latest version. v1.33.01 Now I'm encountering a different problem: I can start DCS in VR, but I see two different images in each lens, and they don't overlap to form a complete picture. When I close one eye, it feels like I'm shifting toward that open eye. In the cockpit, this makes it feel like I'm sitting on the side of the cockpit. Additionally, the DCS world now appears like a miniature version in front of me. I would appreciate any help or advice to resolve this issue. Thanks in advance!

Flew this mission today (DCS 2.9.7.59263). After contacting Widow (JTAC) and inbound to the target area, the ground fire stopped, and no triggers were set afterwards. Try to kill every target I could find. Did a rearm at the FOB, killed some URAL's, and went back to homeplate. Got a draw (50%) when ending the mission.

Yes I did.

Sorry to hear. It should work. I have the TM TPR as well and don’t have any problems to bind the toebrakes.

Awesome job, looking forward to use it.

Hey everyone, I wanted to share something I noticed while playing the first mission of the UH1 campaign Stormfront. I enabled the "Easy Path Finding" option via the F10 communication menu, and it worked perfectly. However, when I tried to disable it later on, it didn’t seem to take effect. The smoke markers continued to pop up even though I had turned them off through the F10 menu. It seems like this might be a bug. Has anyone else experienced this issue? Cheers!

I’ve got the same problem over here.