virtuali

GSX doesn't have a separate setting to disable AI, it will just use the SODE setting. And, if the scenery uses standard SODE jetways, GSX is not involved in any way in relationship to AI docking to jetways. It is only if the jetways have been placed with GSX.

Don't waste your time trying to play with permissions to get access to the .EXE or any files in the main install folder, they are NOT "just" blocked by permissions, and that's why every technique you know to get ownership of the folder won't work. Those folders are not there! They are "mounted" from an encrypted disk image located in Program Files\WindowsApps\MSIVC folder, each set of files are the app virtual folder structure, encrypted. So, don't lose you time trying to access them, because you'll only risk messing up your Windows install badly.

Not sure I could help, since you are reporting a crash on an non-FSDT airport that uses its own SODE jetways, is this correct ?

If this is the problem, you can't, since DD sceneries have their SODE configuration encrypted in a .SDX file instead of a standard .XML file you could edit. Only them can fix it.

It's possible the gate names in the SODE XML file don't match exactly the names in the scenery AFCAD. While this is not a problem if you use SODE from its menu, it is when you use it together with GSX because, the only way SODE and GSX can communicate with each other what parking they are both referring to, is to use the official AFCAD naming, which is data they already both have.

Yes, you are right, it's fixed in the Live Update now.

Correct altitude ( Navigraph Dec-19 charts ) for the airport is 1411 ft, so our scenery is correct. What I can see in your screenshot, is airport objects that don't belong to our scenery mixed in so, perhaps you have a conflicting airport that, in addition to be conflicting, has the wrong altitude set as well. The most common cause of conflicts are AFCAD files supplied with AI Traffic product, or perhaps another scenery for the airport you installed long ago and forgot about that.

I've got word from Microsoft the update has been released yesterday night.

Hello, we just released a massive update for our Vancouver for MSFS. The scenery is now completely updated to 2020 status, here's the list of additions: • Main Terminal Pier D extension added, complete with interiors. • Airside Operations building area added, including a working Wind generator that reacts to wind direction and speed. • Updated and added ground details to the West De-icing pad. • Added D5-D7-D9 taxiways at the start of RWY26L. • Added displaced threshold to RWY26L. • Added overrun areas to runways 13/31 ends. • Added Windsocks and ILS antennas. • Updated background and aprons around the former fire training area. • All Ground Markings for parking spots updated to current visual style. • All parking spots positions and numbers updated, to match current 2020 charts. • Many ground markings added or updated. • Added several GA parking spots in the south area of the airport. • Many new vehicle paths added or updated to match the airport changes. • Updated Magnetic variation to 2020. Fixed all ILS auto-approaches. • Added HSBC logos to jetways. • Added more varied textures for shops in the terminal interiors. • Fire Training airplane moved. The update can be downloaded now, by running the FSDT Live Update. We also sent the product to Microsoft, so users buying from the MS Markeplace ( when it will be available ), will get directly the updated version.

Converted sceneries work now, but later on MSFS users will demand things specifically made for MSFS. Yes, and they'll look better too, and can do fairly easily things that are hard to do in P3D, like sloped airports. Yes, P3D V5 supports sloped runways now, but they basically work only in the AFCAD ( all the rest of 3d modeling is not integrated with it, like MSFS ) and are made in a very convoluted way: each node of the AFCAD must have its height. MSFS is so much easier and elegant: the airport is made flat, and the simulator engine automatically adapts everything to the rolling terrain, which can be easily terraformed. A sloping airport is so difficult to do and comes with so many restrictions, that most large airports in FSX/P3D were made entirely flat for that reason.

We surely hope it will possible to customize such things with a future update of the SDK. However, at least for 3d lights, the quality of the default object is fairly high, I'd say higher than anything we did for FSX/P3D.

If you use the MSFS SDK *properly*, it's quite complex, because there are many design decision that should be made at the start of a project that, if you know the scenery will be made natively for MSFS, you can do some things entirely differently, and spare lots of work. It's much easier to convert from P3D to MSFS than the other way around.

Not really. We are only been very busy in first learning MSFS, then bringing several products out for it, to have a new line of products that can sustain our business in the future.

You mean you installed the FSDT Addon Manager INSIDE the P3D own folder ? That's not very smart and, in fact, it's a reason why our MSFS installer doesn't allow users to do the same mistake of installing "inside" the sim. I already explained how you can undo that. Uninstall everything from FSDT, reply YES to the question "Do you want to remove the Addon Manager ?", and when you reinstall, it will let you choose any combination of drive/folders, which will hold all FSDT products together. Activation won't be affected, so it's really an easy procedure, if you want to clean up your installation.

Either you haven't see the default CYVR, or you haven't seen this.

Nothing is "mixed" here. P3D won't even know there's an MSFS folder inside the Addon Manager folder, and MSFS will never know there are P3D folders there as well. Instead, you get the convenience of having to start just ONE Updater to get the latest updates so, it's ESPECIALLY useful *because* you also use P3D too.

You still don't understand what is happening here. The installer obviously DOES recognize the MSFS location: how else you think the scenery would show up otherwise ? It's just that, instead of polluting your MSFS install with hundreds of files, it will just place a symbolic link there. Again, that's what OrbX does too, and it's a smart choice. It's the same as when P3D4 came out: users entrenched in hold habits attacked us for installing OUTSIDE the sim, as LM suggests. Because, of course, we are always the first doing something right. Today, users finally understood how much better is to install outside the sim, and almost every developer NOW follow that approach. So what ? Don't you know that if you are "spreading" ( you said it as if it was a bad word ) add-ons on different physical drives, they will load FASTER, because the PCI bandwidth is way higher than any SSD throughput so, the more drives you have running in parallel, the faster the sim and the scenery will. load ?

I thought you said: "How nice that it installs OUTSIDE the MSFS folder, so I don't mess it up with stuff, which will be helpful in case I need to reinstall the sim, and how nice the scenery gets easily updated with the FSDT Live Update, together with all your other FSDT products in one go" You don't, and you shouldn't. Is there's something in the text of the screenshot you posted that is not very clear ? If you uninstall all your FSDT products AND reply YES to the question "do you want to remove the Addon Manager ?", on the NEXT install it will ASK a new destination for the Addon Manager, which should NOT be the MSFS package folder and, in fact, the installer will prevent you from doing that. You can install *everywhere* ( every folder or every drive ) EXCEPT the MSFS folder. You'll thank me for that later. Not that we are doing anything "strange". OrbX does that too: install in their own folder, with a symbolic link to the Community folder. That's the best solution, trust me.

As of today, when you buy a scenery from the MS Marketplace, it's .BGL files are encrypted using the Marketplace DRM. This means, if you have some 3rd party utility that needs to read the airport file for any reason, for example a Flight Planner that reads the parking or the navaids from the airport, will be unable to do so, since the airport file ( what used to be called "AFCAD" in FSX ) cannot be read. This is of course the current situation. Nobody knows if the MS DRM will improve at some point, either allowing developers to tell Microsoft not to encrypt some files, or allowing access to the airport data even if it's encrypted, for example using an updated Simconnect.

I think my previous link to the post on our forum indicates all Pros and Cons quite extensively. And yes, for a new user, the price will be the same.

Explained here: http://www.fsdreamteam.com/forum/index.php/topic,24167.msg160563.html#msg160563 Always run the installer and always run the uninstaller, if there is one. First, it's not possible to install our products for MSFS without running the installer, because the installer will check your license first. And, it will create a symbolic link to the scenery in the Community folder, so it will stay in its own folder, together with all the other FSDT products, which makes it easier to keep it updated automatically with the FSDT Live Update. Yes, the installation is identical to Key West or KORD V2, and it's the same regardless if the scenery is bought from FSDT or from Simmarket. The MS Marketplace will install differently, and it will be like any other add-on in the MS Marketplace.

If you installed the whole simulator ( App and Content ) using the default location, then yes, that option to move the app in the Windows setting will work just fine. Instead, if you opted ( at install time ) to install the Content ( which it takes most of the space ) in a separate folder, it's probably easier to create a new folder on the other drive, let's say you call it E:\MSFS, and use Windows Explorer to MOVE ( cut and paste ) the "Community" and "Official" folder under there so, you'll end up like this: E:\MSFS\Community E:\MSFS\Official Then, go in the folder up above the Community folder and open the "CONTENT.OPT" file with Notepad or another text editor and find the last line, which contains a command like this: InstalledPackagesPath ( then a space, then the path of the current Content ) And change it to the new drive location so, following the previous example, it should be like this: InstalledPackagesPath "E:\MSFS" Note the double quotes around the path and the space after the InstalledPackagesPath. Save the file, and you should be good to go. The CONTENT.OPT is located here, if you have the MS Store version: %LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache Or here, if you have the Steam version. %APPDATA\Microsoft Flight Simulator

We have such a long list of airports coming up for MSFS that, by the time we'll finish them, you'll DEMAND something to land your brand new PMDG for MSFS on to, and you'll complain if we weren't ready for it. That's what I meant, when I tried to explain when I said we must make decisions for the future.

This is a thread about JFK, and I obviously reply to that. Not sure what really is your point about your off-topic comment about KPIT. You wanted to change this subject into another clone of the already very long "Why scenery developers focus on MSFS instead of P3D?" topic ?

I was sure somebody would have brought up DD but no, they are not a factor, not in the slightest. They also have a product which includes New York with 3 airports which more recent and competes with our JFK that came out in 2013 as a half-remake of the original version from 2009, and it never had ANY effect ( not even in the slightest ), to our sales of KJFK. Is as if that scenery never existed. So no, there's no difference between JFK and KORD, they both have a competitor with "more value" ( although somebody here said that our KJFK from 2013 looks better than DD from 2018... ), the ONLY difference is that JFK is available for FSX and P3D, while KORD V2 is P3D4 only. Which makes it the BEST product for P3D users. And I think you misunderstood me: it's not as if we are not happy of KORD V2 sales, because they HAVE been fairly good. However, it still remains the fact that not enough users of the old O'Hare decided to "pay for the upgrade", even if it was discounted, and even if the scenery was completely remade for the ground up. So I'm sorry, but the sad hard fact is, without the Flight Simulator user base, we cannot really sustain a business of making large airports, maybe other developers from countries with a lower cost of living can, but not us. Maybe if MSFS never came out, we would probably started to support X-Plane, but that's not what happened. But it blew out of the water any competition when VFR/GA is concerned. Why you think we just released Key West ? And we'll have another small airport in a beautiful area coming out shortly. You, as an user, have the luxury to live in the present, and it's easy to make the "right" choices in this case. We can't do that: if we need to start a new large airport that will take a lot of time, we must guess what the market situation will be in 18-24 months. And in the next 18-24 months, I'm fairly sure there will be several high quality payware airliners for MSFS.