All Activity

Perhaps I am missing something, but I cannot figure out how to click the DLC arm button on top of the spoiler without moving the camera all the way down in front of it and rotating it so I can see it. I am sure it was very easy for the captain to reach down and press it (though I do find myself wondering at the wisdom of having the lights being on the forward end of the spoiler vs elsewhere, I guess he had to stick his hand in front of it to see if the lights were on?) Can a clickspot be added on a screw somewhere or something similar to arm DLC, please?

Liveries also affect performance. First-party liveries are mostly decal-based, which use VRAM more efficiently by scaling with camera distance. Texture-based liveries, common in community creations, are often high resolution (4K or 8K) to preserve detail up close, which increases VRAM usage. While ours are optimized, community liveries may not be, and that could impact performance. What we're doing We’ve reached a point where further optimisation could mean reduction in visual quality or require removing features (example no-cabin variant). We’re continuing to review incoming reports and are carefully evaluating all options for future updates. So we please ask to include in your reports also the sim settings, along with your specs and the in-sim fps counters. Interim Recommendations If you are suffering from VRAM overruns frequently, try the folllowing settings - Set Texture Resolution to Medium - Adjust Object and Terrain LOD as needed (120 is a good baseline to begin with to then adjust as headroom allows) - Disable Raytraced Shadows - Lower Volumetric Clouds (avoid Ultra in heavy weather) - Keep resolution at 1440p or below on 8GB VRAM systems

I recently bought PHNL scenery (MSFS2020) and downloaded the GSX profile using INIMANAGER. I cat use any jetway, it says Bad Gate Info (or something like that) How to fix this?

I can confirm this! Finally had a chance to test the update…feels switching views has way more stuttering. Is there any chance of seeing low res interior textures for this bird?

i see I already mentioned this haha

Hi, Thanks, we’re open to reviewing this further. Do you have any references to support it? Our current understanding is that the smoke occurs before internal combustion, caused by residues and oils burning off after the engine has been sitting idle. So basically during ignition prior to fuel being introduced.

Interesting, internal testing reports are exact opposite but appreciate it. We also have further optimisations coming in v1.0.3 (potentially next week). Please check again and let us know. With regards to degraded perf/stuttering, let us know if theres any specific conditions where you particularly notice it. Or any actions taken that trigger it. Thanks!

In fs2024 the dash 8 100/200 is a missing aircraft that would be a blast in career modes (would work for passengers, cargo, and VIP) and generally missing from career mode action (the 200 is a upgrade built on the 100 platform) plus there’s going to be different cockpit configurations now that there’s a cockpit upgrade in the works for the dash 8 IMG_7935.webp

I today found a workaround which seems to solve the issue even through restarts of the MSFS 2020 (not sure if it also survives a PC restart but potentially): Start the sim and place the plane to an airport which fails Switch to desktop and open the System tray menu Right click the "Couatl" and select "Restart" Switch back to sim and wait for GSX to reboot Go to GSX menu/Reposition aircraft and select a gate For me, the plane was placed correctly at the gate. Going to menu and selecting another faulty airport also worked from now on. Closing and restarting the game still works. Not sure if that somehow entered some GSX profiles but for now it looks good. Tested on FAOR and EDDF, both with 3rd party addons. EDIT: Verified on another airport which previously failed on all positions (ASOBO KSFO) with no problems. Aircraft spawns correctly at the gate. So after executing the steps from above, no further actions are required besides spawning the airplane as usually from the MSFS menu to a parking position.

More liveries for a350 on xbox when, been asking for months

... seems to have started working suddenly using SAM2 (the smaller plugin, 12MBs as opposed to SAM3's 1.14GBs!). Some of my airports need SAM3 tho -can the EGKK jetways work with that plugin too somehow?

Make sure you switch from INS/GPS mode to Radio mode - Localiser and ILS will not work otherwise - I too however have had issues with the Autoland configuration. I know that its a fail pass system that needs to have everything done in order for it to activate but I'm not sure what those things are. Fully configured with VRef set, flaps 33, gear down, autobrake med, both navrads tuned to the ils and courses set, both CMD active and GS intercepted from below, yet I still cant make the ** thing work Hope that helps some of you at least with the ILS/LOC issue, but Autoland seems kaput

Via IniBuilds, I have bought the Origami London Gatwick - my (very) local airport, just a mile or so away - and am trying to get the jetways to move. I have the SAM plugin installed, but no luck so far. Which version of SAM do I need for EGKK jetways to work (and where will I find the most recent version? SAM Suite, SAM3, SAM2, SAM_Library..? The link in the EGKK User Manual does not work - the file is no longer there on Github). Are there detailed instructions somewhere as to how to get the jetways moving at this specific airport? Gave up using SAM to be honest - it was more trouble than it was worth, but want to give it another go for the sake of EGKK. Assuming the SAM I have installed (I have SAM 2 and SAM3 plugins to choose between, plus the SAM library in Custom Scenery), what must I do to see moving jetways? When I open the SAM3 window via the plugin menu, it shows EDLP, not EGKK as my departure. Sam2 shows the new EGKK in its plugin interface if I uncheck the auto option, but clicking on any gate does nothing -all seems dead. Thanks

I can confirm I am still having this issue. Is this something that will be resolved in an upcoming update ?

Most of iniBuilds WASM crash is during MFD_gauge_update execution with code : 0xc0000005. So that's not SIM's issue. That's bug inside the plane's code. This is 100% fixable.

How do I add new textures to the F27 in MSFS2020?

Currently hit or miss. When it WASM-crashes during early stages of FMC programming, it doesn't hurt so much, but more than half of all flights end in WASM-crashes or freezes. @Ini: Is there an update you can provide or a roadmap? I'm trying to understand if you're close to fixing this or if this will persist midterm / for the foreseeable future. Especially flying in a VA and constantly cancelling flights or disconnecting on controllers on the network is unpleasant, to say the least.

Had a freeze today when approaching Indira Ghandi Airport in the A359 (no cabin) while setting the BTV. 😞

Greetings, Any chance we could get an eta on this? Thank you John

Also it will go from the last loaded waypoint back to WP1 if the remaining waypoints are left blank In my case of flying arounn a hand full of waypoints, I left WP8 and 9 blank.. so it automatically switched from WP7 to WP1. 🙂

Just to add to the above, after some further flying around in circles and testing out the waypoints - I think the INS sturggles or does not recognise changing to a waypoint when the LAT/LON is either N/S0000.0 or W/E00000.0. This may be because it thinks the LAT or LON has not been loaded yet.. How each waypoint starts out when not loaded (WPT8 in this example). I changed the waypoint in the example above to N5006.0, E00000.1 and it worked by automatically changing to the next waypoint. Hope that helps - I just can't quite find any data on that being a real world issue.. only thing close it something called null island issues.

Okay another flight done and noticed some things with repaints. Just flew BAW Landor G-BLUS and everything worked perfectly. Pan Am I flew before had no DH tape and also the ILS issue. So I wonder if its repaint dependant.

I cheat and make the OAT 36 when doing the calculations. Any higher and it doesn't give all the information.

Did a flight today, can report that tuned nav1 and 2 with both autopilots engaged. She captured the LOC as I could not engage the ILS button. Once on the LOC and catured I could activate the ILS switch. Would not capture the G/S however. So 50% there.

Thank you! Worked a real treat, all installed. Good work. Doing a (not at all similar to the before test flight) fully loaded, 222.5 ton YSSY-RJTT flight. Climb out to 1500 on 34L, turn to RIC NDB. Hit INS and VS 1000fpm till clean, around 250IAS. Hit TM and VNAV. Engines roll back from .6EPR to idle then move to climb .445 and kind of maintain 250, a lot of VS changes (500-2500). After FL100, plane drops to 500FPM until 320IAS. Now we are happily porpoising to FL320. From 500-2000. Captured FL320 in a fairly unattractive style, 500 feet before the engines rolled back then reved up. How ever we did not blast past and sat happy at FL320. It had a more solid climb performance in the initial release, I would say the 1.0.2 update made some aspects worse.