Jump to content
The simFlight Network Forums

flying-w

Members
  • Content Count

    2,853
  • Joined

  • Last visited

  • Days Won

    43

flying-w last won the day on February 22

flying-w had the most liked content!

Community Reputation

66 Excellent

2 Followers

About flying-w

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://www.supertrafficboard.com

Profile Information

  • Gender
    Male
  • Location
    England

Recent Profile Visitors

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

  1. Yes that's correct, and something I've seen before: Whenever I do, I try to improve the messages that STB puts out to explain the situation. In your case, it said: "FLW.STB.Utilities.StbDisconnectException: Invalid XML detected for airport SWTQ(Termas Pousada Do Rio Quente). Please check the runways.xml file found in the Prepar3D V4 installation folder at line 1718799 position 12, and the AFD/AFCAD file that implements the airport." Hopefully that helped you understand the problem. Thanks Simon"
  2. Yes, that's certainly possible. What I should be doing is using the Windows "Send to Compressed Folder" option as that creates a universal zip. I like 7z but that's just a personal preference, so I'll switch back to regular zips now. Thanks for pointing this out Simon
  3. In general LM did a great job with observers, there's just a little icing they missed off of the cake as you describe.
  4. Here is the latest official update for STB V3 for Prepar3D V4 (and STB Data Server) You can download the STB Client Update (V4.2.2020.04000) update from here: http://bit.ly/2OFELnb For the STB Data Server (only required on the Prepar3D computer when running STB Client on a separate computer), the latest available version is also V4.2.2020.04000 and is fully compatible with the above STB Client. You can download the STB Data Server combined installer and updater from here: http://bit.ly/37hdn5z Summary of Additional Changes since last official update (V4.2.2020.01900) AIG OCI Content updated for all packages available to Flying-W as of 9/2/2020. Distances calculated between AI Aircraft and Airports (and the user aircraft and airports) are now rounded up or down to the nearest decimal point value required. Previously they were always rounded down. Fix airport compilation error relating to decimal based airport attitude rounding and conversion experienced by a small number of users (makerwys support as introduced in update V4.2.2020.01900). 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
  5. Not something I've a lot of control over I'm sorry to say. The only situation I am aware of that may cause this to happen is having the STB Observer feature enabled, which it is by default. For a reason I cannot understand, LM gives us the ability to create observers but not delete them through SimConnect, and nor do they appear to give us any control over whether that appears in the view cycle or not. STB uses an observer for a number of AI views, those where the camera is at a fixed point (i.e. the "from runway, from parking, from airport centre" views) and also the AI Flyby. If you don't use those, you can disable the observer: Configuration -> Settings -> AI Views tab, uncheck the "Enable AI Observer" control. Save your STB settings, and restart P3D That should remove it from the view cycle in P3D (because it is not created in the first place), but only after you restart P3D. Thanks Simon
  6. I've been working 16 hours today, and then decided I'll sleep when I'm dead. Looking at the code, I effectively do a "round (airport arrival distance, 0)" in the case you mention. This goes to a the default rounding method of "nearest even number" which I don't think is what we want. The alternative is nearest number away from zero, which rounds up for numbers greater than .5 and down for numbers less than .5 Here's the good stuff. https://docs.microsoft.com/en-us/dotnet/api/system.math.round?view=netframework-4.8#midpoint-values-and-rounding-conventions I'll need to change my code for the next update.
  7. Interesting observations and thanks for the good results. I don't think I've tried precision 0. Did it used to work differently than now? I may just truncate rather than round, I'd have to look at the logic. There are too many airlines and airports in the world right now, managing the logo library is a never ending task! Simon
  8. Hello Uwe, I checked your trace and it looks like the airport altitudes are working correctly now. STB is rounding down to the nearest whole number in each case, so altitude 100.99 becomes altitude 100. However STB does not require super accurate altitudes, as the only place I recall it being used are in the observer based views and a one foot error makes no noticable difference there. So I'd say the fix is good, and I'll commit it to the next update which should come soon now. Many thanks for checking this out for me If anyone else wants to try, please do and let me know the outcome! Thanks Simon
  9. OK, while I don't have the problem here, I've written a new way of rounding numbers to a whole number. I don't know why the inbuilt .net routies are not working, but this one does it slightly faster anyway. Please try out this version of FSObjects and report back, the instructions are the same as before. Note the version number of the updated FSObjects, V4.2.2020.03300. 1) In your STB Install folder, make backup copies of FSObjects.dll and FSObjects.pdb 2) Download the zip, and unpack into your STB Install folder. This should replace both FSObjects files above with the debug versions (4.2.2020.03300) 3) Switch on verbose tracing as per Appendix C of the STB user guide. 4) Recreate the problem. When it occurs, close down STB 5) Send me the trace file, and switch off the trace. FSObjects.V4.2.2020.03300.zip
  10. And of course if it is humanly possible to fix it, I will. This is why we do betas, a program runs perfectly here but not so for everyone else.
  11. Thanks but the trace file does not help as there are no verbose messages in there. Did you set up the verbose trace as described above?
  12. That's strange, because there's a well tested fix already in place to handle the floating point numbers that makerwys is now generating. I'll look into it and get back to you Thanks Simon
  13. Yes, that would be for a future version. FSX and Prepar3D have some logic built in to handle this. I think if an AI is deleted on the ground (by STB or anyone), it won't come back unless you reset your flight. However those whom are airbourne according to the schedule usually do come back. Nothing I can do about that I'm afraid, it would require changes to the underlying traffic schedule (BGL etc). Thanks Simon
  14. I think I have that in the next update - Thanks
×
×
  • 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.