V.1.0.3 Released
-
@jfoguet61 Thanks, good post and just what I see as well. I don't understand how they could put this out to market, from the installer to the update procedure, it's from the '90s. These updates should be pushed out from the app, I just stumbled across their email that there was an update. Then their process of "Scour our old files from your hard drive yourself and re-install the new application". This is a weak effort and money wasted.
-
What kind of installer ist this. I am working with addonlinker. On install you have no option where you want to install the whole thing. at the end i have to copy 24GB. When it comes to an update, de installing and install everything again is a nightmare on such big files. For now i have to copy all in my own folder. That process ist horrific. 1 Hour.
where i can get refund?
-
Hello,
I made several test flights over the weekend and the outcome is the following regardless of which is departure airport and arrival airport
Departure Airport:
- There is departing Traffic
- There is no arriving traffic
Destination Airport:
- There is few or zero departing traffic
- There is arriving traffic
For example:
LIRF-EBBR
Departing traffic at LIRF; no arriving traffic at LIRF
Few or zero departing traffic at EBBR; arriving traffic at EBBREBBR-LIRF
Departing traffic at EBBR; no arriving traffic at EBBR
Few or zero departing traffic at LIRF; arriving traffic at LIRFPlease note that there are no bugs in the scenery. I check on Little navimap any spawned traffic, so much before it could be canceled by the scenario due to a bug. And also when the same airport is the departing one there are departures and no arrivals, when it is the destination one there are arrivals and few or no departures.
The above mentioned flights are just to mention a couple. I checked also at many other airports such as LICJ, LIME, LIMC, LIML, EDDK, LFPO. The outcome is the same.
Spotting time has always been not less than 40-50 minutes.
Do you have a explanation/resolution for it?
-
I’d be very interested in knowing when JFT spawns in the departing aircraft at our destination airport.
Is it when we spawn in at our departure airport?
Is it when we arrive at our destination?
If the former then does the Time Before Departure value in TCC apply to the arrival airport too?
If, for example, I set my TBDv at 90 minutes, but it takes me 120 minutes to get to my destination, have the departing aircraft at my destination already departed prior to my arrival?
-
@bpfonteyn
Absolutely not. Traffic at arrival is spawned when your destination airport is few miles (around 40) from your aircraft. This is the reason why if you fly a direct approach to runway without a circle to land or overflying the airport area due to your procedure it will be very difficult to find a live airport…since it will take time since spawning. FS traffic team says this is a limitation of MSFS, which it is, but for example FSLTL spawns traffic with a much wider range
-
With respect, how do you know it’s 40 miles out that the departing aircraft spawn at the destination airport?
Many thanks.
-
@bpfonteyn
Very simple. It’s enough you use little navmap during the flight and you can see exactly when and at what distance the traffic is spawned
-
Ah, I was not aware of that. Thank you 👍
-
Hello, Could I please have a feedback from you?
-
@sebastiano148 I’m afraid I don’t without more information. What we really need to do is get hold of your console log. I tested LIME and LIML and had arriving traffic. Have you raised a support ticket at all?
John - Just Flight
