Update to P3D 5.3 causes Makerwys to crash.

[IanHarr]

Makerwys has worked fine for years. After upgrading yesterday to P3Dv5.3 it is throwing an error.Runways.txtRunways.txt

Error log

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Error" />

  <EventID Qualifiers="0">1000</EventID>

  <Version>0</Version>

  <Level>2</Level>

  <Task>100</Task>

  <Opcode>0</Opcode>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2021-12-03T13:41:03.3072511Z" />

  <EventRecordID>68439</EventRecordID>

  <Correlation />

  <Execution ProcessID="0" ThreadID="0" />

  <Channel>Application</Channel>

  <Computer>IAN-PC</Computer>

  <Security />

  </System>

- <EventData>

  <Data>MakeRwys.exe</Data>

  <Data>5.1.2.8</Data>

  <Data>61446bc1</Data>

  <Data>MakeRwys.exe</Data>

  <Data>5.1.2.8</Data>

  <Data>61446bc1</Data>

  <Data>c0000005</Data>

  <Data>0000000000005156</Data>

  <Data>11c8</Data>

  <Data>01d7e84b69d0ba63</Data>

  <Data>D:\Prepar3d v5\MakeRwys.exe</Data>

  <Data>D:\Prepar3d v5\MakeRwys.exe</Data>

  <Data>9d6c6e47-5421-40ec-bd4a-72c2aea3c31f</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

 

[Pete Dowson]

Did you use "run as administrator" to start MakeRwys? If not, you need to.

Is there a MakeRwys_Scenery.cfg file produced in the P3D root folder? If so please ZIP it and attach to a reply.

Do you see any window appear before this crash? Are any files at all produced -- e.g. especially the Runways.txt file which is started right after MakeRwys is started. Or does it appear to start okay, then crash.

I've installed 5.3 on my main system today, and I've run MakeRwys okay. I have many add-on airports. The only thing I can think of which can cause the crash is a corrupted BGL scenery file, but then it would have at least started scanning.

Note that there have been no changes to BGL airport data formats for 5.3. So, when did you last run MakeRwys, and with which version of P3D? Have you added airport scenery since then?

I can't even begin to look at this without more information. Do you have Addon Organiser? If not please install it (it is freeware). Does that list all of your addon scenery okay?  Please run it and right-click on the main display and select "export list". Then append this (ZIPped) to a reply here, along with any other information or files you can based on my questions above.

Pete

 

 

 

[IanHarr]

1) Yes. Set in properties to run as Admin.

2) Yes. It forms a block headed makerwys v 5.218 Then it stops and a block headed "Makes scenery files for assorted utilities" appears which contains the error message.

"Makes scenery data files for assorted utilities has stopped working.. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" With a Close program box.

3) There is a runways.txt and a runways.xml  Can't attach the xml as it is too big.

4)Last run for P3D5.2 probably about 2 weeks ago. I ran it after adding a new Airport. EHAM v2.

I will do another reply with files.

[IanHarr]

Files as requested.

I have tried to run it through RC4 as well. Same result.

If you need more info please ask and I will do my best.

Runways.txt runways.zip SceneryExport.zip

[Pete Dowson]

15 hours ago, IanHarr said:

3) There is a runways.txt and a runways.xml

I assume the runways.xml file is from a previous session, as it is one of the 15 or so files produced when MakeRwys has finished scanning. Are the rest deleted?

I also asked:
"Is there a MakeRwys_Scenery.cfg file produced in the P3D root folder? If so please ZIP it and attach to a reply."

so does the fact that you've not provided it mean there isn't one? If that's the case the LorbySceneryExport.exe program is either missing, or has a problem.  Please see if there is a LorbySceneryExport.exe.log file. If so please provide that too.

The fact that it has done virtually nothing by the time it crashes is odd, pointing to some problem running the Lorby program, which is needed.to ferret out the Addon.xml installed scenery and the correct priority layering. Or maybe the CFG file starts with some invalid entry -- I've seen such before, generally caused by an incorrect P3D scenery.cfg file.

BTW I'm sure it isn't anything to do with the change from 5.2 to 5.3 as that should change nothing affecting the program. A similar (but different) problem is also reported just yesterday by a 5.2 user. So it is related to some other change in the system. I will need to determine what that is, because I cannot reproduce any problem on either of my P3D5.3 installations.

Pete

 

 

[IanHarr]

MR.Scenery.cfg is only a couple of lines. attached. Must have overlooked it previously, sorry.

Lorby attached.

Runway.xml is old. There are no others.

Hope this all helps.

MakeRwys_Scenery.cfg LorbySceneryExport.exe.log

[Pete Dowson]

2 hours ago, IanHarr said:

MR.Scenery.cfg is only a couple of lines. attached.

That's made by the LorbySceneryExport program, so that has evidently gone wrong.

I think your main P3D scenery.cfg file must be corrupted. Checking the exported list from AddonOrganiser there are two redundant entries:

The Default Terrain is normally the first entry in scenery.cfg. Some scenery installer has added two incorrect entries before it, and these are messing the LorbySceneryExport program up, so it ends with only:

[Area.001]
Title=

It looks like that nonsensical entry causes MakeRwys to crash too, so I'll look at adding code to deal with this more tidily. However, your problem needs fixing by correcting the Scenery.cfg file. Perhaps you could use AddOnOrganiser to delete those two entries (which will appear right at the end, as AO orders them with the latest/last at the top.

If you can't fix it, ZIP up your scenery.cfg (the one in the ProgramData path) and attach that and I'll try to fix that here for you.

Pete

 

[IanHarr]

Thanks for the help so far.

I found those two entries easily and removed them with LorbyAoO.

Sadly it makes no difference. I then took the drastic step of renaming the scenery.cfg and let P3D rebuild it. Lorby now shows no errors that I can see but still there is no joy.

Makerwys crashes on start up still. What I do notice is that normally there is that momentary flash when it calls Lorby, that is missing.

The MRscenery.cfg file is still stopping at one line as before. I have attached the current scenery.cfg (Program Data).

What else would you like me to send you (apart from a bottle of Scotch).

scenery.zip

[Pete Dowson]

18 minutes ago, IanHarr said:

I found those two entries easily and removed them with LorbyAoO.

Sadly it makes no difference. I then took the drastic step of renaming the scenery.cfg and let P3D rebuild it. Lorby now shows no errors that I can see but still there is no joy.

Makerwys crashes on start up still. What I do notice is that normally there is that momentary flash when it calls Lorby, that is missing.

I've never noticed such a "flash". It's normally just running invisibly.

21 minutes ago, IanHarr said:

The MRscenery.cfg file is still stopping at one line as before

So there's a NEW MakeRwys_Scenery.CFG but it just contains:

[General]
Title=Prepar3D Scenery
Description=Prepar3D Scenery Areas Data
Clean_on_Exit=TRUE

[Area.001]
Title=

If so, something is preventing the Lorby program running correctly! Ouch.

Just to verify this, can you temporarily rename the LorbySceneryExport.EXE program so that it doesn't run. MakeRwys should then just use the sim's scenery.cfg. The results will be missing all of the Addon.xml sceneries, but should otherwise be complete.

If that is okay I suspect one or more of the AddOn files is corrupted in such a way as to make the Lorby program fail. Strange, though, considering the AddOnOrganizer works okay. I thought the Exporter made for MakeRwys was based on that.

If it is the Lorby program I'll have to hand this over to Oliver to see if he can isolate which Addon is the problem. If you know which sceneries you've added or updated since the last time MakeRwys worked for you, that would be very useful as I could check those entries specifically.

Pete

 

[IanHarr]

Renamed it. Still the same, MR crashes straight away.

[Pete Dowson]

6 minutes ago, IanHarr said:

Renamed it. Still the same, MR crashes straight away.

Nothing in the Runways.txt file?

This is completely perplexing.  First, from that MakeRwys_scenery.CFG file it is evident that the Lorby program isn't working, but without that MakeRwys just defaults to the normal old-style scenery scan.

I've no idea how to proceed at present. It would be nice to know what's changed on your system since it last worked okay, apart from updating P3D to 5.3 that is.

I'll think about how to move forward on this, but I can't promise anything over the weekend.

Pete

 

[Pete Dowson]

There is one more test you could do, please:

Run LorbySceneryExport.exe "as administrator". It should generate a file "LorbyScenery.cfg" (which, when it is started by MakeRwys, becomes MakeRwys_Scenery.cfg).

Please show me (or attach as a ZIP) the generated .cfg file. It should be the same as that bad one you've already showed me. If so then at least it proves that whatever is affecting MakeRwys also affects that Lorby program, so I can enlist Oliver's help.

Pete

 

[IanHarr]

Make Runways File: Version 5.127 by Pete Dowson

That's it. Runways.txt.

Pete, I really appreciate your trying to help.

All I did was update 5.2 to 5.3.

Somehow the paths to various things have got messed up during this. I did not change anything else. 

Makerwys, FS2Crew and Ailightsreborn were all affected. 

Ailights has been fixed it was a wrong path error that suddenly decided to become critical, having worked perfectly in 5.2.

I updated ActiveSky and had to re-install PMDG planes, all of which worked.

I really don't know what else, unless I was sleepwalking.

As you suspect here is that cfg.

[General]
Title=Prepar3D Scenery
Description=Prepar3D Scenery Areas Data
Clean_on_Exit=TRUE

[Area.001]
Title=
 

 

[Pete Dowson]

2 hours ago, IanHarr said:

All I did was update 5.2 to 5.3.

Somehow the paths to various things have got messed up during this. I did not change anything else. 

Makerwys, FS2Crew and Ailightsreborn were all affected. 

Ouch! I wonder what could have gone wrong. All my updates to P3D have been flawless (and as a Beta tester I do it frequently!).

2 hours ago, IanHarr said:

As you suspect here is that cfg.

[General]
Title=Prepar3D Scenery
Description=Prepar3D Scenery Areas Data
Clean_on_Exit=TRUE

[Area.001]
Title=

Okay. I'll ask Oliver, the author of the LorbySceneryExport program, if he can offer any help identifying the reasons., because I'm stuck!

I won't do this till Monday though. I like my weekends and suspect others do too.

Pete

 

[IanHarr]

8 minutes ago, Pete Dowson said:

Ouch! I wonder what could have gone wrong. All my updates to P3D have been flawless (and as a Beta tester I do it frequently!).

Okay. I'll ask Oliver, the author of the LorbySceneryExport program, if he can offer any help identifying the reasons., because I'm stuck!

I won't do this till Monday though. I like my weekends and suspect others do too.

Pete

 

👍

[Pete Dowson]

I've tested MakeRwys with the bad MakeRwys_Scenery.cfg file being generated on your system, and all that happens is that it finishes saying no files were produced - zero airports etc. This is what should happen.

So now I know that it isn't the bad file which is causing a crash. I still need to ask Oliver why the LorbySceneryExport program is failing to find any scenery -- I'll do that tomorrow -- but meanwhile I've added a few more log lines to Runways.txt to try to identify how far MakeRwys is getting before the crash. I have no other way of determining what is happening. I suspect the version of FS is being detected incorrectly, which could mean some standard FS-related paths are incorrect.

Once the section of code is identified I will probably need to narrow it down further with more logging. But this one should do as a starter. So please replace your MakeRwys.exe with the one attached and let me see the resulting Runways.txt file.

Pete

MakeRwys.exe

[IanHarr]

Hi Pete, Working on a Sunday? 

Attached is the file.

I may have inadvertently got a clue from my FS2Crew problem.

They told me where there program should go and when investigating, I found what could be the error.

The thing complicating the matter is that P3D works perfectly as the file structure stands.

However, I seem to have files in a directory called Lockheed Martin and also in one called Prepar3d v5.

Maybe the programs are looking in Lockheed Martin\Prepar3d v5 when it should be Prepar3d v5 or vice versa.

Just did a test with MR and Lorby in the other directory. (from where they throw the errors).

IT WORKS.😂

Where that Lockheed Martin came from only P3D knows.

Question now is should I try to fix it, if so how? Or leave well alone?

Cheers

Ian

Going to leave it now as I am off to a Carol service this evening. (Also working on Sunday!)

Runways.txt

[Pete Dowson]

12 minutes ago, IanHarr said:

However, I seem to have files in a directory called Lockheed Martin and also in one called Prepar3d v5.

Maybe the programs are looking in Lockheed Martin\Prepar3d v5 when it should be Prepar3d v5 or vice versa.

Just did a test with MR and Lorby in the other directory. (from where they throw the errors).

IT WORKS.😂

Where that Lockheed Martin came from only P3D knows.

That is VERY different. My additional log lines didn't apply , but lots of attempts to scan MSFS scenery have appeared! Nothing I changed could do that! It is actually deciding that there is no FSX or P3D installed in its folder, so it must be an MSFS installation!

So something has changed on your system before I supplied this little update!

11 minutes ago, IanHarr said:

The thing complicating the matter is that P3D works perfectly as the file structure stands.

But are you starting it from the short-cut it installs? If so, look at the properties of the shortcut. Maybe it is being loaded from someplace other than where you installed MakeRwys.

13 minutes ago, IanHarr said:

However, I seem to have files in a directory called Lockheed Martin and also in one called Prepar3d v5.

Maybe the programs are looking in Lockheed Martin\Prepar3d v5 when it should be Prepar3d v5 or vice versa.

Just did a test with MR and Lorby in the other directory. (from where they throw the errors).

IT WORKS.😂

So, how many "Prepar3D.EXE" files do you have installed? Evidently you've been trying to run MakeRwys from the wrong folder. This would explain why MakeRwys and the Lorby program cannot work, though it doesn't explain the crash of MakeRwys. And you last test, with my revised EXE looks lie it closed without crashing ... so something else is different from yesterday.

I think I need to leave you to sort out what seems to be a complete installation mess. Maybe a full uninstall and re-install is warranted.

17 minutes ago, IanHarr said:

Question now is should I try to fix it, if so how? Or leave well alone?

Up to you, but if the registry points to folders which are wrong it could mess with any future installs you try.

Pete

 

[IanHarr]

3 minutes ago, Pete Dowson said:

That is VERY different. My additional log lines didn't apply , but lots of attempts to scan MSFS scenery have appeared! Nothing I changed could do that! It is actually deciding that there is no FSX or P3D installed in its folder, so it must be an MSFS installation!

So something has changed on your system before I supplied this little update!

But are you starting it from the short-cut it installs? If so, look at the properties of the shortcut. Maybe it is being loaded from someplace other than where you installed MakeRwys.

So, how many "Prepar3D.EXE" files do you have installed? Evidently you've been trying to run MakeRwys from the wrong folder. This would explain why MakeRwys and the Lorby program cannot work, though it doesn't explain the crash of MakeRwys. And you last test, with my revised EXE looks lie it closed without crashing ... so something else is different from yesterday.

I think I need to leave you to sort out what seems to be a complete installation mess. Maybe a full uninstall and re-install is warranted.

Up to you, but if the registry points to folders which are wrong it could mess with any future installs you try.

Pete

 

Pete, 

Thanks for everything. As it seems to be a Installation/Registry problem, I think I will take your wise advice and do a full un-re- install. 

As you rightly say, it will probably save a myriad of problems later on.

BTW Only one Prepar3d.exe file and it is in the Lockheed Martin version of the directories.

I was completely unaware of this discrepancy and was happily pointing everything to the Prepar3dv5 directory.

Amazing how dumb supposedly intelligent people can be sometimes.

Thanks again.

Ian