PAZFLOR31

I hope you are not talking about me guys, since I'm the one who started this post...😂 First time ever that I post on something. Sounds like there is a lot of paranoia going on around here. Must be exhausting, so much suspicion... By the way, FSHUD, you forgot my paycheck this month

What does he say? I have him on my "ignore" list since his very first comment on my post 😂😂 You should do the same.

The arrival at CYHZ was boringly perfect as far as ATC (FSHUD meaning) is concerned. I guess that's the end of my post, for now. FSHUD 1.3.103 beta (and further devs) it is. Good job FSHUD

Another tryout flight with my newly acquired 739ER (A330 is taking too long to come out to the market, and I am not too much a a patient guy😄), All settings Ultra . Anyway, EGLL to CYHZ. Heathrow absolutely packed with traffic, long queue for take off, communication incredibly dense, but no hiccups as far as FSHUD (1.3.103 beta may I remind) is involved. Perfectly real time comms on the ground and airborn. Step climb impeccable: Initial FL60 as per restriction, then FL210 and eventually FL300 which was my filed CRZ level. I am now at FL340 above the ocean. ETA in 3 hours. I'll tune back in after my arrival. So far so good😉

New trial flight with Fenix A320, FSLTL, FSHUD, payware addons at departure and arrival. The flight was: LFPG 09R LGL5G LGL A5 NTS R14 NORMI A5 XAMAX XAMA9A LPPT 02 LFPG was nicely populated with both static and active aircrafts. Taxi when well (no runway crossings though, so unable to check), ATC followed me without a hitch Take off clearance went well. Step climb through FL190, FL210 to my Cruise level 360 went well. Cruise boringly ok. Received my expected arrival 30 NM before TOD, which is really a nice touch from FSHUD. Upon announcing my readiness for descent I was requested to descend to FL140. Shortly after being cleared for the STAR, Center transferred me to approach. Approach made me descend to 4000' as per STAR altitude restriction, and finally I caught the ILS LOC, my copilot announced "Established on localizer" Got my clearance to land with the required wind parameters, and here I am at Gate 107 with GSX having taken care of logistics, stretching my legs after an absolutely perfect FSHUD-1.3.103 beta monitored flight. 10 over 10. My flight within Argentina, the other day, went equally as smooth. Only my previously flight in Oceania area was like a travel in the twilight zone. So I guess that there must be some mapping (?) issues in some areas of the planet. I would say that FSHUD is really onto something good. I'll stick to it.

Well at least now I can be sure that FSHUD picked on my post😂😂

I am glad that you are so happy. Good for you. As you may have have noticed through going all the reviews about ATC addons (I'm sure you have), what each person looks for in an ATC add on may differ quite significantly from one to another. So this is very subjective and what you find bad may seem good to another and vice versa. Now I confirm that FSHUD is indeed the ATC addon that satisfies me the most (considering my own expectations), and I bought them all since the very first one got on the market. As for the the listing of problems, you may notice that far from winning and or complaining, I simply list the occurrences as I experience them, the goal being that FSHUD may pick on my post (and hopefully other's) in order to see and understand what needs to be improved. Have a good life

Ok since I get no feedback on simforums, I keep posting here. The the mystery deepens and diversifies🤣 So, I re-flew my YSSY-WAJJ but with less resources hungry plane, namely the Fenix 320. I did by night to avoid to much traffic and with significantly reduced Graphics settings. Just to see the difference. Here is my Flight plan, because further down it will help visualize some issue: YSSY RIC5 RIC H76 NBR H105 SULMI Q165 TL V153 CS A216 KIBAV H782 IKERU H667 DOTUB B456 VANKA VANK2B WAJJ The part that I will be looking at is the H76 one between RUTOS and OVMIN. But let's not get ahead our ourselves, and let's go back to earth to taxi. The one thing that repeated itself was the delay in the runway crossing clearances. Only this time I did a huge detour that avoided me crossing 07/25 (got lost actually🤪) and only crossed 34L/16R. The clearance came, like in the previous flight (See above), very long time after. And not only did I get cleared to cross 34L/16R, but also 07/25 which I never crossed... Bizarre, bizarre. what did not repeat itself on the ground, was the take off clearance. I got it right upon lining up. Then, the issue which I will simply quote from my previous post repeated itself identically: But now that I was more in a monitoring mood here's what I found: Well, at the exact same position, at the exact same altitude the exact same thing happened. During the H76 segment, at RUTOS I am told to contact BRISBAN center on 135.50. My copilot reads back sets the frequency and then says nothing. So I start nosing around, and although I find out the Brisbane center is actually on 135.50, I also find that on the FSHUD menu, I am tuned to the correct frequency but it is Richmon Tower. Ole! As the Spanish would say. So what happened? What happened is that I got transferred to Brisbane center at a 60 miles before reaching the Brisbane FIR. So what did my copilot do, he didn't want to speak to Richmond and kept to himself for about 12 minutes until the frequency was the Brisbane's one, right after passing OVMIN. When he called, he gave the information that was valid when we got transferred, that is to say that we were crossing FL230 for FL320, when we had already reached 320 minutes ago. Just exactly as in the previous flight. So here there is a Controlled spaces frequencies issues... All right, so I am going to interrupt my flight now and try in another area of the world, see what happens. When I see all the little bugs that can hide in programs, not to mention when many programs talk to, and influence each other, I pity the one who has to chase the word not allowed throughout Kilometers of programming lines. What a Headache it must be. Onto the next flight, which I hope will be near perfect.

Ho. There is a beta forum? Stupid me! Where can I find it?

So, here comes another flight using FSHUD 1.3.103, and some odd issues coming up which I do not understand where they come from. The flight is YSSY-WAJJ, using PMDG 737. Initially, after having started the flight, FSHUD and FSLTL, I left the computer for an hour. When I came back to start with the flight I found the airport VERY nicely populated. A few seconds after initiating taxi, I am requested to hold position, because, indeed, there was a traffic about to cross my path. Nice. This traffic was heading towards Rwy 25, and God, when I looked to my left,... poor him, he must have been nber 15 in the queue to take off. Luckily, I had chosen 34L just to have a nice long runway for my fully loaded plane. Anyway, and that's where the twillight zone effect starts, when the traffic moves out of my way, I patiently wait for GRD to tell me to resume taxi. Nothing. 30 seconds more and still nothing. So I decide to resume taxi on my own, and a few seconds later the controller, who was probably taking a nap, allows me to. On my way to Rwy 34L I have to cross 07/25 and the 34L/16R. As I arrive at the first crossing I stop, hoping to hear GRD telling me to contact TWR for the crossing. Controller is having another nap obviously, so I decide to cross anyway, not after having checked for traffic on that very busy runway. After I cross, I expect the controller to wake up too late again, but no. So I keep taxiing until I arrive at the second crossing. The controller is now deeply sleeping and so I cross again without clearance. At about 200m from the 34L hold point, I am requested by GRD to communicate with TOWER. A bit early this time, I am thinking, but no. I am just being cleared by TWR for my First crossing (Rwy25). A few seconds later almost at the hold point, same again, I am cleared for my second crossing which is half a minute behind me. When I arrive at the hold point for my take off at 34L, this time right on time I am requested to communicate with TWR. I declare ready for take off. "Line up and wait". So I do, and then, again nothing. I wait, because my runway crosses the 25 and we wouldn't want to kill so many virtual passengers. After a minute I think that, maybe, the program doesn't see me in the proper position so I move forward a few meters and,... zilch. Another few meters. Nothing. Luckily I had chosen a looooong runway. Eventually I decide to proceed with my take-off and at about 80 knots, I receive the clearance. What a relief, I won't loose my license just yet. But this is not where the weirdness stops. As I fly my SID and am about to reach FL200, which I was initially cleared for, I am instructed to climb to my CRZ Level of 320, so I keep climbing. At about 30000' I check what my optimal cruise level would be and it's 360. So I am about to request this new flight level, but FSHUD menu only offers the option to cancel my flight?! No cruise level change option... odd. Ok, I think maybe I have to wait to reach 320 for the FSHUD to offer me further climb, and soon enough I reach it. No change in the menu. This goes on for a couple of minutes, and then out the blue I hear my copilot communicating with the tower and stating that we are crossing FL230 for FL320!!!!! We had been at FL320 for a couple of minutes already... TWR with a very british cool attitude responds: maintain FL320. And just after that the FSHUD menu wakes up and offers the change of flight level. So, what was all that? Looks like, exept for altitude, the delays in reading my actual position have been piling up somehow. But why was my arrival at the hold point immediatly reacted to? Was it the amount of traffic at the airport? The amount of communications was low enough not conclude it. Is it my computer? I use a decent MSI gp76 Leopard laptop with RTX 3070 (I must say when MSFS in running, I could cook an egg on top of it, but it runs smoothly). Is it an issue with FSHUD or between FSHUD and FSLTL? As far as I am concerned, with my total absence of computation knowledge, "Mystere et boule gomme" as they say in France. Something isn't right though...

In previous version of FSHUD my initial climb clearance was never higher than 2 or 3000 feet AGL, which was a bit annoying. This time with beta, it cleared me to FL210, which is a lot more confortable. As for the approach, I received the expected arrival and approach infos well ahead of TOD, which comes very handy and the arrival and approach process was handled by ATC both realistically and practically. Good job FSHUD. If this is only beta, I can't wait for stable. As for the gentleman who spoke about my account dating from 2012, the only answer that occurs to me is: Ok,so?

First time ever that I bother sharing my humble opinion about anything related to FS. I am, as I write performing a flight (SAWH-SAZS), using FSHUD 1.3103 beta version, FSLTL and the unavoidable A320 Fenix, and so far, it's a charm. On ground comms with AI work totally fine. I have seen a few complaints about voices on the forum. Well, indeed some of them do not sound like you and me, but I sense the FSHUD is exploring new options and that the ones that they will choose to keep in the future will be fine tuned later on. So, Bravo, keep up the good job and don't mind the chronically unsatisfied who just need attention. The background noise options work fine for me, especially for my copilot who now sound like he is in the cabin (zero background noise) and not a few miles away talking through a radio. That's nice. So far FSHUD has impressed me and satisfied my (very own) expectations of what a nice ATC could be. As for total immersion, well there are flight schools for those who do not realize that flying a PC is not flying a plane. I am 1h away from TOD. Let's see what comes next.