All Activity

Little add-on for the explTable, WW2-bombs: ["SC_500_J"] = { explosive = 213 }, In use with the Fw-190 D9. Same data for the near relative of the SC_500_L2-model. (thx for the script!)

Updated all Tanker speeds. Updated weather and wind. Updated enemy bombers. Added all modules are selectable slots.

I will if I can get it up and running again. I'm sure if anyone else sees this and have successfully done it, they can post it. Cheers! Sent from my SM-A536B using Tapatalk

Huh, didn't realize that. Shame. And yes, hopefully next year, and by that I mean I want it 1/1/2026 EDIT: I assumed all the FC stuff worked like the Su-25T

Using the legacy F-5E with AIM-9, the tone should not be audible outside of the plane, yet it growls wherever the camera is.

Thank you for the help. I am familiar with the process of editing the lua but it has been a long time since I have done so. If you get the chance to look at your edited files I'd really appreciate it. Thanks, Jim

@OKC_Jim I tried to find the post I used. But Google's AI came in handy. Hopefully the instructions are displayed correctly for you. The instructions are correct, but as you mentioned, the actual line might be different from heli to heli. My computer died, or I would've checked my edited files. I had trial and error a bit to get them working, and they break IC, which is very unfortunate. I so wish ED would let us store these changes under Saved Games for all these indicators. Best of luck! To move the DCS World cargo indicator, you must manually edit the aircraft's cockpit scripts, specifically the cargoindicator_page.lua file found in the Mods/Aircraft/[Aircraft_Name]/Cockpit/Scripts folder. Within this file, locate the line responsible for the initial position and adjust the X and Y coordinates or add a new variable to shift it to your desired screen location. Steps to Move the Cargo Indicator: Locate the Script File: Navigate to your DCS World installation directory, find the Mods folder, and then Aircraft. Choose the specific aircraft you are flying (e.g., UH-1H, CH-47) and go to Cockpit/Scripts. Open cargoindicator_page.lua: Open the cargoindicator_page.lua file in a text editor. Find and Edit Position Values: Look for lines related to the initial position of the indicator. These are often defined by X and Y coordinates. Adjust these coordinate values to move the indicator to your preferred location on the screen. Alternatively, a new variable like topmonitor with a value of -0.5 can be added to move it to the bottom right corner, as found in some community solutions. Save the File: Save the changes to the .lua file. Restart DCS: Restart DCS World for the changes to take effect. Important Considerations: Create Backups: Before making any changes, back up the original file to avoid potential issues and to easily revert if something goes wrong. DCS Updates: Be aware that DCS updates may overwrite these file changes, so you may need to re-apply your modifications after a patch. Monitor Specificity: The X and Y coordinates are screen-dependent, so you may need to experiment to find the exact values that work for your multi-monitor setup.

And? It should be in English regardless of coalition when game localization is set to English.

Not reused from 23. But same indicator is reused in other places.

Can you point me to clear instructions on how to do so? All I have found so far is links saying it has to be done like the Hip. Those posts mention having to modify lines #,#,#, with no actual mention of what is in the line or, most importantly, if those lines in the Hip even correspond to the same lines in the Chinook. I hate to modify lines, for example 8,9, and 10, when actually I need to modify 13,14, and 15. Thanks.

Jump for Joy is my favourite. [emoji6] Sent from my SM-A536B using Tapatalk

Bye Phant

Is the gear/flap indicator also reused from the MiG-23? It has markings for a half-flaps setting but to my eye it looks very MiG-29 shaped. It would be weird to have an indicator that shows half flaps on a specific airframe when that same airframe doesn't have half flaps.

A real idea, actually, but one that did not pan out. At one point, hunting Soviet A-50s was indeed considered as a mission for the F-117A. The "F" designation suggests that the idea of making the Nighthawk an actual stealth fighter had some traction. In the end, though, it was judged it didn't perform well enough to be useful for this. That IR sensor above the nose might be a remnant of this.

As earlier mentioned, there is no "takeoff" position at all. The "takeoff" position button gives the exact same flap/slat settings as the "landing" position. This makes sense from a manufacturing perspective because it's easier to re-use MiG-21 cockpit parts or whatever instead of making an entirely separate switch box for the MiG-29. However what I don't get is why the indicator also shows a half-flaps settings when it's clearly been designed in the shape of a MiG-29 and has not been recycled from another aircraft like the flaps switch box has.

MiG-29A Fulcrum Development Progress This update introduces the first iteration of the 3D damage model, an optional English HUD/HDD, lower-resolution cockpit textures options for increased performance, addition of the controls indicator, autostart, HUD repeater export, and new Georgia 2008 missions. Radar improvements include more stable STT extrapolation, refined close combat sensitivity, and adjustments to lock indication and missile launch logic. Numerous fixes address animations, repair logic, DTC issues, IFF on dedicated servers, autostop, INS alignment, and other cockpit elements. The manual has also been updated with corrected instrument details and missile-pair launch information. Here are some points we want to highlight: We saw discussion about SPO-15LM RWR operations with onboard Radar, we gave an elaborated explanation here. We saw some questions about mobile RSBN/PRMG stations usage. Please see the RSBN/PRMG guide for a deep explanation of its use. Autopilot oscillation is a priority, and it is being worked on. Some players reported difficulties with radar use, mainly due to incorrect mode selection. This update includes several radar fixes, and documentation will be improved to clarify proper usage. Check the latest video from Wags on Ground Attack. Bye Phant

It doesn't work that way. You have three buttons for flaps: off, takeoff, and landing. Having two flap buttons won't give you the takeoff position, for example. The current setup doesn't work on an up and down basis (which is realistic, but not very convenient, as I mentioned, if you only want to use two buttons for flaps only).

Pronunciation of a word and pronuncation of a specific keyboard key the user needs to press are not equivalents. Instructions stating to press a specific key letter should use some kind of clarification like "J for Juliet" or "J for Joy" etc.

Bye Phant

But you can‘t slave the HSI to the NS430 to make the needle pointing at the waypoint direction, correct? Further you can‘t use the VHF frequency right?

Okay, so, the difference as Miki said is trim button in Hind resets AP, so you fight the attitude hold AP as you pitch down and then trim and the extra cyclic to fight the AP is no longer needed as trim button centers attitude hold. I really recommend against using trim hat too much, look at right control + enter screen. You will hit the maximum limit of the pitch AP MUCH MUCH faster just using trim hat. Trim hat is meant for small adjustments. When your pitch AP hits its limits, it can no longer stabilize you or dampen your movements. I talk about it in my video on the Pitch/Roll AP and I give 3 different solutions to the “uncommanded pitch” after trim phenomenon. It slightly depends on your kind of stick, with FFB I prefer just rapidly trimming 2-3x. If you watch this, it will explain everything

It is the whole reason S-24 points down. It caused a Mi-28 crash IRL. As someone else said. Launch from 100 kmh or higher

So I guess no way to make it say “Check Ekran” lol

Sooooooo SPO-15……..

Cheers!