Rongor

some irregularities with LSGI Thanks for the hint. Found the solution right next to it: MAIN MENU > NAV SELECT > EGI POWER > MASTER EGI OFF > VERIFY EGI OFF resets alignment and resets AUTONAV in the CNI-MU back to big font, so you can initiate fresh alignment there.

Placing the new C-130J for cold start form ramp onto Wunstorf airfield auto-moves it to Hannover airport, so I guess the parking positions if Wunstorf don't accept the Hercules (by size)...

If you run out of patience until this is patched, you can add in "Germany, " into line 864 of Eagle Dynamics\DCS World\Mods\aircraft\C130J\Entry\C_130J_30.lua or replace that file with the attached C_130J_30.lua... No idea what the Integrity check will say to this though, so might not work when joining your favorite MP server. This file then should automatically be replaced again when the patch is coming.

are you sure you are in the correct subforum? This here is for issues around the C-130 module, which is a payware DLC for the free DCS World. Regularly in DCS, you alternate mouse control use between moving either the cursor or the view. If you are in view mode, you can't click on anything. If you are flying a low fidelity module such as any Flaming Cliffs aircraft or the Su-25 in the basic free DCS, you also can't click on anything as these don't have clickable cockpits.

Say I am still sitting on the ground and a brief power outage corrupts the EGI alignment, what is the procedure to realign? Initiating the Autonav again isn't possible since it doesn't return to the big sized format...

This is valid for the "sim - no tests" realism setting. Checklist wants the crew to power up the AIR COND (2nd image). This will fail because the Pressurization switch to Auto item is missing in the preceding Pressurization panel section (1st image). Hence the switch will still be in AUX VENT setting (which is the current default for cold ramp start spawns), which will deny setting AIR COND to ON. Only on the following Before starting engines checklist this gets remedied, as both systems get addressed again, this time with the correct Pressurization mode switch setting mentioned.

Logitech g502 hero, same issue. With 1000 Hz I had total freezes as long as I moved the mouse while sitting in cockpit. When I stopped moving the mouse, all went back to normal. Could reliably solve it by restarting my PC and/or restarting DCS. Appeared randomly, but when it did, then only with the very first launch of DCS. Only now I did install the Logitech Gaming software, as this is the only way to adjust the poll rate. Reduced it to 500 Hz and currently don't run into this issue anymore.

If you fetch resources from an airfield to generate cargo, the cargo always adds 3300 lb when loaded into any aircraft. No matter if you only order a single Sidewinder or 23xGBU-24, the resulting package will have a mass of 3300 lb. While I can assume this might still be w.i.p., I couldn't find any mention of it in the forums, so to make sure its getting attention I provide this report with attached (short) track. The calculated mass total of selected stuff in the resources window is correct, yet when the package is created, it only ever has a standard mass of around 3300 lb. Besides it being unrealistic to be able to carry 100k lb of ordnance with this method it causes problems for the lighter weights too, as for example even with zero fuel a Huey is instantly overweight when loading a cargo of 3300 lb. Attached track demonstrates this with a Huey, loading a Sidewinder (189 lb) and also 23 GBUs (55k lb) and in both cases receiving 3300 lb additional load.Foothold-GERMANY-COLDWAR_V3.81_mad_v3-20251030-175227.trk Also tested with CH-47, same results. I could take off with 80 AIM-54C on board, no problem...

Tbh I wasn't aware the A-10C II did ever receive a gateway function already, be it with the implementation of the ARC-210, before or afterwards. So in my world, seeing a L16 Viper, Hornet or any flight's PPLI on the TAD seems wrong at this point, regardless A-10C or A-10C II, so I think the OP has a valid point. ED's manual for the A-10C II doesn't mention any gateway at all. Regarding datalink and TAD, it specifically focuses on SADL, which is incompatible to L16. I don't see how the fact that we can see L16 PPLIs on the TAD is basis for the assumption that we received a gateway capability. For now its a bug, unless ED confirms this is intended as simulating a gateway in any of the both A-10Cs we have.

No idea what DTC issue you are assuming, since the partition containing navigational points hasn't been implemented so far. As above, its a result of a wrong utilization of the route tool. Enter elevations, otherwise any point will default to 6523 ft. Also FIX would be the wrong method to "fix" this, as 1. this is an altitude issue and 2. you would only adjust a correct alignment to a different one (with a wrong system altitude).

What you describe there is the result of you not entering elevations in the route tool. You seem to assume the route tool will set each new STP at ground by default. It doesn't. By default its at some 6500 ft or so. I can agree this isn't optimal but you just have to deal with it. If you ignore this and load in your route with all STPs at 6532 ft, its only correct to expect the TGP pointing into higher elevations, touching the ground only in the distance if at all.

You never mentioned exact boresight distances and stations. Also you didn't mention these for your handoff attempts. So this could still all be coincidental. For each of the both smart stations carrying Mavericks, you have to boresight independently. After both boresightings, both stations' Mavericks will point exactly at the TGP's POV only at the exact distance, relative nose bearing and elevation as both the TGP and the respective station's Mavericks were in the moment of boresighting. If you boresighted the left station at 4 NM and then later attempt to handoff to a Maverick at 8 NM, a maverick hanging under your port wing will point to the right of the target. If you boresighted the starboard station at 8 NM distance and 4000 ft altitude and then later try to handoff to a maverick on that station from 20000 ft and in 4 NM distance, the Maverick will also point to the right of the target and the chance of seeing errors in elevation will be be high.

With today's 2.9.19.13478 this seems to be fixed.

Can confirm this has been fixed with today's 2.9.19.13478

DCS 2.9.18.12722 - 22.07.2025 A lot of nice stuff has been added in July. Read more about how George as CPG is managed on pages 582-603 in the manual. \Eagle Dynamics\DCS World\Mods\aircraft\AH-64D\Doc\DCS AH-64D Early Access Guide EN.pdf