Justin.thomas7
Members-
Content Count
15 -
Donations
$0.00 -
Joined
-
Last visited
Community Reputation
1 NeutralProfile Information
-
Gender
Male
Flight Sim Profile
-
Commercial Member
No
-
Online Flight Organization Membership
none
-
Virtual Airlines
No
-
So waiting patiently - recently made the plunge to MSFS with PMDG 737 and uninstalled P3D. Very much missing FS2Crew. Noting the delay is not your fault (waiting for the SDK) - can we at least find out what the big changes will be for the MSFS product? You said they were a secret before.
-
You have had some of these in the 787, but just to make sure: QFA "QANTAS" VOZ "VELOCITY" (Virgin Australia) JST "JETSTAR" RXA "REX" (Regional Express - Australia) ASY "AUSSIE" (Royal Australian Air Force) EVY "ENVOY" (Royal Australian Air Force - 34 Squadron) ANZ "NEW ZEALAND" (Air New Zealand) KIW "KIWI" (Royal New Zealand Air Force)
-
Feature Request - Departure Delays
Justin.thomas7 replied to Justin.thomas7's topic in FS2CREW: QUALITYWINGS 787
It can take 40 minutes to fill a 787 for a long haul flight - so add boarding / deboarding (for some reason GSX won't refuel QW 787 when boarding/deboarding even with an aerobridge). It's not really my point that we need more time, just trying to simulate real life where not every turnaround goes to plan, fuel trucks are busy etc. It makes it more dynamic rather than every turnaround going to script every time - that gets boring very fast. I believe GSX are working on an API so maybe one day your boarding events can fire GSX requests - that would be awesome (unless UGCX expands to replace GSX completely). -
This isn't just for 787 but that's what I'm using at the moment. Is it possible to put a pause button on the preflight screen to stop the counter (and associated events). If I'm using GSX and refuelling is taking longer - or I was late to start boarding etc, it would make it a lot more realistic where I won't have the cabin manager telling me we are ready to go and we haven't even started boarding yet.
-
[30 January 2021] QW 787 V1.4 Released! Change Log
Justin.thomas7 replied to byork's topic in FS2CREW: QUALITYWINGS 787
I have worked out the problem - still a bug but even smaller than originally thought. If you change the voice after preflight has started, the callsign will use the first voice and will not change dynamically - where as the rest of the content changes straight away. Obviously the answer is probably "don't change the voice during a flight" - but if you want perfection - either all of the voice should change or none of it should. I'm not particularly bothered by it now I understand the cause. -
[30 January 2021] QW 787 V1.4 Released! Change Log
Justin.thomas7 replied to byork's topic in FS2CREW: QUALITYWINGS 787
There is a small bug with 1.2 (that didn't happen with 1.1 or 1.0). If you have the Qantas callsign selected, using the UK voice, the voice is UK but when the word Qantas is spoken it reverts to the US voice (just for that word, then returns to UK). If you have the EU voice, it uses the UK voice. The US voice works fine. I tried the American callsign and this didn't happen. I didn't try other callsigns. Edit: I think the bug occurs when you change the language after you start preflight. -
[30 January 2021] QW 787 V1.4 Released! Change Log
Justin.thomas7 replied to byork's topic in FS2CREW: QUALITYWINGS 787
It’s definitely takeoff. Even non-ICAO USA. A departure is an entire procedure (SID, visual departure etc), take off is the act of leaving the runway for the air. Two completely different things. As for landing clearances, this might vary, in my part of the world you contact tower (just callsign) and they will acknowledge with either “cleared to land” or “continue approach” depending on what else is happening. Same for ground when vacating the runway, you don’t ask for taxi clearance, they just give it to you on first contact. -
[30 January 2021] QW 787 V1.4 Released! Change Log
Justin.thomas7 replied to byork's topic in FS2CREW: QUALITYWINGS 787
I really like the ATC clearance features you’ve added. One petty thing to bring up - why did you use the phrases “ready for departure” and “cleared for departure” when it should have been “take off”? Also it would be nice to add landing clearances and taxi to gate as well. -
English accent changes - Buttons
Justin.thomas7 replied to Justin.thomas7's topic in FS2CREW: ULTIMATE GROUND CREW X
Surely it’s easy to get the English accents working together? It adds so much realism having this feature. I note your aircraft products do this. -
English accent changes - Buttons
Justin.thomas7 replied to Justin.thomas7's topic in FS2CREW: ULTIMATE GROUND CREW X
Yes, I have that selected (well it says use regional sound set). My problem is the captains voice also changes. Eg, take off from Sydney, both Australian. Land in London, both British. -
When I first started using UGCX, you could set your voice to a specific accent (eg US, Australian etc) but the ramp agent accent would change depending on what country you are in. I don’t know what I’ve done, or if it was an update, but now both the pilot and the agent accent changes as I move around the world. I want the pilot accent to stick to the one I chose and have the other one change. Have I messed up my configuration or was this feature broken in an update?
-
Any chance of AU voices in the next update? I hear AU ground voices though which is good.
-
Is there any way to modify the sound files to include real world safety briefings? Ie, instead of the standard FS2Crew voice doing the safety briefings, use an uploaded sound file of a real world airline (Qantas, AA etc - you can get them all on youtube). Otherwise, could this be a feature in a future update? It would make FS2crew even more realistic.
-
[2 June 2022] UGCX VERSION 2.6 RELEASED!!!
Justin.thomas7 replied to byork's topic in FS2CREW: ULTIMATE GROUND CREW X
I was having lots of problems with the menu not showing up in v1.2 (ie, click UGCX in the addons menu"), it says "Loading data..," and nothing happens. Sometimes, doing this 3 or 4 times it will finally show up, others it will not show up at all. Was this a known issue, and is it fixed for 1.3?