-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
P3D v4 P3DV4......let us know how it goes
- Thread starter pinkjr
- Start date
- Messages
- 5,214
No problems with ADE (yet?) but how do I get to point ADE to P3Dv4?
With MCX I have the same problem more or less plus the fact that effects have changed and do not correspond to what you see in MCX and what you see in P3Dv4 (e.g. attached effects x,y,z placement problem that already showed up in FSX as well).
And, of course AIFP, where Don is trying his best to make it compatible ASAP but still lacks some stuff4P3D.com
(Have not yet found time to inform him because I am still finding out what works and what not.
The main problem for me at this time is that I cannot trust MCX any longer to make things show up the same as it shows up in P3Dv4.
Another problem is (as said before) is that AIFP (and the flightplans and the AI aircraft) do not show up as they did before. Could be that AIFP is not at fault at all but that it is a not yet advertized quirk of v4.
With MCX I have the same problem more or less plus the fact that effects have changed and do not correspond to what you see in MCX and what you see in P3Dv4 (e.g. attached effects x,y,z placement problem that already showed up in FSX as well).
And, of course AIFP, where Don is trying his best to make it compatible ASAP but still lacks some stuff4P3D.com
(Have not yet found time to inform him because I am still finding out what works and what not.The main problem for me at this time is that I cannot trust MCX any longer to make things show up the same as it shows up in P3Dv4.
Another problem is (as said before) is that AIFP (and the flightplans and the AI aircraft) do not show up as they did before. Could be that AIFP is not at fault at all but that it is a not yet advertized quirk of v4.
Menu bar : Settings -> Options -> Folders
Scenery.cfg -> C:\ProgramData\Lockheed Martin\Prepar3D v4
FS main folder -> F:\Lockheed Martin\Prepar3D v4
BglComp -> F:\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Scenery
ShiptoVec -> F:\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Terrain
Not tried presently to amend an existing airport, nor creating a new one, but these settings do point my ADE to the v4
Blue skies
Scenery.cfg -> C:\ProgramData\Lockheed Martin\Prepar3D v4
FS main folder -> F:\Lockheed Martin\Prepar3D v4
BglComp -> F:\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Scenery
ShiptoVec -> F:\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Terrain
Not tried presently to amend an existing airport, nor creating a new one, but these settings do point my ADE to the v4
Blue skies
- Messages
- 5,214
Thank you but I knew that.
I meant to ask how you get to have P3Dv4 show up in the "choose FS version".
Guess I should have asked Jon.
Edit: oops, this thread is already in the right forum.
And, by the way, FSX compiled airports do work in P3Dv4 for me as well.
I meant to ask how you get to have P3Dv4 show up in the "choose FS version".
Guess I should have asked Jon.
Edit: oops, this thread is already in the right forum.
And, by the way, FSX compiled airports do work in P3Dv4 for me as well.
Last edited:
- Messages
- 34,981
- Country
To get it to show up in the list requires me to update ADE to support that. At the moment if you want to use it then you need to set your own paths. I can't say when an update to include V4 as an option will be available. Right now I am watching folks reports. I would rather open the code once when I know what needs to be done (or not)
- Messages
- 259
- Country
I have had "mixed" results. I have a P3D v3.4 version of the airport KAUS that I have developed with extensive detail. Works great with P3D v3.4, along with ORBX but ADE 1.71, configured to point to the P3D v4 SDK fails to compile, stating: "System Exception: Unknown ID 62 found in airport record"
I have no clue as to what ID 62 is and the log file is no help (to me) in trying to narrow down what might have gone wrong.
I have attached a screen shot of the ADE error message.
I have successfully recompiled and run another airport AD4 (KEDC) of less complexity.
Any pointers / insight would be GREATLY appreciated.
Can also supply the ADE log file if needed.
Thanks in advance.
I have no clue as to what ID 62 is and the log file is no help (to me) in trying to narrow down what might have gone wrong.
I have attached a screen shot of the ADE error message.
I have successfully recompiled and run another airport AD4 (KEDC) of less complexity.
Any pointers / insight would be GREATLY appreciated.
Can also supply the ADE log file if needed.
Thanks in advance.
Attachments
- Messages
- 34,981
- Country
Just to confirm you loaded a P3Dv3 airport into ADE configured for v4 and when you compiled it you got this exception? If so can you attach or send me (jon AT scruffyduck DOT org) the project file that failed?
- Messages
- 5,214
If I compile a FSX saved project and then compile it for FSX, it shows up as it should in P3Dv4 except for the add effects that will not show up in P3Dv4 at all (and that is not too much of a surprise because you have to really rework the effect files but the fact remains that even if you do the effect files the P3Dv4 way, they are not placed by ADE).
From a cursory check, it appears that PV4 will use either the FS8-style GPs or the Pv3_style. My next check will be to see if LM has also reinstated Separation Planes and BGL_LIGHTs.
Don
EDIT: Unfortunately, v4 doesn't go back that far. Separation Planes and BGL Lights don't work in v4.
Don
EDIT: Unfortunately, v4 doesn't go back that far. Separation Planes and BGL Lights don't work in v4.
Last edited:
To the best of my knowledge and the information I have received from other users, AIFP is fully compatible with P3Dv4. Nonetheless, I look forward to your input.
The traffic file format in PD4 appears to be unchanged. However, it appears PD4 is a lot more picky than PD3 as regards the aircraft it displays.
Don
Just be clear, earlier this week I made a development release of AIFP that has proven generally to be P3Dv4-compatible. (The current AIFP general release is not Pv4-compatible.) That development release is available from http://stuff4fs.com.
Once we're satisfied that AIFP IS fully P4D-compatible, I'll make a general release. At the moment, we're still in the test phase, hence a development release.
Don
Once we're satisfied that AIFP IS fully P4D-compatible, I'll make a general release. At the moment, we're still in the test phase, hence a development release.
Don
Have now had a chance to check my 6 FSX-based airports under Pv4 and to explore the SDK. All airports (compiled for Pv3 but don't use any Pv3-unique features) appear to be fully compatible with Pv4.
Some (but only some) of my custom AI either don't show up or are missing bits. I suspect those aircraft are early-version-FS9 vintage and are incompatible. There does not appear to be any changes for AI traffic files and no issues related to Pv4 have been reported for AIFP after a week of experience with the recent Pv4-compatible update.
The only other thing I noticed is that LM has replaced the taxi_asphalt texture with a much darker version. I use various taxiway textures to reflect the different shades of paved surfaces at the real airport, and the new taxi_asphalt detracts from that. (Unfortunately, LM has named the old texture "taxi_asphalt_old, but didn't provide for its use.) I've written a little utility that scans the .xml and replaces each instance of ASPHALT with MACADAM, the current lightest of the paved surface textures. That fixes the problem. Of course, I could simply have overwritten the new texture with the old, but that would then affect every airport. LM has also replaced taxi_concrete, but the difference is only minimal. On the positive side, LM has introduced a couple new airport features dealing with timezones and daylight savings time which will affect PDE..
Jon, the Pv4 installer places an entry in both the 64-bit and 32-bit registries. NET 4.5 seems to handle that quite nicely. Also, be aware the structure of the SDK is totally changed. The stuff we're interested in is in the new World section.
Don
Some (but only some) of my custom AI either don't show up or are missing bits. I suspect those aircraft are early-version-FS9 vintage and are incompatible. There does not appear to be any changes for AI traffic files and no issues related to Pv4 have been reported for AIFP after a week of experience with the recent Pv4-compatible update.
The only other thing I noticed is that LM has replaced the taxi_asphalt texture with a much darker version. I use various taxiway textures to reflect the different shades of paved surfaces at the real airport, and the new taxi_asphalt detracts from that. (Unfortunately, LM has named the old texture "taxi_asphalt_old, but didn't provide for its use.) I've written a little utility that scans the .xml and replaces each instance of ASPHALT with MACADAM, the current lightest of the paved surface textures. That fixes the problem. Of course, I could simply have overwritten the new texture with the old, but that would then affect every airport. LM has also replaced taxi_concrete, but the difference is only minimal. On the positive side, LM has introduced a couple new airport features dealing with timezones and daylight savings time which will affect PDE..
Jon, the Pv4 installer places an entry in both the 64-bit and 32-bit registries. NET 4.5 seems to handle that quite nicely. Also, be aware the structure of the SDK is totally changed. The stuff we're interested in is in the new World section.
Don
- Messages
- 5,214
Morning,
I am using the AIFP 3.2.06(f) latest dev.version.
>I open a Traffic file that I ported over from FSX to P3Dv4;
>in the select compile parameters I select the P3Dv4 sceneryworld/scenery path (I get a warning that target version is different);
>I substitute an aircraft for a model that is P3Dv4 compatible;
> click on compile and compile is successful. Great.
But...when I open the traffic file again, the new aircraft is red, has no parking radius, type or code.
Double clicking on the aircraft tells me it is missing in the selected FS version and the
A long story short, if the aircraft is not in both FSX and P3D then that is what happens.
How would I set AIFP to select the P3Dv4 version?
I am using the AIFP 3.2.06(f) latest dev.version.
>I open a Traffic file that I ported over from FSX to P3Dv4;
>in the select compile parameters I select the P3Dv4 sceneryworld/scenery path (I get a warning that target version is different);
>I substitute an aircraft for a model that is P3Dv4 compatible;
> click on compile and compile is successful. Great.
But...when I open the traffic file again, the new aircraft is red, has no parking radius, type or code.
Double clicking on the aircraft tells me it is missing in the selected FS version and the
A long story short, if the aircraft is not in both FSX and P3D then that is what happens.
How would I set AIFP to select the P3Dv4 version?
- Messages
- 783
- Country
Download the latest version, then add the latest Development Release, I think it is 3.2.06(i).
Regarding ADE171:
Tried the P3D4 compiler two times, only get a fault message, so using the P3D3 compiler still. Recently shoved 3o airports into P3D4, no problems there, only had to tune GP asphalt colours like Don mentioned.
Regarding ADE171:
Tried the P3D4 compiler two times, only get a fault message, so using the P3D3 compiler still. Recently shoved 3o airports into P3D4, no problems there, only had to tune GP asphalt colours like Don mentioned.
Last edited:
- Messages
- 5,214
That one works. Thank you Don (and Andrew).
Edit: only up to a point:
Then I downloaded the flight plans again in FSX and copied them over to P3Dv4 and then they show up in AIFP P3Dv4 version.
I then tried a smaller FP out of FSX that was a weekly one:
- AIFP does not accept the registry no. (C-GERZ);
- P3Dv4 Traffic Toolbox gives me Japanese or Chinese characters for departure and arrival time.
Edit: only up to a point:
Then I downloaded the flight plans again in FSX and copied them over to P3Dv4 and then they show up in AIFP P3Dv4 version.
I then tried a smaller FP out of FSX that was a weekly one:
- AIFP does not accept the registry no. (C-GERZ);
- P3Dv4 Traffic Toolbox gives me Japanese or Chinese characters for departure and arrival time.
Last edited:
That has always been the case. If an aircraft is not in the "stable" of the current Targert Version, it will display in red. However, the traffic file will still compile and will include any "missing" aircraft.
AIFP is not selective as to registration numbers. Without knowing the context, I can't comment further.
Roby, lets move the AIFP discussion (if there's any left) over to the AIFP forum.
Don