Orphee 3 Posted April 13, 2016 Share Posted April 13, 2016 Hi, i have a little problem when i will export pln file in p3d v3 files folder, in pfpx i get a warning alarm : Please login to display this image. http://img11.hostingpics.net/pics/796353pfpx.jpg[/IMG] Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 14, 2016 Deputy Sheriffs Share Posted April 14, 2016 Hi there, that image shows your folder configuration, but no error message. But I guess you are writing here because of the missing sub folder in the P3Dv3 export path, right? That's easy to fix: select that line, click the "Browse" button in the top row of the window and then select the proper folder. Link to comment Share on other sites More sharing options...
Orphee 3 Posted April 14, 2016 Author Share Posted April 14, 2016 Ho yes sorry false picture! So simply :-) But don't work, i have now :" <Documents> Prepar3D v3 files" without "/" between "<documents>" and "Prepar3D files" and on top i Set for document folder "\\P3D\Users\Orphee\My documents\" (with "/" and end) Link to comment Share on other sites More sharing options...
Orphee 3 Posted April 14, 2016 Author Share Posted April 14, 2016 I correct it, but the warning message is here (pfpx is in admin mode) Please login to display this image. http://img11.hostingpics.net/thumbs/mini_545239pfpx.jpg[/IMG] Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 15, 2016 Deputy Sheriffs Share Posted April 15, 2016 As I am not using any UNC pathes, what if you map that network path as a local drive and use that in the configuration of the "documents" folder. Have you made sure, that you have enough access privileges from your PFPX machine to the "Prepar3D v3 files" folder on your P3D machine? Link to comment Share on other sites More sharing options...
Orphee 3 Posted April 15, 2016 Author Share Posted April 15, 2016 I test to a local folder and the problem is the same, same warning message I can access to the network folder with explorer, without any problem Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 15, 2016 Deputy Sheriffs Share Posted April 15, 2016 22 minutes ago, Orphee said: I can access to the network folder with explorer, without any problem Have you tried to copy a file into it? Link to comment Share on other sites More sharing options...
Orphee 3 Posted April 15, 2016 Author Share Posted April 15, 2016 Yes i can! I just re test it Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 15, 2016 Deputy Sheriffs Share Posted April 15, 2016 I can reproduce the warning, but only if the configured folder does not exist. So there must be something wrong with your v3 folder. What if you configure the "Prepar3D v2" export item in the list to the v3 folder? Gives that a warning, too? Link to comment Share on other sites More sharing options...
Orphee 3 Posted April 15, 2016 Author Share Posted April 15, 2016 No, it work so! Thanks for your help Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 15, 2016 Deputy Sheriffs Share Posted April 15, 2016 I have no explanation for this behaviour. Are you using P3D v2 and P3D v3 simultaneously? If not you can just keep the export configuration like this, otherwise only the developer would be able to help. Link to comment Share on other sites More sharing options...
Orphee 3 Posted April 15, 2016 Author Share Posted April 15, 2016 yes i keep this export configuration, thanks Tom! Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 15, 2016 Deputy Sheriffs Share Posted April 15, 2016 You're welcome Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.