Buzzer1977

I wanted to create a track file for another bug (Tomcat blocks cat), and while waiting for the Tomcat remaining on the cat, my client F/A-18c moved on it's own over the deck after a few minutes time. I was able to reproduce it. Happens with the Hornet no matter if cold or hot, with or without wheel chucks in place. After some time the Hornet glides over the deck. MagicOnCarrier.trk TRAINING_CAUCASUS.miz

Just found out that there is already a J-15 livery for the Su-33 from the chinese assets pack, but the Su-33 can't be assigned to China, only to a joint group.

Current OpenBeta doesn't allow China to have Su-33, but provides via Joint Task Force a Su-33 with Chinese J-15 livery from the chinese asset pack.

There are some low hanging fruits that should be very easy to achieve, but would give so many new options .... - The Kuznetsov is already modeled, so it would be easy to add another livery to get the Chinese Liaoning and Shandong aircraft carrier, both Kutznetsov class carrier vessels. - A J-15 livery for the Su-33 or the J-15 as another real Flanker derivate - Su-25UTG and/or Mig-29K to have another red aircraft on carrier vessels. Base models already exist in DCS, so it should be not too expensive to develop.

I've set up a joint training mission. Landing a blue Su-33 on the blue CVN-73 works just fine, but taxing on the carrier it randomly explodes. Aircraft and vessel are both on the blue team. Track is attached. Su-33_explodesOnCarrier.trk

It's likely a known problem ... https://forums.eagle.ru/topic/275743-dcs-complete-hung-occassionally-on-refly-mission/?do=findComment&comment=4709150

AI refueling is FUBAR since some time ... There's a truck load of issues with AI refuling problems ...

Works only when DCS is started in VR

LeapMotion sensor is connected, calibrated and works with the LeapMotion Diagnostic Visualizer, but DCS just says: "Connect device"

Nothing. When it happens, it happens everytime i put on the VR glasses and the blue 'Input is assigned to VR' appears. As soon as this happens the mouse pointer is dead. But as i said it happens not all the time, but quite often.

Hi, when i switch between DCS in VR and the Desktop (Alt-Tab) the mouse pointer in DCS sometimes get's stuck. Pressing the WMR Windows-Y input change also doesn't bring back mouse control in DCS. Windows 21H1, all recent updates as of today and HP Reverb G2.

Have the same system configuration here. Had similar issues. What helped me was: - Recent BIOS based on AMD AGESA 1.2.0.2 or higher to solve the x570 USB issues - Recent AMD chipset driver to solve the x570 USB issues - Recent Reverb G2 firmware 15 Rev A If the problem remains, ask HP support for a new cable. P.s. while loading, the flashing and hangs are normal in DCS.

F/A-18c, is the ultimate work truck. Air2Air refuel, Carrier Ops, all kind of gear to throw at others under the wings, ...

AI is completely bugged recently, can't refuel, can't fight, can't fly.

Jepp. Would be great to have this option.

Could reproduce it. Error happens when the room is too dark. I turned on the lights, recalibrated and it worked.

Not possible, because i've placed all the tankers west of the AWACS. And why does the A-50 work for probe equipped AC, but E-2D and E-3A don't work at all ?

I've placed the F-16 behind the boom tanker 120 NM east from the other client AC, heading 90°, so it shoud get another reply if it's refering to bulls eye. But bulls eye or not doesn't matter. I've called for a tanker, which doesn't work obviously.

I don't think so, because the F-16 from the second mission i've added get's the same 278°, 45NM reply. (See AWACS Tanker-Bug2.miz / E-2D-E-3A-ReportWrongTankerToF16.trk)

Forgot that i've also have the Su-33 ... same result. I also added a F-16 directly behind the KC-135 flying 90° heading. Get's the same 278°, 45NM reply from the E-2D and the E-3A. But the A-50 messes up with F-16 too, sending it to the drogue tankers instead of the boom tanker infront of him. AWACS Tanker-Bug2.miz E-2D-E-3A-ReportWrongTankerToF16.trk E-2D-E-3A-ReportWrongTankerToSu33.trk

I've set up a mission to reproduce the error. There are 4 drogue equipped tankers directly in front of the aircraft with heading ~0 , and one KC-135 with a boom ~120 nm east, heading ~90. And three AWACS (A-50,E-2D,E-3A) west of the AC, so all the drogue tankers are closer to the AWACS then the boom tanker. The A-50 always gives the right tanker, while the E-2D and the E-3A always give directions to a non existing tanker with heading ~ 278, 45nm. I've verified this with all probe equiped AC i have, namely JF-17, FA-18, F-14 and AV8B. AWACS Tanker-Bug.miz E-2D-E-3A-ReportWrongTankerToAV8B.trk E-2D-E-3A-ReportWrongTankerToF-14.trk E-2D-E-3A-ReportWrongTankerToF-18.trk E-2D-E-3A-ReportWrongTankerToJF17.trk

Seems also to happen with Su-33 on IL-78m ... AI get stuck with huge nose down attitude.

I've got a problem with the G2 since yesterday, that the pilots head is always centered in the cockpit. If i lean forward to have a closer look at the gauges they move away. Until yesterday i could even look outside the canopy, now i can't even look at the gauges.

And again ... seems quite reproduceable AI-CFIT2.trk

My 3 AI wingmen just have flown into the sea on their way to the tanker for no reason. See the attached track file AI-CFIT.trk