These will affect all the airports in the region(s) they are written for and can affect which vehicles are available for your airport services.Okay, at first it was an annoyance that happened every 4th flight or so. You also might want to search for LivingWorld_cfg files as well. The SDK is super expansive on this topic with plenty of instructions and examples and hints and tricks, but it seems many developers don’t have time to actually read the SDK or bother to follow it’s instructions. But filenaming and contents of the Services file is super important to it working properly. So just removing all of them is a brute force method of fixing. I put Services files in all my packages and they work fine. On Xbox, pretty much your only recourse is to remove the offending product.
Tune atc radio to ground Pc#
If you’re on PC it’s easy enough to fix by following the naming procedure above and updating the layout.json file with the new path and filenames. IOW…if you find any files in a package called services or service or whatever, and it’s not in AirportServices\ Airport_ICAO_Abbreviation\Services.spbĪt the root level of the package, and it’s possible even the capitalization is important, then it’s highly likely a rogue Services file that can “break” your system. My own testing in the past refutes this, but that testing was all done prior to SU9, so I may be out of date on functionality changes since then). If it doesn’t have that directory, the services file contained within will affect your system globally.įinally the Services file has to be named Services.spb (or Services.xml, though, somebody else has claimed that Services.xml files also break the system. Then inside that, you have to find a directory named the ICAO name of the airport. If it’s labeled anything other than that, like “Airport Services”, it needs to be renamed to the former. (Small note- I also moved this thread to # self-service:scenery)Īs stated above, you want to search through all your packages for packages that have an “AirportServices” folder.
Tune atc radio to ground install#
(I would always back up the Marketplace folder first and restore it before any update appears in content manager for that airport- or simply delete the airport and install it fresh if there were ever to be an update!)
Tune atc radio to ground how to#
I am not sure exactly how to get a faulty marketplace purchase working in such an eventuality… It is possible that the same process of removing “AirportServices” and editing layout.json would work. You could then run MSFS in safe mode, which would disable marketplace purchases, and see if ground services are working using the default A320 at a large airport. To check if that is the case, in that scenario, I would alt-f4 out of MSFS to force the prompt “normal or safe mode” the next time MSFS is run. If you still run into the issue with an empty community folder and have marketplace purchases in your Official/OneStore folder then it could be a marketplace purchase. However, I can’t guarantee that all marketplace purchases are checked for airport services across all airports. If I remember correctly the encryption process for marketplace purchases removes this possibility. I don’t think that marketplace purchases can suffer from the modellib issue. QQ, as you are knowledgeable, do products installed in the official folder (purchased in the market place) can also be subject to this issue and the one of the modellib one? or are these checked by MSFS before anyone purchase it to ensure they don’t conflic?
So I would also check out that the issue is not specific to certain parking spots. If the parking gate is coded as “small” then there will never be a pushback tug available there for an airliner. One final point, even with 3rd party handcrafted airports, not all gates/parking spots have pushback tugs enabled for airliners. Removing the “AirportServices” folder (and probably editing layout.json to remove all references to that folder) should give all the scenery to the airport and allow services to return to all airports. Once you have identified any such problematic add on, you could still enjoy the add on and have airport services across all airports. This might speed up identifying which airport could be casuing the problem. If it is a 3rd party add on then it would probably have an “AirportServices” folder. It can be quite time consuming to track down which add on may be causing the issue. If it is there then the root cause is a problematic 3rd party airport. If you want to check that this is the cause then maybe try running MSFS with an empty community folder and then load into one of the larger airports with, say, the default A320 and see if a pushback tug is available. The lack of airport services across all airports can sometimes be caused a 3rd party airport and has always been the reason why I lose airport services.
0 kommentar(er)
