Jump to content

tasimm

Members
  • Posts

    11
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The 9-11 AoA is when I start to balloon on flaps down, usually. It’s easier to manage because I’m so close to on speed. Yesterday it was 15 and impossible to manage. I’ll try a repair and see what happens. Maybe something got borked in the update.
  2. I basically only fly the Hornet around the boat these days, because I just don’t have the time for missions. Its basically launch, get in the stack, break, 3 or 4 passes, then a trap and I’m out. I was flying today and I had a <profanity> ton of trouble trimming it up after the break. I’m usually on the numbers at paddles and today I couldn’t get it to do anything right. Gear down at 250, let it ride, flaps half, trim to bracket, flaps full, trim to bracket. At that point I’m nose down AoA at 15, WTF, and working the throttles just to get back to a reasonable altitude for the groove. Something has changed. I went from having a problem with ballooning at paddles trim, which I could deal with because I was still on speed at 9-11 AoA, to now having a lead weight on my nose and trimmed out to 15 AoA. Even though the bracket says I’m on speed, it’s obvious I’m not. Once I’m settled it seems to be manageable, but it still feels nose heavy. And there was no way I was even close to the numbers after the break. I tried multiple times. Just wasn’t happening. What gives? Anyone else having this problem?
  3. Telling the GHub S/W not to load at start up seems to be the answer for me until this gets fixed. This way I can still utilize the pedals as rudders and fire up GHub when I want to play AC. it’s an extra unnecessary step, but it will work for now. UPDATE: I discovered last night that as long as I have load at startup disabled on GHub, I can start the GHub s/w manually and DCS will still work.
  4. I have zero experience in dissecting these logs, but the only difference I see is that when G Hub is uninstalled it fails the steering wheel centering test, loads the guidFFDriver and moves on. When it’s installed it looks like it finds what I’m assuming is the force feedback driver, (guidFFDriver), but doesn’t test the wheel. After that it seems to hang. I have no idea if this is normal behavior or if it should run the test after it finds the driver.
  5. Ok, here is my log with Logitech G Hub software uninstalled. dcs.log
  6. Let me uninstall tomorrow when I get some time and I’ll post the log.
  7. The Ghub Software had an update applied today. Still having the same issue. I've attached my DCS.log. dcs.log
  8. The one thing that concerns me with going AMD is that the G2 doesn’t play nice with the X570 chipset. I think there may have been a bios update to patch the issue from some mobo manufacturers, but even so, the G2 is a finicky piece of hardware and I’ve already been at my wits end with it in the few months I’ve had it in hand. I’ll have to do my due diligence if I do decide to go down that road, to ensure that I can avoid that problem in its entirety.
  9. As the title implies, I’ve finally acquired a 3080, so now I’m ready to start my new build. Just curious if anyone has any suggestions on a CPU for DCS? I play DCS, FS2020, and Assetto Corsa with a Reverb G2, so VR performance is what I’m aiming for here. I’d also like to future proof somewhat for DCS and be able to utilize Vulkan at an optimal performance level, if that ever happens. Any opinions on AMD vs. Intel for DCS future proofing? I’m thinking either a 5800x or a 10700k right now, any opinions, or better yet facts, would be greatly appreciated.
  10. Have any of you with this issue tried removing the Logitech G Software? I had the same issue, and it went away when I uninstalled it, returned when I reinstalled.
×
×
  • Create New...