Vancouver+ 3.0 and P3D
- Thread starter rewasiuk
- Start date
Hi guys:
Nearly all scenery packages for both FS9 and FSX which were authored in part by Holger Sandmann since his latter freeware days require various specific edits to the FS Terrain.Cfg, and more recently, several other FS "system" files as well; such edits are best made by specially-written install/configuration utilities to avoid irreparable damage to one's FS system files.
IMHO, it would may not work very well to simply add the Vancouver Plus V3 (aka "Van3+") scenery Area layers to the P3D scenery library GUI stack of layers, as you will likely be missing some scenery content, and may have certain areas which are not excluded so that replaced / overlaid custom scenery content can be properly visualized at run time in FSX.
It is possible that you could "trick" the Van3+ installer into thinking it is installing into FSX by making backups of certain Windows registry keys and FS system files, then re-naming certain FS system files prior to copying your FSX.exe executable into the (temporarily re-named) P3D main root folder.
However, this would still put your P3D installation at risk, and there may be additional considerations not mentioned here. which would also be needed to get Van3+ to work properly in P3d, so unless you are willing to make an extra backup of your entire P3D installation, it might be best to not try installing into a re-named Prepar3D folder chain.
At best, you might be able to trick the Van3+ installer into targeting a "dummy" FSX folder chain in addition to making (temporary) edits to certain keys in the Windows registry so you can study what files are put where, but that may fail if the installer launches and runs the "configurator" ...which might need to find and change FSX files other than just Terrain.Cfg.
Furthermore, after installation the Van3+ "configuration" utility would not work on the P3D system files after a manually-implemented setup, so I think it likely that the official advice from the author(s) and publisher might be for end-users to not attempt doing a manual "port" to P3d.
Perhaps upon receiving additional inquires about P3D installation, the author(s) and publisher may subsequently make available to registered users of Vancouver+ v3, an "official" P3D installation / configuration utility ? :ques:
You may wish to inquire at the support forum to see if Holger and/or Jon Patch would be willing to offer a modified installer, or to post a vetted workflow which is more comprehensive (and authoritative) than what I have described above.
FYI: Apparently Bryan Wallis inquired about proting Van3+ over to P3D around 18 Months ago, and the idea was still under consideration by the author(s) and the publisher.
http://fsaddon.eu/wpfsaddon/?page_i...ouver-plus-v3-and-prepar3d-by-lockheed-martin
FSAddon Vancouver Support Forum
http://fsaddon.eu/wpfsaddon/?page_id=1055/vancouver-support-forum
Hope this helps !
GaryGB
Nearly all scenery packages for both FS9 and FSX which were authored in part by Holger Sandmann since his latter freeware days require various specific edits to the FS Terrain.Cfg, and more recently, several other FS "system" files as well; such edits are best made by specially-written install/configuration utilities to avoid irreparable damage to one's FS system files.
IMHO, it would may not work very well to simply add the Vancouver Plus V3 (aka "Van3+") scenery Area layers to the P3D scenery library GUI stack of layers, as you will likely be missing some scenery content, and may have certain areas which are not excluded so that replaced / overlaid custom scenery content can be properly visualized at run time in FSX.
It is possible that you could "trick" the Van3+ installer into thinking it is installing into FSX by making backups of certain Windows registry keys and FS system files, then re-naming certain FS system files prior to copying your FSX.exe executable into the (temporarily re-named) P3D main root folder.
However, this would still put your P3D installation at risk, and there may be additional considerations not mentioned here. which would also be needed to get Van3+ to work properly in P3d, so unless you are willing to make an extra backup of your entire P3D installation, it might be best to not try installing into a re-named Prepar3D folder chain.
At best, you might be able to trick the Van3+ installer into targeting a "dummy" FSX folder chain in addition to making (temporary) edits to certain keys in the Windows registry so you can study what files are put where, but that may fail if the installer launches and runs the "configurator" ...which might need to find and change FSX files other than just Terrain.Cfg.
Furthermore, after installation the Van3+ "configuration" utility would not work on the P3D system files after a manually-implemented setup, so I think it likely that the official advice from the author(s) and publisher might be for end-users to not attempt doing a manual "port" to P3d.
Perhaps upon receiving additional inquires about P3D installation, the author(s) and publisher may subsequently make available to registered users of Vancouver+ v3, an "official" P3D installation / configuration utility ? :ques:
You may wish to inquire at the support forum to see if Holger and/or Jon Patch would be willing to offer a modified installer, or to post a vetted workflow which is more comprehensive (and authoritative) than what I have described above.
FYI: Apparently Bryan Wallis inquired about proting Van3+ over to P3D around 18 Months ago, and the idea was still under consideration by the author(s) and the publisher.
http://fsaddon.eu/wpfsaddon/?page_i...ouver-plus-v3-and-prepar3d-by-lockheed-martin
FSAddon Vancouver Support Forum
http://fsaddon.eu/wpfsaddon/?page_id=1055/vancouver-support-forum
Hope this helps !
GaryGB