Jump to content
The simFlight Network Forums

flying-w

Members
  • Content Count

    2,977
  • Joined

  • Last visited

  • Days Won

    47

Everything posted by flying-w

  1. As well as the flight number override box already done, maybe another override box for IATA. Maybe.....
  2. I will consider it. The IATA code comes from the Airline Objects configuration in STB, accessible through the Settings Notebook, which in turn is linked to the callsign in the aircraft.cfg (or whatever SimConnect says it is, that's where STB really gets it from). So if you have "Speedbird" as your aircraft.cfg, you will get "BAxxxx" as your flight number. Simon
  3. Thanks for the marvellous pictures, I've often considered a portrait screen might be good for STB.
  4. Available in update 20800, posted today:
  5. Here is the latest update for STB V3 for Prepar3D V4, with the latest content for AIG and the ability to override the user aircraft flight number in STB You can download the STB Client Update (V4.2.2020.20800) update from here: https://bit.ly/3hUmUVW STB Data Server (only required on the Prepar3D computer when running STB Client on a separate computer), has not changed and remains at the previous update level. It is available here: https://bit.ly/3dD6QW5 Summary of Additional Changes since last official update (V4.2.2020.17900) Content Improvements (logos and configuration): AIG OCI for all packages available to us as of August 1st 2020. Flight number can now be provided in STB for the user aircraft which is used instead of that available from the simulator aircraft.cfg Note: to get the departure flaps changes, you need to reload the aircraft configuration either through the configuration wizard (starting over with a new configuration, or loading the file through the settings notebook, Objects tab. Load either the Universal or AIG Aircraft file from the samples folder in your install directory. Let me know how this works out for you! In the meantime, next in the tubes is an update for Prepar3D V5. Many thanks Simon
  6. It's quite clear there's a lot of buzz around this and rightly so. Well finally at just about the eleventh hour I've receive a certain email, so at long last I can evaluate the SDK, the AI exprience and it's relevance towards STB. Nothing formal to announce at this time, but news in due course.
  7. OK, this one is nearly cooked. Will try to get it out over the weekend, baring one or too distractions now I've finally got my invite to a certain Beta program....
  8. If this can be done, it would need to be UTC based. That's what all simulator time is with respect to, and translated to local time with timezone information. I don't have an information source for the zone each airport finds itself in.
  9. I can set the flight number so it shows up in STB however you want it, but I cannot change it in the simulator as SimConnect does not appear to permit it. Therefore in your conversation with ATC (if you use that), the old flight number from the aircraft.cfg is still used. Does that defeat the object of what you would like to acheive, or is it still useful to see the flight number change in STB only? Simon
  10. I hope future sims can come up with a better way of implementing this configuration, but it's only a hope at this stage.
  11. Again let me emphasize this has been a problem in Microsoft .Net forever, and they still haven't fixed it. The workaround/fix is as suggested here. That said, it might only be a .Net V3 problem, and FSX is stuck in that world I'm afraid. Simon
  12. This is a periodic bug that occurs in Microsoft Windows. Please delete the file mentioned in the message, i.e. C:\Users\KUBA\AppData\Local\FlyingWSimulation\TrafficBoardFrontEnd.exe_Url_5xvhbqbnxytxvnujbo51zne3g5gxstmm\3.6.2018.14100\user.config Thanks Simon
  13. It's hard to provide generic advice about solving problems in simconnect.xml. Please compare it with the working model you have for Prepar3D V4, nothing should be different in the following part: <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <Address>0.0.0.0</Address> <Port>2024</Port> <MaxClients>64</MaxClients> </SimConnect.Comm> It's possible you have may have a different IP address value or port, and as long as that is consistent with the corresponding information in simconnect.cfg on the client, that should be fine. Simon
  14. It only falls into Event Viewer if something goes wrong really early in the startup, before STB's own error handling has been configured. It's very rare and difficult to recreate, but I'll try to find an example and report it here so if it reoccurs you've something to work with. Thanks Simon
  15. There should be another record in event viewer with more details alongside the one you have included above? This one just tells me there was an exception in .net, not what the exception is. Thanks Simon
  16. Reinstalling almost never solves any problem. Can I have a little more information please? What version of STB? What simulator are you using? Has it ever worked? If it did work previously, what has changed? Have you checked Windows Event Viewer?
  17. Send me a verbose trace with the 0 setting please Thanks Simon
  18. This may be possible, I will have a look into it. Are you Prepar3D V4 or V5? Thanks Simon
  19. Sorry to say it may well be Windows 7, we don't support that platform any longer as Microsoft have ended support. If STB works there, that's great, if not as in your case there's not much I can do to fix it. However, if Windows 7 is your only choice it may be possible to work around this. Please contact me via PM as it's not a discussion suitable for everyone. Thanks Simon
  20. At what point during the installation does this occur? What happens immediately beforehand? The V5 installer is built with the same software as V4, and the configuration is virtually the same (except for changing "V4" to "V5") Simon
  21. No, sorry next heard of this one. Can you post a screenshot of the error please so I can put it into context? What's the name of the installer you are using? Thanks Simon
  22. The cause of the error is a Windows problem. Another way to fix would have been to delete the file mentioned in crash.txt Thanks Simon
  23. Glad it's fixed. Useful utility for helping with these sorts of problems is "currports". It will tell you which applications have which ports open so you can see whether Prepar3D and STB Data Server are open for business. 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.