No joy with P3DV4 latest hotfix running W10. Will not connect using simconnect. FSUIPC% works just fine though

Vic

Attached fyi are two plans  - the PLG plan was exported from PLG as a pln file. It was then loaded into P3Dv4 and was evidently autosaved by P3D. The p3dpln file is that same file. You can easily see the differences in the XML file. The p3dv4 file will not load into FSX.

Vic

Sorry for the delay Tim - tracked it down. It seems that when you load a PlanG exported plan into P3D4, it gets rewritten. The XML Version is changed to 4 and the format of the waypoint coordinates is changed. The .pln file can no longer be loaded into FSX after this. Not a PlanG problem.

I'll try to upload a before and after pln FYI.

Vic

Same here Emile but for now, FSUIPC connection works. I assume Tim will update when he can.

Vic

This is a freeware tool that will create a dummy scenery.cfg that can be read by other programs. I believe Pete is using this method. Of course, it requires that the user have this installed along with PlanG.

http://lorby-si.weebly.com/uploads/6/0/8/2/60827113/addonorganizer_install_p3d_v4_0_97.zip

Vic

Using the latest test version I created a plan, exported it to .pln format and sent to to a few friends. They were unable to read the plan in FSX. After going back and forth and re-exporting the plans I noticed something.

In the xml code of the .pln file - the ones that failed showed <appver>4 and the one's that worked showed <appver>10.

I've never had this happen before. Does PLG generate it's own xml code for the export? Can you think of anything on my system that would affect the generated code?

Thanx,

Vic

FWIW, plan-G will not connect to P3DV4 using simconnect. FSUIPC not available yet to test.

Vic

ok - got it sorted. whew!  I think the time factor was the issue. Put my old key and new id in and it worked. Yesterday it did not.

Glad that's out of the way.

I appreciate the help!

Vic

Well, I must be getting dumber in my old age cuz I cannot get the new key to work. First question, the 3.1.4 mapbox key has two entries. The mapobo id from the link is only one. Tried a mix and match of old and new key - just a mess.

I thought the "old" mapbox was easy to set up - this new one is not user friendly imho  Was able to get a useless map to show.

Is there a way to use the "old" map project I designed and link it to the new key ( assuming I can figure out part 1 and 2.

Frustration level increasing exponentially........

Thanx,

Vic

Dempsey - I know my id - it doesn't work in this version - it works just fine in the old version. It's the version not the id.

Vic

Hi Tim -   3.1.4 auto installed over prior version with no problem. However, I can not get my MAPBOX id to work. I still use the original type of id xxxxxx.xxxxxx and 3.1.4 will not display any tiles. I tried filling in both boxes, splitting it between, etc - no joy. Went back to earlier version - works just fine.

Vic

OK - what am I missing - I can NOT get this version to accept my MAPBOX id. I am not using V4, cannot find any reference to v4 on Mapbox site. Tried my usual ID - no joy - tried mapbox.streets.access key - accepts but get blue screens.

It's probably something simple but so far, I cannot use this version.

Thanx!

Vic

Not using mapbox 4 just the old id. Getting blue 404 errors on map.

Thanx,

Vic

ok - that makes sense Roman.

Not a problem then, just hadn't seen it before.

Vic

Here's what I see and the log. Don't see any reference to intersections but perhaps I'm missing something.

Thanx,

Vic

edit: fyi - if I hover on the dark triangle it gives the name and (K3) if I hover on the red it shows same name and (K2).

if that helps.