Jump to content

John JF

Commercial Member
  • Content Count

    45
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

98 Good

1 Follower

Profile Information

  • Gender
    Male
  • Location
    UK
  • Interests
    Aviation and Weather.

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

About Me

  • About Me
    Does stuff with Navigation data for a living.

Recent Profile Visitors

832 profile views
  1. Thanks @B777ER this will be fixed in the next update. In the meantime you can download a new version from our support page. https://support.justflight.com/support/solutions/articles/17000134398-vpilot-error-loading-ruleset-
  2. Hello everyone. I'm pleased to announce that FS Traffic update 1.0.5 is now live. This update includes brand new aircraft models, new schedule's and reworked core system. https://www.youtube.com/watch?v=O078mruXaAc Available here: https://www.justflight.com/product/fs-traffic-microsoft-flight-simulator Changelog: https://community.justflight.com/topic/4240/update-change-logs-v1-0-5-released-edited-20-06-2023 John - Just Flight
  3. Hello everyone. The call for testers has now closed. Please look out for news very shortly. John - Just Flight.
  4. Hello everyone. After a few weeks of tracking down some bugs and internal testing we believe we now have a build that is ready for release. Before that we’d like to get this tested on as many systems as possible, therefore we are going to open up the latest version to a limited number of users. If you wish to be part of this team that we will be hosting on Discord, please email richard@justflight.com Successful applicants will receive a private link to our FS Traffic server. Please note that you will need to be an existing user of FS Traffic and have access to Discord.
  5. Hello everyone. I’d like to share a provisional changelog base on the work of the past couple of months. We’ve reworked some major parts of the core traffic module which should improve destination and cruise traffic generation as well as many other bug fixes and features. This update will also include the A350-100, 757-200, 757-300, 767-300 and 737 Max 7/8/9. We shouldn’t be too far away from a release however there are still some things we’d like to tackle as well as testing. The changelog can be viewed at https://community.justflight.com/topic/3494/fs-traffic-for-msfs/51 and will updated as we get closer to release.
  6. You can reduce the Time Before Departure value in the Options page of the Traffic Control Centre. This will reduce the number of models spawned in at the gates but ensure you still see the correct number of departures and arrivals. The reason for the slider being removed was that it was causing instability which would cause FS Traffic to crash. Great to hear! The A350-100, 757-200/300, 767-300 and 737 Max are coming soon.
  7. Hello. A new update to the core installer is now available. This update focuses mainly on improvements to the Traffic Control Centre. No need to reinstall the fleet package, V1.0.3 is still current version. Changelog is as follows. v1.0.4 - FS Traffic Core Installer ONLY TCC: Reskinned Traffic Control Centre interface TCC: All pop-up interfaces now always on top TCC: Crash when creating flight plans at airport where no plans currently exist - fixed TCC: Clear button now clears the fields TCC: Warning added for when a database cannot be accessed successfully TCC: Additional feature - when creating a new schedule, if a pln file doesn't exist it will create it for you TCC: Generated random flight number changed to 4 digits when creating a new schedule TCC: VMR file and database updated TCC: Error when deleting an entry from the Aircraft Livery Manager - fixed TCC: Aircraft Manager->Livery Manager: Saves not applying to newly created aircraft - fixed TCC: Updated manual Module: Airlines database update - Norwegian Air NAX>NOZ Module: Aircraft ini file update - Norwegian Air NAX>NOZ Module: Five Title= entries in ini files now supported (increased from three) Thanks John - Just Flight
  8. The update addressed a bug that was stopping traffic activating at the same time so your density of movements should increase with this update. Anything specific that's putting you off updating? This was always outside the scope of the initial FS Traffic release. Unfortunately most default airport gates in MSFS aren't set up with parking codes for airlines or cargo. Something we are looking at for the future. Not in this update. This was mainly to address overall stability. We will be updating the database at some point along with including some past databases. John - Just Flight.
  9. Hello everyone. 1.0.3 is now available. You'll need to reinstall both the core and fleet packages as both have been updated. Keep track of the changelogs here: https://community.justflight.com/topic/4240/update-change-logs-v1-0-3-released-edited-01-03-2023 Looking forward to your feedback. John - Just Flight.
  10. Hello all, I just want to keep you in the loop of where we are with the next update for FS Traffic. The initial plan was release today however we need the weekend to track down a bug and be sure the software is as stable as possible. Release should be early next week now. An important update is that we have changed the parameters have to be met for destination traffic to be compiled. This is now set to 1000ft/60knots/5mins. This means you will see destination traffic even if you’re flying low and slow. The code which handles the time detection has been re done meaning that you will now consistently see the correct departure and arrivals at both your departure and destination airport. Callsigns for departure traffic will now be read out correctly, a shoutout to Whakamolenz from FSLTL who advised on this. The changelog is as follows but may be subject to change: Module: Departures now using correct callsign callouts Module: Destination airport detection revisions Module: New system for handling departures Module: Additional cruise AI scenarios added, plus increased randomness Module: Additional airports added to database Module: SF3 added to aircraft database Module: Remove traffic/Regenerate traffic system improvements Module: Bug when switching to an airport with no scheduled arrivals - fixed TCC: VMR template exporting/importing bug TCC: Right clicking headers in the TCC would cause a crash - fixed TCC: Localisation issue fixed Misc: In-sim menu not showing ICAO code when reopened during flight - fixed Fleet: Added Cebu (CEB) Pacific A320, 320_SL and A320_NEO, A321_SL, A321 NEO, a330-300, ATR72 Fleet: Added Air China 747-400 Fleet: Added Air New Zealand 777-300ER Fleet: Added Asiana 747-400 Fleet: Added Aurigny E195,ATR72 Fleet: Added Iraqi 747-400 Fleet: Added REX 737-800 Fleet: Added Singapore 777-300ER Fleet: Added Smart wings 737-800 Fleet: Added missing A320NEO textures. AVA, QDA,SKU,LAN,IBE Fleet: Colour matched BA fleet Fleet: Rebuilt Aircraft.CFG's to correct some callsigns Fleet: Updated wheel anim code Fleet: Added bogie tilt to A330-200/A330-300/747-400/747-8/787-8/787-9 Beyond this we will continue to make improvements and will be working with our livery artists to prepare the free model pack which will be included in a later fleet update. John - Just Flight
  11. This is a result of the schedule data that we use, unfortunately it lists the regionals under the same code as the Majors. Something we'd like to do in future is much more manual processing of this data so that we can separate the regional carriers and include the correct callsign. In the meantime I'll set up a bug report in our system to remind us of this.
  12. With FS Traffic you have an option in the control centre to increase the time before departure value which will fill your airports up. We also have implemented cruise traffic at altitude and there’s also a setting to increase this as you wish. Different solutions but they are both implemented. John - Just Flight.
  13. I wouldn't use the MSFS ground aircraft slider as this will also inject generic models. All you need to do is simply increase the time before departure value in the FS Traffic Control Centre options page. I personally prefer 120 mins for a realistic scene. John - Just Flight
  14. Hello. The radius aircraft are spawned on the ground isn't be something we have control over but we did reduce the default time before departure value from 180 mins to 90 mins. This might be why this behaviour is more obvious. Please feel free to change this as you wish. We can always report this as a bug to Asobo. As you've seen update V1.0.2 is now live. Changelog is as follows. Core Installer (v1.0.2): Fixed compatibility issue with the FS Traffic In-Game Menu causing CTDs with other third-party in-game panels (a very big thank you to Fabio at FlightControlReplay for helping us discover and fix this issue). Added an alternative way to set your destination airport in the Traffic Control Centre (this will serve as a workaround should any additional conflicts arise and will serve as a workaround for VR users who may not be able to access the MSFS toolbar). Fixed an issue where the FS Traffic module would crash when changing aircraft and/or liveries in the MSFS Main Menu, preventing aircraft from generating at the departure and arrival airports. Fixed an issue where the FS Traffic module data would not be correctly reset between flights if the user was particularly quick in navigating through various MSFS menus. Various changes to default settings in an attempt to reduce the likelihood of traffic generating invisible at the departure airport. -Fixed unhandled exception error in the Traffic Control Centre when trying to add a new route that already exists. Traffic Fleet Installer (v1.0.1): No changes from previous build (no uninstall/reinstall required) Thank you all John - Just Flight.
×
×
  • Create New...