Thallios

After the latest Open Beta Patch the Countermeasures Display in the SA page is missing when Dispenser is set to bypass. When the Dispenser switch is set to ON the display appears. Is this a Bug or working as intended?

It also seems to be related to the AIM-7 if no AIM-7 is equiped it worked just fine recentyl

Bug seems still to be present in OB DCS 2.5.6.59625.1 Encountered the Bug today on one of my multiplayer games, unfortunatelly no track file available

The problem not only exists in TWS MAN Mode. If you change from TWS Auto to RWS the same problem occurs. The radar elevation can not be changed manually. You always have to cycle through TWS Auto and TWS MAN manually several times until you end up with TWS MAN then you can change once the radar elevation. If you then change to any other mode (TWS or RWS) radar elevation is stuck again until you change back to TWS MAN manually (after once cycling through TWS AUTO). This is a short time work around but surely not intentionall as you can not change modes and change radar elevation. In a BVR engagement this is not really a situation you want to handle additionally.

There is a slight workaround Make HUD SOI go into SPI Submode by TMS Aft short and then slave TGP to SPI via China Hat fwd long; Its not realy boreshight but close to

As most of the switches will probably remain the same; will it be possible to import the bindings from the A-10C Modul in order to avoid redoing all the keybinding work of the "normal" controls like TMS/DMS/CMS etc

Observed this behavior today, after switching to CAP from CAS loadout. Even when TGP was removed after rearming this issue occured. Undesignate didn't change anything. I didn't try undesignate in A/G Mode though

I agree, a comprehensive TPod tutorial with all modes is required and what the Tpod will do if you switch modes

Ok now I have splitted the zip file For unpacking please rename the files as followed otherwise I was not able to upload the splitted file due to file extension restrictions GBU_12_Fail_001.zip ==> GBU_12_Fail.zip.001 GBU_12_Fail_002.zip ==> GBU_12_Fail.zip.002 GBU_12_Fail_001.zip GBU_12_Fail_002.zip

Ok, I just watched the track file myself. Now the problem gets odd. The target point is completly off the target now. When I flew the mission the Point track was on target (tank). Now in the replay the Target Point is approx. 20 feet away from the target see first image. After bomb release the deviation gets even worse. I seem to have completly missed the Island although I dropped the bomb as usual. In the live game the bomb hit the ground maybe 20 feet away from the target. In the replay image of the overview map I seem to be miles away from the target. In single player / offline mode GBUs work just fine.

How can I upload the track file. It contains 17 Mb of Data limit is 5 Mb

Yes Laser codes were identical

Yes bomb was in range. Bomb was dropped with Auto mode. Balistic curve before laser lock in the initial phase showed that the bomb would have overshooted the target as usual, then laser lock kicks in and bomb dives towards target but then still misses in the last 2 seconds. And this is not my fist time dropping laser guided bombs from the F18. The last 2 months several hundred bombs dropped from an F-18 hit the target with pinpoint accuracy, same procedure as always.

Yes Laser is armed, TRIG boxed and LTD/R is shown. Tested multiple times with GBU-12 and GBU-10, also with buddy lasing and using JTAC laser. Every time same result. After drop bomb starts to track but then misses the target even when using the JTAC laser.

When I drop laser guided bombs from the F-18 like GBU-12/10 using my TPOD, the bomb starts to track the laser and everything seems normal. However in the last seconds of the drop shortly before impact the bomb seems to lose track and misses the target by a few meters resulting in no dmg to the target. This happens in point and area track. My wingman and I observed this behaviour on at least 2 servers and 2 completely different clients. We tried several times to make sure that the impact point was not lost. We even tried manual correction in area mode; no effet.