Problem running Makerwys.exe from a mapped P3D network disk

[whityini]

Hey Pete,

I have mapped my P3Dv3 disk to be able to see it into my network and the shared disk has read/write rights.

Now if I run makerwys.exe v.4.8.0.1 from the server (using also Lorby-SI AddonOrganizer program) everything works fine and all the files are correctly created, but if try to run from the client pc I get this error message:

 

Failed to make all the data Files!

Failed to make FStarRC RWS File!

Total airport = 0, runways = 0

 

Any idea about the possible solution?

Thanks for help,

Andrea

[Pete Dowson]

1 hour ago, whityini said:

Now if I run makerwys.exe v.4.8.0.1 from the server (using also Lorby-SI AddonOrganizer program) everything works fine and all the files are correctly created, but if try to run from the client pc I get this error message

You CANNOT run it from anywhere but the base folder of the simulator program you wish to generate files for. That has always been the case and it will remain the case. Please do read the document supplied with it!

Pete

 

 

[whityini]

There is no place into the document where it is written that the file cannot be run from a mapped disk. 

It is written that Makerwys must be placed into the main folder of FSX/PD3 and from there must be run.

If I try to do the same thing mapping the FSX disk instead of P3D disk, I can run Makerwys.exe from remote without any problem. This look strange to me.

Andrea

[Pete Dowson]

48 minutes ago, whityini said:

It is written that Makerwys must be placed into the main folder of FSX/PD3 and from there must be run.

Yes, inthere, not in another PC. 

The reason it is not possible should be obvious. You'd have to share your ProgramData folder on the Server (which is not allowed by Windows), and all the folders containing scenery, because when you run a program from nother PC it is running in that PC, NOT in the PC where you are getting it. All you were doing is getting Windows to fetch a copy of the EXE to the other PC so it could run it there.

Pete

 

[whityini]

Sorry Pete I don't want to be boring but it is exactly as you say. 

I have also the ProgramData shared, which inside has the folders containing scenery.cfg file for both FSX and P3D, so there should not be any access problem. The confirmation of this is that for FSX the process runs smoothly.

It seems to me that for some reasons what is working correctly with FSX doesn't run for P3D. 

Have a nice day. Andrea 

[Pete Dowson]

1 hour ago, whityini said:

It seems to me that for some reasons what is working correctly with FSX doesn't run for P3D. 

It makes little sense to me that it can wor in FSX, let alone P3D. But the differences between what it does for FSX and P3D version 3 are non-existent. It just detects which Sim it is by the version of FSX.EXE or Prepar3D.exe in the directory it is running in, using this information to determine the ProgramData folder name to use, 

Maybe it is AddOnOrganizer which cannot cope. For P3Dv3 you shouldn't be using it in any case. To use AddOnOrganizer for P3Dv3 a new version is required AND an update to MakeRunways.

Additonally, I've now found that L-M have changed the scenery formats for P3Dv4 and new P3D4 dedicated sceneries arriving cannot be decoded using the information I have. It will be a very big job, because there is no documentation of the new internal formats. Decoding by hand takes many hour of intense detective work and there's simply no way I can do this in any reasonable timescale. That is a more pressing need too FSDT, for example, press ahead using the new tools.

Pete

 

[whityini]

Thanks Pete. I'll do some more tries.