Callsign JoNay

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.

@BIGNEWY Here's a picture of it happening. I've got three friendly contacts ahead of me. The closest man at ~15nm is below my scan elevation, but the two contacts at my 11 o'clock ~50nm are within my scan volume as represented by the bricks in RWS. All three are also showing friendly circular HAFUs in the SA page. The AZEL is empty though. I should have two HAFU/hits at my 11 o'clock co-elevation and another showing below my yellow box scan volume at 11:30ish o'clock. Here's another picture of it happening. I have a jamming contact coinciding with a nails-29 possibly beyond my scan limits and maybe outside of the AWACS L16 coverage so disregard him, but at my 2 o'clock right below the dugout I have a brick in RWS coinciding with a non-jamming hostile L16 HAFU in my SA page on a hot aspect. At the very least that hostile should be presenting within the yellow box scan volume on the AZEL at 2 o'clock but the entire C-scope is just empty. When this bug occurs it lasts the entire flight from take off to touch down. Re-slotting is the only fix I've found. As I said above I have no idea how to reproduce it, it just happens occasionally in about 5-10% of my multiplayer flights.

The problem is I don't know how to reproduce it. And I'm trying to think back if I've even encountered it in SP, or only MP. It's possible it's an MP thing, in which case I won't be able to supply a short track. I can try to get photos of it the next time it happens, but that might be the best evidence I can provide since I don't record tracks by default.

There's a long standing persistent bug with the AZEL page. In about 1 in 10 of my Hornet flights I have an empty AZEL page, no DL or radar contacts. I've tried cycling AA/AG, I've trying cycling power off/on on the DL, tried changing weapons, nothing seems to jump start it's functionality. It only resolves if I re-slot. Does anyone know what causes this bug? Maybe some cold start switch activation order that should be avoided? I can't figure it out. Edit: It's happened to me in hot start too, so disregard what I asked about cold start switch activation.

F-15E WSO recruitment is closed at this time. As of the date of this post, we are only recruiting for AH-64, other BluFor helos, and LotATC controllers. We are also still interested in standing up a Harrier squadron, and are on the lookout for an experienced Harrier driver to take lead on it, or to merge/collaborate with an established Harrier squadron. And we are still collecting RedFor freelancers to participate in our PVP events.

Can anyone from ED comment? Oversight? Or you guys just like it this way for some reason?

I think that is working on my end. If I box L+S and TDC depress through the AZ/EL/FLIR page on something within radar range, the TGP slews and slaves to the L+S contact. My only problems are when something is out of range or if my radar is snoozed, I can't put the TGP in any area of the sky where a L16 contact exists, which is pretty dumb. Has this feature ever worked properly, or it's been this way since AZ/EL was released? I've been a Tomcat guy for the last few years, and just starting to deep-dive into the Hornet.

Ok great, that makes a lot more sense than the current implementation.

Hey guys, I've been playing around with the AZ/EL's FLIR sub page, and I noticed a behavior that I suspect is not accurately modelled. I can use the TDC to move the FLIR octagon to any empty spot on the AZ/EL page, but I am unable to move the FLIR onto any Link-16 contacts. I'm not a Hornet aficionado, but this is illogical and I don't see how this could be accurate to real life, since it defeats the entire purpose of the AZ/EL FLIR sub page. What good is this sub page if we are only able to slew the FLIR pod to empty areas of the sky, but not onto anything useful? Video demonstration:

F-15E driver recruitment is closed at this time, still recruiting WSOs. Thanks everyone for their interest!

Bump. Nobody sees the inconsistency going on here?

I'm sure this has been asked before, but I couldn't find the existing topic. I'm curious why ED models the size of the HMD/HMCS based on FOV but they model the NVGs as a fixed size on our displays.

A-10C recruitment has been closed at this time. Thanks to everyone for the applications.

Enjoy this twitch VOD of a recent A2G/CAS weekly practice session: https://www.twitch.tv/videos/1954595580?filter=highlights&sort=time In other news our F-16 recruitment is closed at this time, likely to re-open in the winter. We are still recruiting for F-15E driver and WSO, A-10C II, AH-64D, other BluFor helos, LotATC, and RedFor pilots. We are also still looking for an experienced AV-8B pilot to stand up a Harrier squadron in the 51st VFW, OR an already established Harrier squadron operating in the North American timezone evening hours who are interested in joining our virtual wing.