Jump to content
The simFlight Network Forums

gfd

Members
  • Posts

    171
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Alberta, Canada

Recent Profile Visitors

2,177 profile views

gfd's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for the background. I'll post to them over at their place and see what they have to say. I couldn't figure out how I might have invoked some elevated debug activity in FSUIPC. I use ASN and therefore do not make extensive use of your miscellaneous options. The exceptions being VAS tracking via the log page and the facility to start the session with accurate time. Controller assignments and WideFS buttons are something else altogether. I mention this as you expressed concern about P3D v3 playing nice with FSUIPC. I don't know what significance this will have, but: -as stated elsewhere, P3D v3 appears to respect the stripping of controller assignments from its options. I have had controllers drop out the reinstalled them, without automatic assignment. The controllers checkbox is filled. The only controls I use in P3D are those for the avatar. -was able to make use of FSUIPC calibration. In one case, I was able to assign 75% of the travel of an axis to spoilers using FSUIPC calibration, and the final 25% to arming/disarming ground spoilers direct through P3D; using the strpped facility on the right side of the tab. -other axes that do not calibrate through FSUIPC, appear to work correctly including those assigned to the Airbus thrust lua file you put out awhile ago. Probably should be a separate post. However, I hate to pass up on an opportunity to be verbose.
  2. Thanks for that. Just to clarify, let's say I have two identical controllers. 1=A and 2=B. Each has a distinct GUID: 1=controller 1.GUID={123} 2=controller 2.GUID={234} A=controller A.GUID={123} B=controller B.GUID={234} Say the controllers drop out and get reversed. I correct that by changing the letters on both pairs of lines? Thanks again.
  3. I am using the latest version of FSUIPC along with LINDA in P3D v3 inside of Windows 10 64 bit. I have started getting an error in the FSUIPC log as follows: *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory There are several instances of this error in the log. This file does not exist on my computer. Please see the log below. I should point out that I looked at this thread: http://forum.simflight.com/topic/80259-i-need-help-for-lua/ Have I inadvertently put FSUIPC into debug mode? Is this something I need to be concerned about? If not, please disregard with thanks. ********* FSUIPC4, Version 4.948 by Pete Dowson ********* Reading options from "S:\P3D\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 8.0 Module base=57550000 User Name="Graham Derreck" User Addr="gderreck@shaw.ca" FSUIPC4 Key is provided WideFS7 Key is provided 4656 System time = 08/11/2015 21:15:08 4656 FLT UNC path = "\\GFD-DESKTOP\Documents\Prepar3D v3 Files\" 4656 Trying S:\P3D\Modules\SimConnectP3D2.dll 4656 Found it: trying to connect 4672 FS UNC path = "\\GFD-DESKTOP\P3D\" 4765 Finished: 0 Profile files created 4812 ---------------------- Joystick Device Scan ----------------------- 4812 Product= Saitek Pro Flight Quadrant 4812 Manufacturer= Saitek 4812 Vendor=06A3, Product=0C2D (Version 2.1) 4812 Serial Number= Saitek 4812 Product= SideWinder Force Feedback 2 Joystick 4812 Manufacturer= Microsoft 4812 Vendor=045E, Product=001B (Version 10.0) 4812 Serial Number= Microsoft 4812 Product= Saitek Pro Flight Combat Rudder Pedals 4812 Manufacturer= Saitek 4812 Vendor=06A3, Product=0764 (Version 2.1) 4812 Serial Number= Saitek 4828 Product= Pro Flight Cessna Trim Wheel 4828 Manufacturer= Saitek 4828 Vendor=06A3, Product=0BD4 (Version 1.7) 4828 Serial Number= RD014075 4828 Product= Saitek Pro Flight Quadrant 4828 Manufacturer= Saitek 4828 Vendor=06A3, Product=0C2D (Version 2.1) 4828 Serial Number= Saitek 4828 Product= Saitek Pro Flight Quadrant 4828 Manufacturer= Saitek 4828 Vendor=06A3, Product=0C2D (Version 2.1) 4828 Serial Number= Saitek 4828 ------------------------------------------------------------------- 4859 Run: "S:\P3D\Modules\linda.exe" 4937 LogOptions=00000000 00000001 4953 ------------------------------------------------------------------- 4953 ------ Setting the hooks and direct calls into the simulator ------ 4953 --- CONTROLS timer memory location obtained ok 4953 --- SIM1 Frictions access gained 4953 --- FS Controls Table located ok 4953 --- Installed Mouse Macro hooks ok. 4953 --- Wind smoothing fix is installed 4953 --- All links okay (except older global weather setting method) 4953 ------------------------------------------------------------------- 4953 SimConnect_Open succeeded: waiting to check version okay 4953 Trying to use SimConnect Prepar3D 4968 VRI port 1 "com3" opened 13062 VRI MCP2B ("MCP2 Boeing") detected on port com3 29078 Running in "Lockheed Martin� Prepar3D� v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0) 29078 Initialising SimConnect data requests now 29078 FSUIPC Menu entry added 29093 \\GFD-DESKTOP\Documents\Prepar3D v3 Files\A2A_172_KFHR.fxml 29093 \\GFD-DESKTOP\P3D\SimObjects\Airplanes\A2A_C172\C172.air 44218 Weather Mode now = Theme 47468 \\GFD-DESKTOP\P3D\SimObjects\Airplanes\Aerosoft Airbus A319 CFM\A319.air 47468 \\GFD-DESKTOP\Documents\Prepar3D v3 Files\AC_A319_CYVR.fxml 100328 System time = 08/11/2015 21:16:44, Simulator time = 20:15:38 (04:15Z) 100343 Aircraft="Airbus A319 Air Canada C-GITP" 101328 Starting everything now ... 101343 LUA.0: beginning "S:\P3D\Modules\ipcReady.lua" 101343 LUA.0: ended "S:\P3D\Modules\ipcReady.lua" 101359 LUA.1: 101359 LUA.1: ************************** START ************************* 101359 LUA.1: [sTART]LINDA:: Loading... 101359 ASN active function link set 101359 Ready for ASN WX radar 101375 LUA.1: LINDA:: [sTART] VRInsight MCP Set = mcp2 101500 LUA.1: LINDA:: [sTART] New Aircraft Selected - restarting... 101500 LUA.1: LINDA:: [sTART] Aircraft: Airbus A319 Air Canada C-GITP 101500 LUA.1: LINDA:: [sTART] Air file: \\GFD-DESKTOP\P3D\SimObjects\Airplanes\Aerosoft Airbus A319 CFM\A319.air 101562 LUA.1: LINDA:: [sTART] Aircraft module detected: Aerosoft Airbus 101593 LUA.0: LINDA:: [iNIT] Starting Initialisation... 101609 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-aivlasoft 101609 LUA.0: LINDA:: [LIB] AivlaSoft library loaded... 101609 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-ATC 101609 LUA.0: LINDA:: [LIB] ATC library loaded... 101609 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-fallback 101625 LUA.0: LINDA:: [LIB] FSX standard library loaded... 101625 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-FS2Crew 101625 LUA.0: LINDA:: [LIB] FS2Crew library loaded... 101625 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-fsx 101640 LUA.0: LINDA:: [LIB] FSX Functions loaded... 101640 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-IVAO 101640 LUA.0: LINDA:: [LIB] IVAO library loaded... 101640 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-realityxp 101640 LUA.0: LINDA:: [LIB] RealityXP library loaded... 101656 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-saitek 101656 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-user 101656 LUA.0: LINDA:: [LIB] User Library loaded... 101656 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-VATSIM 101656 LUA.0: LINDA:: [LIB] VATSIM library loaded... 101672 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-vrinsight 101672 LUA.0: LINDA:: [LIB] VRInsight Function Library loaded... 101672 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-weather 101672 LUA.0: LINDA:: [LIB] Weather library loaded... 101672 LUA.0: LINDA:: [iNIT] loading optional library: linda/libs/lib-a2amap 101687 LUA.0: LINDA:: [LIB] A2A MAP library loaded... 101687 LUA.0: LINDA:: [iNIT] Initializing Common Variables... 101734 LUA.0: LINDA:: [iNIT] User GLOBAL config loaded... 101734 LUA.0: LINDA:: User's modifications script is loaded... 101734 LUA.0: LINDA:: [iNIT] User FUNCTIONS loaded... 101750 LUA.0: LINDA:: [iNIT] VRI MCP config loaded... 101765 LUA.0: LINDA:: [iNIT] Finalising Initialisation... 101765 LUA.0: LINDA:: [COMM] DSP Mode 1 101797 LUA.0: LINDA:: [COMM] Checking VRI 101797 LUA.0: LINDA:: [COMM] Enabling VRI 101812 LUA.0: LINDA:: [COMM] ConnectMCP - Connecting to MCP Panel... 101812 LUA.0: LINDA:: [COMM] ConnectMCP completed - 320530620 101812 LUA.0: LINDA:: [COMM] InitMCP - Initialising MCP... 102281 LUA.0: LINDA:: [COMM] Initializing MCP2 (Boeing)... 102500 Advanced Weather Interface Enabled 110687 LUA.0: LINDA:: [COMM] RADIOS : Empty command for :: COM1 Select 110750 LUA.0: LINDA:: [COMM] InitMCP - completed 111890 LUA.0: LINDA:: [COMM] MCP Started... 111890 LUA.0: LINDA:: [iNIT] Initialising HID devices... 111906 LUA.0: LINDA:: [iNIT] Loading a fallback joysticks config... 111922 LUA.0: LINDA:: [iNIT] Loading Aerosoft Airbus joysticks config... 111922 LUA.0: LINDA:: [iNIT] Module: Aerosoft Airbus Started... 111937 LUA.0: LINDA:: [iNIT] Initiating Autosave true 114578 LUA.0: LINDA:: [iNIT] Ready to go, Captain! 114593 LUA.0: LINDA:: Offsets watching list cleared! 114765 LUA.0: LINDA:: LVars watching list cleared... 114953 LUA.0: LINDA:: Offsets watching list cleared! 115109 LUA.0: LINDA:: LVars watching list cleared... 116125 LUA.0: LINDA:: Offsets watching list cleared! 116187 LUA.0: LINDA:: LVars watching list cleared... 116343 LUA.0: LINDA:: Offsets watching list cleared! 116468 LUA.0: LINDA:: LVars watching list cleared... 116593 LUA.0: LINDA:: Offsets watching list cleared! 150297 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150297 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150297 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 150297 LUA.2: Global: ipcPARAM = -2991 150328 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150328 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150328 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150328 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 150328 LUA.2: Global: ipcPARAM = -4421 150359 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150359 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150359 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150359 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 150359 LUA.2: Global: ipcPARAM = -6111 150390 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150390 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150390 LUA.3: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150390 LUA.3: S:\P3D\Modules\AirbusX_Thr2.lua:1 150390 LUA.3: Global: ipcPARAM = -7932 150422 LUA.3: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150422 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150422 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150422 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 150422 LUA.2: Global: ipcPARAM = -8842 150437 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150437 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150437 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150437 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 150453 LUA.2: Global: ipcPARAM = -11052 150468 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150468 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150468 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150468 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 150468 LUA.2: Global: ipcPARAM = -12353 150500 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150547 LUA.3: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 150547 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 150547 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 150547 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 150547 LUA.2: Global: ipcPARAM = -15473 150562 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155015 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155015 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155015 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155015 LUA.2: Global: ipcPARAM = -15213 155047 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155047 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155047 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155047 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155047 LUA.2: Global: ipcPARAM = -11312 155062 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155078 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155078 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155078 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155078 LUA.2: Global: ipcPARAM = -7282 155093 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155093 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155093 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155093 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155109 LUA.2: Global: ipcPARAM = -3641 155125 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155156 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155156 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155187 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155187 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155187 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155187 LUA.2: Global: ipcPARAM = 1408 155218 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155218 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155218 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155218 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155218 LUA.2: Global: ipcPARAM = 3712 155250 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155281 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155312 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155328 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155328 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155328 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155328 LUA.2: Global: ipcPARAM = 11520 155359 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155359 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155359 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155359 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155359 LUA.2: Global: ipcPARAM = 14208 155390 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155390 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155390 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155390 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155390 LUA.2: Global: ipcPARAM = 15616 155422 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155890 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155890 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155890 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155906 LUA.2: Global: ipcPARAM = 15488 155937 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155937 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155937 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155937 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155937 LUA.2: Global: ipcPARAM = 14080 155953 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155953 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155953 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155953 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155968 LUA.2: Global: ipcPARAM = 12800 155984 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 155984 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 155984 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 155984 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 155984 LUA.2: Global: ipcPARAM = 10624 156015 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156047 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156047 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156047 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156047 LUA.2: Global: ipcPARAM = 8064 156078 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156078 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156078 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156078 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156078 LUA.2: Global: ipcPARAM = 4992 156109 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156109 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156109 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156109 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156109 LUA.2: Global: ipcPARAM = 3712 156140 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156140 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156140 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156140 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156140 LUA.2: Global: ipcPARAM = 1280 156172 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156172 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156172 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156172 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156172 LUA.2: Global: ipcPARAM = -1040 156203 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156203 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156203 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156203 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156203 LUA.2: Global: ipcPARAM = -3511 156234 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156234 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156234 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156234 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156234 LUA.2: Global: ipcPARAM = -6111 156265 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156265 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156265 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156265 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156265 LUA.2: Global: ipcPARAM = -7282 156297 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156328 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156328 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156328 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156328 LUA.2: Global: ipcPARAM = -10532 156359 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156359 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156359 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156359 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156359 LUA.2: Global: ipcPARAM = -11833 156390 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156390 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156390 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156390 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156390 LUA.2: Global: ipcPARAM = -13003 156406 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156406 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156406 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156406 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156406 LUA.2: Global: ipcPARAM = -14173 156437 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156468 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156468 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156468 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156468 LUA.2: Global: ipcPARAM = -15083 156500 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 156500 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 156500 LUA.2: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 156500 LUA.2: S:\P3D\Modules\AirbusX_Thr2.lua:1 156500 LUA.2: Global: ipcPARAM = -16384 156531 LUA.2: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 240609 Sim stopped: average frame rate for last 141 secs = 32.3 fps 252656 *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory 252656 LUA.3: beginning "S:\P3D\Modules\AirbusX_Thr2.lua" 252656 LUA.3: S:\P3D\Modules\AirbusX_Thr2.lua:1 252656 LUA.3: Global: ipcPARAM = -16384 252656 LUA.3: ended "S:\P3D\Modules\AirbusX_Thr2.lua" 321437 Sim stopped: average frame rate for last 23 secs = 34.1 fps 556015 Sim stopped: average frame rate for last 120 secs = 30.5 fps 612937 Sim stopped: average frame rate for last 56 secs = 33.2 fps 867343 Sim stopped: average frame rate for last 249 secs = 34.1 fps 1146968 Sim stopped: average frame rate for last 64 secs = 27.1 fps 1206109 Sim stopped: average frame rate for last 20 secs = 25.5 fps
  4. I am bumping my own topic as I need some help. As indicated above, the Saitek throttles drop out after restarting Windows. The only way to get them back is to reinstall the driver. This reorders the controllers in the OS. I had thought that FSUIPC reassigned the controller order to compensate. I may have been mistaken. I reinstalled the driver after a reboot and two of the throttle quadrants were reversed. No amount of tinkering with FSUIPC4.ini corrected the situation. I looked in the manual, but didn't find a solution. I'm sure it's there, but I'm probably too thick to get it. I had AutoAssignLetters=Yes setup in the ini file. In my case, the 'G' controller got reversed with the 'F' controller. Perhaps someone with more wherewithal than me can walk me through how to get the correct controllers reattached to the proper assignments. Assume you are addressing a 6 year old. In this case, that's where I'm at :) I would like to avoid having to go through reassigning all of my profiles if possible. However, if that is the only alternative, I would like to know this in order to avoid spinning my wheels any further. Any assistance would be most appreciated.
  5. I can confirm that P3D seems to respect the deleted controller assignments when there is a disconnect/reconnect.
  6. Yeah, that's how I do it. However, until the latest version, I found that when I reinstalled my controllers, due to the useless Saitek drivers; I had to mess around getting FSUIPC controllers back in order. This is the first time I reinstalled drivers and didn't have to do some engineering in order to keep the controllers in line. Perhaps I was doing something wrong in the past, but the compliment still stands.
  7. Just wanted to say thanks for making good on the plan to have FSUIPC track controller changes. As some of you may know, Saitek controllers tend to misbehave on Windows 10; particularly if the are more than 1 of the same controller. In my case, I have 3 throttle quadrants. On startup, I occasionally lose 1 or more controllers. That requires running the driver installer to get the controllers back. I decided to uninstall all of the throttles and manually point them to the inf file for the driver. I don't know if that will work. However, upon reinstalling the drivers, the throttle IDs in Windows changed. Changing the order using JoyIDs didn't work. There is a point to this post coming :) I was afraid I would have to manually change my assignments in FSUIPC...arghhh. Guess what...when I opened Prepar3D, the assignments were still correct. That is so cool!! Thanks for that.
  8. True enough. Am having some issues testing other controllers. Saitek is a mess in Windows 10. Will reply here when I get it sorted out.
  9. Will do. Should point out that when I initially installed P3D v3, assignments were populated for the Sidewinder.
  10. It was a Sidewinder II FFB. Do you want me to unplug something else and check? I have Saitek throttles, Saitek combat rudder pedals, Xbox 360, Saitek trim wheel.
  11. Thanks for the reply. I can tell you that: -disconnected joystick from USB port -ran P3D v3 -closed P3D -plugged joystick in -ran P3D -nothing was assigned in P3D for the joystick Don't know if this was any value, given other's mileage may vary. As far as getting into trouble, I've done it every way imaginable. I now use file backup for minor changes and a disk image for major changes. That doesn't make me smart. It just mitigates the effects when I do dumb stuff.
  12. Greetings, I read your post suggesting that controllers be disabled in P3D version 3. With one exception, that doesn't matter to me. The exception is, if I disable the controllers in the check box, FS Force can no longer control the trim in the aircraft. That is one of its most compelling features. I have disabled all buttons and axes in P3D controls. The setup includes a Saitek trim wheel. After starting windows, the controller needs to be spun a number of times. The controller then drops out and reconnects. I can confirm that the trim wheel is not assigned in P3D controls after this event. Furthermore, I have tested this with, and without P3D running. Does that satisfy your request to ensure that FSUIPC and P3D controls are not at odds? I am using your latest version 4.947. Thanks
  13. Thanks Paul. You've given me a start at getting this solved. Graham EDIT: Just as a follow up, I compared the ini and profile files. You were bang on. I had gotten rid of a number of lua files and what was once CL19 is now CL5. This is in addition to the fact that perhaps FSUIPC gave the lua files different reference numbers in the new installation. It is all so very elegant and simple. Too bad I didn't figure it out for myself. Thank you again Paul, for turning me in the right direction.
  14. Greetings, I know Peter is away until the 4th. However, I have an issue that I would appreciate some help with. I reinstalled my system, upgrading to Windows 10. I did a clean install. I did save all of my flight data, including the Modules folder. I have just upgraded to the latest version of FSUIPC. I did a comparison on WinMerge and was able to merge the old and new FSUIPC ini file. There were few differences; mainly had to move the profile references into the new ini file. FSUIPC loads without issue. The controllers are recognized by FSUIPC correctly. The profiles (in folders) are recognized. I have setup WideFS button screens on a networked machine. Just an excellent feature! Saves a bundle on hardware costs. I digress. I have LUA files setup with custom scripts for button assignments. I loaded a flight with an aircraft that had a profile (in this case the A2A 172). The axes were setup as expected in the FSUIPC GUI. However when I pressed buttons on the controllers, the lua file did not show up. Only the parameter numbers. It seems FSUIPC forgot the lua file. I looked in the profile and noticed entries like CL19, CL20, etc. Is that the code for the lua file(s)? Sample button entry in the profile: 21=R68,12,CL19:R,51 Is CL19 the reference to the lua file? If so, can re-train FSUIPC to recognize the files? If not, I suppose I'll have to reprogram FSUIPC for each of the profiles; at least the file reference. Not a big deal. Just curious. Many thanks in advance for your assistance, Graham
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.