Jump to content

byork

Commercial Member
  • Content Count

    25,735
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by byork

  1. You said before that according to your UGCX Log file "Advanced Animations" in FSX was not selected, but in your FSX menu Advanced Animations was indeed checked?
  2. Can you post your log so we can see exactly what you're saying?
  3. Hi Mark, This happens to you when using the pre flight events when the time reaches 0? Normally you'd call for the "Before Start checklist" well before the time reaching 0. Then you'd run the "below the line" portion of the checklist at around time 0. You can cancel any checklist by speaking, I recall "Cancel Checklist". Then you could call for the intended checklist again. Also, with Flows, using the "manual flow selector", you can manually trigger any Flow you like at basically almost anytime. But it happens to you again, be sure to look at the Log in the Info Center. It will tell you what the speech system actually heard. Maybe the system though you said "After Start Checklist" inadvertently? Only the log will say. But let me know. If there is something we can tweak or polish, we'd like to know so we can address it.
  4. That's going back a long time... but I recall it was several months.
  5. That's going back a long time... but I recall it was several months.
  6. We really don't know... the ball is in PMDG's court.
  7. Yes, we're updating SOP3 to match their new procedures. Cheers,
  8. We've had no reports of any issues with Pushback Express and the new 737. It should work fine.
  9. Much, much shorter. The FBW took a long time because we had to go back to square 1 since everything about MSFS was new and different. But now we haver a pretty good handle on MSFS.
  10. Much, much shorter. The FBW took a long time because we had to go back to square 1 since everything about MSFS was new and different. But now we haver a pretty good handle on MSFS.
  11. No news. Their release seems to have gone pretty smooth. Hopefully we'll know something soon.
  12. Hi Mhazy, 1. Please open the Info Center panel in the program. Please look at the Speech Status panel. It will tell you if speech recognition is even running. 2. There's also a log file. It will tell you what voice commands the system "heard". What do you see? 3. I assume other voice commands are working?
  13. byork

    MD 82

    Thank you for the kind words! We're "aiming" to have the Maddog out around the end of the month, give or take. Key word - aiming!
  14. Hi Ian, 146: No plan for it. If there's a lull in our schedule and sufficient time, maybe we can slot it in. MD82: Aiming for the end of this month. 737: As mentioned elsewhere, the PMDG EULA states all 3rd party must interface with the 737 using the PMDG SDK. As far as I know, PMDG has not yet released the SDK.
  15. Hi John, Please see this thread:
  16. That's our hope to support them all.
  17. All rides on the SDK. If you look at the EULA for the MSFS 737, you'll note that it says 3rd party cannot interface without the using the official PMDG SDK. This was same as FSX/P3D. Also, we're making a big change for the Maddog and 737... We are trying something new... we don't want to just rehash FS2Crew for FSX/P3D 737.
  18. Just to let you all know... we're not resting on our laurels here at FS2Crew 😉
  19. Hi JD, 1. Yes. 2. I think I mentioned this via the support ticket, but please check the manuals: http://www.support.fs2crew.com/help/manuals/#pageid=ultimate_ground_crew_x Here's a user created training video that might help: 3. Yes, default and payware. 4. Confirm you have "advanced animations" selected in FSX and your graphics drivers are current. I think you told me they are.
  20. If the crash happens when MSFS starts loading, it's likely you have corruption on your EXE.xml file. The EXE.xml file controls which programs autostart when MSFS loads. Should there be an invalid character on your EXE.xml file, things will not load properly. Please do this: 1. Make a backup copy of your EXE.xml 2. Delete your EXE.xml file. 3. Re-install FS2Crew. FS2Crew will create a fresh, new EXE.xml file that we know is perfect. Your EXE.xml file is located here: MS Store Version: YOUR USER NAME -> AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml Steam Version YOUR USER NAME ->AppData/Roaming/Microsoft Flight Simulator
  21. Make sure you run the voice training. If you're a native speaker, assuming nothing is wrong with your hardware, you should be getting 90 plus percent accuracy easily. Even non native speakers can get very high results.
  22. In the Info Center panel, in the Speech STS section, it will say if speech recognition is actually running. Also ensure you selected "voice control" in the Interface method drop down menu. You may still be in Button Control mode.
  23. When you say nothing shows, you're not expecting a "green bar" are you... the Green Bar was a FSX/P3D thing. If you go into the Info Center section of the app, you'll see a Speech Status section. It will tell you if voice recognition is running. Logs are also available in the app to tell you what the speech system heard.
×
×
  • Create New...