Claude Troncy

March 31, 2019

Thanks Pete for your comments.

Claude

March 30, 2019

Bonjour Pete,

May be your informed opinion could help me understand this:

-Same computer
-Two disk with the same OS windows 7, one for P3D stable, and the other for development and test.

On one system the restart of P3D on the fly is very quick, on the other it is very long. I don't see any reason for that, so if you have an idea ?

FSUIPC log

Quick Load between 1966 and 1778

Quote

1513 Initialising SimConnect data requests now
1513 FSUIPC Menu entry added
1513 ... Using Prepar3D with Academic License
1513 \\FLIGHT1\Users\Troncy\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
1513 \\FLIGHT1\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
1529 ### The user object is 'F-22 Raptor - 525th Fighter Squadron'
1529 ### Mode is NORMAL
1778 ### Mode: PAUSE on
1966 Loading Complete ...

Long Load between 24008 and 1934

Quote

1528 Initialising SimConnect data requests now
1528 FSUIPC Menu entry added
1528 ... Using Prepar3D with Academic License
1544 \\FLIGHT1\Users\Troncy\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
1544 \\FLIGHT1\C\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
1560 ### The user object is 'F-22 Raptor - 525th Fighter Squadron'
1560 ### Mode is NORMAL
1934 ### Mode: PAUSE on
24008 Loading Complete ...

Merci

Cheers
Claude

March 20, 2019

😃😃

Everything seems to be OK now and FSIPanel is happy with the new runways files.

Again thank you very much Pete.

Claude

March 20, 2019

Hi Pete,

Thank you very much, the airport magvar are now well reflected for each runway, but in the runways.xml, it seems that the <Hdg> and <ILSHdg> tags don't reflect the correct magnetic heading, and whatever the magvar is, these value don't change.

Cheers

Claude

February 17, 2019

Thank you Pete.

You don't have to apologyze. You make such a great job for the world of FSX... P3D.
Take your time to fix the problem. I wish you nice holidays.

Cheers

Claude

February 17, 2019

42 minutes ago, Pete Dowson said:

Did you check, for instance, Paris de Gaulle (LFPG)

Yes all airports have this problem.

42 minutes ago, Pete Dowson said:

I'm amazed the FSAerodata does not amend the runway entries.

I only change the MagVar in the global airport section and it was reflected by MakeRwys for all the runways. In fact I do not find any MagVar data in the runway subrecord. Where is this data ?

Claude

February 17, 2019

Hi Pete,

I made a mistake!
In fact with fsaerodata, the MagVar should be 0.780

I investigate with an hexa editor in the different files.
- In the files situated in the 3 sceneries at the top, the MagVar is coded as 0.780
- But in the file APX48140.bgl (provided by fsaerodata) they did not change the initial P3D MagVar, and is -2.00

That explain the difference in the files generated by MakeRwys.

Now if I modify the fsaerodata APX48140.bgl with the correct MagVar 0.780 instead of -2.00 then all the date made by MakeRwys are coherent and FSIPanel is happy.

When FSIPanel is not happy the A/C is positionned far to the left or the right of the runway axe and after the A/P doesn't capture the ILS (PMDG 737 NGX)

I am going to send an email to fsaerodata asking them why there is an inconsistency, between the MagVar values in their files.

I hope they will not say that the MagVar in the top sceneries must overide the one in the APX48140.bgl.

Again thank you for helping me to understand where the problem was.

Cheers

Claude

February 16, 2019

Bonjour Pete,

10 hours ago, Pete Dowson said:

Take a look in your Runways.txt file

So the infos are for LFPO

Quote

Airport LFPO :N48:43:23.9967 E002:22:45.9997 291ft
Country Name="France"
State Name=""
City Name="Paris"
Airport Name="Orly"
in file: Scenery\0601\scenery\APX48140.bgl

Runway 6 /24 centre: N48:43:39.9347 E002:20:20.1818 291ft
Start 6 : N48:43:12.9826 E002:19:03.9770 291ft Hdg: 61.8T, Length 11961ft
Computed start 6 : Lat 48.720020 Long 2.317014
Offset Threshold primary: 984 feet
Start 24 : N48:44:06.8868 E002:21:36.3851 291ft Hdg: 241.8T, Length 11961ft
Computed start 24 : Lat 48.735500 Long 2.360865
Hdg: 61.840 true (MagVar -2.000), Concrete, 11961 x 148 ft
Primary ILS ID = ORE
........ etc

**********************************************************************************************************************************

Airport LFPO :N48:43:23.9967 E002:22:45.8403 291ft
Country Name="France"
State Name=""
City Name="Paris"
Airport Name="Orly"
in file: C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\P3D\PROC\scenery\LFPO.BGL

FSM A/P LFPO, lat=48.723331, long=2.379400, alt=291

**********************************************************************************************************************************

Airport LFPO :N48:43:23.9967 E002:22:45.8403 291ft
Country Name="France"
State Name=""
City Name="Paris"
Airport Name="Orly"
in file: C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\P3D\PROC_SIDs\scenery\LFPO_SIDS.BGL

FSM A/P LFPO, lat=48.723331, long=2.379400, alt=291

***********************************************************************************************************************************

Airport LFPO :N48:43:23.9319 E002:22:45.9885 291ft
Country Name="France"
State Name=""
City Name="Paris"
Airport Name="Orly"
in file: C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\Comms\scenery\FSAD_comms.BGL

COM: Type=8 (APPROACH), Freq=123.87, Name="ORLY"
COM: Type=8 (APPROACH), Freq=124.45, Name="ORLY"
COM: Type=8 (APPROACH), Freq=118.85, Name="ORLY"
COM: Type=8 (APPROACH), Freq=120.85, Name="ORLY"
COM: Type=8 (APPROACH), Freq=126.57, Name="DE GAULLE"
COM: Type=1 (ATIS), Freq=126.50, Name="LFPO"
COM: Type=1 (ATIS), Freq=131.35, Name="LFPO"
COM: Type=7 (CLEARANCE), Freq=121.55, Name="ORLY"
COM: Type=7 (CLEARANCE), Freq=120.50, Name="ORLY"
COM: Type=9 (DEPARTURE), Freq=124.35, Name="DE GAULLE"
COM: Type=9 (DEPARTURE), Freq=127.75, Name="ORLY"
COM: Type=9 (DEPARTURE), Freq=133.37, Name="DE GAULLE"
COM: Type=9 (DEPARTURE), Freq=128.37, Name="ORLY"
COM: Type=5 (GROUND), Freq=121.70, Name="ORLY"
COM: Type=5 (GROUND), Freq=121.82, Name="ORLY"
COM: Type=6 (TOWER), Freq=118.70, Name="ORLY"
COM: Type=6 (TOWER), Freq=120.50, Name="ORLY"
FSM A/P LFPO, lat=48.723324, long=2.379441, alt=291

MakeRnwys detects LFPO airport in 4 files, the last three, which are at the top of the sceneries doesn't have any MagVar at all.

Cheers

Claude

February 15, 2019

1 minute ago, Pete Dowson said:

I don't really see what I should do any differently in MakeRunways. Having different variations for the same airport just seems wrong.

I perfectly understand.

5 minutes ago, Pete Dowson said:

Are you expecting it to show 0.78 or -2.00

-2.00 is expected.

2 minutes ago, Pete Dowson said:

I tried to analyse LFPO_SIDS.BGL with ADE

I tried too and the file looks strange, but I think it is in this file (or the other two) that MakeRwys find the wrong value 0.78 associated with the airport. But is it really an airport ?

When the 3 sceneries are not active then MakeRwys find the correct value in Scenery\0601\scenery\APX48140.bgl. This file is also provided by fsaerodata and overwrite de initial one.

Claude

February 15, 2019

45 minutes ago, Pete Dowson said:

It looks like your fsaerodata updater only updates one of these -- the airport headers, not the magvar associated with each runway. I think perhaps this could be a problem with ILS orientations.

I know that with aero.sors the problem is identical. https://www.fsipanel.com/forum/viewtopic.php?f=6&t=233

That means the problem is not in the data provided by aero.sor and fsaerodata.

As the problem doesn't seem to be with MakeRwys, I am going to check again with FSIPanel.

Nevertheless I'll try the aero.sors data and let you know.

Merci

Claude

February 14, 2019

27 minutes ago, Pete Dowson said:

But all that cannot make any difference when the same value is used at the same time for all.

I agree with you. That is incomprehensible.

29 minutes ago, Pete Dowson said:

Maybe I just need whatever FSAD BGL is it which was logged for your XML file

OK I attach them.

Thanks

Claude

FSAD_comms.BGL

LFPO.BGL

LFPO_SIDS.BGL

February 14, 2019

Continuing the investigation I found that fsaerodata adds 4 sceneries at the top

Extract of MakeRwys_Scenery.cfg

Quote

[Area.175]
Title=FSAD_Navaids
Local=C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\Navaids
Layer=175
Active=TRUE
Required=FALSE

[Area.176]
Title=FSAD_Approaches
Local=C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\P3D\PROC
Layer=176
Active=FALSE
Required=FALSE

[Area.177]
Title=FSAD_Approaches1
Local=C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\P3D\PROC_SIDs
Layer=177
Active=FALSE
Required=FALSE

[Area.178]
Title=FSAD_Comms
Local=C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\Comms
Layer=178
Active=FALSE
Required=FALSE

If one of FSAD_Approaches, FSAD_Approaches1 or FSAD_Comms is active then Runways.xml (LFPO data) is construct with the first one which is active.

Quote

<File>C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\Comms\scenery\FSAD_comms.BGL</File>
<SceneryName>FSAD_Comms</SceneryName>

<File>C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\P3D\PROC_SIDs\scenery\LFPO_SIDS.BGL</File>
<SceneryName>FSAD_Approaches1</SceneryName>

<File>C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\P3D\PROC\scenery\LFPO.BGL</File>
<SceneryName>FSAD_Approaches</SceneryName>

If none is active the data from the standard BGL file "Scenery\0601\scenery\APX48140.bgl" is used.

In all case Runways.txt and I suppose r4.csv are built using the standard BGL file "Scenery\0601\scenery\APX48140.bgl"

Cheers

Claude

February 14, 2019

What is strange is that the bgl file detected in the runway. txt and in the runway.xml is not the same.

See my first post

Claude

February 14, 2019

Hi Pete,

So I deleted three files . r4.csv, Runways.xml and Runways.txt.

I then run MakeRwys and for LFPO
- In r4.csv the MagVar is -2.00
- In Runways.txt MagVar is -2.00
- In Runways.xml MagVar is 0.780

The three files have the same "Date modified" value.

Without fsaerodata all the MagVar values are equal to -2.00

Cheers

Claude

February 13, 2019

Bonjour Pete and John,

May be you can help !
I have just installed fsaerodata and it confuse FSIPanel, which use MakeRwys to build it's own database.

Investigating the problem, I compared the runway.xml, and I found a difference in the magvar data. For LFPO it is -2.00 without fsaerodata and 0.780 with it.
Nevertheless if I compare the two runway.txt (with and without fsaerodata), i do not see any difference both are at -2.00.

**** Runway.txt  --- with fsaerodata ****
Airport LFPO :N48:43:23.9967  E002:22:45.9997  291ft
          Country Name="France"
          State Name=""
          City Name="Paris"
          Airport Name="Orly"
          in file: Scenery\0601\scenery\APX48140.bgl

          Runway 6 /24  centre: N48:43:39.9347  E002:20:20.1818  291ft
              Start 6 : N48:43:12.9826  E002:19:03.9770  291ft Hdg: 61.8T, Length 11961ft 
              Computed start 6 : Lat 48.720020 Long 2.317014
              Offset Threshold primary: 984 feet
              Start 24 : N48:44:06.8868  E002:21:36.3851  291ft Hdg: 241.8T, Length 11961ft 
              Computed start 24 : Lat 48.735500 Long 2.360865
              Hdg: 61.840 true (MagVar -2.000), Concrete, 11961 x 148 ft

**** Runway.xml  --- with fsaerodata ****
<ICAO id="LFPO">
<ICAOName>Orly</ICAOName>
<Country>France</Country>
<City>Paris</City>
<File>C:\Users\Troncy\Documents\fsAerodata Files\Navigation Data\Comms\scenery\FSAD_comms.BGL</File>
<SceneryName>FSAD_Comms</SceneryName>
<Longitude>2.379441</Longitude>
<Latitude>48.723324</Latitude>
<Altitude>291</Altitude>
<MagVar>0.780</MagVar>
  
***  In R4.csv ---  with fsaerodata  ****  The magvar is the same than the one in runway.txt but different thank the one in runway.xml
  LFPO,0020,48.717541,2.376687,291,20.340,7866,110.30,197,-2.000,48.727779,2.381833,0

I do not know if it is the source of the problem for FSIPanel, but is there something which could explain the difference between the xml and the txt file for the magvar data.

Thanks for youy help

Cheers
Claude

February 4, 2019

Hi Pete,

Of course you are right, it is obvious now that the script terminate before it has the time to display the window. What an idiot I am.
I have 50 years of software development behind me, and it looks like a beginner's mistake. May be I am getting younger...😃 or NOT !

Thanks Pete

Cheers

Claude

February 4, 2019

Bonjour John,

Print is here only to have a trace in the fsuipc log file.
The script is called with a joystick button.

I have of course use the console to trace the lua script, and have activate the lua log but nothing special in it.

Quote

********* LUA: "test_sound" Log [from FSUIPC version 5.15] *********
1372840 System time = 03/02/2019 18:58:21, Simulator time = 14:23:03 (13:23Z)
1372840 LUA: beginning "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\test_sound.lua"
1372840 LUA: ...s\Lockheed Martin\Prepar3D v4\Modules\test_sound.lua:1
1372840 LUA: Global: ipcPARAM = 0
1372840 LUA: display
1372840 LUA: ...s\Lockheed Martin\Prepar3D v4\Modules\test_sound.lua:2
1372871 LUA: ...s\Lockheed Martin\Prepar3D v4\Modules\test_sound.lua:3
1372934 >>> Thread forced exit (ipc.exit or os.exit) <<<
1372934 System time = 03/02/2019 18:58:21, Simulator time = 14:23:03 (13:23Z)
********* LUA execution terminated: Log Closed *********

The script is this one

Quote

print("display")
ipc.display("HI")
ref = sound.play("GearUpCall")

The print "display" works and I can see it in the fsuipc log
The display("HI") doesn't work
The sound is played without a problem.

Cheers

Claude

February 3, 2019

Bonjour,

I have this simple script

Quote

print("display")
ipc.display("HI")

No window appears on the screen and of course nothing is displayed even when I try the non simconnect window using the parameter NoMessageWindows=Yes in the ini file.

What can I do investigate more ?

Thanks

Claude

October 17, 2018

Hi John,

On 10/15/2018 at 5:18 PM, John Dowson said:

Do you have the action required set to 'Send direct to FSUIPC Calibration'?

No as the axis assignement is done in P3D V4. I only want the calibration done by FSUIPC as I do with other axes.

On 10/15/2018 at 5:18 PM, John Dowson said:

The axis action should also be 'Steering Tiller' on the left hand side ('This side to send axis values''), and not 'Axis Steering Set'.

I do not have the 'Axis Steering Set' in the combo box.

On 10/15/2018 at 5:18 PM, John Dowson said:

Also make sure that you are using the latest version of FSUIPC, 5.141e.

Yes I have this version installed.

Cheers

Claude

October 13, 2018

Bonjour,

In P3DV4, I have the axis assignement "Axis Steering Set" assigned to the Rz axis of my Saitek X52 PRO.
I cannot find it in the FSUIPC (V5.14) joystick calibration. When I move the Rz axis of my X52, nothing is displayed in the Steering tiler box. It seems that this axis is ignored ?
I have no problem with the other axes.

Any Idea ?

Cheers
Claude

October 20, 2017

Bonjour Jean

you can find the 5.121.c in the updated module section here

http://forum.simflight.com/topic/80977-updated-modules/

Cheers

Claude

October 15, 2017

Thanks Pete. Everything is OK now with the 5.121c.

Cheers

Claude

October 14, 2017

55 minutes ago, Pete Dowson said:

It will be version 5.121c.

Thank you very much.
What I do not understand is why it was working in 4.0 ? LM has certainly change something.

Claude

October 14, 2017

Same problem with the latest driver from Nvidia.

Claude

October 14, 2017

1 hour ago, Pete Dowson said:

Can you go into full screen mode, please, and there change that display to whatever you want -- wider, taller, in a different position. That should work and be saved.

No that did not work......
But I found something new !
I use DSR (4.00x (native resolution)) with my nvidia 1080. It is the best way for me to have less shimmering with a good AA.
My native resolution is 1920 X 1200, P3D use 3840 X 2400 and the GPU downscale to the native resolution.

When I do not use DSR, I do not have the problem, and everything is as it was in P3D V4.00.

I will install the latest nvidia driver and see what happens.

1 hour ago, Pete Dowson said:

How often do you swith between them?

It is not a problem I can live like that, and wait for your interim update.
There is no hurry !

Claude

Sign In

Claude Troncy

Posts

Joined

Last visited

Content Type

Profiles

Forums

Events

Gallery

Downloads

Posts posted by Claude Troncy

Looking for information on P3D startup.

Looking for information on P3D startup.

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Magvar and MakeRwys

Problem with ipc.display

Problem with ipc.display

Problem with ipc.display

Tiler axis problem.

Tiler axis problem.

FSUIPC 5.121.b and P3D V4.1 Strip display

FSUIPC 5.121.b and P3D V4.1 Strip display

FSUIPC 5.121.b and P3D V4.1 Strip display

FSUIPC 5.121.b and P3D V4.1 Strip display

FSUIPC 5.121.b and P3D V4.1 Strip display

Browse

Activity

Important Information