Jump to content
The simFlight Network Forums

No arrival for user aircraft


Recommended Posts

Hi Joe, need some more information please?

1) What version of STB, and which simulator?

2) Is there any particular arrival airport it does not work for, or all?  Please send a screenshot of what the arrivals screen looks like?

3) Please post the flight plan file here?

Thanks
Simon

Link to post
Share on other sites

Hi,

thanks for the prompt reply. To answer your questions:

1. STB 4.2.2018.20200 on P3D 4.4 (but was the same also with P3D 4.3).

2. All airports seem to be affected ( I cannot send a screen capture before the end of the week.. but I see my user flight at the departure airport with the right destination and parking gate info, but nothing (no row) at the arrival airport). Another minor issue (but may be significant?) is that at departure the only missing info is the flight number (displayed as 'LH0') even if I have set it in the aircraft.cfg (as 'LH955').

3. Below an example of a flight plan I loaded:

<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="AceXML" version="1,0">
<Descr>AceXML Document</Descr>
<FlightPlan.FlightPlan>
<Title>LICR Reggio Calabria - LIRZ Perugia</Title>
<FPType>IFR</FPType>
<RouteType>HighAlt</RouteType>
<CruisingAlt>32000</CruisingAlt>
<DepartureID>LICR</DepartureID>
<DepartureLLA>N38° 4' 31.00", E15° 39' 21.00", +000095.50</DepartureLLA>
<DestinationID>LIRZ</DestinationID>
<DestinationLLA>N43° 5' 84.00", E12° 30' 60.00", +000692.50</DestinationLLA>
<Descr>LICR, LIRZ</Descr>
<DeparturePosition></DeparturePosition>
<DepartureName>Reggio Calabria</DepartureName>
<DestinationName>San Egidio</DestinationName>
<AppVersion>
<AppVersionMajor>10</AppVersionMajor>
<AppVersionBuild>61472</AppVersionBuild>
</AppVersion>
<ATCWaypoint id="LICR">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N38° 4' 31.00", E15° 39' 21.00", +000095.50</WorldPosition>
<ICAO>
<ICAOIdent>LICR</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="PIGER">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N38° 32' 80.00",E15° 24' 40.00",+010500.00</WorldPosition>
<Descr>PIGER</Descr>
<ICAO>
<ICAOIdent>PIGER</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="AGNIS">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N39° 48' 40.00",E14° 45' 00.00",+034000.00</WorldPosition>
<Descr>AGNIS</Descr>
<ICAO>
<ICAOIdent>AGNIS</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="SOR">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N40° 34' 95.00",E14° 20' 10.00",+034000.00</WorldPosition>
<Descr>SOR</Descr>
<ICAO>
<ICAOIdent>SOR</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="TEA">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N41° 17' 80.00",E13° 58' 23.00",+034000.00</WorldPosition>
<Descr>TEA</Descr>
<ICAO>
<ICAOIdent>TEA</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="VELIM">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N42° 8' 53.00",E13° 15' 91.00",+021000.00</WorldPosition>
<Descr>VELIM</Descr>
<ICAO>
<ICAOIdent>VELIM</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="PRU">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N43° 6' 10.00",E12° 30' 71.00",+001000.00</WorldPosition>
<Descr>PRU</Descr>
<ICAO>
<ICAOIdent>PRU</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="LIRZ">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N43° 5' 84.00",E12° 30' 60.00",+000692.50</WorldPosition>
<Descr>LIRZ</Descr>
<ICAO>
<ICAOIdent>LIRZ</ICAOIdent>
</ICAO>
</ATCWaypoint>
</FlightPlan.FlightPlan>
</SimBase.Document>

Thanks again and KR

Joe

 

 

 

Link to post
Share on other sites

Thanks, however I can't reproduce this one.  Would you be interested in installing the latest beta update and checking whether your problem exists there?  If it does, that's a better place to debug it from and any fixes would require this level of code in any case?  If the problem does exist, please set up a "Verbose" trace as per Appendix C of the user guide, reproduce the problem and send me the trace file please.

Update is here:

Many thanks
Simon

Link to post
Share on other sites

While investigating your problem I noticed the user aircraft was being counted twice in the airport summary, so it would count +2 departures or +2 arrivals for the airports concerned.  That's fixed in the above beta, so it's already been a fruitful journey.

Simon

Link to post
Share on other sites

Hi,

happy to inform that after the beta installation the issue has been solved!!! Now I see the flight at departure and arrival airports!

Thanks a lot for the great support.

By the way the minor issue related the flight number (displayed as LH0) is still present: is there a way to solve it?... by the way not so important.

KR

Joe

 

Link to post
Share on other sites

Thanks for the aircraft.cfg.  The important thing is this:

atc_flight_number=738

And it can also be set through the Prepar3D UI when configuring your flight.  Either way, it's working for me so far:

image.png.d27db1e57e719fc8a1ca252fb8446dca.png

Let's try to find where it goes wrong for you.  Please set up a verbose trace as per Appendix C of the user guide, restart STB, reproduce the problem and send  me the trace file.

Many thanks

Simon

Link to post
Share on other sites

Here's what's in the trace concerning your flight number:

26-Dec-18 21:42:00.101: > FsUserDescriptionUpdate(): Received Type: BOEING, Model:B738, Title:Boeing 737-800NGX LH fictional (D-ABZA), atcId:D-ABZA, atcAirline:LUFTHANSA, flightNumber:0 DepAirport:LROP, ArrAirport:LWOH, Cruise:514, GearsWork:1, FlapsWorks:1

So it would appear when STB asks for it, the simulator says it is zero.  I will have to think about this one, but I really don't know what to suggest when the simulator does not provide the correct information.

In the mean time, please take a flight in one of the standard Prepar3D aircraft in the same way you would with PMDG, and see if you get the flight number then.  For example: "Lockheed Martin C-130J-30 - USAF"

Simon

Link to post
Share on other sites

Thanks for the test results.  Sorry to say there's nothing I can do to fix this one.  The complexity of PMDG aircraft is well understood and one of it's strengths, but perhaps the complex system implementation somehow stops the flight numbers working.

Simon

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.