Jump to content
The simFlight Network Forums

Makerunways does not work with msfs


Terry Phelps
 Share

Recommended Posts

Have been using makerunways for years with P3D and recently with MSFS. Had a system crash so reloaded msfs and makerunways. When I click the make runways exec. it only creats a file called runways but it is empty. I had it working before reload. My msfs is and was on my d drive under the default WpSystem folder. Any assistance would be appreciated. i use the program with msfs and Pilot2 atc. As stated worked fine for a while.

Link to comment
Share on other sites

First, can you check that you are using the latest version, 5.126, and if not, download that and try again.
If you still have issues, please let us know what happened (did you see a pop-up) and attach your runways.txt file (if not empty, and let us know if you are using an MS Store or Steam version of MSFS. Thanks.

Link to comment
Share on other sites

17 minutes ago, Terry Phelps said:

I am using version 5.126, I did see a popup, it added a  runways text file that is empty. I am using the store version. I did a full reload last night thought it may be because of all the patches. Same results.

What did the popup say?

I have MSFS updated to WU4, and MakeRunways 5.126 works fine here. My MSFS is from the MS Store like yours. Is there another update yet, to fix WU4's WASM problem?

The start of my Runways.txt file reads like this:

Looking for:
   "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\content.xml"
    ---- okay, Content list loaded
Now looking for:
    "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt"
Checking:
    "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\"
Found MSFS official scenery in:
    "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\"
Loading language pack from:
    "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base\en-US.locPak"
Loading materials list from:
    "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base-material-lib\MaterialLibs\Base_MaterialLib\Library.xml"
Found MSFS community scenery in: 
  "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\"
Reading MSFS scenery:

On another PC I have the files in E:\Wpsystems, but otherwise the paths correspond. Where are those files are on your system?

12 hours ago, Terry Phelps said:

As stated worked fine for a while.

Well, obviously MakeRunways hasn't changed. Does FSUIPC7 install and connect okay? 

Pete


 

 

Link to comment
Share on other sites

I will reinstall fsuipc, but it does work all my peripherals load. When I run the MakeRwys application I end up with a blank text file it does not say anything like you posted. A popup with the title MakeRwys pops up for a sec and then disappears.

Link to comment
Share on other sites

1 minute ago, Terry Phelps said:

I will reinstall fsuipc, but it does work all my peripherals load.

I just wanted it to check that it can actually install, because it too needs to find the correct folders.

I'll have a look to see if there's any logging I can add to find out why is fails. But first, please can you look into the Windows Event Viewer -- Windows Logs - Applications, to see if there are any entries referring to MakeRwys.exe. If there are any please post details here.

Also please confirm that you are running MakeRwys "as administrator". Best to change the EXE file properties to make it run as administrator in any case (right click - Properties - Compatibility). And tell me if you use any of the command line options.

I can't get to look at this till tomorrow (Monday) afternoon in any case.

Pete

 

Link to comment
Share on other sites

I did have it set up as admin.

Event log 

Log Name:      Application
Source:        Application Error
Date:          4/18/2021 7:11:55 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-T4G2RSF
Description:
Faulting application name: MakeRwys.exe, version: 5.1.2.6, time stamp: 0x605dcd8f
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process id: 0x3e98
Faulting application start time: 0x01d73443a3d7f8e0
Faulting application path: C:\Users\Terry\Desktop\makerunways\MakeRwys.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 097fd529-97c6-4644-8187-4ecab203bf7b
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<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-04-18T11:11:55.3966988Z" />
    <EventRecordID>33949</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-T4G2RSF</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MakeRwys.exe</Data>
    <Data>5.1.2.6</Data>
    <Data>605dcd8f</Data>
    <Data>ucrtbase.dll</Data>
    <Data>10.0.19041.789</Data>
    <Data>2bd748bf</Data>
    <Data>c0000409</Data>
    <Data>0000000000071208</Data>
    <Data>3e98</Data>
    <Data>01d73443a3d7f8e0</Data>
    <Data>C:\Users\Terry\Desktop\makerunways\MakeRwys.exe</Data>
    <Data>C:\WINDOWS\System32\ucrtbase.dll</Data>
    <Data>097fd529-97c6-4644-8187-4ecab203bf7b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

Thanks for all your assistance.

Link to comment
Share on other sites

12 hours ago, Terry Phelps said:

Faulting application name: MakeRwys.exe, version: 5.1.2.6, time stamp: 0x605dcd8f
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x0000000000071208

Okay. that helps a lot, thanks. I'll look at this later today. Looks like a stack overflow. So I'm now thinking that some of the paths it needs to find the files are much longer than any seen before.

Since you reinstalled FSUIPC7, can you please show me its Install Log so i can see what paths it is using?

Pete

 

 

Link to comment
Share on other sites

1 hour ago, Terry Phelps said:

here is the log file, hope it is right one. Added another in case it helps.

One is the Install log and the other is the run-time log. Thanks.

This is making me thing that some of the paths to the files MakeRwys needs is too long:

D:\WpSystem\S-1-5-21-2263347563-3261326988-2989552293-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\Official\OneStore\carenado-aircraft-ct182t-skylane-g1000\SimObjects\Airplanes\Carenado_CT182T_Skylane_G1000\aircraft.CFG

That path itself is 242 characters long. It wouldn't take much to put it over the normal "MAX_PATH" of 260 characters.

I'm not sure exactly how to get over this. I think it needs a Windows registry change to make certain Windows functions, one which MakeRunways has to use, allow longer pathnames when constructing paths for access. however, I've made some small changes as a test. Please run this one and let me know:

MakeRwys.exe

Whether it still crashes or not, please see what files it generates, if any. Best to delete any older files first, or run this copy in a different, new, folder. If there's a "runways.txt" file, please show me that -- or at last the first 20 lines or so.

Pete

 

Link to comment
Share on other sites

1 hour ago, Terry Phelps said:

This is what I got just like before.

Curiouser and curiouser ... !

Can you post the Windows crash data for me again, please. 

It seems to be crashing before it even does anything except open the log, which makes no sense.

Pete

 

Link to comment
Share on other sites

Here it is I hope.

Log Name:      Application
Source:        Windows Error Reporting
Date:          4/23/2021 9:05:42 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-T4G2RSF
Description:
Fault bucket 1522365582079123582, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: MakeRwys (2).exe
P2: 5.1.2.601
P3: 607ec63b
P4: ucrtbase.dll
P5: 10.0.19041.789
P6: 2bd748bf
P7: 0000000000071208
P8: c0000409
P9: 0000000000000005
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94B9.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95B4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95C5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95C3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95D3.tmp.txt
\\?\C:\Users\Terry\AppData\Local\Temp\WER95F5.tmp.appcompat.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MakeRwys (2).exe_e39f445d8146eae219cb5a25bc4414c196c7b17_f4271b22_20256abc-7034-4505-80e8-0807aad607ec

Analysis symbol: 
Rechecking for solution: 0
Report Id: d5b6fb62-1f99-4e53-9878-acb29885c8b6
Report Status: 268435456
Hashed bucket: 8b3f8370ae1acdd84520876e5a1b607e
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-04-23T13:05:42.9138136Z" />
    <EventRecordID>34235</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-T4G2RSF</Computer>
    <Security />
  </System>
  <EventData>
    <Data>1522365582079123582</Data>
    <Data>5</Data>
    <Data>BEX64</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>MakeRwys (2).exe</Data>
    <Data>5.1.2.601</Data>
    <Data>607ec63b</Data>
    <Data>ucrtbase.dll</Data>
    <Data>10.0.19041.789</Data>
    <Data>2bd748bf</Data>
    <Data>0000000000071208</Data>
    <Data>c0000409</Data>
    <Data>0000000000000005</Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94B9.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95B4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95C5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95C3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95D3.tmp.txt
\\?\C:\Users\Terry\AppData\Local\Temp\WER95F5.tmp.appcompat.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MakeRwys (2).exe_e39f445d8146eae219cb5a25bc4414c196c7b17_f4271b22_20256abc-7034-4505-80e8-0807aad607ec</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>d5b6fb62-1f99-4e53-9878-acb29885c8b6</Data>
    <Data>268435456</Data>
    <Data>8b3f8370ae1acdd84520876e5a1b607e</Data>
    <Data>0</Data>
  </EventData>
</Event>

Link to comment
Share on other sites

The error logged is different this time, and in a Windows library DLL, so it doesn't really help I'm afraid.

I really cannot see any reason for it to crash before it really gets to do anything. It is very strange -- and you are the only one reporting this.

Desperate measures are called for. Here's another temporary update.

MakeRwys.exe

The only changes are that it forces some checkpoint lines into the Runways.txt file. Not knowing where or why it crashes I've only put a few of these in at present, to see how far it gets in the initial setup.  Please run it and show me the Runways.txt file (you can paste its contents here -- makes it faster and easier).

This may take several iterations with different checkpoints being added as I narrow it down.

Pete

 

 

Link to comment
Share on other sites

20 minutes ago, Terry Phelps said:

Did something a little more

Ok, thanks. That eliminates quite a lot.

Here's another to try -- if it doesn't find it this time then it's a lot of extra logging for each layer of scenery. But since it isn't making a "scenerylist.txt" file I don't think it will come to that.

MakeRwys.exe

Runways.txt afterwards, please.

Pete

 

Link to comment
Share on other sites

19 minutes ago, Terry Phelps said:

Getting a lot better

Not really. This just shows it is something to do with one of the layers. Getting to that is more difficult.

Was a SceneryList.txt file produced? It should have been. If so I need to see it please.

Anyway, I'm getting more and more convinced it must be related to one (probably add-on) scenery which has extraordinarily long folder names, or just very many subfolder levels. I did have checks on these, but I've added to these in this version:

MakeRwys.exe

Try that one please, and show me (or attach) the scenerylist file, if there is one, and the runways.txt file.

This is about all from me till tomorrow.

Pete

 

Link to comment
Share on other sites

I think it's something in your Community folder. This is my last test today, with more logging in the Runways.txt file:

MakeRwys.exe

There should now be a full path listed for each MSFS and Community scenery layer, till it gets to the one causing the crash.

As well as running this and showing the runways.txt, could you please tell me the folder names of each add-on in your Community folder?

I'm definitely off-line now, at least for a few hours.

Pete

 

Link to comment
Share on other sites

Okay. I think I know what is happening.

My Windows 10 used for MSFS must have been set by some program or other to allow Long File Names, because although, like you, I have the install separate from the default, MakeRunways doesn't get into trouble with long file paths. The separate install has a longer path because of all that weird guff after the D:\WpSystem part. Just 25 characters extra, but enough to make some of the subfolders paths way over the limit accepted by some Windows file functions.

I looked this up using Google, and found two ways to handle it. One seems to be to pre-pend the path name with \\?\. So i've done this in this version for you to test:

MakeRwys.exe

Please try this. I'd still like to see the Runways.txt, but if this test works it will be a very large file, so please show me only the lines up to the "Reading MSFS scenery" line.

The other way is to set Windows to accept long filepaths in any case. But that's a Registry change. So we'll try this way first.

Pete

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.