All Activity

In the next DCS update, George AI Pilot will be receiving some improvements to his existing logic and behavior in an effort to make him more realistic along with several new features to make him more capable. The most noticeable change is the addition of an AI Helper Interface wheel that functions in a similar manner as what is seen when controlling the AI CPG, which will help players understand which commands are available at any given time. The second change is the addition of a new command to the AH-64D CPG controls called "Multifunctional Input (Center)", which functions similarly to the Consent To Fire command for the AI CPG in that it corresponds with the actions displayed within the center of the AI Helper Interface wheel. Accordingly, the Consent To Fire command in the AH-64D Pilot controls has been renamed to "Multifunctional Input (Center)" to more accurately represent the evolution of this command following the changes to George AI CPG in the July 23rd update to DCS. In the graphic below, the new AI Helper Interface is shown for when the player is in the CPG seat, with some new commands identified when the interface is in Flight (FLT) mode. The player can now toggle the AI Pilot's speed reference between ground speed (GS) and true airspeed (TAS) with a short press (<0.5 seconds) of the Multifunctional Input command; or toggle the AI Pilot's altitude reference between radar altitude (R) and barometric altitude (B) with a long press (>0.5 seconds) of the Multifunctional Input command. One additional change that is worth noting is that the Right-Short commands have been swapped between Combat (CMBT) and Flight (FLT) modes to improve the workflow when using the AI. Now, when the AI Interface is set to FLT mode, Right-Short will command George to navigate the current route; and when the AI Interface is set to CMBT mode, Right-Short will command George to turn to where the player is looking. New Speed Settings & Altitude Conversions When set to FLT mode, the player will have additional speed options, which can be particularly useful when trying to creep along the terrain at NOE altitudes or when trying to synchronize a planned time-on-target. These speed options will now include 20, 40, 60, 75, 90, 100, 110, 120, and MAX, with the new speed options underlined. When toggling the altitude reference between radar and barometric, George will now perform a correct conversion between the AGL and MSL equivalent altitudes based on the elevation of the terrain below the helicopter. This will aid in a more natural switch between altitude references. Ground Operations George can now be commanded to perform start-up and shutdown procedures by accessing the new Ground (GND) mode of the AI Interface any time the helicopter is landed. FULL START - George will perform a full start-up procedure from turning on the battery to preparing the helicopter for takeoff. ENG FLY - George will initialize all systems, start the engines, and bring the Power levers to FLY, but will leave the APU on and wheel brakes applied until the player commands him to turn off the APU and release the brakes. Alternatively, this may also be used to command him to start the APU and apply the wheel brakes after landing. ENG IDLE - George will initialize all systems and start the engines, but will leave the Power levers at IDLE until the player commands him to bring the Power levers to FLY and/or prepare the helicopter for takeoff. Alternatively, this may also be used to command him to start the APU, apply the wheel brakes, and bring Power levers to IDLE after landing. APU ONLY - George will start the APU and initialize all systems and announce when he is ready to start engines. Alternatively, this may be used to command him to start the APU, apply the wheel brakes, and shut down the engines after landing but keep all systems initialized with the APU on. SHUTDOWN - George will perform a full shutdown procedure, to include shutting down the engines, powering down systems, turning off exterior lighting and the APU, and switching off the battery. CMWS ON/OFF - George will toggle the CMWS power on/off. When CMWS is on, he'll set the CMWS/NAV switch to CMWS for combat operations. When CMWS is off, he'll set the CMWS/NAV switch to NAV for non-tactical flights. Defense Settings In order to provide a more efficient workflow during missions, the CMWS mode has been removed from the typical AI Interface flow of FLT -> H-B -> CMBT and can only be accessed using a long press (>0.5 seconds) of the George AI - Show/Hide command. In addition, a new command for commanding George to configure the exterior lighting has been added, and the mode itself has been renamed to Defense (DEFN). The following exterior lighting configurations can be selected using the Right-Short AI Helper command. DAY - Day, non-combat operations. Anti-collision lights set to WHT. NT BRT - Night, non-combat operations. Anti-collision lights set to RED and navigation lights set to BRT. NT DIM - Night training missions. Anti-collision lights set to OFF, navigation lights set to DIM, and formation lights set to BRT. NT FORM - Night training/combat missions. All lights off except for formation lights. LTS OFF - Night training/combat missions. All lights off. Improved Flight Logic George's overall flight logic has been improved, most notably to avoid exceeding the engine or powertrain limitations or ensuring the helicopter has sufficient power for what the player is asking George to do. George will use the PERF page calculations to properly assess the power margins and will now provide verbal feedback to the player if he is asked to adhere to airspeed or altitude parameters that exceed the acceptable power margins for the current gross weight, altitude, and temperature. In addition, he will automatically switch between "nose-to-tail trim" at low speeds and "aerodynamic trim" at high speeds. NOTE: Although George's flight logic has been improved, it is still possible to force him into a situation in which he may collide with terrain or obstacles, particularly when he is being ordered to adhere to extremely low altitudes, operate with a high gross weight and narrow power margins, or fly at MAX speed (or a combination of these factors), the player should use prudence when selecting the airspeed and altitude combinations, and occasionally cross-check his flight path just as a real crewmember will typically do. As an example, if the helicopter does not have sufficient power margin to clear a ridgeline, the player can order George to slow to 75 or 60 knots TAS to improve his climb rate or climb angle. But if that is not sufficient, the player should order George to alter heading to avoid the rising terrain. When the AI Interface is set to Combat (CMBT) mode and the player presses the Up-Short command, George will perform the following contextual behavior. ALIGN TO TADS - George will align the nose towards the azimuth of the TADS sensor. ALIGN TO NTS - George will align the nose towards the FCR Next-To-Shoot (NTS) target. However, if the player's selected sight in the CPG seat is set to TADS or FCR and has actioned rockets, George will turn towards and actively maintain horizontal alignment with the Rocket Steering Cursor for 30 seconds, permitting the player to engage moving targets with rockets or make subsequent aiming adjustments. An updated George AI chapter describing the improvements to George AI Pilot will be included in a future edition of the DCS AH-64D Early Access Guide, but will not be finished in time for the upcoming update. We hope that these new features to George AI Pilot will allow players to utilize the front gunner seat more effectively across more phases of each mission while improving the player's reliance on George's piloting abilities.

He's mentioned somewhere on his Discord that he'd like to do that, but it'll be a significant rebuild. It's an old campaign, after all.

Yes it’s still superb fun, and if you’re interested in helicopters there’s plenty of time before DCS 3.0 (the time were issues could arise) to get your money’s worth. The only bug that’s in your face right now is also a very minor one: the calculation for endurance doesn’t display decimal numbers but I for one display the remaining fuel amount all the time (rocker down twice) so that’s not really a problem.

Maybe a different problem but the game freezes trying to load a MP mission. On Visualizer Starts Simulation dcs.log

Banner image for DCS REFORGER 25-4 Once again it is my pleasure to welcome you back to the next entry in our recap post series about the DCS REFORGER cold war milsim event series. This time we dared experimenting a little and rolled out a new mission format which we titled the "Fighter Weapons Competition". Loosely based on observations made watching archival footage of the NATO fighterbomber competition BULLS EYE '73 as well as reading through reports about the USAF William Tell Shootout of 1962, we aimed to give participating squadrons a certain mission set which focused on core competencies of fighterbomber wings in order to allow participants to evaluate their squadron's combat readiness in key competencies such as: domestic procedures Time on Target adherence Pop Up Attacks Low Level Navigation Defensive ACM in a 2v1 scenario Here are some images of the source material used to formulate our scoring criteria... Score Board as seen in the video about BULLS EYE'73 Score Board as used in USAF William Tell Shootout of 1962 Having gained what we thought to be a decent understanding about what it was that these competitions were aiming to do, we came up with the following general plan for our event. Participants would take off out of Ramstein AB, fly east along the Frankfurt airport airspace and enter a low level navigation corridor. They would then follow the corridor all the way into EDR 16, the for our purposes prepared Wildflecken Truppenübungsplatz, and perform a pop up attack on a circular bullseye target using general purpose bombs. After the A2G section of the event participants would transit and recover at the Fliegerhorst Pferdsfeld, homebase of the host squadron Jagdbombergeschwader 35, and refit for the A2A section of the course. A controller staffing the station at Pferdsfeld would then coordinate a time slot for the participant's 2v1 ACM task of the competition course and dispatch them to one of the two lanes in the TRA Lauter (TRA 205/305) over Ramstein. Once the A2A section was completed, participating pilots would recover again at Ramstein AB and take a break for scoring and debriefing their sortie before they head out again for the second run through the entire course. The recommended route for participants was marked in orange in order to guarantee proper separation along the competition route A closer look at the planning material provided to pilots, pictured here is the low level flying corridor leading into EDR16 And a shot of TRA205/305 including the lane split down the center which allowed for two separate ACM engagements to occur at the same time. Note also the LUCA tanker track right above the TRA. This allowed us to stay in the action acting as aggressors for the participating squadrons for the entire duration of the event. Concluding, it can be said that despite some technical shortcomings as well as being short staffed on the controller as well as the aggressor side, the event was a success and we all had a massive blast flying it. It definitely turned out to be a much different event compared to large scale COMAO style exercises we have previously organised and it left us with lots of ideas on how to improve on this format should we decide to bring it back in the future. I would like to thank everyone who participated in the event, every controller, flight lead, anyone involved in planning and producing briefing material for it and will leave you guys with some screenshots of the event, credit for which in great part belongs to Gen from ALA17 'Toros' who went through the trouble of watching the entire track file of the event more than one time in order to bring us some truly fantastic, mesmerising screenshots. Enjoy... Some photos of the different flights on their departure out of Ramstein AB 801st NAS of JSW during their T/O from Ramstein AB ALA17 'Toros' flying Mirage F1-EE 526th TFS of the Iron Curtain Aviators were also participating again, they put on a very strong performance 601st FS brought a two ship of F-16s to the party As the host squadron of the exercise, we decided to jump into their role when our MiG-21 aggressor pilots suffered a scheduling issue and had to back out of the event last minute. This meant that we got a lot of face time with the Texaco 1 boom operator, which allowed us to stay in the action and serve every flight entering TRA205 with at least one 2v1 ACM engagement. 526th TFS on their strike in EDR16 Though the MF-1EE is equipped with a standard bombing sight without advanced trajectory calculation, the pilots of ALA17 scored remarkably high using the direct delivery method. 601st FS on their run in to the target A couple of photos of the recoveries at Pferdsfeld, the homebase of JaboG35 Lots of action shots from the ACM section of the competition course And some bonus photos from our recovery And that's it! Thank you very much for reading and I am looking forward to hosting another DCS REFORGER event in the near future! If you are are part of a cold war milsim squadron and may be interested in the the type of events we organise, please don't hesitate to reach out and contact us for details on participation prerequisites, event structure and planning horizons. All the best and have a nice week, Rohrkrepierer o7

I want to find this texture to note something on it.

I get EXACTLY the same jitters and jumps which you describe - when I eventually get the headset to talk to the base stations . I do have a ticket raised with customer support but I do not have a response yet. Can you please post here if you find a solution? I does seem like trial and error with the base station setup. Very frustrating.

It has its faults, but its still the greatest helicopter in the game. If you want to fly it, go ahead and enjoy it.

The Dot! LOL If you press Dl, you lose the DOT. So I had no problems. Hehehe

Or open the refuel probe before requesting the refuelling: that depressurises the tanks allowing external tanks to get fuel too. This is still not perfect, as the amount of fuel the external tanks will get greatly depends on how much fuel remains in the internal tanks, but apart from dropping the tanks before landing it’s the best solution - until ED implements a separate slider for external fuel in the rearm/refuel window.

A lot of the terrain size comes down to variety of color imagery and resolution of the elevation map. Flying high, you may not notice, but down low and slow in a chopper, things like river beds in valleys, roads cut in the side of mountains and even farm paddies increase the realism significantly. Sadly they consume vast quantities of bits. And we all like big maps with distant borders.

Not possible. That source code is intellectual property owned by whoever the dev was, even if they have abandoned updating it, so it's not public domain. Even if ED had the source code and was legally able to update it if the dev abandoned it, that still wouldn't allow it to be public domained. A certain other sim that's a modded version of an abandoned sim is only possible because they have an agreement with the owner of intellectual property involved (not the original dev since they sold the IP for it).

Right, so it doesn't actually work yet? Sent from my SM-A536B using Tapatalk

first of all thanks a lot Eduardo. - what he means with the trim is at around 13'35 - what I mean is at around 16'35'' enjoy the trip !

Someone on YouTube cut off a part of the mounting plate to get the pivot point of the Rhino closer: it’s one of the downsides that the Rhino is a bit too far away by default, and the reason I use that Z-extension. The chair is a Monstertech MFC-1, the first iteration so perhaps later versions fixed some of the issues. Also, I checked their website and they seem to have a newer version of the Rhino mounting plate too which allows for some adjustments.

Dropping them before landing is the usual trick. Sent from my SM-A536B using Tapatalk

I would suggest the OP adjust his pagefile as suggested before grabbing another log file anyway. 16 GB RAM with a 2,432 MB pagefile just isn't gonna cut it.

You have the F-18? There is a color mod, so

Thanks for the feedback. It's been bothering me for a while but wasn't sure. I guess in the meantime I'll just drop my tanks before landing or replace it when rearming.

Some awesome aerial footage from, amongst others, the C-130(J?)

Can you please attach your DCS log file. Looking at the text you've copied and pasted here this is not from a full startup into the game, so I'm assuming your Windows is hiding file extensions and this is actually from dcs.log.old if that is the case. You may have a text document named just "dcs" if your Windows is hiding file extensions.

We all have our own preferences. I think it's a good thing that we're moving towards more realistic modeling of RWR's. The perfectly timed dance between missile launch-RWR warning-notch is such a DCS-ism and it makes the gameplay very predictable. Ideally, changes would be implemented for all modules, but it is likely something that will happen slowly over time. A few days ago ED made a post about Mi-24P SPO-10 changes. Aircraft like AJS-37 Viggen, JF-17 F-4E, F-14 already has complex RWR's implemented. Upcoming F-14A (early) and F-100 will also feature a more complex RWR. Modern fighters like F-16C, F/A-18C and JF-17 is obviously a little more problematic. But they are not really the main opponents for the MIG-29A Fulcrum. I am all for options. Don't get me wrong. Some players like a more accessible and gameplay-like approach. That's why I also suggested adding R-77 as an option if we're already asking for more SPO-15 options. Possibility to tailor the aircraft to how the players want to fly it.

Yes. Let's say Flag 3 is for a random value between 1 and 3 inclusive. Set that on a Mission Start event. Then for the Condition of the aircraft start/activation you do this: TSF xx 1200 Flag 3 = 1 OR TSF xx 2400 Flag 3 = 2 OR TSF 3600 Flag 3 = 3 Is that what you are looking for? WC's Flags.txt

Platform: Windows 11 DCS version: 2.9.20.15384 Steps to reproduce: Open Mission Editor. Create an aircraft unit with a waypoint. On the waypoint, add an Advanced Action "Perform Command > Script File" and select a .lua file containing the single line: trigger.action.outText("command executed", 10) (Optional) In the same waypoint also add a "Perform Command > Run Script" (inline) action with a similar "trigger.action.outText(...)" line for comparison. Start the mission and fly the unit over the waypoint (or let AI reach it). Expected result: the message "command executed" appears for 10 seconds when the waypoint action triggers. Actual result: the inline "Run Script" action executes and shows the text, but the "Script File" action does not execute / no message appears. Additional info / notes: I checked the DCS.log for Lua errors after mission run. There were no visible errors. I verified the .lua file was embedded into the .miz (opened the .miz with a ZIP tool and saw the Lua file under l10n\DEFAULT path). Attached files: Minimal reproduction mission DCS.log from the run Please tell me if you’d like me to attach anything else. Thank you! bug-wp-action-script-file.miz dcs.log