[Update to P3D 5.3 causes Makerwys to crash.]

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

[Update to P3D 5.3 causes Makerwys to crash.]

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

[Update to P3D 5.3 causes Makerwys to crash.]

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

 

👍

[Update to P3D 5.3 causes Makerwys to crash.]

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=
 

 

[Update to P3D 5.3 causes Makerwys to crash.]

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

[Update to P3D 5.3 causes Makerwys to crash.]

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

[Update to P3D 5.3 causes Makerwys to crash.]

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

[Update to P3D 5.3 causes Makerwys to crash.]

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

[Update to P3D 5.3 causes Makerwys to crash.]

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.

[Update to P3D 5.3 causes Makerwys to crash.]

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>

 

[RC4 not showing in P3D v4]

Pete,

Thank you.

I hang my head in shame and embarrassment. That was exactly the problem and I hadn't noticed it. Duh!

(I know RC doesn't use Simconnect but the Radar Contact message window in P3D is titled "Simconnect message window", so I just wondered ).

[RC4 not showing in P3D v4]

After a re-install of P3D v4.3 due to a silly action on my part caused it to stop loading, I now have a problem with Radar Contact where the notification window

(Simconnect, I think) doesn't show. It always worked perfectly previously.

Radar contact works in itself, as if I press the necessary keys, I get the expected responses. I just cannot see any messages.

FSUIPC is v5.14. And I have run the 3 .msi files of simconnect inP3D redist.

Could you perhaps help?

Thanks

Ian Harrison

[FSPS and DX10]

I have switched to DX10 with the program SteveFX to add the necessary shaders.

Do I need to adjust the settings in FSX Booster 2013 or do they work as well with FSX DX9 settings?

[Program (86)]

Strange, because I installed it direct onto my "Flying" SSD under its own name and it is working perfectly.

[FSX Booster 2013-No improvement to Bojote's Tweaks]

Well, all I can say is that I have exactly the opposite experience to you!

Bojote's tweaks (and Kosta's) did nothing for me.

Booster 2013 has improved my Heathrow Extreme landings from 12-15 to about 20fps with extra detail and smoothness.

 

I am very satisfied.

 

(Running PMDG737NG, REX,GSX,and Custom Airports).

I don't have Gatwick but stationary at EGLL

VC =16

2D=18

Ext.=18

[Makerwys]

Pete,

I had an issue on the RC forum, which is now resolved. In a reply, you contributed a couple of comments, twlling me that f5 and others are now produced by Makerwys.

I downloaded 4.45 and ran it but there are still no files with a 5 after the letter.

I have in the RC data directory:a,c,f,i,m,n,p,r,s,z all with 4 after.

What's wrong and more importantly, is it a problem?

[Limiter problem]

Up to about 3 updates ago, my FSX Booster was running Limiter 0.2 with no problems. With the last 2 or 3 updates I keep getting the error "fsx.exe.limited.bat not found in FSPS Booster folder". But it is most certainly there.

I have removed Booster and completely re-intalled it but it is still wrong.

Help please.

[D008 can't change etc.]

Thanks for the info.

I have adjusted the priority of RC and raised it to the same level as FSX.

I don't know if this is a lasting solution but so far,so good. I flew for 5 hours yesterday without a problem.

[D008 can't change etc.]

Actually an old topic which has resurrected itself, this time on my PC!

I have been flying happily for months with FSX,FSUIPC,FSPassengers, Aerosoft Autobrake,Radar contact and the Trafficx programs all co-habiting happily.

Last week Radar contact stopped mid flight and when I opened it I found the old "D008 can't change XXXXXXXXX remains xxxxxxxxx" story.

I wrote to JD but in his usual terse way, he said it's not him it must be me, as nothing has changed in RC.

I tried re-installing FSUIPC as he suggested, it fixed it once but the next time (today) it was back again after RC stopped mid-flight.

Any suggestions as to where I can look for the cause of the problem?

Ian