September 10, 20205 yr I have received taxi clearance to RW 08 at Innsbruck. I taxi to runway, line up. There are no options for take off, the speech remains on "clear to taxi runway 08 and let us know when ready". How do i get the program to advance. There are no more instructions to say on pressing "?". have the tower tuned there is no other frequency to use. I have loaded a flight plan from MSFS (the one I'm using). Everything is set, but I cant get past the taxi instructions. FYI, I'm in the Neo with the Flybywire mod on. But the Com radio does not change with the freqs from Pilot2ATC. I have disabled the two selections in the sim menu. Thanks EDIT. I got the clearance to take off by reloading the flight plan, made from the MSFS sim planner. Went to the little "?" menu and found the correct sequence. Then I requested take off, verbally. Things looked good. Received take off clearance, then I lost all joystick controls and lost the mouse clicks in the cockpit? I tried going from windowed (my usual viwe to full screen and back, no joystick control and no mouse clicks in cockpit. I could still click on the Pilot2ATC UI. here are the FSUIPC logs; User Name="MSFS Tester" User Addr="Time Limited 311020" FSUIPC7 Key is provided WIDEFS7 not user registered, or expired 6041687 System time = 10/09/2020 21:26:23, Simulator time = 14:06:47 (14:06Z) [Continuation log requested by user] 6086156 Sim stopped: average frame rate for last 90 secs = 96.9 fps 6086156 Max AI traffic was 1 aircraft 6086156 ------------------------------------------------------------------- 6086234 === QUIT notified! Saving "Previous Flight" ... 6093078 MSFS no longer running - exiting 6093078 === Hot key unregistered 6093078 === Stop called ... 6093094 === Closing external processes we started ... 6094094 === About to kill any Lua plug-ins still running ... 6094234 === Closing global Lua thread 6095250 === About to kill my timers ... 6095453 === Restoring window procs ... 6095453 === Unloading libraries ... 6095453 === stopping other threads ... 6095453 === ... Button scanning ... 6095562 === ... Axis scanning ... 6095656 === Releasing joystick devices ... 6095656 === Freeing macro memory 6095656 === Removing any offset overrides 6095656 === Clearing any displays left 6095656 === Calling SimConnect_Close ... 6095859 === SimConnect_Close done! 6095859 === AI slots deleted! 6095859 === Freeing button memory ... 6095859 === Closing my Windows ... 6095859 === Freeing FS libraries ... 6096859 === Closing devices ... 6096859 === Closing the Log ... Bye Bye! ... 6096859 System time = 10/09/2020 21:27:18 6096859 *** FSUIPC log file being closed Minimum frame rate was 9.6 fps, Maximum was 184.9 fps Average frame rate for running time of 6065 secs = 43.5 fps Maximum AI traffic for session was 12 aircraft Traffic deletions 0 aircraft Memory managed: 2 Allocs, 1 Freed ********* FSUIPC Log file closed *********** ******** FSUIPC7, Version 7.0.0-Beta (8th September 2020) by John & Pete Dowson ********* No registry entries found for MSFS - setting paths from APPDATA env variable Cannot open UserCfg.opt at 'C:\Users\herky\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt' No FS path found in C:\Users\herky\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt Windows 10 Home 64 Bit reported as Build 18363, Release ID: 1909 (OS 10.0) Reading options from "C:\Users\herky\OneDrive\Desktop\FSUIPC7\FSUIPC7.ini" Checking the Registrations now ... User Name="MSFS Tester" User Addr="Time Limited 311020" FSUIPC7 Key is provided WIDEFS7 not user registered, or expired 31 System time = 10/09/2020 19:45:41 47 ------------------------------------------------------------------- 78 Registered default HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 109 FS path = "" No registry entries found for MSFS - setting paths from APPDATA env variable Cannot open UserCfg.opt at 'C:\Users\herky\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt' No FS path found in C:\Users\herky\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt 156 ---------------------- Joystick Device Scan ----------------------- 156 Product= Saitek X52 Pro Flight Control System 156 Manufacturer= Saitek 156 Vendor=06A3, Product=0762 (Version 1.35) 156 GUIDs returned for product: VID_06A3&PID_0762: 156 GUID= {B922C160-EF7B-11EA-8001-444553540000} 156 Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255 156 ------------------------------------------------------------------- 172 Device acquired for use: 172 Joystick ID = 0 (Registry okay) 172 0=X52 Professional H.O.T.A.S. 172 0.GUID={B922C160-EF7B-11EA-8001-444553540000} 172 ------------------------------------------------------------------- 219 LogOptions=00000000 00000001 3062 Simulator detected 8094 SimConnect_Open succeeded 8094 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 8094 MSFS version = 11.0.282174.999 8094 Initialising SimConnect data requests now 8172 flights\other\MainMenu.FLT 8172 .PLN 8172 SimObjects\Airplanes\Asobo_C172sp_classic\aircraft.CFG 8172 User Aircraft ID 1 supplied, now being used 8172 .PLN 8203 Aircraft loaded: running normally now ... 8390 System time = 10/09/2020 19:45:50, Simulator time = 20:01:48 (18:01Z) 8390 Aircraft="Cessna Skyhawk Asobo" 14390 -------------------- Starting everything now ---------------------- 221219 Planned flight from LOWI to EDDF 221219 C:\USERS\HERKY\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\NEO LOWI TO EDDF.PLN 221234 C:\Users\herky\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-aircraft-a320-neo\SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG 221250 Sim stopped: average frame rate for last 213 secs = 95.6 fps 221250 Max AI traffic was 0 aircraft 221250 ------------------------------------------------------------------- 222078 Aircraft="Airbus A320 Neo Asobo" 224500 Planned flight from LOWI to EDDF 224500 C:\USERS\HERKY\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN 224922 C:\Users\herky\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 269687 **** Restarting traffic scanning due to non-reception **** 5982672 Sim stopped: average frame rate for last 5752 secs = 40.7 fps 5982672 Max AI traffic was 12 aircraft 5982672 ------------------------------------------------------------------- 5989172 flights\other\MainMenu.FLT [Log closed by user request, and continued in new file] 6036125 System time = 10/09/2020 21:26:18, Simulator time = 14:06:41 (14:06Z) 6036125 *** FSUIPC log file being closed Minimum frame rate was 9.6 fps, Maximum was 184.9 fps Average frame rate for running time of 6017 secs = 43.1 fps Maximum AI traffic for session was 12 aircraft Traffic deletions 0 aircraft Memory managed: 2 Allocs, 1 Freed ********* FSUIPC Log file closed *********** User Name="MSFS Tester" User Addr="Time Limited 311020" FSUIPC7 Key is provided WIDEFS7 not user registered, or expired 6036125 System time = 10/09/2020 21:26:18, Simulator time = 14:06:41 (14:06Z) [Continuation log requested by user] [Log closed by user request, and continued in new file] 6041687 System time = 10/09/2020 21:26:23, Simulator time = 14:06:47 (14:06Z) 6041687 *** FSUIPC log file being closed Minimum frame rate was 9.6 fps, Maximum was 184.9 fps Average frame rate for running time of 6022 secs = 43.1 fps Maximum AI traffic for session was 12 aircraft Traffic deletions 0 aircraft Memory managed: 2 Allocs, 1 Freed ********* FSUIPC Log file closed *********** Edited September 10, 20205 yr by charlie130 Lost controls ion cockpit
September 10, 20205 yr Commercial Member The SayIt takeoff request variations are listed in the Requests -> Takeoff. The simplest one is "<CallSign> ready for departure". I don't believe P2A or even FSUIPC does anything that would make your joystick and mouse stop working in MSFS. I'm no FSUIPC expert, but I do see 2 log entries indicating the SIM stopped, which would explain the non-responsive mouse and joystick. Perhaps you should report this on the MSFS and FSUIPC forums for a better response.
September 10, 20205 yr Author 23 minutes ago, Dave-Pilot2ATC said: The SayIt takeoff request variations are listed in the Requests -> Takeoff. The simplest one is "<CallSign> ready for departure". I don't believe P2A or even FSUIPC does anything that would make your joystick and mouse stop working in MSFS. I'm no FSUIPC expert, but I do see 2 log entries indicating the SIM stopped, which would explain the non-responsive mouse and joystick. Perhaps you should report this on the MSFS and FSUIPC forums for a better response. Thanks Dave. I have had no issues with MSFS until tonight when I used FSUIPC so I suspect there is something amiss with it? I'll try tomorrow with the Cessna 172 or the TBM which Clumsy uses. Could be that the Neo was not able to use the programs? It certainly did not accept radio freqs from PILOT2ATC. But then again, a lot of features don't work on the Airbus (yet). Thanks.
September 11, 20205 yr For MSFS 2020, everything works OK until departure. Once departure responds to my check-in after takeoff, I never hear from ATC again.
Archived
This topic is now archived and is closed to further replies.