Please give us some info and best practice about destination
-
Hello all,
I want to like this product but I'm frustrated to say it the least.
To me it's a game of luck to get traffic at the departure airport (3 times out of 5 no traffic at all - sim fresh restarted every time!).
But it needs even more luck to get traffic at your destination!!So please can the developers and the successful beta-testers give us users and buyers some infos, hints and best practices about traffic at the destination airport?
- when (distance, time before landing ...) approx. is traffic at the destination injected? And recognizable in, for example littlenavmap?
- when do flights at destination start to depart (approx.)?
- min/max distance between departure and destination?
- min/max flighttime between departure and destination?
- min/max distance to change your destination in cruise?
- min/max flighttime to change your destination in cruise?
- best moment to put in and confirm destination (before takeoff, during cruise, before landing etc.)?
- what happens if I change my destination very often during a low level scenery cruise with my ga-plane?
- what happens when you accelerate the sim-time (2,4,8)? Good or bad idea?
- is it a good or a very bad idea to pause the sim to check some of your (control, graphics etc.) options during a flight?
- how can you check if the module is still operative?
- what are the best option settings to have decent arriving and departing(!!) traffic at your destination (best before my arrival!)?
Yes, I know the manual and the FAQs and No I don't open a support ticket, since this are just a few questions.
Thank you and regards, Stefan
-
@steve67 said in Please give us some info and best practice about destination:
Hello all,
I want to like this product but I'm frustrated to say it the least.
To me it's a game of luck to get traffic at the departure airport (3 times out of 5 no traffic at all - sim fresh restarted every time!).
But it needs even more luck to get traffic at your destination!!So please can the developers and the successful beta-testers give us users and buyers some infos, hints and best practices about traffic at the destination airport?
- when (distance, time before landing ...) approx. is traffic at the destination injected? And recognizable in, for example littlenavmap?
- when do flights at destination start to depart (approx.)?
- min/max distance between departure and destination?
- min/max flighttime between departure and destination?
- min/max distance to change your destination in cruise?
- min/max flighttime to change your destination in cruise?
- best moment to put in and confirm destination (before takeoff, during cruise, before landing etc.)?
- what happens if I change my destination very often during a low level scenery cruise with my ga-plane?
- what happens when you accelerate the sim-time (2,4,8)? Good or bad idea?
- is it a good or a very bad idea to pause the sim to check some of your (control, graphics etc.) options during a flight?
- how can you check if the module is still operative?
- what are the best option settings to have decent arriving and departing(!!) traffic at your destination (best before my arrival!)?
Yes, I know the manual and the FAQs and No I don't open a support ticket, since this are just a few questions.
Thank you and regards, Stefan
Hi Stefan
Some useful questions and we will try and get back to you asap. Question - are you using anything like GSX to add ground objects or similar?
-
@derek Hi Derek, yes I use GSX Pro. I already reduced the ground clutter and tweeked the ground options in fs traffic. I'm able to get decent traffic on bigger addon-airports during departure, like on LatinVFRs KMIA, FlyTampa KBOS or Simflight EDDM and others.
It's just I'm uncertain about my practice with the destination. If I could understand the things under the hood better, then I would maybe use the product in a better way.
-
-
-
@steve67 I've done flights as short as 30 minutes and as long as 5 hours. I've yet to see any difference - both resulted in no traffic being generated past the departure airport. In theory I believe the 120 minute departure setting would effect how far out the schedule is reaching to load planes. But I've swapped those numbers all over the board to no effect.
-
@qazme Thank you for your infos! This exactly what I'm looking for. I've done my flights with 60min departure setting. I disabled GSX. Did a short flight last night from KFLL to KMIA with the Turbo Arrow. Traffic (departures and arrivals) at departure, no traffic at all at destination.
Maybe with 60min departure time my time of flight and time before flight was to short to spawn traffic...
I don't know, maybe you have to set a small departure time setting to get traffic at destination?That's why I wanted to have some of my questions answered!
I can not imagine/understand how this software passed the beta-test...
-
-
@steve67 said in Please give us some info and best practice about destination:
@qazme Thank you for your infos! This exactly what I'm looking for. I've done my flights with 60min departure setting. I disabled GSX. Did a short flight last night from KFLL to KMIA with the Turbo Arrow. Traffic (departures and arrivals) at departure, no traffic at all at destination.
Maybe with 60min departure time my time of flight and time before flight was to short to spawn traffic...
I don't know, maybe you have to set a small departure time setting to get traffic at destination?That's why I wanted to have some of my questions answered!
I can not imagine/understand how this software passed the beta-test...
I can confirm that I have flown multiple flights from/to Dublin from/to Liverpool and Manchester using FS Traffic, which are roughly 50/60 min flights and have my time before departure set to 90mins and always seem to get a decent amount of traffic at dep and arr airports. Clearly the higher you set this number the more traffic you will see. I did a test of setting it to almost 4 hours and got loads of traffic at Dublin (too much, in fact, where it started to affect performance).
Ironically I don't have an issue with traffic generation now, it's more that the schedules seem off by half an hour to an hour most of the time. Once this is fixed I think I will be pretty happy.
-
The update is now out and should address many of the reasons you are not seeing destination traffic.
@steve67 In your case you are likely not seeing any traffic at your destination using the turbo arrow because currently there is a requirement that you pass 250knots at 5,000ft to activate the processing of the flightplans. When our attention turns to GA we'll look at changing this.
@balzbac Currently we recommend starting a new flight in between legs. Something we will be taking a look at soon.
John - Just Flight
-
@jf-john said in Please give us some info and best practice about destination:
The update is now out and should address many of the reasons you are not seeing destination traffic.
Thank you for the info. Sadly I have no time this weekend to update and check, but I will ASAP!
... currently there is a requirement that you pass 250knots at 5,000ft to activate the processing of the flightplans. When our attention turns to GA we'll look at changing this.
Ah, this answers some of my questions and confirms some of my impressions.
Probably I was just to slow and low on some of my short test-flights (even with the 737)! I should have known this before ;-)
I will tests this. Thx! -
@steve67 No problem. It was done for performance reasons. Basically the sim has to process a tonne of flight plan data and we thought it would be best to do it away from any dense scenery to avoid stutters. We will be seeing if we can make this less restrictive though.
John - Just Flight
-
@jf-john said in Please give us some info and best practice about destination:
When our attention turns to GA we'll look at changing this.
And of course do we want to see traffic at our destination in GA-planes and helicopters! ;-)
Why shouldn't we?!Basically the sim has to process a tonne of flight plan data and we thought it would be best to do it away from any dense scenery to avoid stutters.
Understand. I just like to have more infos like this to better understand the philosophy behind all this and to better understand and expect whats going on and what not.
-
I did a again a very short tesflight today with the update.
Started in KMIA with traffic, in- and outbound. Very nice.
After 20Min. I took off to a short flight to KFLL. I flew 260Kts and was above 6000ft. Arrived at KFLL with only ONE aircraft waiting for me!!!
C'mon guys!!! Please answer my questions in the first post. I don't get your philosophy about the destination!
Are my flights to short? Or what is my/the problem?I'm frustrated and disapointed and back to FSLTL for the next couple of weeks unitl there is a best practice, "Dos and Don'ts" and fixes.
Sorry, I just want to have fun and this definetly isn't (for me)! :-( -
@jf-john said in Please give us some info and best practice about destination:
@steve67 In your case you are likely not seeing any traffic at your destination using the turbo arrow because currently there is a requirement that you pass 250knots at 5,000ft to activate the processing of the flightplans. When our attention turns to GA we'll look at changing this.
You do realise that people who fly smaller aircraft will buy your software because they too want to see planes coming and going from their departure and arrival airports?
There is nothing in the requirements for the software that says anything about needing to exceed 250 knots and 5000 feet to activate flight plans either.
Why not lower it now to something more attainable, say 1000 feet and 80 knots? At least then people flying GA and VFR who also paid for the software see some traffic.
-
However. No traffic on most flights on arrival. No matter if i fly 30000 feet, 250kts or whatever. Most of the time...the destination airport is empty. Today it was KLAX, coming in with the PMDG 737. Only 2 or 3 planes in the sky....over the westcoast. FS Traffic is still in BETA. I remember hight quality software form JF.
-
Yes, the application has a lot of potential and is easy to install and use, but there are too many factors to take into account that make the experience not a very good one in most cases.
I understand that the simulator has many limitations that limit developers a lot, but other developers have worked around some of them with imagination, getting a better experience, so it is possible to improve the software.
Waiting for the next update and see what the great developers of Just Flight can surprise us with.
-
Indeed. I am looking forward to the next update.
My main complaints are:
- Lack of AI traffic enroute (always nil for me)
- Destination airports frequently empty
- Phonetic pronunciation of callsigns for AI aircraft.
Other than that I think FS Traffic is great. I know JF are working on these issues, so hopefully we’ll see the fixes soon. 👍
-
@cbcdesign We are looking at bringing this requirement down.
Perhaps I should explain why this was done in the first place, I can imagine its baffling without any info.Basically it all boils down to performance. The in-sim module has to process the flight plans for the destination traffic. This does have some overhead and can introduce stutters if its done in an area with dense scenery, close to the ground and close to the airport. We don't deny that in current form FS Traffic is aimed at commercial airline flying. We do need to change this as we think about GA in the future and were also becoming more comfortable with what we can and can't get away with in terms of performance.
What the above all boils down to is that we are currently working on revamping the whole system.
John - Just Flight.
