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!

In theory yes, but I have the 5800X3D and there was no measurable impact (in measured memory bandwidth and in X-Plane) from running my 3600 RAM at 3200. Others might know better but I believe that this chip does not make use of faster DDR4 RAM. Dual channel: yes, you should try to have pairs of equal RAM in the assigned paired slots. If you are unsure just run a RAM speed test with and without that 3rd slot taken and in the correct paired slots or wrong ones. You should be able to measure a clear difference (Dual vs. Single should have ~+50% bandwidth). I run 2x32 + 2x8 btw...

Absolutely nice touch with the radar echo of the other plane 🙂

sim/operation/override/override_planepath is an integer array. -- Define override dataref for plane path local dr_override_planepath = XPLMFindDataRef("sim/operation/override/override_planepath") -- Function to set override (1 to override, 0 to disable override) function setOverridePlanePath(override) XPLMSetDatai(dr_override_planepath, override) end if you want to continue to use the XPLM... functions continue here (I know you refactored your code already... here's an official example using it for example https://github.com/X-Friese/FlyWithLua/blob/master/FlyWithLua/Scripts (disabled)/VFR weather.lua#L6) Your error "attempt to call a nil value (global 'XPLMFindDataRef')" should come from something else. I am certainly using them in my scripts and do not have any special things in ./FlyWithLua/Modules apart from what the default installation brings. You have to use XPLMSetDatavi( DataRef, table, inIndex, inMax ) to set the array value. (See docs https://github.com/X-Friese/FlyWithLua/blob/master/docs/FlyWithLua_Manual_en.pdf page 86). XPLMSetDatavi(dr_override_planepath, { [0] = override }, 1, 1) -- (or maybe [1] = ..., I dont know currently how it works when you only want to start writing from index 1)

FlyWithLua has XPLMFindDataRef(), XPLMSetDataf(), ... built-in like Ahmet uses them. You do not have to do the `require("ffi")` dance to use them. By the way I like this explicit API more than the implicit variable binding with dataref(). So what you do with DataRefs looks totally correct. I stumbled over your readPlaneData() which only sets local variables ("local" is the function scope in this case [https://www.lua.org/pil/4.2.html]) but does not return anything. But you are not using that function anywhere so we can also ignore that. So it must be something about the DataRefs to set AI plane positions and angles. It wouldn't explain random jumping, but maybe you have to set sim/operation/override/override_planepath? (array index 1 for AI #1). I've found a reference to it here https://forums.x-plane.org/index.php?/forums/topic/219328-controlling-ai-aircraft-in-x-plane-11/&do=findComment&comment=2375823 (mentioning that it had to be set on every frame). Maybe you can get some ideas from https://forums.x-plane.org/index.php?/files/file/50534-formation-flying-flywithlua-script/

FF had premium prices before. But I don't regret the B767 ($120 for the Global Package) because I enjoy it a lot and it has a unique function (execute checklists). It sounds they integrated something like that now again with their Co-pilot functions. (I really don't care for their extensive crew and ground functions but that seems to be a trend among aircraft developers and the buyership seems to like it?) $75 for a buggy X-Crafts E-Jet is hefty, but $90 for a FlightFactor widebody seems reasonable to me. Personally I don't know yet if I will get it.

Yeah, prices have sky-rocketed with COVID and are still higher. For VATSIM a simple cheap one will do when you are in a quiet environment. What I always look out for is an USB connection rather than an audio cable because even very cheap ones will have an integrated soundcard circuitry matching the specific microphone - and in my experience that always leads to better voice. I currently use a simple Jabra Evolve 20 MS and am very happy with it. For very good, nice sounding voice (for video conferencing) I like Logitech. But unfortunately the 2 or 3 of the H390 series that I had all had problems with the plastics after some years.

Having multiple views is certainly a missing feature in X-Plane. I liked it in FS4 🙂

Ignore the path that Navigraph draws there. That's not correct: a) because it doesn't do an alignment turn. b) the path shown is for approach categories A&B, your chart is for C&D. Ignore all dashed lines. That is the missed approach. Thanks @Overload for the better chart 🙂 With that out of the way, you'll arrive at the NDB 3000ft+ (in your case from the North), do an alignment turn just as you would when entering the holding (inbound course 297°, left turns) there. From your inbound course it would be a teardrop entry. After this alignment turn you'll be on course 297° directly inbound to the NDB. That's where the procedure wants you (IAF often includes direction, not just location). Assuming approach categories C or D, you leave the NDB on QDR ("radial", but we don't use that word for NDBs) 277° 2500ft+, at DME 5 ICDF you descend to 2200ft, at DME 8 you do a standard turn (3°/sec) to an intercept course of the ILS. Latest at DME 6 you shall have the LOC intercepted (+/- 1 dot) and be on 2200ft. Then follow the glideslope down. That's what I would fly when cleared for the whole procedure ("cleared ILS 12 out of CDF") without any vectors.

Yes mostly (Lua), apart from the X1000 plugin which does only the display of the engine instruments as far as I know. You ask because you want to interface with it? That should be easy.

Well it's out for XP12 since over half a year, has 10.000 downloads, 80+ thanks and 40+ reviews. You are daily on the forums and haven't noticed it yet? Of course it is great and Vlad's video is, too. https://forums.x-plane.org/index.php?/files/file/89178-king-air-c90b-evo-g1000-blackhawk/ Their great Wiki: https://mgateno.github.io/JP_Evo/