flyinion

Same, it's instantly noticeable when my LG drops below 46fps and pops out of Gsync/Freesync range. Rarely happens except maybe the end of a flight in a dense area like KLAX or EGLL now though. Also, two pages here and I think only one person mentioned their resolution. You can not have a conversation about FPS without mentioning what resolution you're running at.

nevermind, user error

After looking closer I realized that the factory cable actually has a longer tip, the housing still sits outside the unit. So I've decided to just go with an extension cable and use the factory one with it. I did find a couple long tip (9 & 12mm) cables on Amazon but they had mixed reviews about breaking or not working with data in some cases even though they support data transfer. Instead picking up a Monoprice male to female USB 3.0 extension. I know micro USB doesn't even support USB 3 speeds but I'm already using 3 of these same extensions in my rig for a couple years now and they've worked flawlessly. Bonus is I'll leave the factory cable connected unless I need to store the MiniFCU and reduce wear on the connector in the unit.

Has anyone found a good cable with a slim micro usb connector to use with the MiniFCU? The included cable fits well but of course is comically short in length. I bought a 3ft cable off Amazon which mostly works but I realized I can easly wiggle it and lose connection because the plastic around the connector is much chunkier and won't slide into the metal housing and I'd like to get a cable that just works instead of trying to shave down the one I bought.

The kickstarter just started shipping, I'm sure they'll have a storefront once that's done

Not till they finish shipping to all of us Kickstarter backers which from their last update sounds like mid-January. They're currently projecting to ship about 700 units a week and they're barely up to 2000 at this point if I read and remembered the updates correctly.

All of the 54x.xx drivers have been getting slammed with negative feedback in Nvidia's official feedback threads for them. 537.xx series is supposed to be the last "decent" one. Not sure I'd touch the 54x.xx ones unless it meant I couldn't play a new title at all.

Also don't forget it's only freeware if you already have Premium Deluxe since it uses the Asobo 787-10 as a base. If you don't have Premium Deluxe with access to the 787-10 from Asobo, you won't be able to run the 787-9 or the Kuro 787-8 mod.

Well I feel dumb, apparently I added back in some of UWA's lighting mods for aircraft including the 787. As soon as I took that out, it worked. Totally forgot about those when I was trying to figure it out earlier.

Yes but not for a while now. Not since the first AAU updates that modified the default 787. Even when I used it I was using the addon linker to link it in. The only mods I don't use the addon linker with are payware sceneries and aircraft that just install to the community folder by default. edit: thankfully I use a bunch of presets when I install stuff with addon linker so I can go one at a time to do them in chunks and hopefully more quickly narrow down where the issue is. I suspect it must be some sort of livery conflict, but that still makes no sense if I had no 787 or 787-8 liveries installed since there's no reason for liveries for other default aircraft type to be affecting the 787.

Well this is weird, I removed ALL of my non-payware mods (via addon linker) and now it's working. NO idea where to start looking because right before I tried that, I removed all 747 and 787 3rd party liveries and that still hadn't fixed it. So somehow airport or other aircraft liveries are breaking the 787. That makes no sense.

I thought the EFB was supposed to be enabled in the 787 with SU13? Mine looks just as unpowered as ever. No updates showing in Content Manager, default livery, no 787 mods installed, etc. The Simbrief option is there now in the MCDU, but the EFB panels just have no power and the buttons that seem like they are enabled have no effect either.

Well, not sure what changed, but updated from 2.7.6 to 2.7.8 fixed it. Also the Couatl process shows up under MSFS in task manager now instead of a separate process in the list. Having never looked for it before this issue though I don't know if that was correct behavior previously as .7 they recompiled the engine with SU13's SDK (but this was happening originally on SU12). Going to guess 2.7.4 or .5 didn't install correctly and it took a couple updates to fix it. I had even cleared the downloads/install caches for Virtuali before updating to 2.7.6 as per a fix I found on their forum for a thumbnail error that was occurring.

Now I'm really confused on this. After updating to SU13 I did some more testing. With just my payware mods installed I loaded up a flight with the Fenix and the scripting engine would exit when returning to main menu. Exited and added my usual collection of addons back in via addon linker. Tested again with Fenix, and same behavior. Then loaded up the FBW latest Dev (which I had been using when I originally posted this issue) and I'm wondering if it's an issue with FBW's GSX integration options because returning to main menu left it running still.

Nope the sim is not still actually running. Closing out Couatl in the task manager reverts the Steam "play" button back to the green "play" state. There's nothing in the event log except the startup error for afc_bridge that happens when my Bravo is not connected but that's it.