Peaches

I didn't realize we had AI SU-17s. How do they work, and what is the blue counterpart?

*work

I saw that on the release notes but am struggling to understand why that is a good decision, given that DS and nighttime currently do not with together. Wouldn't it be better to leave the option to turn DS off until the lighting model works for nighttime?

BigNewy, can you point us to the bug trackers for the A-10C for 2.5.1? It seems like several key things got broken in this version (TGP, not being able to turn off DS for nighttime, SADL).

Another request to allow us to turn off deferred shading. With it on, the A-10C cockpit is too dark at night, as deferred shading kills the light supplied by the flood lights.

Confirming Thermal's observations on the A-10C TGP. I found an easy comparison between the broken 2.5.1 and the working 2.5.0 by simply running the instant action missions in each engine and comparing the results. With 2.5.1, the TGP is almost useless for target spotting.

This update OB 2.5.1 has borked the TGP for the A-10C.

First time flying around last night in winter. Seasonal rotations are very nice!

Xcom, could you check the spawn position of red troops at Arhyz FARP? Currently they are spawning inside the treeline after the farp is closed.

Good to hear. This ability is also important to deconflict your self-lased bombs if flying in multiplayer with a wingman who is also using LGBs. In that case, you'd want to change your bomb code and TGP lasing code to a value other than the default 1688.

You need to change the bomb laser code in the INV page of the DSMS to match the JTAC code.

Thanks, Xcom. Could you also remind us of the IP address of the site that has the TacView files for each pilot?

Is there a Buddy Spike Discord channel? If so, what is the address?

Thank you for the forward-based A-10C's!

I think the other issue is that the airfield frequencies are not common across all the aircraft types, which degrades its usefulness as a coordination tool. Another vote in support of fewer night missions, at this time while we are testing the open beta. I think we still have some invisible/malfunctioning units--Apsheronsk, I am looking at you.

EWRs have traditionally aided the GCI without the need for AWACS.

Got it. How does this approach work for invisible SA-3 sites? Seems like bombers and mortars could not get into position for taking out a site.

Dino, are the invisible units not causing problems for capping bases, etc anymore?

I believe the user-deployed EWRs are invisible but functional.

+1

Bug report 0400Z SA-3 group at Apsheronsk is invisible. It was like watching ICBMs coming out of silos!

Also, nice add of the Sovremenny DDG at Gelendzhik. Calling all Viggen pilots for naval strike! Or was that a Neustrashimyy FFG?

Bug report 0500-0600Z Beslan and Nalchik airfields spawned invisible and indestructible assets, thus preventing capture. For Beslan, it was a sandbox. For Nalchik, it was a group of houses/barracks. Similar issue had been reported on the Dynamic Caucasus server. Thank you for your work making the transition to 2.5!

I have multi monitor setup and sometimes have this same issue. Alt-tabbing to another open application and then back to DCS solves the problem for me. Hope this helps.

I read AD as active duty.