Melika Posted April 28, 2021 Report Share Posted April 28, 2021 Hi - 1st, thanks for FSUIPC and MakeRwys they have so improved my flightsim enjoyment. 2nd, I have read guidelines etc but am not sure if this exactly where support requests should be made. Anyway here goes - 3rd - the issue.... over many months now many of my NAV/APPR approaches are leaving me of centre on runways. Finally looking into it and although I felt I had been using LorbySceneryExporter.exe and MakeRwys.exe as directed, not so sure now. I think my .net is well up-to-date. I do not understand if my P3D v5.1 is: "abiding by the new L-M system". Both Lorby and MakeRwys are set to run as admin. When I look in the Lorby and MakeRnwys .cfg I was surprised to find them empty. That is when I thought the of centre approaches are due to me not using MakeRwys properly. I tried to do that PowerShell run of LorbySceneryExporter.exe. but not sure what that did, if anything. I think the errors on approach line-up are limited to add-on sceneries of which I have a lot of ORBX and 3 UK2000. So, I now suspect that my addon scenery is not being 'read' by Makerunways. I have the full Lorby P3DAddonOrganiser and things look OK there - there is one file that is not green though ? Otherwise P3D runs fine, no scenery error messages and it looks good - the UK2000 and ORBX airports and scenery look great. As we all know flightsim is at times as much tinkering with and updating addons, sims themselves etc - so it has taken me a while to dig into this particular issue AND get some quality 'flying' in as well 🙂 I have been working on this for a number of days now and am starting to run out of ides. I have checked many of the previous discussions on this and tried the solutions identified -without success. So thought I would ask if it were possible to get some help. I uploaded a number of files. LorbyScenery.cfg MakeRwys_Scenery.cfg Runways.txt scenery.zip Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 28, 2021 Report Share Posted April 28, 2021 3 hours ago, Melika said: When I look in the Lorby and MakeRnwys .cfg I was surprised to find them empty. Really this is a question for Lorby, as it is his program which cannot get over the problem with your corrupt Scenery.CFG file. You have these bad entries near the beginning of the file: [UK2000 Common Library] Active=FALSE [UK2000 Leeds Xtreme] Active=FALSE [UK2000 Newcastle Xtreme] Active=FALSE I've no idea how they got there, but as they are not [Area.nnn] sections they seem to stop the Lorby program in its tracks. Looking at the rest of the file it all seems to be default -- no add-on scenery there. So you might as well delete the Scenery.CFG file, then run P3D to let it generate a good one. I think Lorby's AddOnOrganizer program also has an optionto check and repair corrupt CFG files (but i'm not sure). Pete Link to comment Share on other sites More sharing options...
Melika Posted April 28, 2021 Author Report Share Posted April 28, 2021 Thanks very much Pete - I took your advice, deleted P3D scenery.cfg. I looked also in Lorby P3DAddon Organiser and there was a double entry to the path for ORBX Library - the out-of-date one I unchecked. Ran MakeRwys and it has scanned the addons this time. Proof of the pudding they say though - I did the same flight into EGNT and the NAV/APPR approach put me right on the centre-line ! That seems to have done the trick. Naturally will be keeping an eye on local landing at my present airport - CYYJ - couple of kilometers away from me. Also, Pete I really appreciate your time already on this, particularly as it is not an issue with MakeRways working correctly. ( it is my confusion using the MakeRwys with the freeware Lorby tool.) Anyway, no need to respond at all and I will carry on as things do seem to be working better now. It would help me going on though, if I could ask - 'Using the app: 1. LorbySceneryExporter will request full administrator privileges, so it is able to access all config files. 2. Use the Command Line, Powershell or similar to start the app - "LorbySceneryExporter" will create the result file "LorbyScenery.cfg" in the same location - "LorbySceneryExporter filename.cfg" will create the result file as <filename.cfg> in the same location.' Do I have to try to this Powershell business each time I run MakeRwys (i.e. when I install new scenery) And 2. As I continue on to sort this out - Active=TRUE Required=FALSE -. Is this a good entry or should both Active and required be TRUE ? And 3. - a big ask - I attached the same files much more populated this time - Do they look OK now ? (!) - the LorbyScenery.cfg which is virtually empty ? The Runways.txt file even zipped by Peaazip is too large but I copied some text here that is encouraging "Make Runways File: Version 5.126 by Pete Dowson Using "LorbySceneryExport.exe MakeRwys_Scenery.cfg" LorbySceneryExport executed: Checking for "MakeRwys_Scenery.cfg" Reading Prepar3D v5 scenery: The CFG file being used is: "F:\P3D\MakeRwys_Scenery.cfg" ============================================================================= Area.001 "Default Terrain" (Layer=1) Path(Local/Remote)=Scenery\World ============================================================================= Area.002 "Default Scenery" (Layer=2) Path(Local/Remote)=Scenery\BASE ============================================================================= Area.003 "0000 Base" (Layer=3) Path(Local/Remote)=Scenery\0000 ============================================================================= Scenery\0000\scenery\APX03070.bgl =============================================================================" And - the test airport I used (EGNT) - (my home toon !) got a result - rather long but is this essentially what I am looking for ? Airport EGNT :N55:02:16.4917 W001:41:23.2898 265.99ft Country Name="United Kingdom" State Name="" City Name="Newcastle" Airport Name="Newcastle" in file: Scenery\0501\scenery\APX47120.bgl Runway 7 /25 centre: N55:02:16.4917 W001:41:23.3300 265.99ft Start 7 : N55:02:01.2016 W001:42:20.9214 265.99ft Hdg: 65.2T, Length 7627ft Computed start 7 : Lat 55.033524 Long -1.706383 Offset Threshold primary: 394 feet Start 25 : N55:02:31.7818 W001:40:25.7404 265.99ft Hdg: 245.2T, Length 7627ft Computed start 25 : Lat 55.042305 Long -1.673244 Offset Threshold secondary: 450 feet Hdg: 65.190 true (MagVar -2.000), Asphalt, 7627 x 151 ft Primary ILS ID = INC ILS: INC 111.50 Hdg: 65.2 , Flags: GS DME BC Slope: 3.00, "CAT III ILS/DME 07" Secondary ILS ID = INWC ILS: INWC 111.50 Hdg: 245.2 , Flags: GS DME BC Slope: 3.00, "CAT III ILS/DME 25" *** Runway *** EGNT0070 Lat 55.033524 Long -1.706383 Alt 265.99 Hdg 67 Len 7627 Wid 151 ILS 111.50, Flags: GS DME BC *** Runway *** EGNT0250 Lat 55.042305 Long -1.673244 Alt 265.99 Hdg 247 Len 7627 Wid 151 ILS 111.50, Flags: GS DME BC COM: Type=8 (APPROACH), Freq=124.375, Name="NEWCASTLE" COM: Type=1 (ATIS), Freq=118.375, Name="EGNT" COM: Type=8 (APPROACH), Freq=125.825, Name="NEWCASTLE DIRECTOR" COM: Type=5 (GROUND), Freq=121.725, Name="NEWCASTLE" COM: Type=6 (TOWER), Freq=119.700, Name="NEWCASTLE" Taxipoint #0, type 1 (normal): N55:02:35.9607 W001:40:34.7252 -- Forward Taxipoint #1, type 1 (normal): N55:02:37.5480 W001:40:31.6658 -- Forward Taxipoint #2, type 1 (normal): N55:02:37.2889 W001:40:26.9473 -- Forward Taxipoint #3, type 1 (normal): N55:02:35.6692 W001:40:26.3357 -- Forward Taxipoint #4, type 1 (normal): N55:02:16.3945 W001:42:24.4491 -- Forward Taxipoint #5, type 1 (normal): N55:02:16.7509 W001:42:22.4196 -- Forward Taxipoint #6, type 1 (normal): N55:02:16.3621 W001:42:14.7238 -- Forward Taxipoint #7, type 2 (Hold Short): N55:02:11.8269 W001:41:33.7665 -- Reverse Taxipoint #8, type 1 (normal): N55:02:11.3086 W001:41:42.8640 -- Forward Taxipoint #9, type 2 (Hold Short): N55:02:09.7537 W001:41:41.6346 -- Reverse Taxipoint #10, type 1 (normal): N55:02:07.0974 W001:41:39.5586 -- Forward Taxipoint #11, type 1 (normal): N55:02:05.2509 W001:41:38.0957 -- Forward Taxipoint #12, type 1 (normal): N55:02:09.8185 W001:42:16.0032 -- Forward Taxipoint #13, type 1 (normal): N55:02:13.2847 W001:42:15.5705 -- Forward Taxipoint #14, type 1 (normal): N55:02:14.9368 W001:42:15.3596 -- Forward Taxipoint #15, type 1 (normal): N55:02:09.2678 W001:42:22.9410 -- Forward Taxipoint #16, type 1 (normal): N55:02:04.1819 W001:42:23.2838 -- Forward Taxipoint #17, type 2 (Hold Short): N55:02:02.4326 W001:42:22.2313 -- Forward Taxipoint #18, type 1 (normal): N55:02:01.0720 W001:42:21.4298 -- Forward Taxipoint #19, type 1 (normal): N55:02:20.2495 W001:42:14.4775 -- Forward Taxipoint #20, type 1 (normal): N55:02:22.2255 W001:42:14.3587 -- Forward Taxipoint #21, type 2 (Hold Short): N55:02:08.7819 W001:41:58.3086 -- Reverse Taxipoint #22, type 1 (normal): N55:02:32.4945 W001:40:23.0222 -- Forward Taxipoint #23, type 1 (normal): N55:02:32.1058 W001:40:24.4561 -- Forward Taxipoint #24, type 1 (normal): N55:02:22.8086 W001:40:59.4749 -- Forward Taxipoint #25, type 1 (normal): N55:02:13.3819 W001:41:34.9977 -- Forward Taxipoint #26, type 1 (normal): N55:02:08.4903 W001:41:53.4807 -- Forward Taxipoint #27, type 1 (normal): N55:02:00.6833 W001:42:22.8734 -- Forward Taxipoint #28, type 1 (normal): N55:02:07.2593 W001:41:30.1712 -- Forward Taxipoint #29, type 2 (Hold Short): N55:02:06.8706 W001:41:53.7109 -- Reverse Taxipoint #30, type 1 (normal): N55:02:04.0847 W001:41:54.1101 -- Forward Taxipoint #31, type 1 (normal): N55:02:05.1861 W001:41:50.5549 -- Forward Taxipoint #32, type 1 (normal): N55:02:04.9593 W001:41:47.0386 -- Forward Taxipoint #33, type 2 (Hold Short): N55:02:33.4987 W001:40:25.1465 -- Forward Taxipoint #34, type 1 (normal): N55:01:59.2903 W001:41:54.1246 -- Forward Taxipoint #35, type 1 (normal): N55:01:58.7396 W001:41:59.1554 -- Forward Taxipoint #36, type 2 (Hold Short): N55:02:25.1410 W001:40:57.8382 -- Forward Taxipoint #37, type 1 (normal): N55:02:15.7790 W001:42:03.4987 -- Forward Taxipoint #38, type 1 (normal): N55:02:16.1030 W001:41:55.0787 -- Forward Taxipoint #39, type 1 (normal): N55:02:16.6861 W001:41:49.0293 -- Forward Taxipoint #40, type 1 (normal): N55:02:17.8523 W001:41:42.9816 -- Forward Taxipoint #41, type 1 (normal): N55:02:30.9072 W001:40:53.7411 -- Forward Taxipoint #42, type 4 (ILS Hold Short): N55:02:25.3354 W001:40:57.6904 -- Forward Taxipoint #43, type 4 (ILS Hold Short): N55:02:02.5945 W001:42:22.3230 -- Forward Taxipoint #44, type 4 (ILS Hold Short): N55:02:11.6326 W001:41:33.6024 -- Forward Taxipoint #45, type 4 (ILS Hold Short): N55:02:06.7086 W001:41:53.7350 -- Forward Taxipoint #46, type 4 (ILS Hold Short): N55:02:08.7819 W001:41:58.5887 -- Forward Taxipoint #47, type 4 (ILS Hold Short): N55:02:09.5269 W001:41:41.4720 -- Forward Taxipoint #48, type 4 (ILS Hold Short): N55:02:33.6283 W001:40:25.2319 -- Forward Gate G2 [#G0]: N55:02:14.4833 W001:42:24.6374 Type 8 (Small Gate), Size 18.0m, Hdg 183.5T Parking Park1 [#G1]: N55:02:20.3142 W001:42:17.9845 Type 2 (GA Ramp Small), Size 10.0m, Hdg 272.9T Parking Park2 [#G2]: N55:02:22.1931 W001:42:10.8421 Type 4 (GA Ramp Large), Size 18.0m, Hdg 87.6T Parking Park3 [#G3]: N55:02:20.2171 W001:42:10.8421 Type 3 (GA Ramp Medium), Size 14.0m, Hdg 87.6T Gate G1 [#G4]: N55:02:13.4790 W001:42:21.0952 Type 8 (Small Gate), Size 18.0m, Hdg 267.5T Parking Park4 [#G5]: N55:02:22.2579 W001:42:17.6224 Type 12 (?), Size 16.0m, Hdg 272.1T Taxipath (Name #0): Type 1 (Taxi), Start#=0, End#=1, Wid=30.48m Taxipath (Name #0): Type 1 (Taxi), Start#=1, End#=2, Wid=30.48m Taxipath (Name #0): Type 1 (Taxi), Start#=2, End#=3, Wid=30.48m Taxipath (Name #0): Type 3 (Parking), Start#=4, End#=G0, Wid=15.24m Taxipath (Name #0): Type 4 (Path), Start#=4, End#=5, Wid=15.24m Taxipath (Name #0): Type 4 (Path), Start#=5, End#=6, Wid=15.24m Taxipath (Name #1): Type 1 (Taxi), Start#=8, End#=9, Wid=30.48m Taxipath (Name #1): Type 1 (Taxi), Start#=9, End#=47, Wid=30.48m Taxipath (Name #1): Type 1 (Taxi), Start#=47, End#=10, Wid=30.48m Taxipath (Name #1): Type 1 (Taxi), Start#=10, End#=11, Wid=30.48m Taxipath (Name #0): Type 1 (Taxi), Start#=12, End#=13, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=13, End#=14, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=14, End#=6, Wid=21.34m Taxipath (Name #2): Type 1 (Taxi), Start#=12, End#=15, Wid=21.34m Taxipath (Name #2): Type 1 (Taxi), Start#=15, End#=16, Wid=21.34m Taxipath (Name #2): Type 1 (Taxi), Start#=16, End#=43, Wid=21.34m Taxipath (Name #2): Type 1 (Taxi), Start#=43, End#=17, Wid=21.34m Taxipath (Name #2): Type 1 (Taxi), Start#=17, End#=18, Wid=21.34m Taxipath (Name #0): Type 3 (Parking), Start#=19, End#=G1, Wid=15.24m Taxipath (Name #0): Type 4 (Path), Start#=6, End#=19, Wid=15.24m Taxipath (Name #0): Type 4 (Path), Start#=19, End#=20, Wid=15.24m Taxipath (Runway 7): Type 2 (Runway), Start#=22, End#=23, Wid=46.02m Taxipath (Runway 7): Type 2 (Runway), Start#=23, End#=24, Wid=46.02m Taxipath (Runway 7): Type 2 (Runway), Start#=24, End#=25, Wid=46.02m Taxipath (Runway 7): Type 2 (Runway), Start#=25, End#=8, Wid=46.02m Taxipath (Runway 7): Type 2 (Runway), Start#=8, End#=26, Wid=46.02m Taxipath (Runway 7): Type 2 (Runway), Start#=26, End#=18, Wid=46.02m Taxipath (Runway 7): Type 2 (Runway), Start#=18, End#=27, Wid=46.02m Taxipath (Name #0): Type 3 (Parking), Start#=20, End#=G2, Wid=15.24m Taxipath (Name #3): Type 1 (Taxi), Start#=25, End#=7, Wid=30.48m Taxipath (Name #3): Type 1 (Taxi), Start#=7, End#=44, Wid=30.48m Taxipath (Name #3): Type 1 (Taxi), Start#=44, End#=28, Wid=30.48m Taxipath (Name #0): Type 3 (Parking), Start#=19, End#=G3, Wid=15.24m Taxipath (Name #0): Type 3 (Parking), Start#=13, End#=G4, Wid=15.24m Taxipath (Name #0): Type 1 (Taxi), Start#=26, End#=29, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=29, End#=45, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=45, End#=30, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=30, End#=31, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=31, End#=32, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=32, End#=10, Wid=21.34m Taxipath (Name #4): Type 1 (Taxi), Start#=26, End#=21, Wid=21.34m Taxipath (Name #4): Type 1 (Taxi), Start#=21, End#=46, Wid=21.34m Taxipath (Name #4): Type 1 (Taxi), Start#=46, End#=12, Wid=21.34m Taxipath (Name #0): Type 4 (Path), Start#=30, End#=34, Wid=16.76m Taxipath (Name #0): Type 4 (Path), Start#=34, End#=35, Wid=16.76m Taxipath (Name #0): Type 3 (Parking), Start#=20, End#=G5, Wid=15.24m Taxipath (Name #5): Type 1 (Taxi), Start#=6, End#=37, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=37, End#=38, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=38, End#=39, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=39, End#=40, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=40, End#=41, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=41, End#=0, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=0, End#=3, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=3, End#=48, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=48, End#=33, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=33, End#=23, Wid=21.34m Taxipath (Name #6): Type 1 (Taxi), Start#=41, End#=42, Wid=30.48m Taxipath (Name #6): Type 1 (Taxi), Start#=42, End#=36, Wid=30.48m Taxipath (Name #6): Type 1 (Taxi), Start#=36, End#=24, Wid=30.48m Taxiname: #0 = Taxiname: #1 = F Taxiname: #2 = A Taxiname: #3 = E Taxiname: #4 = B Taxiname: #5 = D Taxiname: #6 = C TaxiWay : G0-4-5-6-14-13-12 TaxiWay : G1-19-6 TaxiWay : G2-20-19-G3 TaxiWay : G4-13 TaxiWay : 26-29-45-30-31-32-10 TaxiWay : 35-34-30 TaxiWay : G5-20 TaxiWay : 2-3 TaxiWay : 1-2 TaxiWay : 0-1 TaxiWay A: 12-15-16-43-17-18 TaxiWay B: 26-21-46-12 TaxiWay 😄 41-42-36-24 TaxiWay 😧 6-37-38-39-40-41-0-3-48-33-23 TaxiWay E: 25-7-44-28 TaxiWay F: 8-9-47-10-11 FSM A/P EGNT, lat=55.037922, long=-1.689803, alt=265.99 🙂🙂 Alan Alan P3D.zip Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 29, 2021 Report Share Posted April 29, 2021 10 hours ago, Melika said: t would help me going on though, if I could ask - 'Using the app: 1. LorbySceneryExporter will request full administrator privileges, so it is able to access all config files. 2. Use the Command Line, Powershell or similar to start the app - "LorbySceneryExporter" will create the result file "LorbyScenery.cfg" in the same location - "LorbySceneryExporter filename.cfg" will create the result file as <filename.cfg> in the same location.' These are instructions for separate use of the LorbySceneryExporter. MakeRwys does it all for you -- it runs the exporter automatically. So just follow the MakeRwys instructions, not the Lorby ones! It doesn't need "Powershell". Just run it "as administrator". To avoid forgetting this, I simply right-click on the MakeRwys EXE, selection Properties-Compatibility and check "run as administator" there. After that it will always be okay. 10 hours ago, Melika said: And 2. As I continue on to sort this out - Active=TRUE Required=FALSE -. Is this a good entry or should both Active and required be TRUE ? No, leave as it is. "REQUIRED" just means it's essential or the sim won't load. I don't think any normal scenery needs it or wants it. 10 hours ago, Melika said: And 3. - a big ask - I attached the same files much more populated this time - Do they look OK now ? Sorry, I'm not checking your scenery. If it works, it's okay. 10 hours ago, Melika said: the LorbyScenery.cfg which is virtually empty ? That file is nothing to do with MakeRwys. As the log says, The CFG file being used is: "F:\P3D\MakeRwys_Scenery.cfg" I suggest you stop fussing and get on with flying. Your original problem was a corrupted P3D scenery.cfg file. You fixed that. Pete Link to comment Share on other sites More sharing options...
Melika Posted April 29, 2021 Author Report Share Posted April 29, 2021 (edited) Your advice has really helped me along and.... good advice on getting on with flying ! Cheers - Alan 👍 Edited April 29, 2021 by Melika Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now