All Activity

Interesting.

1-Set radio to contact Beslan (Caucasus) ATC: R-853 to channel 6 (141MHz) or YADRO-1 to 4750KHz 2-Select R-863 (all left) on SPU-8 3-Contact ATC to request Start-Up 4-SPU-8 "automagically" selects VHF (second position left to right, not functional as by Chuck's Guide) Have to re-select the correct radio before any contact with ATC. DCS 2.9.19.13478 I don't have a log/track file(gave up using the radio, the last one I did has already been overwritten)... if you can't reproduce let me know (so I jump into the chopper and make a new one

https://discord.gg/HtsEbAmG7z Our Discord link!

ChatGPT and other LLMs are a fantastic tool, but are not a replacement for doing actual research. I personally don't find it overly productive to just copypaste AI-written text on online forums, especially when it's not cited.

What mod is this?

Nothing wrong with that, you should try it. Agreed I was just trying to explain that they cannot look the same for every airframe. I would be good with a very simplified version. The same way we have custom effects for the lex vapors on the F-16, F-18. Harrier...

CCIP bombing has been within reasonable drift values again as of last patch by my testing. It is once again more accurate than CCRP (as is expected), but just barely.

.miz updated with the new lua. No changes to anything in the lua script except the commented-out lines with the instructions. It now specifies that you should set the fuel capacity to the internal tank capacity only. No need to touch the lua script if you are only testing the Corsair. You must open the lua file and change the fuel capacity only if you wish to test on another aircraft.

That must have been a truly glorious sound!

Excellent news Sir. A very much anticipated recreation of a sorely missed type. Watching this thread repeatedly.

From big YouTubers sure but I guess no one else from DCS was there? Would have been nice if someone at ASC could have put together a promo video. Maybe Baltic Dragon could film himself flying the supply mission and kind of talk us through it since not much seems to be out there?

Can I get another link?

Could this be why CCIP also seems "off"? Perhaps the HUD/HMCS is just "askew"? -Ryan

null

Easiest is just delete the entire folders and they will regenerate.

The config files will automatically regenerate a version with default settings on running DCS if you delete them. Re-install won't touch them since they're in the Saved Games folder. That's why the 1st advice for anything controls related is to rename at least that part of the DCS Saved Games folder.

I really like this way of learning about the F/A-18. Well done and thank you Gunthrek and Bagel. 8/10

This seems to be broken, I have reported it now. Thanks!

About a week ago, the Crystal Super 50 ppd was delivered at my home. I used the video of Tally Mouse for setting headset up for DCS. With daytime missions it looks stunning, but nighttime mission, i also got some strange effects on the edges of the clouds. Way less than the picture of Twwhitey. Inside the cockpit everything looks fine. Already set the brightness in Pimax Play to 99 and in DCS to 1.6. (Came from 2.1 ) I still want to try the solution wich MissionCMDR mentioned. But i got some days left of those 14 days. My question i have, is the problem wich is mentioned in this topic an software issue, or should i send this Crystal Super back because there is issue with hardware itself?

Thanks for the reply, I did a power reset to my router and here is the PING result: 3 PINGs without VPN: Pinging 1231349722.rsc.cdn77.org [2a02:6ea0:c800::33] with 32 bytes of data: Reply from 2a02:6ea0:c800::33: time=191ms Reply from 2a02:6ea0:c800::33: time=191ms Reply from 2a02:6ea0:c800::33: time=192ms Request timed out. Ping statistics for 2a02:6ea0:c800::33: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 191ms, Maximum = 192ms, Average = 191ms ------------------------- Pinging 1231349722.rsc.cdn77.org [2a02:6ea0:c800::24] with 32 bytes of data: Request timed out. Reply from 2a02:6ea0:c800::24: time=167ms Reply from 2a02:6ea0:c800::24: time=167ms Request timed out. Ping statistics for 2a02:6ea0:c800::24: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 167ms, Average = 167ms ------------------------- Pinging 1231349722.rsc.cdn77.org [2a02:6ea0:c800::25] with 32 bytes of data: Reply from 2a02:6ea0:c800::25: time=190ms Reply from 2a02:6ea0:c800::25: time=189ms Request timed out. Reply from 2a02:6ea0:c800::25: time=190ms Ping statistics for 2a02:6ea0:c800::25: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 189ms, Maximum = 190ms, Average = 189ms 2 PINGs with VPN: Pinging 1231349722.rsc.cdn77.org [2a02:6ea0:c800::24] with 32 bytes of data: General failure. General failure. General failure. General failure. Ping statistics for 2a02:6ea0:c800::24: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), -------------------------- Pinging 1231349722.rsc.cdn77.org [2a02:6ea0:c800::27] with 32 bytes of data: General failure. General failure. General failure. General failure. Ping statistics for 2a02:6ea0:c800::27: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Unfortunately, everything is as usual...

Limiting FPS within DCS Settings is good but I have to set it above my HMD refresh rate which It is set now at 90hz. I limit FPS to 95 in DCS because I found out that sometimes, FPS count goes to 91 very briefly and this is causing stutters when the FPS limiter is at 90. Not sure what is happening but setting the limiter above 90 cured the stutters.

Just finished all 3 campaigns over an extended period of time. Really enjoyed them and I am definitly more comfortable flying the A10C II now. Thanks for keeping the campaigns up to date after nearly 10 years and responding to bug feedback. Really appreciated that. Thanks