flightwusel

I think I should clarify and say "low spec PC or run X-Plane on a huge screen resolution". Because I know some people have a $3000 PC but run into FPS/VRAM problems due to huge resolutions.

I am totally with you. I can't stand the default sim's boring landclass textures and low-res elevation data. I mean it is ok, they are just the base product which is just a placeholder for ... X-Plane with Orthos 😉. Unless you have a low spec PC I honestly can't understand why people fly with the default landclass scenery!

Come on, stop it. That's so low.

I am not sure what's planned. The last thing I've seen properly communicated was https://developer.x-plane.com/2024/09/around-the-office-friday-the-13th-edition/. Planned for 12.1 and still missing: Capable plugin-controlled Weather API + new Weather Radar API. (And for @Mike_CFII_MEL: "weather branch also has network sync of trucks and jetways to external visuals"...) Planned for 12.2: Dark cockpits/lighting

Even doing manual XP weather is not really reliable for that low fog/cloud layer case. If you reduce visibility without any cloud layers, it seems to use that visibility from GND-UNL (ok). When you add a low cloud layer, it works nicely, applying the visibility from GND to the lowest cloud layer (ok) – that looks good by the way. When you remove that cloud layer again, it might now work nicely as well, keeping low clouds visible (?!) So it is not just live/automatic weather still having problems translating well to X-Plane weather values, sometimes it is also the engine being plain buggy and somehow having a bad initial state or hidden state variables. But I mostly get lucky with live weather these days.

Navigraph seems to have a hickup with the 2501 AIRAC. https://forum.navigraph.com/t/cycle-2501-installer-packed-with-2413-data/18433

Why always snarky when this stuff comes up? Relax.

There is a lot of thought and truth in that list.

There are new developer groups (Jetstream and RetroWings for example) and high-profile releases (Torquesim Citation 525), but they are not on the .org and they don't get reviewed on that review site. Go figure 😉.

My first step is to see if fans are doing more RPM than needed. Keep a close watch on temperatures and adjust the response curves in the BIOS or in an external program (or your graphics card driver program). I try to have them turn as fast as I just can't hear them yet even for lower temperatures to prevent heat build-up. Watch airflow. Is it too warm in your computer case? If they turn increasingly quicker like in your case that might be the case (pun intended). Is it better if you keep the case open? Maybe an additional case fan helps or a new case with good cooling. Always go for the biggest fans – they are more quiet because they turn slower to shuffle the same amount of air. And 4 fans at low RPM make less noise than 1 on high RPM.

There is no base mesh but Ortho4XP works fine to create scenery if you have elevation data. I've flown Svalbard-Anchorage once Svalbard-Anchorage and didn't have navigational problems in a ToLiss A32N.

You can build your tiles (also for AutoOrtho if you want) with Ortho4XP. Use apt_smoothing_pix=16 or higher as the one used with the default AO scenery packs was found to be too low in several places. Or create a JOSM patch as usual. Maybe also interesting for you and others with these old AO scenery packs https://forums.x-plane.org/index.php?/files/file/90288-autoortho-scenery-sets-patches/

When? Just soon™ is like zero information...

I would like them to finally implement holdings to make the whole line VATSIM capable. Can be a viable workaround, like we have with the default GPSes with SUSP and OBS.

That's related to my request here: https://github.com/albar965/littlenavmap/issues/1048 It would be great if littlenavconnect would terminate cleanly when it receives SIGTERM. Btw. I am using the -q command line switch now in my automation, but it is a workaround IMHO. Thank you big time for your dedication to Little Navmap!