Jump to content
The simFlight Network Forums

Makerunways ends too fast


Recommended Posts

Hi,

I've been using Makerunways for a long time now.

I'm on P3D v5.2

Suddently I've noticed Makerunways start running but completed within ~4 seconds and I also get no error but the usual message that everything ran OK.

This doesn't make sense since I'm used to it running for a minute or two with it going over all scenery entries.

I've attached my scenery.cfg

What could be the issue? 

 

Thanks,

 

Shomron

scenery.cfg

Link to comment
Share on other sites

2 minutes ago, Shom said:

I've attached my scenery.cfg

What could be the issue? 

Could you attach your Runways.txt file please, if that exists (you can zip it if its large). Also, if there is a MakeRwys_Scenery.cfg file produced in the P3D root folder, please ZIP it and also attach.

Thanks,

John

Link to comment
Share on other sites

Very strange. The scenery list looks okay, but the log (Runways.txt) doesn't even get as far as looking at the first entry.

14 hours ago, Shom said:

I also get no error but the usual message that everything ran OK.

It says OK with all files produced?

Just in case there was a crash, please check the Windows Event Viewer. If one is reported please show the details.

Pete

 

Link to comment
Share on other sites

3 hours ago, Pete Dowson said:

Very strange. The scenery list looks okay, but the log (Runways.txt) doesn't even get as far as looking at the first entry.

It says OK with all files produced?

Just in case there was a crash, please check the Windows Event Viewer. If one is reported please show the details.

Pete

 

No error, although it shows 0 out of 0 entries scanned. It runs, shows only Aerosoft EDDK and stops. Then it gives the usual messages that a4 was built successfully etc...

When I'm back near the computer I'll check for any errors shown on the event viewer.

Link to comment
Share on other sites

52 minutes ago, Shom said:

No error, although it shows 0 out of 0 entries scanned. It runs, shows only Aerosoft EDDK and stops. Then it gives the usual messages that a4 was built successfully etc...

Sorry, I don't understand. Where is this 'Aerosoft EDDK" shown? And what is "a4"?

The only EDDK entry is this one:

[Area.485]
Title=EDDK Cologne-Bonn Airport Scenery
Local=C:\Users\user\Prepar3D v5 Add-ons\Cologne-Bonn Professional - P3Dv5
Layer=485
Active=TRUE
Required=FALSE


and that is the last entry but one. It must have scanned the previous 484 entries already, but the log (Runways.txt) shows nothing scanned whatsoever.  So I cannot understand where this "Aerosoft EDDK" display comes from.

Pete
 

Link to comment
Share on other sites

On 12/5/2021 at 11:49 AM, Pete Dowson said:

Okay. Thanks for letting me know.

Pete

 

OK so this issue is back again... with same missing info in runways.txt and makerunways cfg files you have observerd before

I am getting an error in the event viewer - 

Faulting application name: MakeRwys.exe, version: 5.1.2.8, time stamp: 0x61446bc1
Faulting module name: MakeRwys.exe, version: 5.1.2.8, time stamp: 0x61446bc1
Exception code: 0xc0000005
Fault offset: 0x000000000000db8f
Faulting process id: 0x11e4
Faulting application start time: 0x01d7eecce690effa
Faulting application path: E:\P3D\Program Files\Lockheed Martin\Prepar3D v5\MakeRwys.exe
Faulting module path: E:\P3D\Program Files\Lockheed Martin\Prepar3D v5\MakeRwys.exe
Report Id: 20df0767-da8b-4ee0-bee1-e8cf70305ae3
Faulting package full name: 
Faulting package-relative application ID: 

 

and this event 2 seconds later - 

Fault bucket 1965314263580765799, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MakeRwys.exe
P2: 5.1.2.8
P3: 61446bc1
P4: MakeRwys.exe
P5: 5.1.2.8
P6: 61446bc1
P7: c0000005
P8: 000000000000db8f
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC090.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC16C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC17D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC17B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC18B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MakeRwys.exe_333ffe4565314edd6fc8b46eb1e45f6be451801e_b2fa44d8_ad1dcecf-9a71-4bf8-93d7-d32947a853e8

Analysis symbol: 
Rechecking for solution: 0
Report Id: 20df0767-da8b-4ee0-bee1-e8cf70305ae3
Report Status: 268435456
Hashed bucket: b95576a01764d69dcb4632e8f8bd6e67
Cab Guid: 0

 

Thanks,

 

Shomron

 

 

Link to comment
Share on other sites

2 hours ago, Shom said:

OK so this issue is back again... with same missing info in runways.txt and makerunways cfg files you have observerd before

Sorry, you need to show the files. You not had this error before. Or at least if it similar why no crash in Event Viewer before?

You also need to try and work out what is different this time from when it was okay 12 days ago! I'm not changing MakeRunways and no one else has this problem so it must surely be something in your system which is changing or messed up. We need to determine what that is.

Please ALWAYS show the files, not just say "same missing info". 

Pete

 

 

Link to comment
Share on other sites

6 hours ago, Pete Dowson said:

Sorry, you need to show the files. You not had this error before. Or at least if it similar why no crash in Event Viewer before?

You also need to try and work out what is different this time from when it was okay 12 days ago! I'm not changing MakeRunways and no one else has this problem so it must surely be something in your system which is changing or messed up. We need to determine what that is.

Please ALWAYS show the files, not just say "same missing info". 

Pete

 

 

Last time I did not check the event viewer since it suddenly worked again

I've upgraded to v5.3 but this same issue occured in v5.2. 

Last time the only thing which resolved it was probably a restart since I did not do anything else. Could it be a certain process or thread interfering?

Attaching the files here again.

 

Thanks for the help,

 

Shomron

scenery.cfg MakeRwys_Scenery.cfg runways.rar Runways.txt

Link to comment
Share on other sites

6 hours ago, Shom said:

Last time the only thing which resolved it was probably a restart since I did not do anything else. Could it be a certain process or thread interfering?

Not likely, as it is an Access Violation error. This means that some access in memory is being attempted to an address which hasn't been allocated, or is read- or execute- only and a write is attempted.

The only cause of that I can think of is a corrupted scenery BGL file which MakeRunways is attempting to make some sense of. The problem is, though, that no files are yet being scanned according to Runways.txt.

I'll need to see if I can add more logging in the sequences before it logs the first scenery file scan.

Pete

 

 

Link to comment
Share on other sites

I've added log lines which log the layer number area about to be processed and a few other things. Let's see if this narrows it down. Please use this version and return the same files (not Runways.xml though, as the one you have is an old one. MR only makes the result files at then end, as they have to be sorted.

Pete

MakeRwys.exe

Link to comment
Share on other sites

5 hours ago, Pete Dowson said:

I've added log lines which log the layer number area about to be processed and a few other things. Let's see if this narrows it down. Please use this version and return the same files (not Runways.xml though, as the one you have is an old one. MR only makes the result files at then end, as they have to be sorted.

Pete

MakeRwys.exe 95 kB · 1 download

Here you go.

 

 

MakeRwys_Scenery.cfg Runways.txt

Link to comment
Share on other sites

5 hours ago, Shom said:

Here you go

It gets the complete scenery list itemised internally, then commences on Layer 1, which is this one:

[Area.001]
Title=Default Terrain
Local=Scenery\World
Layer=1
Active=TRUE
Required=TRUE

So, it is looking like there is some corruption in the default scenery.  To narrow that down further I'll need to look at adding a lot more logging. I can see to that in the coming days, but meanwhile:

Question: when you updated from P3D 5.2 to 5.3, did you uninstall all three parts and then install? i.e. Scenery, Content and Client? If not please at least do the scenery uninstall/reinstall. Even if you did this already, it might be worth just downloading the Scenery one again (in case the first was faulty) and reinstall.

BUT after you uninstall Scenery, before reinstalling, please look in the P3D Scenery\World|Scenery folder. Are there files (BGL's) left undeleted? If so, these are probably from add-ons and it is more likely be due to one of them that the default files. So, for a test, move all those out to a different folder (eg WorldSaved) then install the P3D Scenery and re-test.

If MR then works properly it was either a corruption in the previous install, or, more likely, a problem in one of the BGLs you moved to WorldSaved (or whatever). So it will then be a process of adding those back -- one at a time if there are only a few, or "by halves" if there are a lot (i.e. put the first half back, test. Then you know which half contains the rogue. So you halve again, and so on.

Let me know please. I'll be back here Monday p.m. (UK time).

Pete

 

  • Like 1
Link to comment
Share on other sites

5 hours ago, Pete Dowson said:

It gets the complete scenery list itemised internally, then commences on Layer 1, which is this one:

[Area.001]
Title=Default Terrain
Local=Scenery\World
Layer=1
Active=TRUE
Required=TRUE

So, it is looking like there is some corruption in the default scenery.  To narrow that down further I'll need to look at adding a lot more logging. I can see to that in the coming days, but meanwhile:

Question: when you updated from P3D 5.2 to 5.3, did you uninstall all three parts and then install? i.e. Scenery, Content and Client? If not please at least do the scenery uninstall/reinstall. Even if you did this already, it might be worth just downloading the Scenery one again (in case the first was faulty) and reinstall.

BUT after you uninstall Scenery, before reinstalling, please look in the P3D Scenery\World|Scenery folder. Are there files (BGL's) left undeleted? If so, these are probably from add-ons and it is more likely be due to one of them that the default files. So, for a test, move all those out to a different folder (eg WorldSaved) then install the P3D Scenery and re-test.

If MR then works properly it was either a corruption in the previous install, or, more likely, a problem in one of the BGLs you moved to WorldSaved (or whatever). So it will then be a process of adding those back -- one at a time if there are only a few, or "by halves" if there are a lot (i.e. put the first half back, test. Then you know which half contains the rogue. So you halve again, and so on.

Let me know please. I'll be back here Monday p.m. (UK time).

Pete

 

I did reinstall the scenery but left customized files in the main P3D folder since I have many addons installed in the legacy way. Also, the older scenery.cfg file was left intact.

The weird thing is that it also happened previously on v5.2 so your theory that it is a corrupted BGL is more likely.

I'll check and report. Thanks for the great support!

 

Link to comment
Share on other sites

7 hours ago, Shom said:

I'll check and report.

Looking again at the Runways.TXT file, the first BGL reported as being scanned is
Scenery\World\scenery\SKCG_ADE_ALT.bgl. I assume this is from one of the Sierrasim add-on sceneries as it certainly isn't from default scenery. In the default set the first occurrence of SKCG is in Scenery\0303\scenery\APX27280.bgl, processed much later.

So, first try MakeRunways with that SKCG_ADE_ALT.bgl renamed to SKCG_ADE_ALT.bgloff. If MR then runs okay, please sent me just that file, as an email attachment to petedowson@btconnect.com. I'd like to see why it crashes MR so I can put in some preventive measures.

Pete

 

Link to comment
Share on other sites

4 minutes ago, Pete Dowson said:

Looking again at the Runways.TXT file, the first BGL reported as being scanned is
Scenery\World\scenery\SKCG_ADE_ALT.bgl. I assume this is from one of the Sierrasim add-on sceneries as it certainly isn't from default scenery. In the default set the first occurrence of SKCG is in Scenery\0303\scenery\APX27280.bgl, processed much later.

So, first try MakeRunways with that SKCG_ADE_ALT.bgl renamed to SKCG_ADE_ALT.bgloff. If MR then runs okay, please sent me just that file, as an email attachment to petedowson@btconnect.com. I'd like to see why it crashes MR so I can put in some preventive measures.

Pete

 

I have SKCG by PKSIM.

On the first run after reinstalling the scenery component MR ran fine.

After adding the older files from the older scenery/world folder it ran fine again.

I guess the real test will be after running the sim for the first time and letting it rebuild etc...

I'll check when I'm back home and report

Link to comment
Share on other sites

37 minutes ago, Shom said:

I have SKCG by PKSIM.

Ah, must be this entry then:

[Area.188]
Title=PKSIM-CartagenaV2
Local=C:\Users\user\Documents\Prepar3D v5 Add-ons\PKSIM-CartagenaV2\data
Layer=188
Active=TRUE
Required=FALSE

37 minutes ago, Shom said:

I guess the real test will be after running the sim for the first time and letting it rebuild etc...

I'll check when I'm back home and report

Thanks. I won't add any more logging yet, then.

Pete

 

Link to comment
Share on other sites

3 hours ago, Pete Dowson said:

Ah, must be this entry then:

[Area.188]
Title=PKSIM-CartagenaV2
Local=C:\Users\user\Documents\Prepar3D v5 Add-ons\PKSIM-CartagenaV2\data
Layer=188
Active=TRUE
Required=FALSE

Thanks. I won't add any more logging yet, then.

Pete

 

Ok so I've launched P3D and MR works fine I have no idea what the issue is/was 🤔

Next time it happens you suggest I disable SKCG entry?

Link to comment
Share on other sites

5 hours ago, Shom said:

Next time it happens you suggest I disable SKCG entry?

That won't eliminate the ALT file its installer placed in the scenery\world\scenery folder. Easier to simply rename it from .BGL to .BGLoff.

But it's very odd that it occurred with what is effectively the exact same setup as before.

Pete

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.