mtbparker

Hey Folks, I'm wondering if anyone on here is flying the new CT182T for X-Plane11. If so, do you see low fuel flow readings compared to what the POH says they should be for your given power settings? Sometimes, I can't achieve the fuel flows listed in the performance charts even with full rich mixture. As a secondary problem, which I think is directly related, the ITT (T.I.T. actually) readings are unusually high. Anyone? Thanks in advance.

My gear lever wouldn't move either. It sounds like we're all experiencing the same issue. I will try to pay more attention to my scenario to hopefully provide more info about how to reproduce it. For me, it seems to be random. Random bugs are always fun, aren't they? Cheers, Tom

I've had this exact same problem happen a few times. It's definitely a bug and it's a bit annoying.

This is an older topic with a work-around already. But I just received the 1709 update yesterday, 12/2, and it didn't contain any patches to correct this flickering problem. But, yes, the uninstall/reinstall fixed the problem. This is just a heads up and a thanks for the support. Cheers, Tom

BTW, the math adds up. If the pause is every 53 seconds, and the act of saving the data takes 7 seconds, there's your 60 second interval. And 7 seconds sounds about right for the time-to-save duration. At least that's what I experience.

Glad it helped. Cheers, Tom

Are you using FSUIPC autosave? Does the pause coincide with the autosave interval? I had the same issue with the 777 P3Dv4. It seems that it now takes significantly longer to save the flight data than it used to. I had to disable autosave to clear my problem. Hope this helps, Tom

Hey Folks, For the sake of record and to help the next guy in line, I'd like to report that I had a fairly predictable CTD with P3Dv4 and that I'm pretty sure I fixed it. I flew three flights with the PMDG 777: 1) KDEN->KIAD, 2) KDEN->KIAD, 3) KDEN->KIAH. All three flights crashed to desktop during the descent on the arrival. Typically around the FL240 mark, which for me is when I start mucking around a lot with things for landing -- particularly the FMC. For flights 1 & 2, it happened in almost the exact same spot over MGW VOR on the GIBBZ2 arrival. Flight 3 was almost the same except of course that I was in a different location. That eliminates a scenery issue. Using AppCrashView, I could see that all 3 CTDs were occurring in clr.dll which is associated with .NET framework. I upgraded my .NET framework from 4.5 to 4.7. I also cleaned out several versions of .NET 4.6. (I'm a SW developer by trade and had Visual Studio 2015 Community Edition installed which brought with it a whole host of .NET libraries. I uninstalled all of that too.) My fourth flight, from KDEN->KIAH was successful. My system setup: EVGA X99 w/ Intel 5930K CPU 8GB RAM 256GB Samsung EVO SSD for Win10 Anniv Ed. OS 256GB Samsung NVMe 950 M.2 SSD for P3D 4TB Western Digital HD for storage. EVGA GTX 970 Graphics Card P3Dv4 4.0.23.21468 ASP4 w/ ASCA B6383 Orbx, all available base packages and NA regions PMDG 777 FSDreamTeam / FlightBeam KIAH, KIAD, KDEN A2A Commanche, A2A C182 I hope this helps. Also, I've only had one successful flight. But the crash was pretty repeatable, so my confidence is high that I got it. Cheers, Tom

Oh my! What a difference!! I can say, without a doubt, it's working. And it now makes me think I've had this goofed up all along, even with the old installation.Being that you're one of the AS team, can I pass along how I got this way? In your installation wizard, somewhere along the way, it asks you to Browse to the FS9 folder with the caveat that for WideFS users, don't browse to the remote FS9 installation. I interpreted that to mean only one thing... the FS9 folder on my local machine. My next logical step was to install FS9 on the WideFS machine and point AS6 to it instead. Obviously, I goofed. It's now working like it's supposed to, but if I could pass feedback to you, it would be to perhaps clarify the installation steps a little better. Specifically, mention that for the WideFS installation, you need not browse to an FS9 folder, but to another directory. (Or something to that effect.)Thank you so much for your help. It's working like a champ now!Tom

Maybe I should provide a little more info that might be relevant.I followed the WideFS installation instructions that were provided with the install package. This means that I have a copy of FS9 installed on the WideFS computer. When I "Browsed to the FS9 folder" during the installation wizard, I browsed to the local installation on the secondary computer computer. At the end of the installation, I mapped a drive from the primary computer, navigated to the AS6 installation on the secondary comptuer and ran the ActiveRadarConnector.exe on the primary.The weather does work. ASV6 does have control of the weather on my primary computer.

Hello All,I was wondering if you could provide me a little help. I have ActiveSky 6 with the SU4 service pack. I've got it setup in the "WideFS" configuration. And I need a little help.This past week, I was forced to rebuild my secondary computer (aka my WideFS computer) from the ground up due to a hard disk crash. Part of that rebuild included setting up WideFS and reinstalling ActiveSky. No worries there.But I'm not entirely convinced that my ActiveSky Graphics and the submittal process is working like it's supposed to, and I was wondering if you could give me a little info on the underlying implementation.When I make my Quick Selections and press the "Send to FS" button, I see a lot of disk activity on my secondary computer, but very little (almost none) network traffic between the secondary and the primary computer (the one with FS9 on it).How does the submittal process work? Are all the textures pre-installed on the primary computer or does the secondary computer transfer a set of textures over to the primary computer when you make the submittal? Based on the disk and network activity, I'm not convinced that my primary comptuer is picking up the graphics changes.Any insight would be greatly appreciated.Thanks,Tom