okopanja

I would need to take a look. I installed the mode once for the co-op mission and got surprised at the level of details of the mod. If the mod implemented the key entry it should be fairly easy. A developer can even do this for arbitrary module on his/her own: https://github.com/okopanja/SharkPlanner/tree/main/Development I would state that by far ABRIS is the weirdest input device in whole DCS. It can have very complex states especially when it comes to the selected items inside menu (it sadly remembers the positions of them, so each time I use them I need to return them to original state for subsequent use). Waypoints are auto-numbered. In PVI-800 they are designated with numbers and there can be up to 6 of them, hence I limited the entry of max 6 of them. Since they are auto-numbered there is not much point into designating them as text. Each waypoint can be also edited with planned speed, altitude and wind information. However it is is possible to enter the annotation "objects" and they can be named in ABRIS. Here I face the problem that the entry is done via dials which are finicky, and already now this is not 100% reliable due to: - non-deterministic time needed for UI to update - inability to always determine if there is already an object surface covered with designation ABRIS cursor. - inability to query the exact state of the UI of ABRIS device (more or less it's a blind entry, although I did hard effort to utilize what little information it provides) Also I would need to fix the following issue first: https://github.com/okopanja/SharkPlanner/issues/108 Even then I can not promis anything and at best the feature may get added as Experimental (non-active by default) since ti can affect the stability of entry.

Clearly Mig-23 or bust!

This!

Just attach it. I can not reproduce it reliably

In a separate topic related to the F-15E it was stated that Red does not have the same accuracy if this option is not enabled. And btw, I am not sure what you are trying to tell me here. Also note that there were some changes with weapons on JF-17 with last release (+ patches) that I have not yet tested.

Any news on this topic?

I understood it as: "govorit radio Moskva". Great effort btw.

Disable local tacview recordings...

Let's not fuel FUD. Everyone got silent (finally), modules are still in the store which means talks are likely underway. Let's just wait and see what comes out...

There is an updated version Chuck's manual. He must have done this in the past 6-9 months, since tablet was included. There you can find some information on what you can do with the NADIR: https://chucksguides.com/aircraft/dcs/sa-342/#pffe As for RL manual: I am pretty sure that Polychop dudes have it. You might want to check with them directly on discord (do not post it publicly, since it may still have some classified parts). Aside from HSI needle that shows direction and distance, there is a vertical gray bar on the ADI, which can be also used to show direction to navpoint, provided that you have switched the selector to DOP. You can also use NADIR to display remaining flight time. Until now I have not played with wind settings for any of the modules, but I assume that wind conditions affect both trimming and possibly autopilot (not sure here).

Probably you wish the feedback from the authors of module, but I hope I can share this from my modding experience. I gather you are using the module documentation and not the IRL manual or similar thing? It's being awhile since I implemented the automatic entry for Gazelle in my mode, but you can find my sequences here: 1. Covers entry into BUT mode, entry of multiple waypoints and optional selection of waypoint 1 (otherwise last entered): https://github.com/okopanja/SharkPlanner/blob/e46db5f85c8dbe01b3295e2170e0a01ceb5e54eb/SharkPlanner/Modules/SA342Gazelle/GazelleCommandGenerator.lua#L42-L47 2. Loops over waypoints https://github.com/okopanja/SharkPlanner/blob/e46db5f85c8dbe01b3295e2170e0a01ceb5e54eb/SharkPlanner/Modules/SA342Gazelle/GazelleCommandGenerator.lua#L55-L59 3. Entry of specific waypoint https://github.com/okopanja/SharkPlanner/blob/e46db5f85c8dbe01b3295e2170e0a01ceb5e54eb/SharkPlanner/Modules/SA342Gazelle/GazelleCommandGenerator.lua#L61-L101 The actual key-presses you can find here: https://github.com/okopanja/SharkPlanner/blob/e46db5f85c8dbe01b3295e2170e0a01ceb5e54eb/SharkPlanner/Modules/SA342Gazelle/GazelleCommandGenerator.lua#L103-L123 Note: NOP command was used to introduced delay between making another keypress in some cases. I never played with fix, so I am interested if you make further discoveries what can be done with NADIR. At present I found it useful for navigation and to keep track of the engagement envelope of SAMs.

@Mootmoot I have VKB Gladitor Evo and no throttle, so I use Nintend Pro controller. Preparations The starting point is to make sure you do not have conflicting bindings. Each DCS action can be bound by 0 or more controllers! 1. Observe the control bindings. You need to verify both Pilot and Copilot for each variant of Gazelle. 2. Select Axis Commands to get the Actions that are of Axis type. 3. In my case I had the Flight controls bound to both Gladiator and Wireless Gamepad (Nintento Pro), so I right clicked on the fields of Wireless Gamepad cells and cleared them! 4. Assign selected Actions of VKB Gladiator the way I did it here 5. Switch to All but Axis Commands 6. Search for Trimmer 7. Assign the gray pinky button on the stick Instructions 1. RCTRL+ENTER to activate the Axis indicator 2. While holding Trim button (pinky), move stick so the small caret moved left and down as in video. You position it touch and slightly cross the center lines 3. Release the Trim button. 4. Use Yaw (pedals) to move the red line at 35-40% to the right 5. Apply the Flight Control Collective so you start climbing (too little will lead to problems, so better to give more than less) 6. Try to stabilize and hover (sorry this you will have to do several times until you figure out the tendencies of the helicopter) Next you need to bind the Trim button. I recommend the pinky gray button at the buttom of the stick.

Unlike Ka-50 which is balanced, the helicopters with vertical rotor in order to counter the main rotor. If I recall correctly you have to "trim" partially and partially twist in another direction (I got Gladiator Evo). Since I did not fly it 5-6 months I need to try it myself before telling you exactly what to do.

Finally realized you were talking about the access to original cockpits.

Presently they aim for this: "Our MiG-29A, NATO codename Fulcrum, will be the export modification of the “A” version that was supplied to Warsaw Pact countries." https://www.digitalcombatsimulator.com/en/news/newsletters/8a53b9baafb8473116ad05970cd8a761/ As for: Romania: they ditched their 29s in favor of upgrade Mig-21 (yes you read this correctly) Moldova: they sold majority of their birds to the USA and kept minimal number for themselves.

The loadput looks like pre-upgrade earlyvariant. Modernized Slovak and Serbian Mig-29 cockpits are almost identical. The later carries R77,R27ER1, Kab-500.

The DL in Mig-29A will be the one received from ground station GCI. However, the GCI controller himself could have received the picture from nearby radar, but also others that were transmitted, and this capability also included integration with passive sensors and AWACS (even during 70s there was quiet a sophisticated background infrastructure). It was assumed that a single flight would attack the single target under direction of GCI officer. Not sure how far the ED will go, but there is also a Mig-23 module which has the same DL, so we can perhaps expects this to be implement at some point (maybe not initially). When equipping the PVO (of territory) had a priority over the troop PVO. This means that they often shared the equipment, so some technical interoperability was there even if organizational interoperability can be questioned. In DCS there is a mixture of both.

It fired near it altitude ceiling. It should be noted that engament zone diagram by distance and altitude can be of different shape based on type of the SAM and chosen guidance law. E.g. SA-6 would have a different diagram than e.g. SA-5. The second one for longer range goes into steep lofting trajectory which produces intererily different resultant shape. No clue if the viper rings take that into account.

One side note: the implemented DCS KUB is not too accurate itself. IRL the terminal guidance can also be command guidance with no radar illumination. Combined with TV/IR used on KUB, it may even launch and guide with no warning. In addition KUB launcher can be slaved to BUK launcher, which also is not implemented in DCS (was a feature from the birth of BUK).

So, how does it take to unpack/pack/move FARP IRL? Does this even make a sense in DCS mission lasting typically 3-8 hours?

The module is at the moment OK-ish when it comes to A-A (e.g. it has some unique features such as target size and front/back ECM. A-G there is a number of issues that await for fixing. If you use the glide bombs LS-6 on servers where "unrestricted sat nav" is not enabled, as red side you will face the problem of precision. It looks like ED thinks the degraded GPS signal is still a thing in 2024, but that was removed in 2000 IRL, and meanwhile GPS is so much widespread that turning degraded signal on would have severe consequences not only for enemy, but also allies (I would understand if they bring jammers and spoofers to the game). Drawbacks in A-A include: subsonic speed (you need to climb/high dive to get it at about 1.3-1.6 Mach). This is visible both in attack and specially defending. Even the hornet will be able to catch you in a chase. missiles do not have INS in DCS (old API), so they require you to guide practically at least until the missile starts downward part of trajectory (otherwise they go stupid and even level the flight!) only 4 BVR missiles ( I typically fly with only 2: hit and run) I started playing with it in September 2023 (I was very skeptical about it, and I regret that), and I must say I enjoy it despite the need for minor overhauls.

For new the new APP (RTX 2070 Super) does not offer possibility to override the HDR setting in DCS. Other than that it is missing: - streaming - auto-overclocking feature I will likely revert to nvidia expirience.

I always wonder why afterburner disappears much sooner than a modest street light. We know for a fact that it should be visible from 10s of km. To paraphrase F-18 pilot: "once you see the afterburner plumes of Mig-25 in the distance, there is very little doubt on what that might be" (book is not with me)

Just try night with lights turned on... But I guess its simply a acceptable limitation.