Jump to content
The simFlight Network Forums

flying-w

Members
  • Content Count

    2,792
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by flying-w

  1. flying-w

    Compiler crashing with Multi-week plans

    I'd like to think it's all complete in the "Official Update", not had any reports of trouble from anyone while it was in beta. You must be on 4.2.2018.20200 or later for this to work, as it changes the content of the traffic BGLs I read. Simon
  2. flying-w

    Compiler crashing with Multi-week plans

    Please see the following: "Major upgrade of the STB Date-Time architecture to support 64bit values and multiweek schedules. The latter provide schedule repeat periods of TWO, FIVE and EIGHT WEEKS in addition to the default. " FSX never claimed to support multiweek schedules for AI aircraft so we are all fortunate this is working in any shape or form. Simon
  3. flying-w

    Configuration crash

    It means in your scenario the file is required, it was always going to be a long shot.
  4. flying-w

    Configuration crash

    Last two suggestions I'm afraid: 1) Delete trafficboardfrontend.exe.config 2) If that does not help, consider reinstalling Microsoft .net V2 and V3.5 Sorry I can't find a better solution. Simon
  5. flying-w

    Crash

    OK, It's one of your "Piedmont" flights. Most are fine, but one is crashing. I'll have to add more debug to determine what the problem is, because it looks fine from the trace. Simon
  6. flying-w

    Is there a way to go back?

    There's a mismatch in your airport database files, so something went amiss somewhere when you were uninstalling. Go to your STB Application Folder, then the Database folder, then delete files ending in ".bin". C:\Users\simon\AppData\Roaming\FlyingWSimulation\SuperTrafficBoard V4 Client\Prepar3D V4\Database
  7. flying-w

    Crash

    Bob, Not sure what you are doing here. None of the trace files demonstrate the problem you are experiencing. What you need to do is..... 1) Set the trace level to verbose 2) Reproduce your problem 3) Close STB 4) Send me the trace file, and reset the trace level to something less than verbose. Thanks Simon
  8. flying-w

    Configuration crash

    I'm sorry to say this is a windows problem and I've no idea why it's happening to you. My only other suggestion is to check the "VirtualStore" folder in your screen shot. Sometimes Windows 7 puts files into there. Send me a screenshot of that too if you wish. If you see "FlyingWSimulation" in there or anything starting "TrafficBoardFrontEnd", delete them. Simon
  9. flying-w

    Is there a way to go back?

    Uninstall, reinstall the base STB version and then whatever update you see fit. Each update has a summary of changes which you'll see in the prolouge. However I don't think it's going to help your situation. The simulator chooses when to generate AI and how much, STB is simply reporting what's there in the simulator. Simon
  10. flying-w

    Configuration crash

    Let me check you are in the right place - screenshot please.
  11. flying-w

    Crash

    Hi Bob Glad your feet are still on the ground! Quite windy here yesterday, of course nothing like what you've seen. Which problem are we debugging here? The trace you sent me is from Data Server, however I need a client trace for logos. Thanks Simon
  12. flying-w

    Configuration crash

    I do: 1) Open Windows File Explorer and navigate to the local application data folder. You can get this by typing %localappdata% into the address bar in file explorer. 2) From there, go into "Flying-W Simulation" 3) You should now be in a folder with a name similar to "C:\Users\simon\AppData\Local\FlyingWSimulation". "Simon" is my Windows user id, yours will be different most likely. 4) You will see one or more folders like this: 5) Delete all the folders that start with "TrafficBoardFrontEnd" Thanks Simon
  13. flying-w

    Configuration crash

    That file is broken. Please try this replacement: TrafficBoardFrontEnd.exe.config Thanks Simon
  14. flying-w

    Configuration crash

    Indeed, you have to adapt the process to your own PC as the problem resolution is described in relation to my PC. Send me the file mentioned in your error, and I'll have a look. C:\Program Files (x86)\FlyingWSimulation\SuperTrafficBoard\TrafficBoardFrontEnd.exe.Config Simon
  15. flying-w

    Configuration crash

    Your problem is "System.Configuration.ConfigurationErrorsException", and the way to fix it is here: See Post dated Feburary 7 2016 Simon
  16. flying-w

    Aircraft Registrations

    In STB it happens as standard function. However your AI package has been designed to do this, over the years I've seen some cheat and just you a single registration for an entire airline fleet. Simon
  17. flying-w

    STB V4 Configuration with Traffic Global

    Good to hear the update helped you. One thing to look out for is incomplete uninstalls. Some of these AI packages leave configuration information behind, such as SimObjectPaths in the p3d.cfg, add-on.xml or other things. STB always calls these out even if the don't cause immediate problems in the simulator, something I might try to be more relaxed about in the future. Thanks Simon
  18. flying-w

    Crash

    That is certainly a suspect, and a trace will confirm it. Once that is understood, I'm sure STB can be made to handle it better (and you will be able to find and fix the underlying problem). Light rain overnight here and it feels warmer than perhaps it should be! Simon
  19. flying-w

    Aircraft Registrations

    Where exactly do you see the aircrft registrations in P3D? If you mean the ones painted on the side of the aircraft, it's a limitation of the simulator. Most AI designers only produce one texture per airline, and that texture as a hard coded (but representative) registration. However the simulator can support unique registrations per aircraft and communicate those to STB, so long as it'd done that way in the traffic schedue. Simon
  20. flying-w

    Crash

    Hi Bob I've a pretty good idea where this is happening, just need to understand a bit more about the context. Could you do a verbose trace please, I reckon it's an airline callsign that's causing the problem right now. Have you added any lately that might contain unusual characters? How was Florence? Simon
  21. flying-w

    Crash

    "System.ArgumentException: Illegal characters in path." In either the name of the folder containing logos or the logo file name itself, Windows thinks there's an invalid character (for example "*", "?" etc). Which one I can't say as it's gone to the default error handler which has no context information. Maybe enabling a trace and reproducing the problem will give me a hint what it is. Simon
  22. flying-w

    Crash

    lol, they visit your house outstay their welcome and leave everything a mess. It's the same the world over.
  23. Summary: STB Client V3.6.2018.20201 is a replacement product for STB V3.2. Obtain the setup program from your original place of purchase (contact me for assistance if you purchased from Flight1). STB Data Server V3.6.2018.14700 is required on the FSX computer when using STB on a separate computer to FSX, and also replaces earlier versions. Download the combined setup and update program from here: http://bit.ly/2OWJ8ZA I've produced a new version of STB for FSX and FSX Steam Edition that contains bug fixes and support for Just Flight's Traffic Global. As we are switching to a new installer framework, it's necessary to completely uninstall your current STB for FSX and then install this one. There is also a new STB data server for those of you running STB and FSX on separate computers. You will need to uninstall the old data server then install the new one also. You'll note a change in terminology here that I started with Prepar3D. The STB Client as it is now known is SuperTrafficBoard itself, which has everything you need to display a list of flights and interact with them. The STB Data Server is required on the FSX computer when using the STB Client on a separate computer. The list of changes are: ⦁ Added configuration content for Just Flight Traffic Global. ⦁ Changed the search order for logo files to make "PNG" the top priority. ⦁ Added high quality logo resizing facility. ⦁ Reset default airline logo size to 125x25. ⦁ Updated logos for a number of airlines, with more planned for future releases. First group are for Just Flight's Traffic Global. ⦁ Bug fix: When determining the width of the airline logo column, the AirlineLogoWidth setting is always used rather than column properties saved to the settings file. ⦁ Add a small margin to the airline logo width column to ensure it displays correctly. ⦁ Upgraded MakeRwys utility to V4.84. ⦁ Bug fix: Traffic BGLs that do not contain any flight plans (e.g. Traffic Global user defined BGL) caused exceptions during airport complication. ⦁ Added limited support for Flight1 UTLive including logos, airline and aircraft configuration content. See user guide for further information. ⦁ Enhance non-BGL scheduled AI presentation (e.g. UT Live) so the scheduled times are updated when the AI becomes active, improving the sort order by time. ⦁ Improved exception handling. ⦁ Flight Plan Complier Bug fix. Don't append "Scenery" to a scenery library path if it already ends with "scenery". ⦁ Inno Setup Framework for all installers. ⦁ Updated user guide. If you would like this now, please contact me with a note of your original software order. It will reach the normal distribution channels in due course, but that always takes a lot of time. Simon
  24. You no longer need to - the new installer is available in all the places that sell STB. Just visit whereever you purchased from and it should be in your account. Thanks Simon
  25. flying-w

    Crash

    Stay safe Bob. I remember visiting Orlando in 2004 shortly after a hurricane, it wasn't a pretty sight. 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.