[Makerwys 82 and Threshold offsets]

Great thanks Pete!

[Makerwys 82 and Threshold offsets]

Hi Pete, 

Thanks for your reply.

Example Airport ICAO code PARD, both runways have displaced thresholds.

Makerwys version  < 82, see runways.txt below for PARD

Airport PARD :N68:01:53.3874  W162:54:08.9516  974ft
          Country Name="United States"
          State Name="Alaska"
          City Name="Red Dog"
          Airport Name="Red Dog"
          in file: Scenery\0000\scenery\APX04070.bgl

          Runway 2 /20  centre: N68:01:53.3874  W162:54:08.9516  974ft
              Start 2 : N68:01:32.0395  W162:54:55.0844  974ft Hdg: 39.0T, Length 5753ft
              Computed start 2 : Lat 68.025360 Long -162.915754
              Offset Threshold primary: 300 feet
              Start 20 : N68:02:14.7352  W162:53:22.8185  974ft Hdg: 219.0T, Length 5753ft
              Computed start 20 : Lat 68.037628 Long -162.889208
              Offset Threshold secondary: 300 feet
              Hdg: 39.000 true (MagVar 19.000), Gravel, 5753 x 120 ft
              *** Runway *** PARD0020 Lat 68.025360 Long -162.915756 Alt 974 Hdg 20 Len 5753 Wid 120
              *** Runway *** PARD0200 Lat 68.037628 Long -162.889206 Alt 974 Hdg 200 Len 5753 Wid 120
          COM: Type=3 (UNICOM), Freq=122.80, Name=""
          FSM A/P PARD, lat=68.031502, long=-162.902481, alt=974

Now same file but produced with MakeRwys 82

Airport PARD :N68:01:53.3874  W162:54:08.9516  974ft
          Country Name="United States"
          State Name="Alaska"
          City Name="Red Dog"
          Airport Name="Red Dog"
          in file: Scenery\0000\scenery\APX04070.bgl

          Runway 2 /20  centre: N68:01:53.3874  W162:54:08.9516  974ft
              Start 2 : N68:01:32.0395  W162:54:55.0844  974ft Hdg: 39.0T, Length 5753ft
              Computed start 2 : Lat 68.025360 Long -162.915754
              Start 20 : N68:02:14.7352  W162:53:22.8185  974ft Hdg: 219.0T, Length 5753ft
              Computed start 20 : Lat 68.037628 Long -162.889208
              Hdg: 39.000 true (MagVar 19.000), Gravel, 5753 x 120 ft
              *** Runway *** PARD0020 Lat 68.025360 Long -162.915756 Alt 974 Hdg 20 Len 5753 Wid 120
              *** Runway *** PARD0200 Lat 68.037628 Long -162.889206 Alt 974 Hdg 200 Len 5753 Wid 120
          COM: Type=3 (UNICOM), Freq=122.80, Name=""
          FSM A/P PARD, lat=68.031502, long=-162.902481, alt=974

 

Offset Threshold information is missing as you can see.

If I check on the r5.bin, this offset information is also never set, always showing 0 feet.

 

Jean

[Makerwys 82 and Threshold offsets]

Hi,

When I read files generated by MakeRwys for P3D V4, the runway threshold offset value is always 0, even on runways with actual displaced threshold.

Do you have same results?

Jean

[PMDG's new B747-400 and FSUIPC5]

Have you tried to compile it with target SDK 8.1 instead of 10?

Maybe something missing on Windows7 causing the issue (If the issue is caused by FSUIPC which is not sure at all)

[PMDG's new B747-400 and FSUIPC5]

Hi Pete,

Did you compile the module on Windows 10 or Windows 7?

J-P

[PMDG's new B747-400 and FSUIPC5]

3 hours ago, stopnicki said:

Just as an additional thought after reading the multitude of reports about this conflict between the QOTS II and FSUIPC5, it appears to me that another factor might be the operating system.

Is it possible that those with Windows7 are encountering  the issues while those on Windows10 are not?

i also posted this thought in the PMDG forums.

Regards,

Roberto

I have 2 systems:

- Windows 10x64 : PMDG747 and FSUIPC5 working perfectly, even if 747 is loaded as first aircraft.

- Windows 7x64  :Problem to load the PMDG 747 if FSUIPC 5 module is running.

I tried everything, starting PMDG module first then FSUIPC, other way around, no chances.

I think this problem is due to a missing system file on Windows 7, Visual C++ redistributable, framework or any other differences on this 2 OS

Let's copy the simple table below to see if the problem is OS related: (just copy paste and add 1 to the faulty OS)

Problems running PMDG747 with FSUIPC on:

• Windows 7x64      2
• Windows 10x64
• Windows 8x64

Jean-Pierre

[PMDG's new B747-400 and FSUIPC5]

24 minutes ago, Pete Dowson said:

Please, try adding the following to the FSUIPC5.INI file [General] section:

NoWeatherAtAll=Yes
ProvideAIdata=No

then see if the 747 is okay. These parameters eliminate two main requests from P3D.

For an unregistered FSUIPC5, which therefore does not scan joysticks or buttons, the only other part I can really eliminate as a test is the L:Var access into PNELS.DLL. I wil add another parameter for that and advise here, in this thread. But please try the above in any case.

Pete

 

Hi Pete,

I just tried adding these 2 lines to the config file, same result, black screens and no landing gear.

It works for me on Win10x64 with FSUIPC5 and 747 but not on the Win7x64.

J-P

[PMDG's new B747-400 and FSUIPC5]

Hi,

I have the same issue, 747 won't work if FSUIPC is running.

If I remove FSUIPC DLL from module folder, 747 works perfectly.

Looks like there is a glitch between FSUIPC and PMDG 747 somehow.

Jean-Pierre

[FSUIPC and PMDG 747 under WIN10]

Hi all,

I've installed FSUIPC 5 under windows 7 and Windows 10 on another computer.

On the Win7, PMDG 747Q2 is working perfectly with FSUIPC5 installed, however

on Win10 machine, PMDG 747 has black screens and no landing gear...

If I remove FSUIPC5.dll from module folder, the 747 works normally.

It looks like there is a compatibility issue under windows 10, anybody else with same issue?

Jean-Pierre