Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


flying-w last won the day on April 11

flying-w had the most liked content!

Community Reputation

57 Excellent

1 Follower

About flying-w

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. flying-w

    Error Message

    Yes, I know all about this one. Welcome to the wonderful world of Windows .net corrupting it's own files for reasons unknown. All you need to do is delete the file mentioned in the error message: C:\Users\conno\AppData\Local\FlyingWSimulation\TrafficBoardFrontEnd.exe_Url_w0yixu2kwawdhvlzenm1gewk313gms3o\4.2.2018.13500\user.config Simon
  2. flying-w

    Installing update

    Hi Bob The update program does not care from where you run it. What it does care about is registry entries put down when you install STB base. In your case your registry entries are either lost or inaccessible, and so far I've just your report of this particular problem so that's quite likely to be the case. Best course of action from here is to reinstall I'm sorry to say. Thanks Simon
  3. Here is the latest official update for STB V3 for Prepar3D V4, previously made available as a beta. If you downloaded and installed the beta, you do not need to apply this update. You can download the STB Client update from here: bit.ly/2vTMfJN The combined update and installer from here (only required on the Prepar3D computer when running STB Client on a separate computer). Note this is V4.2.2919.08800, the latest available, and fully compatible with the STB client update described here. http://bit.ly/2HLpdfT Summary of Additional Changes since last official update (V4.2.2018.20200) Added name and location of the simulator Traffic BGL file supplying each flight to the flight details dialogue. Added content support for Alpha India Group (AIG) “One Click Installer”, covering all airlines and flightplans supported by OCI and the entire Winter 2018 season. Added new and updated logos for major UK airports and Washington State, USA. This is the first stage of a long term exercise to update the logo inventory. Correctly round schedule times to the nearest minute instead of always rounding down. The value can now be rounded-up, which avoids a lot of flights intended to operate on the hour which were being reported at 59 minutes past the previous hour. New Content Error Reporting system to capture STB errors relating to simulator content (Scenery Library, SimObjects, Schedules and Airports). Update Make Runways utilities to V4.8.7.1. Deploy all files associated with Make Runways, not just the .exe file. Added Lorbi-SI redistributables to the Make Runways package included with STB, by kind permission of the author. Added dialog describing the Make Runways related redistributables with links to author webpages and read-mes. 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. Fixed bug which ignored flight plans described in a schedule BGL file where the file extension (BGL) is in upper case. Fixed bug that caused mismatches between materialized flights and predicted flights where the aircraft title > 32 characters. We now support titles up to 64 characters. Fixed bug where calculating departed at times for departure remarks could cause an exception. If insufficient data exists to make the calculation, it no longer happens. Fixed various problems with reporting blank, null or whitespace-based paths occurring in simulator configuration files, to the content error reporting system. Fixed exception generated when a keyword=value pair occurring in a simulator configuration file contains a value which itself contains one or more equals signs. Fixed bug where predicted and materialized AI flights failed to reconcile and created duplicate flights on the board for schedule repeat periods less than a day and for the 2nd or greater repeat period within a day. Fix problem where STB operated aircraft would not go through departure workflow. Fix incorrectly calculated next departure flight schedule time in flight details dialogue. Fixed incorrect aircraft counts at airports mentioned in a user aircraft flight plan. Improved used aircraft handling: Obtain user SimObjectID from simulator instead of defaulting value. Added atc_type and atc_model values to Flying-W Invisible Aircraft to avoid Simulator and STB Content Errors Deprecation of the majority of legacy UT2 code. Added debug to catch and better explain any exceptions occurring during instantiation of the P3DFileHelper class that are directed to the Windows Event Log As always, many thanks for your support and if you do happen to install it let me know how you get along with it. Simon
  4. flying-w

    Total Update Prepar3d V4 and STB

    Fantastic, I don't have the plus version myself but I'm glad it's all working for you. Many thanks Simon
  5. flying-w

    Ghost flights

    No we can't instantly respond to a change in the scenery.cfg without airport compilation, simply because the scenery library is so massive for most people and the only way to find a traffic BGL is to open it and read the content. As you will know, the BGL covers a wide number of scenery formats in FSX and beyond, which is a shame really as a simple filename convetion could have made it so much better. In any case, after making any change to your scenery library I recommend compiling the airport database. If that's too much, then certainly after making any change affecting traffic schedules. Simon
  6. flying-w

    Ghost flights

    STB does use the scenery.cfg, and then we only read those BGLs containing AI traffic schedules. Have you recompiled the STB airport database following the changes you've made to your BGL collection? Thanks Simon
  7. flying-w

    Selecting AI Traffic

    The default "View AI" command has always suffered from this type of problem and it's essentially the same since FSX. Sometimes it works, often many times, and sometimes it does not. It goes wrong because you cannot say I want to view aircraft "xyz". Instead you have to find out where xyz is in a list of all AI aircraft then send the same number of "cycle to next view" commands in to the simulator. So if you have 200 AI, it could take 100 commands to perform which is a lot. If the list changes between STB acquiring it and the simulator acting on the cycle command, it can show the wrong AI. From my side there's not much I can do, but the native Prepar3D camera commands (Extended AI Views and Observors) do not have this problem, so please give those a try. Thanks Simon
  8. flying-w

    Not sure its a problem with P3dv4.5

    Strange one Bob! When the box is yellow, it means we've not received the "simulation started" so we think P3D is in a menu or dialogue or is paused rather than flying. How do you rate P3D V4.5? Simon
  9. Sorry to say from my side I've no idea what's changed in the scenery library. The simulator has some idea things have changed of course, but it's not externalised to third parties. Simon
  10. Sorry to say the link does not provide a picture. Please update. Thanks Simon
  11. No problem, glad we fixed it. Thanks Simon
  12. Hello Uwe In my development system, the user aircraft time was calculated correctly. I've added some additional debug information in case you still have problems, and I will produce a new beta just as soon as I can. At the present time, that's some days away due to other changes, but I'll get done as quickly as I can. Once it's available, I'd like you to install it. If the problem is still there, I'll need a verbose trace to examine it. Thanks Simon
  13. Thank you - that actually makes a lot of sense as we made many changes to STB's understanding of dates and times to support multi-week scehdules in AI flight plans from AIG. It's likely there's a problem with that implementation for user aircraft. Like I say, I'll investigate. Simon
  14. OK, so I think you are saying: "The user aircraft departure date/time is incorrect when I try to set it a certain number of minutes from "now" in the simulator. If that's the case, I'll look into it. Thanks Simon
  15. Hi I think I've seen this problem before and fixed it in a beta release. See here for details of the beta: Thanks Simon

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.