Callsign JoNay

Update: I updated the stick base and throttle firmware through SimApp about 3-4 weeks ago, and I don't think I've had an in-flight disconnection since. Anyone else noticing more reliability lately?

The 51st VFW has re-opened recruitment for the F-15E Driver and WSO slots. Apply at: https://discord.gg/51stvfw

Checkmates are still recruiting! Apply at: https://discord.gg/51stvfw

Perfect, thank you.

That would make a lot of sense. Is there a publicly available diagram or something to confirm?

So you're saying the uplook reticle should be inside the small box?

A friend of mine shared a video with me today that featured an ACM sub mode that I didn't know about called UPLOOK. https://www.youtube.com/watch?v=KfPw8nOSd2g&t=4s (Time code: 18:11) It got me wondering how the HMD is able to project the uplook reticle so far off the boresight of the HMD, when other important symbology like DL16 HAFUs are limited to a very tight central area in the display. Here is a picture to demonstrate: Is this working as intended? I can't help but imagine how incredible our SA would be if we could see HAFUs that far into our peripheral vision.

Bug still present as of the July 22nd patch.

To reproduce: -Create a new mission in the ME. -Place a Supercarrier. -Enter the mission and press R.Alt+F9. -Let the background chatter sound play for a few moments. -Exit the mission and return to the main UI screen. -Choose Instant Action > F/A-18C > Free flight. You can now enjoy the Pri Fly background chatter while you cloud surf in the F-18. Also tested in the F-16 and F-14, so it probably applies to all modules. You can only fix the bug by relaunching DCS.

The patch notes say to press R.Alt+C, but that doesn't do anything on my end. I can get my mouse cursor by pressing L.Alt+C, but I am unable to interface with any of the controls. Trying to change any of the lights or ship direction/speed is unresponsive. In the preview video clips circulating around I see buttons being highlighted when clicked like the attached picture, but they don't highlight like this for me.

Has anyone ever encountered an issue where someone they were flying with was almost inaudible on the F/A-18C MIDS radios, but their mic levels were fine on Pri/Aux and Discord? This isn't a matter of me being a dummy and having my MIDS A/B cockpit volume knobs turned down. Both knobs were set to full volume, and everyone else in the flight had normal mic levels on MIDS. We just have a problem with one person. Any ideas?

The 51st VFW has re-opened recruiting for our USN F/A-18C Hornet squadron, based on the VFA-211 Checkmates. The ideal applicant should be: 18+ and English speaking. Have some form of head tracking and HOTAS. Available to fly in the evening hours of North American time zones. Able to fly with the squadron once per month minimum during the busy times of your life, and more than once per month during normal times in your life. Regularly active on discord, easy to reach, responsive to pings, and plugged into what's happening within the wing. (No Discord ghosts!) Competent with naval ops, CASE I, II, and III, as well as AAR with all three tanker types. Mostly competent with the avionics and weapons. The ideal applicant should be interested in all of the following: A2A missions. Both PVE and PVP. BFM, ACM, and DACT. Anti-ship warfare. SEAD and DEAD. A2G strikes. CAS, COIN Ops, working with JTACs while orbiting over an Echo point and waiting for a 9 Line. Perfecting your CASE I, II, III, departure, recovery, and bolter. You should not apply if: You are intimidated by BVR combat in PVE or PVP environments. You are intimidated or get salty from BFM, ACM, or DACT. You are too much of an action junkie to find stimulation from orbiting at an assigned keyhole while working with JTACs for several minutes to deploy a weapon on target in an uncontested airspace. You are intimidated by having your airmanship around the boat evaluated by human LSOs, Tactical Paddles (LSO bots), or other tools like greenie boards. TL;DR - Be Interested in all the Hornet can do, and have reasonable availability to fly and engagement on Discord. Fill out an application at our Discord: https://discord.gg/51stvfw

Recruiting for all Razbam modules has been put on hold until a light can be seen at the end of the tunnel.

No, I can't be bothered to deal with their customer support.

I've owned my Orion 1 stick base since April 2022, so two years now. These constant disconnects have only been happening to me in the last 6 months or so, or a year tops. My product worked reliably for a long time before that. I wonder if one of the firmware updates have caused an issue, and if there is a way to rollback the firmware to circa 2022.

No, I was testing the winwing fix not whether or not a powered hub makes a difference.

I have used that method as well following all the steps, disabling the sleep mode for all HID and USB devices, and it hasn't made any difference for me.

I caught the bug on video today, as well as @MARLAN_'s fix in action:

I have no idea. Probably low. It's not an expensive hub. Can you confirm that you do have disconnection issues when you plug into the tower instead of the hub?

I have the same problem with random disconnects/reconnects during flight, and so do several of my friends. I swapped out the USB A/B cable for my printer's USB A/B cable, and that fixed my problem for over a month. No connection drops at all but they have returned the same as before. I've tried plugging into powered USB hub and direct to the motherboard, but it makes no difference on my end. I don't have any other flight simulators installed, only DCS. Has anyone experienced disconnection issues while flying in other simulators? It would be helpful to rule out whether or not it is a DCS specific issue with Winwing Orion stick bases.

I'm sorry but that's ridiculous. They are the devs. They have knowledge of the code and surely have tools to get under the hood and investigate. It's their job to fix bugs, not to give up because we can't figure out how to reproduce it for them. We've proven it exists as much as we have the ability to. They should investigate.

Marlan got a track of it above, but it doesn't show in the track. So how would you suggest we do that?

Marked as can not reproduce? So we have to figure out what produces the bug in order for it to be investigated?

Yo! Thanks Marlan, I will give that a try next time.

Ok thank you. Yes please mention it, because I have track recording turned off by default and it's unlikely I'll be able to supply a track for you. I'll make a track if I figure out how to reproduce it, but I currently have no idea what causes it. If anyone else following this thread has insight, please share. I love my AZEL page and would like it to be as reliable as the other systems.