If you use FS HUD, does the traffic it generates use FSLTL aircraft, if it is installed, or does it only use AIG aircraft? 

6 minutes ago, Bobsk8 said:

If you use FS HUD, does the traffic it generates use FSLTL aircraft, if it is installed, or does it only use AIG aircraft? 

Either/or

Both are options as well as default traffic if anyone was still using that... 

i am using AIG liveries  with fsltl injector (if i fly in real time) or aigtraffic injector (if i fly in custom time)

1 hour ago, motishow said:

i am using AIG liveries  with fsltl injector (if i fly in real time) or aigtraffic injector (if i fly in custom time)

No need to use FSLTL/AIG injectors with FSHud, because it injects the traffic itself.

5 hours ago, Bobsk8 said:

If you use FS HUD, does the traffic it generates use FSLTL aircraft, if it is installed, or does it only use AIG aircraft? 

I did for a short time and quit as I did not like the audio portion of the show and went back to BATC.  Yes, it does use FSLTL aircraft which is what I used w/ it.

 

8 hours ago, Ohmsquare said:

No need to use FSLTL/AIG injectors with FSHud, because it injects the traffic itself.

There are currently 3 ways of using AIG traffic flight plans with FSHud: 1) Don't run AIG TC, Use FSHud traffic options: Sim Traffic Ignore or Remove and AIG option checked. 2) Run AIG TC (Beta) without FSHUD option, FSHud traffic options: Sim traffic Enable, AIG option unchecked. 3) Run AIG TC (Beta) with FSHud option, FSHud traffic options: Sim traffic Ignore or Remove, AIG option unchecked and External option checked. There are adavantages and disadvantages with each: 1) FSHud totally in control of the traffic injected, including the amount of traffic, and is very efficient, but it suffers from the problem that only traffic associated with nearby airports are injected (and remembered for future), so the amount of enroute traffic is limited. 2) AIG TC can inject more traffic than option 1) including enroute traffic, but sometimes that is more than FSHud would like, so there's an overhead where TC injects traffic and FSHud simply removes it without re-injecting it. Also, there's a strange problem, something to do with the re-injecting I think, where traffic is temporarily injected at the user aircraft location, before being moved to its correct location. This has the unfortunate side-effect that it can invoke TCAS RAs as the other aircraft is so close. 3) AIG TC will still inject more traffic than 1), including enroute traffic, but it's unable to overwhelm FSHud, because it's using the API which will ignore any traffic it can't cope with, without the overhead of it being injected and removed from the Sim. However, currently the injected traffic is identified by tail number, not Airline and flight number. I don't know if there are any other disadvantages as this is a stopper for me and I use option 2). Apparently the next version of AIG TC will resolve this

Interesting, I didn't know there were multiple options. I think I'll stick with option No. 1 for now, at least until the option No. 3 is fixed and then maybe I will try that one. Thanks.

Now option 3 is fixed with the actual update

Which update? Experimental branch?

I prefer option 3 as well because you also get all BJ and GA traffic from AIG, which is a nice addition over BATC e.g. 

5 hours ago, motishow said:

There are currently 3 ways of using AIG ... etc.

Thanks @motishow. Note that I wrote that months ago. The situation is slightly different now, as using the AIG injector FSHud option, and selecting Simulator traffic - Enabled in the FSHud traffic options panel has improved somewhat over time (Option 3). Have you tried the latest AIG TC to confirm the callsigns are now all correct? I haven't had chance to try it myself but if they are then this will be the option I will use exclusively as it gives better enroute traffic than the in-built AIG option.

7 hours ago, motishow said:

There are currently 3 ways of using AIG traffic flight plans with FSHud:

1) Don't run AIG TC, Use FSHud traffic options: Sim Traffic Ignore or Remove and AIG option checked.

2) Run AIG TC (Beta) without FSHUD option, FSHud traffic options: Sim traffic Enable, AIG option unchecked.

3) Run AIG TC (Beta) with FSHud option, FSHud traffic options: Sim traffic Ignore or Remove, AIG option unchecked and External option checked. 

Thanks for the information. I added some spacing to make this clearer. I wasn't aware of the other two ways of using FSHud; only the first one, but I was never satisfied with the performance. Which one have you found to be the lightest one in FPS?

I haven't done any tests (I'm not too concerned with FPS), but the first one should have the best performance. FSHud is totally in control, there is no AIG TC running to steal CPU, etc.

Option 2 probably has the worst impact on performance. Since AIG TC injects more traffic than FSHud will accept, FSHud therefore tends to drop some aircraft and AIG attempts to re-inject it next cycle. This can happen over and over, so wasting resources.

Option 3 is probably the mid-point. AIG TC is running, so it's taking CPU, but once it uses the FSHud API to inject traffic is should not try again.

Again, this is theoretical as I haven't tested, so YMMV.

12 hours ago, motishow said:

There are currently 3 ways of using AIG traffic flight plans with FSHud: 1) Don't run AIG TC, Use FSHud traffic options: Sim Traffic Ignore or Remove and AIG option checked. 2) Run AIG TC (Beta) without FSHUD option, FSHud traffic options: Sim traffic Enable, AIG option unchecked. 3) Run AIG TC (Beta) with FSHud option, FSHud traffic options: Sim traffic Ignore or Remove, AIG option unchecked and External option checked. There are adavantages and disadvantages with each: 1) FSHud totally in control of the traffic injected, including the amount of traffic, and is very efficient, but it suffers from the problem that only traffic associated with nearby airports are injected (and remembered for future), so the amount of enroute traffic is limited. 2) AIG TC can inject more traffic than option 1) including enroute traffic, but sometimes that is more than FSHud would like, so there's an overhead where TC injects traffic and FSHud simply removes it without re-injecting it. Also, there's a strange problem, something to do with the re-injecting I think, where traffic is temporarily injected at the user aircraft location, before being moved to its correct location. This has the unfortunate side-effect that it can invoke TCAS RAs as the other aircraft is so close. 3) AIG TC will still inject more traffic than 1), including enroute traffic, but it's unable to overwhelm FSHud, because it's using the API which will ignore any traffic it can't cope with, without the overhead of it being injected and removed from the Sim. However, currently the injected traffic is identified by tail number, not Airline and flight number. I don't know if there are any other disadvantages as this is a stopper for me and I use option 2). Apparently the next version of AIG TC will resolve this

3 is not working for me, everything is set as you mention, but nothing is been injected.

2 hours ago, SN737 said:

3 is not working for me, everything is set as you mention, but nothing is been injected.

Hi,

just finished a flight and can confirm option 3 was working fine for me. Just to confirm that you have the FSHud option ticked in the aig traffic manager and FSHud traffic options set to external and sim traffic removed? Also I can confirm that traffic was being identified by call sign and not tail number.

hope this helps in some way

Steve

1 hour ago, egntpilot said:

Hi,

just finished a flight and can confirm option 3 was working fine for me. Just to confirm that you have the FSHud option ticked in the aig traffic manager and FSHud traffic options set to external and sim traffic removed? Also I can confirm that traffic was being identified by call sign and not tail number.

hope this helps in some way

Steve

Can I ask on a slightly unrelated but somewhat related topic if AIGTC has become more stable?  Prior to using FSHUD injection of AIG without AIGTC I had to run a "restart on crash" program just for AIGTC as it would shut down on its own multiple times over a long haul flight.  

I may consider option 3 if AIGTC is more stable.  

Does traffic still get the FSHUD hold short/ cross runway, hold taxi commands etc?  

Thank you.