ConstVoid

1 hour ago, Ron Lefebvre said:

I am confused. Once again. 🙂

It says here not to used the controller with FSHUD with AIG.

https://www.fshud.com/#/site/knowledge/traffic-settings

Start video at 4:53

You guys seem to indicate that you should load it.

 

 

 

You do not use the AIG TC with FSHud. FSHud injects and controls the AI aircraft, based on AIG flight plans. If you do start TC while FSHud is active MSFS will control the aircraft and FSHud will know nothing about them. The only problem I've noticed is that the number of aircraft injected by FSHud is much less that AIG TC knows about, and it doesn't include many en-route aircraft, only traffic originating or terminating at airports close to the user.

2 hours ago, simmerluke said:

I will see if I can give this some further testing over the coming days, but am wondering if it might have something to do with the Airbus TCA quadrant with the autobrake switch still set to an 'on' position until physically moved to 'off'? (with the PMDG 737 I don't map the autobrake switch)

Indeed that will be the problem. I don't know why Thrustmaster decided to use a rotary for that function - do any Airbuses use a rotary for autobrake?

Edit: Checked the actual assignments - I really shouldn't try to do this from memory.

I have mine mapped as follows:

Button24 - set autobrake med

Button23 - set autobrake lo

Button26 - set autobrake hi

This way if the rotary is moved to LO you get low autobrake and then you immediately move it back to BTV (which isn't assigned to anything) - this does not 'unset' the autobrake, just makes it so that it will be released when you commence manual braking.

Similarly to get medium autobrake you move it to 2 then 3, and to get autobrake max you move it to HI then 3.

I've been running like this since I first got the Thrustmaster and it always releases normally as soon as I hit the toe brakes.

You need the models/liveries from one of the products to be installed so that FSHud can use them. For FSLTL you run their injector, which 'talks' to FSHud to do the actual injection. With AIG FSHud reads the AIG plans and injects the traffic itself. In some respects it would be better if the AIG TC talked to FSHud in the same way as FSLTL so that we could benefit from the new features like dynamic GA traffic, but alas that's not the case.

The direction for pushback is not currently given, although I think I've seen it stated that it's on the roadmap somewhere.

There are still one or two bugs where AI traffic and the user might be directed to different ends of the same runway, possibly in variable wind conditions, but usually the separation logic handles that fairly well. I think this will improve more in the near future. 

The inability for 3rd party products to access MSFS weather data will be even more of a hindrance with 24 hr historical weather. Products like ATC add-ons and flight planners need access to the same weather that MSFS is depicting. At the moment it's not too bad because they access the current live weather from other sources, which are approximately the same as MSFS data. With MSFS 2024 I reckon that even if they can get hold of historical data from somewhere there will be more room for differences between their data and MSFS data.

I hope that 3rd party developers do not take view that the best way to match up the data is to only support ASFS for historical weather.

30 minutes ago, pete_auau said:

edit he  was  referring  to  if  you want  the  premium  packs  is  where  you have  to top up  every  month

 

Almost - it's my understanding that you only need to top up if/when your credit runs out.

10 minutes ago, techman said:

Take into account that the FSHud Load-Balancing-Thingie doesnt know about Frame generation, so either turn it off or double the frames in the balancer to have a similar result to NOT using Frame generation. I just tested it and it was a huge difference (just sit on a crowded airfield like EDDF or EGLL to test it).

That seems to be true of anything which limits the FPS. For example I use MSFS options to limit FPS to 30 (I know some of you who love high FPS won't be able to understand this 😀) and the default for the performance limiter of FSHud is also 30, so I have dropped the limiter to much lower and I appear to get more traffic.

I haven't had chance to test this new version yet, but if I encounter any major problems I will raise a ticket so that the developer gets the appropriate logs and has a chance of fixing the problem. Without logs there is next to no chance that it can be fixed.

16 hours ago, motishow said:

when a non robotic voices?

As an FSHud user myself, the most disappointing thing about that video was the voices - I don't know what the reviewer had done, maybe turn the 'radio effect' way up beyond normal, but I have to say I find FSHud's voices, while currently very limited in number, sound very good with only slight 'radio effect' selected.

44 minutes ago, El Diablito said:

My problem is disconnecting it manually, I'm still getting the Red warning on the ECAM with the loud warning despite trying several configs on my TCA and also trying what Bob mentioned (double click on disconnect).

The button on your stick must be set to 'AUTOPILOT OFF', not any other function. If that is done the first press will disconnect the AP and the second will silence the alarm (after a minimum of one cavalry charge I believe),

Are you 100% certain you have no other controller axis assigned to throttle, which might conflict with the one you think you're using? Many people use the Thustmaster stick and throttle quadrant, for example, and the default is for the stick throttle to also be mapped. This leads to the situation where things appear to be calibrated, then all of a sudden the sim starts prioritising the stick throttle over the quadrant and you lose the ability to move the thrust levers via the latter.

On 12/31/2023 at 9:09 PM, BrammyH said:

I don't think the flaps/spoilers have virtual buttons. When I assigned them in SPAD it was always just the full axis.

The throttles do, however. I have used 12 and 16 to set reversers on the PMDG.

Looks like we're both half-right. The speed brake has 5 virtual buttons, but flaps doesn't have any.

On 12/28/2023 at 7:42 PM, cianpars said:

Also, what effect do virtual buttons have?  I did Google it but am still none the wiser.

I don't see any response concerning this part of the question, so I'll try. You can assign virtual buttons which the quadrant will 'press' when the flaps and speed brake levers of the add-on pack are set to certain positions. As far as I'm aware this is a little-used facility, as the Fenix, and I assume other Airbuses in MSFS, tend to read the position of the lever axis to determine which flap/speed brake setting you require. If an aircraft used buttons instead to select brakes or flaps, then you could use virtual buttons to translate the position of your quadrant lever to a particular button press. I've always had virtual buttons disabled.

If you have a problem with the product, as you described in your original post, the most likely way to get it fixed is to submit a support ticket, and give a description of why you think it is not behaving correctly. Support tickets automatically include the relevant logs, which should show the developers exactly what's happening.

The developer has recently been suggesting that actual bugs should only be reported via a ticket, and not via the forums, as the latter does not provide sufficient detail to diagnose the problem.

14 hours ago, rlashier said:

My own peeve - those who use the term “irregardless” when regardless is more than sufficient. 
Rich

Something else that irritates me: On the "Rebuild Rescue" YouTube channel they're always saying something "needs fixed" !?! 

It either "needs to be fixed" or it "needs fixing".

4 hours ago, JetCat said:

Awesome this photo is so retro but also disturbing at the same time 😄 Are these really from 1990? But the compact laser disc and the cassette tape and also floppy disks where already invented back in 1990, I think punched cards are more 1950-1971 technology.

This is so off-topic, but I think you might have to update your end date slightly. Cards were still in use after that. At Uni we had a CTL SAT1 operating as an RJE (Remote Job Entry) station until around 1976. This regularly needed to be rebooted from cards, with the card deck being regularly replaced due to it getting worn out.

It's a long-standing 'feature'. I doubt it will be fixed any time soon.

Just to add to the solution by @Farlis that there's also a problem that if you use the right mouse button to pan around it will cause the same issue - the switch will flicker between norm and ign/start. The work around is to use the middle button to allow panning.

Thanks for the explanation Alex.

I'm curious about from where LNM gets its Airport Names.

For example, LNM gives the name "Arlada - Airport" for ESSA, but MSFS lists it (correctly) as "Arlanda, Stockholm" in the world map, and Navigraph charts refers to it as "Stockholm Arlanda" or "Arlanda (Stockholm)". I even tried searching for "Arlada" in the LNM files and MSFS BGLs to try to find out where this incorrect name comes from, but it seems that if the BGLs contain any airport names they don't appear in plain text.

I guess it's not a major problem but it would be nice to have the correct name in LNM, and also if any other airports have similar issues.

On 11/5/2023 at 10:06 PM, mobeans10 said:

Kevin , with FSHud , I believe you have to be an active paricipant in order for the ATC to work, ie you need to file a flight plan. With the current stock ATC,  that is not required and you can dial in a frequency and just eavesdrop passively.  Most times I like to hear the other traffic without actively being controlled by ATC. Will this be possible with Voxatc or do I have to file a flightplan to kick it all off ?

Without wishing to hijack the thread, I just want to point out that it is possible to just listen in to FSHud without taking part - you just need to have it running and at the point where you would load a plan. Obviously it won't be aware of you at all, so there may be conflicts with other traffic.

Now back to VoxATC.

The TCA quadrant gear lever is a simple on-off switch, so it's interpreted by MSFS as a button. It is correct to have it assigned to both 'GEAR UP' and 'GEAR DOWN', but 'GEAR UP' must be 'ON PRESS' and 'GEAR DOWN' must be 'ON RELEASE'. If they are both set to 'ON PRESS' or both to 'ON RELEASE' then confusion will reign.

OK. Not much else I can think of then, apart from ensure that you disarm the speed brake after take-off, and check that you haven't got a random key binding that might affect it.

21 hours ago, AnkH said:

Geez, Gerard is NOT the creator of the video, the creator of the video has a i5 8400 with a GTX 1060...

Indeed, but a natural mistake. All too often YouTube videos of scenery announcements, product reviews etc. are posted here with absolutely no indication of who the original content creator was.

Do you have the speed brake / flaps add-on for the TCA quadrant. If so, and you recalibrated the thrust levers, as suggested, did you also recalibrate the speed brake? This was mentioned in the notes I posted. The full Thrustmaster calibration instructions for the quadrant with add-ons is at TCA_Quadrant-Throttle-addons_Calibration.pdf (thrustmaster.com)

Here are some notes I posted here a few months ago:

It's vital to take this step by step to determine the cause of the problem.

1) Check using the Thrustmaster control panel that each and every button is working, and that the thrust levers (and flaps and speed brake levers if you have them) show smooth and continuous movement across the entire range. If there is any problem at this stage go back and use the Thrustmaster calibration instructions from their website. If you have the flaps/speed brake add-on note there is a more extensive calibration procedure required.

2) Load up MSFS and check in options that the thrust levers are set to throttle 1 axis and throttle 2 axis - not the 0 to 100% variants. Again check that the display shows smooth and continuous movement across the whole range (don't forget to include the reverse position in your test). Sensitivity doesn't particularly matter at this stage as long as the levers show movement across the whole range. Make sure that you have NO OTHER controls bound to a throttle.

3) load up the Fenix and go through the calibration in the MCDU. Note that until you have completed the calibration I don't think you'll see any movement of the levers in the cockpit, but once they are calibrated you should see the movement you expect.

The above process should show you which part is not working properly. If 1 & 2 work but 3 doesn't then I'm afraid it's back to Fenix to diagnose.

The fact that you can't seem to calibrate the reverse thrust settings suggests that you need to go right from step 1 and ensure that during the Thrustmaster calibration you ensure that you pull up the reverse thrust levers and move the thrust levers fully back when setting the minimum values. Otherwise the calibration will only use the idle position as 0% and TOGA as 100%.