ripple

YSIAD_RIP, thanks for that link - I had not stumbled on the USB issues with x570 AMD boards. Oddly enough I finally got some of my USB ports to work before looking at that, although the x570 workarounds did not help the rest of the ports so I assume there are still board issues they still have to fix. I do have positive news on the "ghosting" x56: after following some of the steps provided by Logi support, I was able to get the x56 working cleanly on my back panel USB 3.x ports. Here are the steps I think made a difference: - updated x570 bios - removed all drivers for saitek (both my old x52pro and my x56) - updated NET framework to latest - reinstall USB/chipset MB drivers - do a clean boot ( https://support.logi.com/hc/en-us/articles/360023183914 ) - reinstall x56 drivers Not sure exactly which made a difference, but my gut says bios and the clean boot option which removed all of the startup noise and other software that might get in the way. After all that, I still had ghosting when my x56 is connected to USB 2.x (back or front) or a USB 3.x powered hub - but surprisingly when connected to USB 3.x back panel there is ZERO ghosting. Tested it all weekend and it is rock solid. The implication is that ghosting is not a mechanical problem with the x56, but a driver/usb issue with the motherboard. One could argue that the x56 still has a mechanical issue in that it is too sensitive to some of this and that is why protecting the wires from interference sometimes helps. I guess the key is whether your stick shows ghosting on any other pc or laptop you test it on.

So my new x56 throttle is showing consistent ghosting as well. I've tried all the non-warranty-voiding actions like powered hubs, 2.0 vs 3.0 ports, front ports, back ports, removing all other USB devices. Some combinations are worse than others, but there is no combination that eliminated ghosting and I'm working through a ticket with Logi support. The smoking gun to me is that I have 3 Win 10 machines - My gaming PC, another desktop, and a laptop. When I installed everything in the other desktop and the laptop, to my surprise neither of them showed *any* occurrence of a ghost presses. Beat the heck out of the throttle for 5 full minutes on each and works perfectly. Pop it back into my Gaming PC and ghosting about every 4-5 seconds with throttle movement. That tells me it's some USB/power thing that is unique to my gaming PC and the stick itself is most likely not "defective" in the sense that it is not workable. There is an argument to make that it's still defective in the sense that it is not working properly on my system of choice...I'm not sure how Logi will respond - hopefully they are still responsible for getting it to work. I'm going to continue to pursue BIOS/firmware/USB driver options as well. Maybe a PCIe USB card, although I'm not sure I understand why that's different than ports off the MB or the back panel...? My motherboard is a Gigabyte X570-UD w/750w PS new last year.

Attaching dxdiag report... DxDiag.txt

New install of BS2 1.1.1.0 on same system where BS1 works well. I can run an instant action in BS2 and fly a mission and it works (though noticeably slower fps than BS1). When I launch a campaign dcs.exe crashes after choosing the mission and before mission summary shows up. I read about the /3GB switch and added that to my startup and rebooted. Now it gets as far as the mission info panel and then crashes after clicking "Fly". There are no crash files that I can find and only the Windows event log entry of: Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 12/8/2011 Time: 5:30:15 PM User: N/A Computer: LONGBOW Description: Faulting application dcs.exe, version 1.1.1.0, faulting module edterrain.dll, version 1.1.1.0, fault address 0x0000cec9. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 64 63 73 ure dcs 0018: 2e 65 78 65 20 31 2e 31 .exe 1.1 0020: 2e 31 2e 30 20 69 6e 20 .1.0 in 0028: 65 64 74 65 72 72 61 69 edterrai 0030: 6e 2e 64 6c 6c 20 31 2e n.dll 1. 0038: 31 2e 31 2e 30 20 61 74 1.1.0 at 0040: 20 6f 66 66 73 65 74 20 offset 0048: 30 30 30 30 63 65 63 39 0000cec9 0050: 0d 0a .. I'm running XP Home Pro SP3 with 4gb ram with a 1gb GeForce 9600 video. Any suggestions? Thanks!

I'm enjoying the campaign - very thorough and realistic feel to the progression. I have yet to finish the fourth mission (alert protect the airfield). I'm able to get the bird airborne just before the hinds pass over but no matter what tactic I try one of the hinds locks onto me quickly and I'm shot to pieces. I tried just running, launching a vikhr, fixed cannon sight, etc. but they all end the same way and very quickly. What's a good strategy for surviving this? Run and get separation or pick one and target? I'm curious how others have approached this. Thanks, ripple

I've struggled with the South Ossetia Pirates mission in that once I find the camp I can't get close enough to take them out. I can see the 2 camps (one group on the east side of the valley and one group on the west side), but since I only have rockets and guns I have to get much closer to them and they take me out with sam's. What strategy have others used successfully?