Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by flying-w

  1. 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
  2. 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
  3. 🙂 Works fine for me without any modifications, and I've not received any error reports from customers. Simon
  4. 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: 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
  5. Thanks for the traces. I can see we are receiving information from the simulator about the user aircraft, but the values received don't match any of the departure states we have on the board. For example: 16/12/2018 10:00:46 AM.436: EvaluateState: Converting departureAirportClosest:True, fsState:(OnGround:1, pushingBack:0, exitIsOpen:0, landingLightsOn:0, parkingBrakeOn:1, engine1Running:0, engine2Running:0, engine3Running:0, engine4Running:0, avionicsCircuitOn:1, flapsDown:0, gearDown:1, fastenBelts:0) to User State (fsState: unknown, sequence: 0). You can see in the above the various elements of aircraft state we are intereted in. Compare this to the spreadsheet in the STB install folder that shows you how the above is translated (data\UserAircraftStates.xls, and you will see there is no match based on the aircraft state elements received. What state do you think you should be in here on STB? To make it work, you need to have aircraft elements state that match a row in the spreadsheet. As far as I can see, you state should be "pre-taxi" but it isn't because "Fasten Seat Belts" is off. Not all third party aircraft play nice with FS internals, and it's not suprising to find the seat belt switch in a third party does not update the simulator internals. Thanks Simon
  6. How does each application know which simconnect settings group it should use? There's nothing to distinguish them, so I think STB will try to use port 500 because it's the first in the file. In your simconnect.xml, you do not open port 500 so it stands no chance. If you have two seperate simulator computers that you are trying to address from a single client, that's beyond the support available in STB which is designed to deal with the 99.9% of simpler scenarios. In your case you'd need to change the simconnect.cfg file each time according to the simulator PC you wish to use. The SimConnect.cfg file The SimConnect.cfg file contains communications information for a client (the SimConnect.xml file contains information for a server). This file is only required if a client is going to access Prepar3D running on a remote machine, and should be placed in the Documents folder, or in the same folder as the client application or library, on the computer the client is running on. Note: SimConnect.msi is no longer needed due to the fact that the WinSxS library has been depreciated. The SimConnect.cfg file can contain a number of configurations, identified in sections with the [SimConnect.N] title. The index number is used as a parameter in the SimConnect_Open function. This is useful for applications that communicate with a number of different machines that are running Prepar3D. The default configuration index is zero, and if there is only one configuration in the file, no index number is required.
  7. Bob, you have two entries sharing the same name in simconnect.cfg, that probably won't work. Why two? Simon
  8. Very interesting setup, sorry to say that running two clients at the same time isn't a supported configuration. But don't panic, that's not to say it won't work and I won't try to help, but please try to reproduce this problem by shutting down one of the clients and just using the other. If it does still occur on a single client, please do the following: 1) Set up a "Verbose" trace as per Appendix C of the user guide. 2) Reproduce the problem, describing the steps you took (and the airports involved) as you did above. Please send screenshots of the dialogues once you have entered values but before you press the "OK" button. 3) Close STB, send me the trace file. Thanks Simon
  9. Thanks - I must have fixed this issue at some point then forgot about it! I'll take a look at the flight number. Can you send me the aircraft.cfg (or sim.cfg) from the user aircraft you are using please? Thanks Simon
  10. lol, "the road to nowhere" or "the road to hell", take your pick 😉
  11. 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
  12. Thanks - it's a long road I'm travelling but the journey has begun. Simon
  13. 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
  14. Can you send me the .pln file please? When I try to load this plan by copying it to a file, Prepar3D tells me:
  15. 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
  16. Always good to hear, thank you. LM is doing a good job of preserving the quality of the interfaces STB uses.
  17. I've tested the last few beta STB builds with the latest update available for Prepar3D and not found any problems. Simon
  18. Coming soon, just need to test STB to STB-DS connection. In the meantime, here's the new stuff: Summary of Changes in V4.2.2018.34000 Update Make Runways utilities to V4.8.6.4. Deploy all files associated with Make Runways, not just the .exe file. Added Lorbi-SI redistributables to the Make Runways package included with STB. Added dialog describing the Make Runways related redistributables with links to author webpages and readmes. Removed MakeRunways prerequisite info dialogue. A separate Lorbi-SI install to support Make Runways is no longer mandatory. Tolerate the presence of P3D "AddOn" related entries in the scenery library configuration file. Added a new Content Error Reporting system to capture STB errors relating to simulator content (Scenery Library, SimObjects, Schedules, Airports and Logos). Added debug to catch and better explain any exceptions occurring during instantiation of the P3DFileHelper class that are directed to the Windows Event Log Added atc_type and atc_model values to Flying-W Invisible Aircraft to avoid Simulator and STB Content Errors. Fix for STB operated flights never begining their departure cycle. Fix for incorrect "Next Flight Departure Time" vthat occurred in the flight details dialogue under certain circumstances. Simon
  19. The next beta will have some code to better detect this kind of error. Meanwhile there's only been one report of this problem so far. Simon
  20. If you are happy with the version you have that's great, for your consideration one day there is a "STB V3.6 for FSX", which is probably the last update that will be produced for the FSX platform. Thanks Simon
  21. I'm not back full time yet, but can you say please 1) Which version of STB, as per the "About" screen in help 2) What happens to the order when you click the schedule column heading. That will try to change the sort order. 3) Have you recompiled the airport database lately. All of the above are schedule times which come from BGLs rather than the simulator. 4) Whan an actual AI turns up, does it have the "correct time"? Thanks Simon
  22. The real challenge here is there is so little information (thanks Microsoft) about the actual cause, it could actually be many things. What was the version number that last worked for you? I can do a code comparison, but FileHelper (which is active at the time of the problem) hasn't changed much at all lately. Simon
  23. This one is hard to debug, because I can't reproduce it and it happens so early in the life of STB the framework adds little value to the exception. Can you also check the messages.dll and simulator.dll, and provide the same information as you did earlier for utilities.dll? Thanks Simon
  24. What I need is a worldwide database of every airport and the timezone it's in for every day of the year, which happens to match the simulator's implementation of timezones (which isn't quite real world accurate). As far as I know, that does not exist anywhere and the simulator does not make such information available. Thanks Simon
  25. Correct, we only know one timezone which is the one the user aircraft is in. All times are with respect to that. When the user moves between timezones, the times are recalcuated on the basis of the new timzone. Simon
  • 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.