FAC257

I've wondered all along why South America & Africa have been almost completely ignored for updates. I think even going back to MSFS2020 they didn't do much with either of them. Even the Caribbean which had a decent 2020 update, went backwards in 2024. Forest

Check the fuses under the panel. The one that controls the avionics may be pulled out. FAC257

Mark, That's encouraging that you have those two working in 2024. Did you copy those over from 2020 or install into 2024 from the Marketplace? I have Verticalsim's KTPF & KSRQ and they are perfectly okay. I may try the email route. I don't use Discord for anything unless it's a last resort. Too much like trying to listen to a conversation in an elementary school cafeteria at lunch time. 🙂 Thanks, Forest

I have the same issue with Clearwater Air Park KCLW and Plant City Municipal KPCM, both Vertical Sim airports from the Marketplace. I had them in MSFS2020 and were eventually listed as compatible in MSFS2024. One doesn't show up at all and the other is missing all of the buildings. They are the only two airports I own that didn't make the 2020 > 2024 translation. I've re-installed them several times as MSFS has evolved, but still no go. Forest

Salasnet, Thank you for this one. Merritt Island was the very first airport I ever flew out of with my father. At the time he was the main flight instructor for the Civil Air Patrol in that area and we used their Aeronca L-16 that they kept here. Followed the link in the readme and grabbed all of your other Florida sceneries this AM. It's good to see some 2024 Florida sceneries showing up. Thanks again. Forest

My first choice when in the mood to fly is always the Boeing 377. Just under 8000 hours in my FSX logbook and 1439 of those hours are hers. FAC

Whenever you load a "Saved" flight directly from the FreeFlight GUI, and the aircraft does not completely load correctly, try reloading the "Saved" flight again from the drop down menu in-sim.From the FSX in-sim drop down menu you can use "Load" or "Reset" on that same "Saved" flight, and sometimes it will bring up the aircraft systems that didn't load correctly straight from the FFGUI.For some reason loading a "Saved" flight straight from the FFGUI and loading/resetting the same "Saved" flight once in-sim are not always the same thing.FAC

I noticed the same thing, but when I looked at the pop-up ToolTip it reads 58PSI. I believe this would technically put the oil pressure in the green.FAC

The turbo flashing nav lights happen on a few FSX aircraft that are using older FS9 configured lighting. I've found it on non-Carenado aircraft also. I thought I had posted this fix in here, but after looking I realize I never did. I went through all of the Carenado FSX hanger and corrected the lighting for any of their aircraft that have the turbo flashing nav light issue. This gets rid of not only the turbo flashing, but also repositions the nav lights so that they more accurate with their 3D placement on the models. The nav lights in FSX float a few inches from their actual locations while flying. This is an FSX problem and not a Carenado issue. I tried to find the best physical location numbers that work most of the time. :) I have everything set to use the default FSX lighting effects so that this fix would work for everyone. I just added the last section the other day after buying the BE58 and finding that they left out the tail light. For the BE58 just use one of the lines I have listed and add it to the bottom of the Baron's lighting section. Personally I'm using the C340's blue strobe on the tail. It's not that it's realistic, I just like the way it looks. :) Arrow [LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -3.05, -17.95, 0.62, fx_navredlight.1 = 3, -2.90, 18.00, 0.62, fx_navgrelight.2 = 10, -1.80, 0, 2.10, fx_vclightarrowlight.3 = 10, -2.25, 0, 1.90, fx_vclightarrow2light.4 = 2, -3.31, -18.13, 0.62, fx_strobelight.5 = 2, -3.14, 18.13, 0.62, fx_strobeMentor USAF/NAVY[lights]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, 0.49, -17.28, 1.5, fx_navredlight.1 = 1, -4.00, 0, -0.79, fx_beaconcarenmenlight.2 = 3, -17.71, 0, 1.98, fx_navwhilight.3 = 3, 0.51, 17.34, 1.5, fx_navgrelight.4 = 2, 0.35, -17.29, 1.5, fx_strobelight.5 = 2, 0.30, 17.35, 1.5, fx_strobelight.6 = 4, 0.30, 0.00, 1.10, fx_vclightcarenmenlight.7 = 4, -4.30, 0.00, 1.10, fx_vclightcarenmenMooney [lights]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -2.78, -17.76, 1.75, fx_navredlight.1 = 3, -2.50, 17.78, 1.75, fx_navgrelight.2 = 4, -3.22, 0, 1.80, fx_vclightcarlight.3 = 2, -3.0, -17.88, 1.7, fx_strobelight.4 = 2, -2.72, 17.88, 1.7, fx_strobelight.5 = 1,-15.50, 0, 6.75, fx_beaconC182RG[lights]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -3.20, -18.11, 2.95, fx_navredlight.1 = 3, -2.90, 18.16, 2.95, fx_navgrelight.2 = 4, -3.0, 0.0, 1.3, fx_vclightcarlight.3 = 1,-20.42, 0, 6.68, fx_beacon_smllight.4 = 2, -3.51, -18.16, 2.88, fx_strobelight.5 = 2, -3.21, 18.19, 2.88, fx_strobelight.6 = 3,-20.37, 0, 1.46, fx_navwhiC182Q/C182QLR [lights]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -3.20, -18.15, 3.03, fx_navredlight.1 = 3, -2.95, 18.20, 3.03, fx_navgrelight.2 = 4, -3.0, 0.0, 1.3, fx_vclightcarlight.3 = 1,-20.42, 0, 6.70, fx_beaconlight.4 = 3,-20.37, 0, 1.46, fx_navwhilight.5 = 2, -3.20, 18.30, 3, fx_strobelight.6 = 2, -3.45, -18.30, 3, fx_strobeC206/C206 Cargo [lights]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -3.12, -18.10, 3.45, fx_navredlight.1 = 3, -2.82, 18.15, 3.45, fx_navgrelight.2 = 4, -3.27, 0, 2.05, fx_vclightlight.3 = 1, -21.1, 0, 7.5, fx_beaconlight.4 = 2, -3.40, -18.16, 3.45, fx_strobelight.5 = 2, -3.10, 18.16, 3.45, fx_strobelight.6 = 3, -21.25, 0, 1.98, fx_navwhiC206 Amphib[lights]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -3.12, -18.10, 3.45, fx_navredlight.1 = 3, -2.82, 18.15, 3.45, fx_navgrelight.2 = 4, -3.27, 0, 2.05, fx_vclightlight.3 = 1, -21.1, 0, 7.7, fx_beaconlight.4 = 2, -3.40, -18.16, 3.45, fx_strobelight.5 = 2, -3.10, 18.16, 3.45, fx_strobelight.6 = 3, -22.1, 0, 1.98, fx_navwhiBE58 Baron light.5 = 3, -24.33, 0.01, 1.87, fx_beaconbluec3, = C340 Blue Strobelight.5 = 3, -24.33, 0.01, 1.87, fx_strobecarc3, = C340 White Strobelight.5 = 3, -24.33, 0.01, 1.87, fx_strobe, = Default White Strobe light.5 = 3, -24.33, 0.01, 1.87, fx_navwhi, = Default White Non-StrobeI have the entire Carenado FSX hanger, so if you don't see one of their aircraft listed here, it's because that particular model doesn't have the problem.FAC257

Looking at the FSX Payload Manager, it looks like there maybe an issue with the default CG. With the aircraft completely empty it puts the CG just behind the prop. If I put a 150 person in each seat, it takes 1000# of weight in the aft baggage compartment, just to bring the CG indicator to the front CG limit mark.With just a pilot and a copilot and 2000# in the aft compartment, the CG is about normal, but then the aircraft is far beyond over MTOW.FAC

I dropped in to start a thread on the nose down tendancy, but you guys are already on it. The one thing that seems to stand out is the aircraft in level flight, flys at what looks like a noticable nose down atitude. Thinking it maybe like some aircraft that start going nose down at high cruise speeds, I brought the speed down quite a bit, but it does not seem to have any effect on the nose down look. Unless I am completely reading the Artificial Horizon incorrectly, it also seems to be showing this nose down cruise atitude. FAC

I've put a couple of mentions and a pic about the RPM gauge inaccuracy in the issues threads already. With the new .air & .cfg fixs the RPM gauge needle now sits firmly on 1900, but the pop-up tool tip is still showing 1850 RPMs. I may be wrong but I've always been under the impression that a pop-up tool tip reading was more accurate than a gauge's graphic indication.It's 50 RPMs shy at all gauge indicated readings on my end.FAC

Well after making all the .air & .cfg changes you guys have worked out and has been working really well for me, I decided to go for a "Certified Ceiling" fun flight. Directly from the Cessna.com's Grand Caravan sales page it's listed as 25,000 feet. I was scratching my head a bit at that but went for it anyway. :) I took off with only pilot weight, full fuel and no baggage or passengers. It took a while but she finally made it to 25,000' and once up there was flying pretty much on the level. I couldn't make the accent in one stage. Up to 15,000 from take off and then in 1000' steps up to 25K. I cruised at that altitude all day until it was time to decend for fuel. An interesting item popped up during decent that I haven't had a chance to double check with another flight yet. Normally I've only been able to top out at around 136 IAS even after the new .air & .cfg changes. On this flight when I leveled off at 12,000' the IAS was sitting at 150 and stayed there until I started the final decent to land. By using a step down to cruise altitude as you would in an aircraft like a B-17, it gave me a few extra IAS that stayed with the aircraft and didn't bleed off. I haven't had a chance to double check that with a follow-up flight yet, but that sure is what it looked like happened. FAC

Thank you guys for all the work on this!Just leveled off on the first flight after making the .cfg & .air edits and what a difference.12,500'OAT 10CITT 721 (maxed)RPMs 1900Torque 1327136KIASStill want to mention again about the minor RPM gauge readout graphics glitch of the indicator needle is off by about 50 RPMs.FAC

Climb to 15,000'OAT -5CITT 720 (Maxed Out)RPMs 1950(indicated)/ 1900(pop-up)Torque 1512 ft-lbs (Maxed Out)119 KIAS / 137 MPHFAC

Climb to 10,000'OAT 15C (It does work) :)ITT 740RPMs 1950(indicated)/ 1900(pop-up)Torque 1300 ft-lbs115-116 KIAS / 133 MPHFAC

I just took off on my second flight.Same aircraft setup. I think the OAT is always 18C, I'm not sure the thermometer is a working gauge?To keep the ITT temp at 740 I've got the torque at 1300 ft-lbs, RPMs at 1900(pop-up)/1950(indicator needle). I've tried the Prop Condition both High and Low which seems to not have an affect on the numbers. Inertial seperator is off as it was last night.Level @ 5000' and showing 118-119 KIAS/135 MPH. That's all she's got. BTW, I realy like the interior night lighting options.FAC

On the first flight last night I was seeing speeds about in the same range as you guys are already mentioning. Cruising at 5000', 18 degrees OAT, no baggage or passengers, RPMs at 1900/red-lined and keeping the temp at 740 degrees, she settled in at 117 IAS. There was nothing I could do to get her going any faster while keeping everything in the green. There was more torque available but the temp would sky rocket. Once in a while I would notice the indicator needle move a little bit. When it did that, mousing over the needle would give me the pop-up showing a fluctuation between 120-119 IAS, but it would always settle back down to the 117 IAS.One thing that I did notice that maybe important is that the RPM indicator needle and the pop-up tool tip for the RPMs never matched. The actual needle was always indicating about 50 RPM higher than the pop-up. At 1900/redline the pop-up was showing about "1850". If the pop-up was the more accurate of the two, I sure would have liked to have that other 50 RPMs.I had to laugh a bit because the plaquard in the center of the console says to land immediatly if unable to maintain 120 IAS in level flight. Well if that was the case I was in violation of that order throught the flight. :) The only way I could manage over 120IAS was to either firewall the torque or start a decent. Even then with the torque and temp maxed out I still don't think I saw 140 IAS.Other than what seems to me to be underpowered, the aircraft itself is one of the best looking aircraft Carenado has done yet.FAC

With W7 try using the "Show Desktop" button down on the Taskbar. This is the small button looking part of the task bar directly to the right of where the time is showing. It's in the extreme bottom right of the screen.I've found that when FSX "disappears" and won't return to full screen, that toggling the "Show Desktop" button will often reset the sim back to normal. FAC

>>> "It's acting like a defect in the coding in ASX and I guess ASA." <<<I'm not sure if this would at all be related but, just before uninstalling ASA and reverting back to ASX I noticed that dual weather data files were being generated. Just after installing ASA I decided to go ahead and uninstall ASX. Out of old habit I started looking for orphaned ASX folders, files and registry entries. After cleaning things up I found that ASX is still lurking somewhere. Each time ASA loads up it was creating it's new asa-wx-info.dat file and a new asx-wx-info.dat file, even though theoretically ASX wasn't on my system anymore. The replicated cloud layers was something I was seeing regularly using ASA & XGraphics. I'm about 99% sure I never saw those with ASX & XGraphics. FAC

Not a problem. The only thing is that the XGauge uninstall program doesn't actually uninstall the gauge. It only removes the references to it in the aircraft.cfg files. With the actual gauge being a .dll file and still in the FSX/Gauge folder and still being listed as an accepted gauge in the fsx.cfg file even after the uninstall, I just wanted to make sure it was completely out of the picture. When checking for problems I try not to leave any loop holes. As for the developer fix, I'm not too worried. The guys at HiFi have been at the upper levels of customer service and support as far back as I can remember. You can bet they are already reading and looking into it. FAC

Well, I just went and disabled the Xgauge completely. Uninstalled it from all the aircraft.cfgs and then disabled the .dll file itself. Renamed it to .old in the Gauge folder and removed the reference in the fsx.cfg file. The problem seems to have corrected itself. I'm back up to what looks like my old constant FPS numbers. This is using the exact same save flight at the same airport. With XGauge active I get the cyclic FPS drop and with XGauge disabled I don't. FAC

I was getting ready to log in and report the very same issue, but saw that you guys were already talking about it. I'm actually getting a little lower FPS drop down to 1.7FPS. It's very cyclic in nature when it starts, but it doesn't seem to happen all of the time. When it starts, about once every minute the FPS will drop to as low as 1.7 for about 2 or 3 seconds and then returns to normal.Been watching it for the last couple of days and the only constants I can come up with so far is that it seems to happen when I'm on and near airports.I'm currently in the Pacific so the airports have been few and far between. When up at cruise altitude it doesn't seem to happen at all that I've seen so far. The other that is a definite is that once FPS drop cycle starts, I can make it stop instantly by shutting down ASA.I've opened up the ASA menu while this is going on to see if it was in the process of updating/downloading data when the FPS drop happens but so far that doesn't seem to be the issue. The question I have after reading what you guys have already mentioned is the XGauge update. What is it? That may have been something I over looked. Thanks FAC

You can check out this old thread with some detailed info on how to change the effects file manually. I put the section together for the Shockwave aircraft but the same technique works for all.http://shockwaveproductions.com/forum/view...?t=7296&start=0Scroll down towards the bottom of the first page. The turbo flashing nav lights is an issue with some old FS9 aircraft when imported into FSX where the creator used custom nav lighting effects instead of the default FS9 lighting effects. Personally I only ran across the issue with Carenado & Shockwaves aircraft. The other and easier work around is to just edit the aircraft.cfg file so that the lighting section entries for the lights that blink too fast point to default FSX nav lighting or some other aircraft's nav lighting that you like.

JimGlad to be of help. ThanksFAC