mmcmah

After all the ideas in here and the validations of removing the 2024 cache, I decided to give it a try, despite having very few stutters. My experience was the complete opposite of others here. I went from very few to many stutters by removing the cache. I re-enabled it.

Does SI see the PSXT traffic? I tend to find that BATC completely ignores the PSXT movements when giving me instructions. I mean, I know they're totally separate systems, but it's like it doesn't see them.

It does work great. I used it at WSSS just to see that it worked. It took a wasn't immediate, but I was looking around the airport and from one second to another I noticed that the jetways were attached. Then I saw one jetway move away and the plane taxied away under ATC instructions (it moved before the instruction, but it was still cool). I normally just use BATC for ATC and PSXT for the traffic.

Hi Nico, I haven't downloaded it yet, but the newest BATC Experimental branch version has jetway connections to their injected traffic. Like PSXT, they don't inject traffic and let the sim control it, they manage the traffic's placement constantly. Here is the description from their release notes: Jetways For AI Traffic (MSFS 2024 only) For the first time in a public build, AI traffic parked at a gate now gets its jetway connected, including arrivals once they reach their stand, so busy terminals finally look the part. Works on MSFS 2024 SUb & SUT, and adapts automatically to the sim version you are running. Jetways reconnect if you move away from an airport and come back, this is a sim 'feature' that we have to work around. Allow around 20 seconds after arriving at a new airport before jetways start connecting. A few stands won't connect where the sim's own jetway data is missing or incomplete for that gate. Requires no particular traffic model set or additional software to work Low resource impact as it does not insert 'ghost aircraft' or any other workaround to get connections

That was a stunningly good video! Watched it start to finish.

COMPLETELY AGREED. I also helped with the beta testing of the H160 back in MSFS2020, so I do love a good helicopter, but lately I've been switching between the Rafale and non-Rafale-aircraft.

I think he means the Map Enhancement mod. I use that as well, although I hadn't seen any difference with the landing gear culling mess, but I will look again. As for the benefits of the mod even with the default map, I do agree that Medium and higher make a very difference to me.

I bought the F-22 for MSFS2020 and it was - fine. I thought it was similar to the F-35 from IFE, and that one had three models and was generally more interesting to me. So, I never flew the F-22 after the first weeks of having it. I contemplated getting it for MSFS2024 when I came back to simming after a hiatus, and saw that there wasn't a 2024 version at that time, but that they were developing one that they were going to list on the Marketplace. Fair enough, more and more devs seem to be doing that and I have chosen to buy things on the Marketplace more as a result. I understand the anti-piracy benefits to the devs. However, where I thought they lot the plot was in telling people that anyone who bought the original outside of the Marketplace was SOL and had to pay the same price as someone buying it new. That killed any interest from me, and I have been ever so happy to be flying the Rafale. It's so far ahead of the F-22 anyway that it was by no means a loss to give that one up.

Thank you!

Thank you, Nico! As always, amazing responsiveness! Please remind me if there is a place to make contributions to your Copilot usage and general maintenance of this wonderful tool.

16.5.1 causes issues with the new versions detection. It is confounding MSFS2020 versions with MSFS2024 versions. Also, it is treating the most recent prior versions of a paid product for which there is now a V2 or V3 products as no longer viable to send. Two examples: From the log file: "Warning: update FlyTampa KLAS to version 3.2.0 first; no airport file is sent to TBLO" - I have the latest version from the V2 release, and haven't decided whether to spend the 5 Euros to buy V3 after I read about a lot of issues with it. In order to use PSXT correctly now I HAVE to buy V3? From the log file (more in the log): "Warning: INIBUILDS EGLL version 1.1.0 is used, but newer version 3.1.4 is available" - The version I have installed is the latest version for MSFS2024. The latest version for MSFS2020 is 3.1.4, so it's mixing two different things. There are other iniBuilds airports that have diverging 2020 and 2024 versions, and also with NZA Simulations. From the log file (more in the log, not just Orbx): "Warning: ORBX ENAL version 1.0.0 is used, but newer version 1.1.0 is available" and "Warning: ORBX LSZS version 1.0.0 is used, but newer version 1.1.0 is available:" - For both of these airports, the version that I have is the latest one one the Orbx Central app.

Fair enough. I am going to be sending you a text file with 15 of them shortly. I have another issues with the latest release, but I will start another topic. Actually, I just added my comments to your pinned post. Thank you.

Hi Nico, I am getting a number of airplanes showing the yellow warning that the wingspan cannot be detected and that the maximum wingspan is being used. I know I can go in and find the aircraft.cfg file and adjust for those that I have available (which is likely most), but might there be a way to please default to the minimum wingspan value rather than the maximum? That might make it easier for everyone, rather than having to edit the files individually or asking you to add a mapping. Thank you.

While in My Library, you should be able to search for "Burning Blue". It should show up as a Community add-on, where you can enable/disable it.

Here are three screenshots at two different locations. The locations are KEYW facing West off of the end of runway 27 and VTSP facing in the general direction of runway 09, but moved off of the airport itself. Each of the locations has: PG Only Bijan Burning Blue Designs Biome Gallery In my opinion, while I really like Bijan's work, I find that it tends to leave the default trees and overall overabundance of trees too prevalent in the sim when you're outside of the areas that have been modified directly. As such, I find that the BBD work leaves everything less dense (maybe too much so in certain jungle areas), but --- to me --- it makes the sim look better because it doesn't look so overgrown. What I will try to do is use BBD for most things and then Bijan for those areas that I know have been modified to see which I prefer for those areas. For the more default areas, I definitely prefer the BBD option. What I found in testing this is that you can have both loaded and enable/disable as appropriate in the My Library configuration options, but once you enable one, you can't go back to the PG only (not that I ever do other than for this test) unless you exit the sim because it will reload the assets from the last-enabled biome edits, at least if you reload to the same airport.

I've been using Bijan's mod for a while. Definitely like it a lot. Tried this one due to the extensive description of what they've done, including getting on their Discord to learn more about it. Boy, am I glad I got it! It's better than Bijan's, in my opinion. It does a better job at really changing the biome look and "feels" more right to me. I feel like Bihan's adds specific tree types but generally keeps the same feel as the default outside of the specific areas that have been addressed directly by Bijan. I will try to post pictures tomorrow, but to my eye, BBD makes a more drastic difference to the scenery. There are things that can be improved a little, but I'm really liking it.

Have you checked your TBLO file (press the TBLO button on the interface)? Are those airports in the file? If so, you need to email the .zip file to Nico.

I had the prior version's installer, but I think that when you run the installer, you get the choice to install the latest version or select "Other versions" and then pick the one you want. I went to the most recent one before this last one.

Last update broke my planes as well. Reverting to the prior version fixed this for me. Disabling automatic updates should be the recommended setting for this add-on!

I will try to capture the exact sequence. In the meantime, after updating to 15.14.0, the timing from first seeing the interface to finishing the scan is 12 seconds for 168 third party and 141 sim-addons. This is after the initial load in 15.14 took 26 seconds, but maybe there were other things being cached/reloaded.

Hi Nico, I notice that in the last few builds you have added an automatic scanning of airports to the program startup. Is there a way to disable that? My enabled airports rarely change and yet I have to wait for the scan to finish. I have the following parameter in my parameters.xml file, but I assume that it is not deprecated? " <parameter name="ALWAYS_SCAN_AIRPORTS" value="false" />" Is it possible to re-enable that, although I note that we have now also lost the ability to launch a scan from the UI? On a separate note, if I start PSXT and the RT app before entering the flight, I find that it's very fragile and PSXT constantly restarts the connection (especially if I started them up during the sim loading). They also almost never work when I load a new flight after completing a flight, entering a constant reconnection cycle in PSXT. Is this a known issue and I should just close them both before starting a new flight? Thank you.

As far as I am aware, you need to download the update if you have downloaded and installed on your system manually. If you are streaming, you should get the update applied whenever it is released. Note that UrgentSiesta's release notes might have come from an email from them (I received one as well), and may not have made it to the Marketplace yet. I haven't looked.

Yes, I saw the video. The plane looks very nice!

Thank you as always, Reset! I'm using the RC, but I don't use RTSS. I did have a quick question on the right way to configure when looking to maintain the auto TLOD as high as possible on landing. I've currently got it set to FPS Sensitivity with native frame gen and FPS set at 90. It works great to increase TLOD as much as possible on the ground and on climb out. However, when landing, I always drop from my Max TLOD to my min TLOD by the time I reach my min TLOD altitude. Any way to keep the TLOD maxed as much as the headroom will allow while landing? I'll go back and read the readme file, just thought I'd ask if anyone knew. Thank you.

I was coming on to post this exact question. I'm on the latest stable build, not a test build.