HarryS

Hi, Just a few tweaks required on the PMDG 737NGXu "apu generator connect" both switches move but nothing happens. If done after with mouse clicks they turn on "engine generator on" same as apu generator.

Don't worry about. It's not a great plane and I don't fly it that much. It's good enough especially if there's no SDK. You did a great job on it.

Hi, Been running through the CS B757-200-III PW2040 flows. Was impressed with how MCE handled this one out of the box. "both stab trim cutout switches to normal" doesn't seem to do anything. That's the command out of the box. Maybe there's another command I'm not aware of? William seems to sometimes trip up a bit with setting speed, heading and altitude. Tends to be a long drawn out process and most times he misses the setting by a click or two. I'm guessing this is more to do with developer coding than MCE. Just thought I'd mention it. Not a big problem. As an aside, the developer here seems to have focused more on eye candy than tuning flight characteristics and other key functions. Harry

No problem, I'm not in any hurry. Thanks.

Hi Gerald, I'm working through the Qualitywings Avro RJ-100 A few issues so far: saying transponder tara, standby, etc. does nothing saying "autopilot engage" does nothing saying "lnav and vnav" does nothing

When .wav files are being played, the co-pilot is listening and responds to various words being said by making changes to the aircraft configuration. Any way to turn that off? I'm aware that .wav files can be used to provide co-pilot commands . I don't use that. I give him/her all commands myself, verbally. If I've missed some, please let me know.

Is there a way to adjust the playback volume of .wav files independent of the first officer volume? When I play a sound file, let's say to ask for coffee, the volume is very low. If the same file is played on the desktop through the default player the volume is much higher. I've looked around but didn't see any obvious way to do it, maybe I missed something?

It's a bit odd how those switches are laid out physically but we've got them working. So for me it's good enough.

I appreciate your response, but I'm not sure I got my point across very well. Let me try again. Like most users of the app I'm really only interested in the functions related to the planes I fly. PMDG 737/747/777 QW 787 Aerosoft Airbus 318/319/320/321 Professional TFDi 717 Anytime I or another user of these aircraft report what might be an imperfection as you call it, how do I/we know it's been addressed and that an update is available? In some cases I may need to make changes to one or more voice flow files to include the changes you've made. From what I can see so far you've already covered 99% of what's wanted/needed for the aircraft I fly, and I appreciate that the coding isn't as simple as 1-2-3. I'm not questioning what you do or how you do it. I too have more customers than I can count, and when we make product changes they need to know what they are. In some cases letting them know is more time consuming for us than the time it took to make the actual changes. The only time you'll hear from me is if a certain function doesn't seem to work, like a switch, or I might suggest the addition of a new function.

That's fine Gerald. Thanks. Didn't realize that two of them were backups.

I have reported various aircraft specific voice command issues that needed to be tweaked. I know that most, if not all have been addressed in several recent version updates. The only way I know this is by testing each new version to see if the changes have been made. Some changes when made require me to make changes to my voice flow files. This is a time consuming process that I wouldn't have to do if I knew what changes where made version to version. Is there a way for me to find out what changes have been made so I don't have to re-test every new version to find out? Thanks

Working through TFDi 717 "left engine air bleed on" works but "left engine air bleed off" doesn't. Have to say "left engine air bleed on" again to get it to turn off. No problem with the right engine air bleed. "irs nav" or "irs align" or "irs one nav" followed by "irs two nav" sets both to "nav" as expected but a banner always comes up after suggesting to re-phrase the command. Unfortunately I have to do all testing on the ground as the plane has a bug that causes the sim to crash when changing views. Apparently Lockheed Martin are working with TFDi to resolve this. That's it for the moment.

Working through the QW787 flows. Saying "emergency lights off" turns them on and so on. Saying "bulk cargo heat switch on" or "off" does nothing. Saying "ventilation on" turns it on but doesn't close the switch cover Stabilizer cutoff red switch covers don't close Might want to have a look at the 4 generator buttons(L1-L2-R1-R2). Unless I'm mistaken somethings not right. L1 & R1 seem to be the only buttons that respond. If I have this wrong please advise how these should work. Saying "QNH Standard" or "QNH Standard Off" does nothing. However, the first officer reports the actions were completed. Engine start doesn't include opening the engine fuel levers. That's it so far.

Hi Gerald, Working through the QW787 flows. Saying "emergency lights off" turns them on and so on. Saying "bulk cargo heat switch on" or "off" does nothing. Saying "ventilation on" turns it on but doesn't close the switch cover Stabilizer cutoff red switch covers don't close Might want to have a look at the 4 generator buttons(L1-L2-R1-R2). Unless I'm mistaken somethings not right. L1 & R1 seem to be the only buttons that respond. If I have this wrong please advise how these should work. Saying "QNH Standard" or "QNH Standard Off" does nothing. However, the first officer reports the actions were completed. Engine start doesn't include opening the engine fuel levers. That's it so far.

Sorry Gerald, didn't answer your question earlier. I'm running P3D 4.5

Thanks Gerald.... That worked. When saying "transponder tara" the selector switch goes past TA/RA to ALT. Also "window heat on" or "window heat off" does nothing. That should be it for this aircraft. Moving on to Qualitywings 787. Harry

Hi, Been setting up flows for the PMDG 747-8. All good except for the following that I've found so far. Not sure if these have been reported previously. "Trim Air On" only turns on the left trim air switch "Trim Air Off" only turns off the left trim air switch "All Packs On" turns them on but "All Packs Off" does nothing. Have to say "All Packs On" again for them to turn off "Emergency Lights Arm" arms them (from the off position) THEN "Emergency Lights Off" turns them on THEN "Emergency Lights on" turns them off "Engine Anti-Ice Auto" doesn't go to auto "Wing Anti-Ice Auto" doesn't go to auto Harry

I'm running an i7 9700k @ 5.0Ghz with a Corsair H100i Platinum cooler. I agree with Alex as regards hyperthreading. On previous systems I saw no real benefit with P3D. I'll be interested to see what sort of resources the new Microsoft Flight Simulator will use.

Hardware is more my forte. Here are a few things to think about. In my experience you'll want a CPU that you can overclock safely and easily. There are any number of opinions regarding hyperthreading, but again, in my experience, there's nothing much to be gained. So something like an i7 9700k will do the trick. Just make sure whatever you get is unlocked so you can overclock it. P3D wants lots of fast CPU, especially from Core #1 (cpu0). Keep it cool, so water cooling is a must. Radiators and pumps for the all-in-ones are all pretty much made by the same manufacturers, just re-badged. In my experience bigger isn't always better. For me it really comes down to fan design and performance. As for motherboards, my #1 priority is having the best available voltage regulation to ensure system stability when overclocking. Beyond that you'll want to research features like WiFi, Bluetooth, RGB and other features that you'll want to use. A board that makes it easy to setup for overclocking without an engineering degree is a bonus. For P3D it seems that 16GB of RAM is plenty. Obviously the faster the better, say around 3200. Personally I wouldn't try to overclock RAM. You'll probably want to stick with Nvidia for Graphics. It seems most do for P3D. Buy the best GTX you can afford. I've never bothered overclocking them for P3D. For a power supply I personally wouldn't go less than 750 watts and good quality. Too much is better than not enough. You'll want at least one SSD, either an M.2, SSD or a combination of both. I have a 500GB M.2 and a 1TB SSD and I'm not hurting for space. Finally the system case. My priority is function/performance more than looks. I don't want to have to stand on my head to build and maintain the thing, so routing of cables and accessibility to fans/mesh/filters/radiator for cleaning is a priority, second only to airflow. Only makes sense the better the airflow the cooler the overall system runs. As for planes, my personal choices are PMDG 747/777 for long haul, Aerosoft Airbus 318/319/320/321 for trans continental and TFDi 717 for regional. As for scenery, airports, etc. Not my forte. There are others throughout the forum who have a better handle on this. It's whatever airports you'll visit and how you want your ground textures, weather, etc. to look. Hope some of this helps.

Farlis, thanks for that regarding HDR lighting. I just assumed.

The cooler is a Corsair H100i 240mm Platinum. It was fan performance that sold me. I've used SGAA almost from the word go and so far haven't had any lockups. Too bad it doesn't work with the TFDi 717 gauges. I'm running the latest Nvidia driver.

For those who may be looking to buy/build a new rig, here in the image below are the specs & results from a rig I built just the other day. At 3rd party airports and framerate locked at 30fps I'm consistently holding 30fps @ 1080p 60hz whether in the air or on the ground with very few exceptions. NO stutters! I have Dynamic Lighting set on and HDR Lighting off (my monitor doesn't support it). As you'll see in the image I've made only a few changes in the BIOS as in my opinion no others are needed. Also the lack of CPU hyperthreading in my experience is of no consequence. The cost difference between an 8700k and 9700k was $26. The M.2 drive actually performs at full spec. and loads Windows in under 10 seconds. Anything related to P3D loads in no more than 30 seconds. Also as a side note, if you are experiencing crashes with the TFDi 717 when changing views, it's a bug that the developers are working with Lockheed Martin to resolve. Also due to the cockpit gauge coding SGAA is not compatible and no changes to the coding are expected. For me the key points in designing the rig were: 1. System Case Cooling 2. CPU performance and stability at 5Ghz 3. CPU Cooler Fan Performance (radiators & pumps are mostly all made by the same manufacturer) 4. GPU out of the box performance. No need for Ray Tracing in my case. 5. RAM stability at full spec. 6. Motherboard Voltage Regulation!!

James & Ian, Spot on! Thanks for taking the time to help.... Harry

As regards P3DV4, specifically version 4.5, it seems that Radar contact doesn't work with either the PMDG 747 or 777 being Cold & Dark . You can power everything up and configure for pushback but still nothing. Works fine from the Default configuration. The Radar Contact window comes up as it should but when you press 1 nothing happens and that's it. The PMDG 737 and all other aircraft I have when Cold & Dark are fine. Any thoughts on how to work around this?