OnCourse Software
http://www.ocs-support.co.uk/forums/

2 small issues after the 9th of May update
http://www.ocs-support.co.uk/forums/viewtopic.php?t=2051		 Page 1 of 1
Author:  TheDuke [ Fri May 13, 2016 2:56 pm ]
Post subject:  2 small issues after the 9th of May update
After the 9 May update I flew RJGG to RKPC on FL240 IFR.

First, the ATIS at RJGG: I start ASN weather first and then P3D, so I expect P3D to have to correct weather atm startup. The PF3 ATIS gives me RWY36 with winds 160/06 and the correct QNH. Later, the Taxi instructions are for the RWY18, so correct.

Second, after passing the JEC waypoint at FL240, ATC calls 'GBXTR Contact CONTROL on 118.65'. My VCP replies with 'Traffic' and my position'. Checking in Pf3_display shows that I'm on Multicom. Hitting ZERO makes my VCP calling 'Traffic' and position again. From the list in Pf3_display I took the next CONTROL frequency, dialed it in, and pushed the ZERO. After my VCP reported as usual to control, I get a Roger from ATC. I guess all is well now (I'm still flying) but this should not happen.

Dirk
Author:  ThomasAH [ Fri May 13, 2016 3:08 pm ]
Post subject:  Re: 2 small issues after the 9th of May update
Please attach logs.
Author:  vololiberista [ Fri May 13, 2016 6:47 pm ]
Post subject:  Re: 2 small issues after the 9th of May update
TheDuke wrote:
After the 9 May update I flew RJGG to RKPC on FL240 IFR.

First, the ATIS at RJGG: I start ASN weather first and then P3D, so I expect P3D to have to correct weather atm startup. The PF3 ATIS gives me RWY36 with winds 160/06 and the correct QNH. Later, the Taxi instructions are for the RWY18, so correct.

Dirk
I have raised this with Dave as well. I had a case where the weather QNH was correctly shown on the aircraft instruments with the correct elevation but the inital ATIS on startup gave a different QNH and then immediately after take-off Approach gave yet another QNH. So it would appear that PF3 is modifying the value given to it by FSUIPC.
Author:  TheDuke [ Sat May 14, 2016 9:10 am ]
Post subject:  Re: 2 small issues after the 9th of May update
Here are the logs and the flightplan.

And one more thing......:
According to ICAO rules, runway numbers 01 to 09 must be pronounced as 'ZERO ONE through ZERO NINER' and not 'ONE through NINER' as in PF3. I guess other purists have reported this already. :lol:

Dirk
Author:  ThomasAH [ Sat May 14, 2016 10:21 am ]
Post subject:  Re: 2 small issues after the 9th of May update
TheDuke wrote:
Here are the logs and the flightplan.
Thank you, now we can check.
TheDuke wrote:
And one more thing......:
According to ICAO rules, runway numbers 01 to 09 must be pronounced as 'ZERO ONE through ZERO NINER' and not 'ONE through NINER' as in PF3. I guess other purists have reported this already. :lol:
Yes, the internal bug report is from two weeks ago, but we're still discussing if AI aircraft using US voices should have a certain chance of dropping the leading zero during their calls/readbacks :)

From https://en.wikipedia.org/wiki/Runway:
Quote:
It is very common in a country such as Canada for a controller to clear an incoming American aircraft to, for example, runway 04, and the pilot read back the clearance as runway 4.
Author:  ThomasAH [ Sat May 14, 2016 12:28 pm ]
Post subject:  Re: 2 small issues after the 9th of May update
TheDuke wrote:
First, the ATIS at RJGG: I start ASN weather first and then P3D, so I expect P3D to have to correct weather atm startup. The PF3 ATIS gives me RWY36 with winds 160/06 and the correct QNH. Later, the Taxi instructions are for the RWY18, so correct.
Code: Select all
13-5-2016 14:13:14: 430 - No active AI at RJGG - Checking wind direction for runway-in-use!
13-5-2016 14:13:14: 430 - Active Runway determined by PF (Wind) selection
13-5-2016 14:13:16: 960 - Wind DIR from weather station  : 298
13-5-2016 14:13:17: 020 - Transcript: 'This is Chubu Centrair International Airport Information Hotel   Weather at 0700 Zulu   winds 298 at 6
  visibility greater than 20 miles.   Sky condition clear   . Temperature 18   . Dewpoint 12   . Altimeter 1017  . ILS Runway 36 in use, Landing departing runway 36  .
  VFR aircraft say direction of flight. All aircraft readback hold short instructions. Advise controller on initial contact you have Hotel '
...
13-5-2016 14:21:22: 230 - Transcript: 'Ground   Golf Bravo X-Ray Tango Romeo Ready to taxi.  '
13-5-2016 14:21:28: 060 - Active Runway determined by PF (Wind) selection
13-5-2016 14:21:30: 590 - Wind DIR from weather station  : 232
13-5-2016 14:21:30: 590 - Active Runway is set to 18
13-5-2016 14:21:33: 350 - Transcript: '  Golf Bravo X-Ray Tango Romeo Roger. Taxi to holding point, runway 18 using taxiway   Bravo   Alpha   Alpha 10   '
So PF3 did the correct thing with the weather information it received from the weather station, but:
Code: Select all
13-5-2016 14:05:54: 620 - Wind_Surf_Dir=160  Wind_Surf_Vel=6  rwyClouds = 0 Cloud_Low_Base = 0
... lots of Wind_Surf_Dir=160 ...
13-5-2016 14:13:01: 350 - Wind_Surf_Dir=160  Wind_Surf_Vel=6  rwyClouds = 0 Cloud_Low_Base = 0
13-5-2016 14:14:42: 580 - Wind_Surf_Dir=298  Wind_Surf_Vel=6  rwyClouds = 999999 Cloud_Low_Base = 0
13-5-2016 14:14:45: 610 - Wind_Surf_Dir=160  Wind_Surf_Vel=6  rwyClouds = 999999 Cloud_Low_Base = 0
... lots of Wind_Surf_Dir=160 ...
Takeoff happens at 14:36:42, now Wind_Surf_Dir starts to change
13-5-2016 14:36:48: 940 - Wind_Surf_Dir=160  Wind_Surf_Vel=6  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:36:51: 040 - Wind_Surf_Dir=161  Wind_Surf_Vel=6  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:36:55: 740 - Wind_Surf_Dir=162  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:36:57: 810 - Wind_Surf_Dir=162  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:36:59: 880 - Wind_Surf_Dir=163  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:37:01: 950 - Wind_Surf_Dir=164  Wind_Surf_Vel=4  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:37:44: 140 - Wind_Surf_Dir=222  Wind_Surf_Vel=3  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:38:05: 640 - Wind_Surf_Dir=225  Wind_Surf_Vel=3  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:38:08: 220 - Wind_Surf_Dir=261  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:38:10: 770 - Wind_Surf_Dir=265  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:38:13: 330 - Wind_Surf_Dir=269  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:38:15: 890 - Wind_Surf_Dir=274  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:38:18: 430 - Wind_Surf_Dir=277  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
13-5-2016 14:38:20: 960 - Wind_Surf_Dir=282  Wind_Surf_Vel=5  rwyClouds = 10535643 Cloud_Low_Base = 0
... further changes up to Wind_Surf_Dir=320 and later down to Wind_Surf_Dir=240 again ...
So ...
- Wind_Surf_Dir in PF3 is directly below the aircraft, while ATIS/clearance is calculated for the center of the airport.
- The wind below the aircraft (on the ground) stays static, while the wind at the airport changes.

I assume offset 04DA is used to determine Wind_Surf_Dir (there also is 0EF2 which will produce an interpolated value) and I would assume 04DA is the most accurate value we can get for the current wind direction.
Dave, would it be feasible to use Wind_Surf_Dir (and Wind_Surf_Vel) below the aircraft as another virtual weather station and include it in the weather calculation? If the effect is weighted by distance, this virtual weather station would have a big influence for the calculated weather at the departure airport and so would reflect the weather experienced by the aircraft more closely.
TheDuke wrote:
Second, after passing the JEC waypoint at FL240, ATC calls 'GBXTR Contact CONTROL on 118.65'. My VCP replies with 'Traffic' and my position'. Checking in Pf3_display shows that I'm on Multicom. Hitting ZERO makes my VCP calling 'Traffic' and position again. From the list in Pf3_display I took the next CONTROL frequency, dialed it in, and pushed the ZERO. After my VCP reported as usual to control, I get a Roger from ATC. I guess all is well now (I'm still flying) but this should not happen.
Code: Select all
13-5-2016 15:28:56: 020 - Transcript: '  Golf Bravo X-Ray Tango Romeo Contact CONTROL on 118.65   '
13-5-2016 15:29:05: 990 - Transcript: 'Roger 118.65   Golf Bravo X-Ray Tango Romeo  ' 
13-5-2016 15:29:13: 480 - COM Freq changed to: 118.65  IPC Set: 6245
13-5-2016 15:29:15: 520 - iMulticomFreq       : 118.65 
13-5-2016 15:29:16: 560 - Transcript: 'Romeo Kilo Papa Charlie (Local) Traffic   Golf Bravo X-Ray Tango Romeo  9 Miles east at Flight Level 240  '
The problem here is, that PF3 has a voice recording of "Multicom" only in the phrase:
Code: Select all
pfchat234=your flight plan has been filed. Contact Multicom on
So having the correct phrase here would require editing 238 voice files. Possible, but only little gain for much work, especially as there are various other things that Dave should work on.
If you can do this, I'm pretty sure he would include it in PF3. I have done a little bit of such editing with Audacity, but you should expect about 5 minutes work per voice file -> 19 hours.
Author:  Dave March [ Sat May 14, 2016 5:41 pm ]
Post subject:  Re: 2 small issues after the 9th of May update
Quote:
I assume offset 04DA is used to determine Wind_Surf_Dir (there also is 0EF2 which will produce an interpolated value) and I would assume 04DA is the most accurate value we can get for the current wind direction.
Dave, would it be feasible to use Wind_Surf_Dir (and Wind_Surf_Vel) below the aircraft as another virtual weather station and include it in the weather calculation? If the effect is weighted by distance, this virtual weather station would have a big influence for the calculated weather at the departure airport and so would reflect the weather experienced by the aircraft more closely.
Tower currently uses weather at the aircraft whereas ATIS uses weather at the weather station (as in the real world) and we use FSUIPC bank CC00-CFFF for that
Author:  TheDuke [ Wed May 18, 2016 11:15 am ]
Post subject:  Re: 2 small issues after the 9th of May update
ThomasAH wrote:
So having the correct phrase here would require editing 238 voice files.
That would certainly not be my solution (as a retired software specialist). PF3 'knows' it's an IFR flight on FL240. PF3 switches the AC to a CONTROL freq. So to me it would be logical that 'Multicom' is out of the question here. But... never mind, I know how to get around it if it happens again.
dmarch wrote:
Tower currently uses weather at the aircraft whereas ATIS uses weather at the weather station (as in the real world) and we use FSUIPC bank CC00-CFFF for that
What I saw in Active Sky Next was the weather at the AC. Would it not be better if all ATIS messages are based on the same thing? Just to avoid confusion. But... on the other hand.... winds can change rapidly.

Dirk
Page 1 of 1 All times are UTC+01:00
Powered by phpBB® Forum Software © phpBB Limited