2alpha-down0

Copy, there was an issue on the last rotation where no one, red or blue, could get the ground crew to do anything. Sent from my iPhone using Tapatalk

Looks like there’s an issue with “Chaos” where the airbases are all neutral. Sent from my iPhone using Tapatalk

Bumping the thread because this is still an issue.

The target was on a mountain at 11,500 MSL; delivery was done level at 12,000 MSL (500 AGL) and 500 IAS (which it seems was my problem).

That would make sense, thanks Sent from my iPhone using Tapatalk

I've been doing a decent amount of F-5 bombing lately, and I just want to confirm what I think I'm seeing. For level delivery of Mk82SEs, I'm seeing a decent amount of variation in reticle depression needed. I stick to 500 AGL/500 IAS delivery profile, and find that at sea level I need around 140 mils of depression. Recently I hit a target at 11,500 ASL, and 140 mils caused the bombs to go way long. A second strike with 100 mils depression was centered on target. It would make sense that atmospheric pressure would change sight setting requirements, and I assume that's what's happening, but I've never seen it mentioned in any manual or tutorial. I assume there's a way to account for this other than trial and error?

It was a good fight; I was the F5. There was a Sabre around somewhere but I think he left before you got there. I was actually blind on you after you got the second 52, then I got a BRAA call at 0 miles, looked to the left, and you overshot just off my wing. :shocking: Fight was on from there. The F5 definitely isn't made for fighting at 40k feet.

Thanks, Miles. Can't wait to try it!

Tested in the F-5, and to a lesser extent in the F-18. Reproducible across multiple simple missions I made. Cold start and air start both experience the issue. ADF navigation receives signal and functions up until a message is transmitted on a different frequency (for instance, ATC). After transmitting the message, the ADF no longer functions. Communication with ground crew doesn't appear to cause a problem. Beacon in use is the TTS 3030 set to 231.875 AM and power at 1000. EDIT: Tested using a fixed beacon on PG map and everything works fine. May just be related to the TTS 3030 DxDiag.txt adf bug.trk adf bug2.trk

*raises hand to jump in line for testing purposes* [emoji38] Sent from my iPhone using Tapatalk

The only potential issue I see with WMR is that they (at least my Odyssey) like brighter playspaces for tracking. If most of the user's light comes from natural light and not LED sources, there would be an issue with IR pollution. I've never had an issue with the mouse, but I also don't use the WMR controllers for anything in DCS.

I actually managed to glitch into the FLIR DDI page last night after a repair/restart. I wish I had a track file or had OBS running at the time, because I can't remember exactly how it happened. Nothing worked except de-clutter, but the placeholder is hidden in the OB version.

Miles, Have you had a chance to test PointCTRL with X-Plane 11, or is it only designed to work with DCS?

Works great, thanks so much.:thumbup:

Anyone have issues using this with VoiceAttack/VAICOM? I just installed it and now the radio no longer works.

Been following this project for a while. Please put me on the list. Sent from my iPhone using Tapatalk