BProduction222

I saw the PTT feature and read the manuals as well, but couldn't find a detailed description of how to assign Joystick Buttons. But I will check out the link you posted earlier. Looking forward to what is in store next.

Thank you for the Information and am looking forward to the update. No need for proof or a test, I can handle it as long as I know something is being done about it. Appreciate the community interaction!

With 1.7 of UGCX, you introduced the Feature where when you select the route that the Pushback Truck should take, you are sent to a Birds eye view and see the Airport and Aircraft too. However the issue is, when flying back and you want to use User Defined Pushback again, the Camera will then Spawn back to where I came from earlier. Example: I flew from Oslo to Dublin. When I departed Oslo and asked for pushback, the outside view was shown. Which is fine. But then when I arived to fly back to Oslo from Dublin, and chose to select User defined Pushback again, then the camera will spawn back at Oslo, Instead of Dublin, where I am actually at. My question was if there was a way to disable this External Camera feature, because it is nice, But I don't really want nor need it. Kind Reagrds Ben Roppoli

Hello, First of all, I am a huge fan of the product and been an owner since day one! Keep up the great work. I also use FS2Crew for all of my Flights if available and can't wait for the CRJ Pro Variant. Either way, I wanted to ask for some help. Either I am doing something wrong or there is a bug in the product. The issue is that whenever I speak using FS2Crew or just in general, UGCX picks everything up, and responds when it thinks I am saying the phraseology it is expecting. To have a better understanding, I make YT videos and sometimes I talk about the flight or whatever I am doing with the Aircraft, and UGCX will think I am saying "Ground From Cockpit" to which it always responds of course and this is annoying. I was hoping to set up Soft Mute, but when using Propeller Sync, it won't work. Not sure why. I tried reinstalling UGCX as well and also tried running a aircraft without FS2Crew. So with this issue, I hope there is a solution to, and if not, I would have a feature recommendation. The Recommendation: As soon as you cleared the Ground Crew to Disconnect and go to Hand signals, UGCX will then disable all voice recognition until requesting something new from the Menu. I hope there is a solution to this. Kind Regards Ben Roppoli

1. I just used the latest beta and tested it, however the issue that I hoped to have changed, isn't 100% perfect yet. After the PM said he is conducting the APU fire test, it took another 8-10 seconds before the APU Aural indication was audible (because the Aircraft isn't just yet powered up completely). I know this because as soon as he said this. I held down the test button and counted up. Perhaps add another 10 seconds to the flow before he does the APU fire test, to wich he can immediately continue with his other Preliminary flows. I would also recommend this extra 70 seconds delay before testing the APU Fire system should only be implemented when the user has the 'USER STARTS APU (PRE-FLIGHT)' set to YES. 2. When the config option 'SKIP EXTERIOR INSPECTION' is set to YES, then when you start the PF Flows, it should start at 30 Minutes instead of 35. With kind regards, Ben

That's awesome! I'm glad I could help. Well, normally you only do an APU FIre test on the First Flight of the day or on a Crew change, so I would say on the FIrst Flight of the Day or crew change, you would want to do it properly, even if it means waiting a Minute. However, I do understand that every Airline does it differently to either save time or other reasons. In a proper Turnaround State, you wouldn't test it again anyways, which will save the airline some time. Either way, looking forward to future updates. Ben.

Hello, What a great product fused with another great product. Ever since development was announced, I followed the threads and Store closely. 1st Impressions: Awesome!!! But if there is one thing I would complain about, is the Preliminary Cockpit Procedure timing is a bit off. To be exact, as soon as the PM turns on the GPU, he conducts the APU fire test and resumes his flows before all systems are booted up. I would hope to see the PM wait until all systems are booted up, until he continues with the APU Fire test and so On. Otherwise he doesn't hear the Aural Indications part of the Procedure. I don't think anyone would change FSLabs default settings of 40 seconds until the Self Tests are conducted, however usually all systems are booted up about 90 Seconds after AC Power is established, which would be a good time for the PM to then do the APU Fire test and the rest of the Preliminary Flows. Otherwise I have nothing. If I do find something, I'll be happy to report. With Kind Regards, Ben