Jump to content
The simFlight Network Forums

Griphos

Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by Griphos

  1. Hey Pete, Sorry. Didn't notice your post. I got it from the forum here. I don't recall how, exactly, since it was more than a week ago. I'm just about to get the full v3.3 version of P3D, so I'll download the latest from the forum here for installing with that.
  2. The new "e" installer worked great. I let it fix the registry entries for v1 and v2 for me and it installed in v3 successfully. Thanks again for the help.
  3. That seems a great improvement. I'll download the new version. Should I just install that one over the top, or do something else first to prepare for that? Should I remove any registry keys? I'm only very basically familiar with regedit. I can find the keys, but don't really understand the entries. Since the first time it asked for P3D it didn't show a version number, that's why I tried to point it. As I said, I'm new to FSUIPC for P3D with this install. I'd removed v1 and v2 a long time ago (each within the month of install to test them out). I used Control Panel uninstall, so I had thought there wouldn't be registry entries for them still. I think the new message will help clarify the process greatly. Also, since I'll be deleting this version soon and installing the permanent version (on a different hard drive), is there something I should do so that FSUIPC installs correctly on the new install? Thanks for your help.
  4. Here you go. Reading through this, it looks as if my pointing to my current P3D v3 install for v1 was written over fine when it found and installed for v3. Seems like everything should be fine. It just never reported to me that it installed for v3. (It also looks like there are still registry entries for the earlier P3D installs I've since deleted). ------------- Installer for FSUIPC4.DLL version 4.953 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=D:\MyGames\FSX\ Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX Parameter"AppPath" Not there, so looking in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... >>> OK! FOUND Prepar3D v1! <<< ... AppPath=D:\Prepar3D\ Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... >>> OK! FOUND Prepar3D v2! <<< ... AppPath=D:\MyGames\P3Dv2\ Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v3! <<< ... SetupPath=F:\Prepar3D v3\ =========================================================== INSTALLATION FOR FSX: SetupPath="D:\MyGames\FSX\" Checking version of the FSX EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: D:\MyGames\FSX\Modules\FSUIPC4.DLL ... Version 4.953 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "D:\MyGames\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Phil\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default.migrated\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Phil\AppData\Roaming" Found FSX.CFG in "C:\Users\Phil\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No FSX.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX and P3D controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC4_Loader.dll" okay =========================================================== INSTALLATION FOR Prepar3D v1: SetupPath="D:\Prepar3D\" Checking version of the Prepar3D v1 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D.EXE ... User identified path: "F:\Prepar3D v3" Checking version of the Prepar3D v1 EXE: ... Version 3.2.3.16769 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: F:\Prepar3D v3\Modules\FSUIPC4.DLL ... Version 4.953 found. Prepar3D v1 Modules folder already exists. Okay -- installed FSUIPC4 into "F:\Prepar3D v3\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Phil\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default.migrated\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Phil\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No Prepar3D.CFG there Cannot edit the DLL.XML file to activate FSUIPC. "Modules\FSUIPC Documents" folder already exists. Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder: Installed "SimConnectP3D3.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX and P3D controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC4_Loader.dll" okay =========================================================== INSTALLATION FOR Prepar3D v2: SetupPath="D:\MyGames\P3Dv2\" Checking version of the Prepar3D v2 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D v2.EXE ... User aborted attempt to find Prepar3D v2. Installation failed. =========================================================== INSTALLATION FOR Prepar3D v3: SetupPath="F:\Prepar3D v3\" Checking version of the Prepar3D v3 EXE: ... Version 3.2.3.16769 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Checking if there's already a version of FSUIPC4 installed in: F:\Prepar3D v3\Modules\FSUIPC4.DLL ... Version 4.953 found. Prepar3D v3 Modules folder already exists. Okay -- installed FSUIPC4 into "F:\Prepar3D v3\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Phil\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v3\Prepar3D.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default.migrated\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Phil\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Phil\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder: Installed "SimConnectP3D3.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX and P3D controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC4_Loader.dll" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC CHECK Checking FSUIPC registration ... Registration check for FSUIPC4 was successful! (result code 00) *************** End of Install Log ***************
  5. I'm finally taking the plunge with P3D, I think. I've always just flown FSX with a registered FSUIPC. Twice in the past (v1 and v2) I've bought a month long developer version of P3D to test it out and both times decided not to get it. This week I bought a month long developer license for v3.2. I like the changes and plan to buy the full version. But, I wanted to install a few things into the dev version to test it with the kinds of addons I usually fly (Orbx region, a few planes, etc). I thought I'd also try to install FSUIPC to calibrate my controls and set them up the way I do in FSX. I got the latest full version (.953) and installed it. It found my FSX and either updated or didn't (I think it was already up to date). Then it asked for the location of P3D since it didn't find it itself. I pointed it to the P3D.exe and let it do its thing. It suggested some problems with registry (which I later realized was because it was looking for v1). I didn't allow it to make any changes, and it looked for v2 and didn't find it, and then finished. It never looked for v3. Did I bugger things up? I see the entry for FSUIPC in the dll.xml file for P3D. Is it the case that FSUIPC doesn't look for or work with the monthly developer version of v3.2? Perhaps this is all moot, since I will soon be completely uninstalling this monthly license version before installing the full version, and will just try to install FSUIPC on that one (and not repeat the same mistake since I know it looks for v1 and v2 before looking for any newer version). Just wanted to see if there's something I should do to make things right before doing that.
  6. Thanks for the reply Andy and for the info from your .ini. As I said, I'm new to the full version of FSUIPC, so am not used to being able to set up different controls for different aircraft, which is certainly a very nice feature (and one I'm sure to start taking more advantage of). So, I had to assign throttle1 as my main throttle for all aircraft since I needed it for some aircraft, and it was not possible to assign it to only those aircraft using FSX controls short of creating several standard.cfg files and a batch file for swapping them, as far as I know. That was too big a pain to contemplate. Since I have never had a problem as a result in all my many years of simming, it didn't occur to me that might be the issue. In fact, it always worked fine with the DODO when FSX was controlling the axis, and fine with all my other helos even with FSUIPC controlling. Don't know if I would have ever thought of it if Pete hadn't deciphered the log for me and shown that the sim or the DODO was sending inputs from the main throttle axis even though it wasn't assigned. But that's the point and the value of these forums.
  7. Sorry, I was going to say something and then decided against it and thought I'd deleted it, but obviously left the quote. I'm a bit stressed today as well and could be reading more "tone" than is there. Anyway, since the general throttle axis was sending signals even though it wasn't assigned, I created a profile for the Dodo and mapped Axis#X to general throttle instead of throttle 1. It works. It's still logging those five inputs at regular intervals, but that doesn't seem to be interfering with correct operation. It's clearly something the Dodo is doing. I'm just glad to be able to use the Dodo again and continue to use FSUIPC to map those axes so I can use the excellent throttle script by PilotJohn for my turboprops. Thanks for your attention and help.
  8. That is helpful. I loaded the Aerosoft Huey, and only got logging for Throttle1 and it logged smooth and appropriate operation. So, even though there is still something odd about moving one axis when in the Axis Assignment page and having its neighbor always pop up, it does appear that there is something fishy in Dodoland. I have posted on their support forum. And, yes, I thought about removing the throttle lua to test, and will do that now as well. PS:
  9. I am not completely unfamiliar with computers. I'm actually quite computer literate for a lay person. I'm completely unfamiliar with FSUPIC, having just bought it. I'm not a software engineer. I'm not thick. Again, I haven't been suggesting there is a problem with FSUIPC, merely that I don't appear to have things set up correctly, despite having followed the guide and instructions to the best of my ability. I am also genuinely disappointed that this isn't a problem that has a clear and readily known solution. And that it appears to be limited to one aircraft that no one else, as far as I can tell, has experienced trouble with. The key bit for me is that when I open FSUIPC and move throttle axis#X, throttle axis#Y is detected and vice versa. That doesn't seem to be correct behavior to me. Perhaps the fault is partially my own as I'm trying to work with you today before you leave even though I'm needing to work at the same time. So both of us are rushed. I do appreciate the speed of your support. I do still think the tone could use some work. I realize you may not be able to respond, but I disabled the controller and tried again and I have the exact same behavior. So, I'm not sure what was "proved" by that. I've posted some of the log below. The elevator still appears to be doing weird things, even with the controller disabled in FSX. I tried changing the .ini file as suggested as well. No luck. I will continue to work ont his while you are gone, obviously, but since the problem continues even with the controller disabled in FSX, it seems clearly to be an issue either with this particular aircraft (which I've not been able to find generally) or with my setup of FSUIPC. ---------------- 790926 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 790926 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -220 (0xffffff24) AXIS_ELEVATOR_SET 790926 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 790926 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 790926 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 791082 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 791082 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 791082 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 791082 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 791082 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 791253 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 791253 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 791253 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 791253 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 791253 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 791409 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 791409 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 791409 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 791409 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 791409 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 791581 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 791581 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 791581 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 791581 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 791581 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 791752 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 791752 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 791752 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 791752 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 791752 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 791908 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 791908 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -207 (0xffffff31) AXIS_ELEVATOR_SET 791908 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 791908 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 791908 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 792080 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 792080 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 792080 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 792080 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 792080 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 792252 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 792252 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 792252 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 792252 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 792252 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 792423 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 792423 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -202 (0xffffff36) AXIS_ELEVATOR_SET 792423 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 792423 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 792423 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 792595 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 792595 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -200 (0xffffff38) AXIS_ELEVATOR_SET 792595 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 792595 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 792595 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 792751 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 792751 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 792751 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 792751 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 792751 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 792922 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 792922 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 792922 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 792922 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 792922 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 793094 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 793094 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -196 (0xffffff3c) AXIS_ELEVATOR_SET 793094 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 793094 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 793094 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 793266 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 793266 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -195 (0xffffff3d) AXIS_ELEVATOR_SET 793266 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 793266 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET 793266 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 793437 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 793437 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
  10. I didn't turn them off. They weren't ever on. The first time I logged, I had to check some of them, which is why I thought I needed to push new log. I will try it with the controller disabled in FSX and see if that makes a difference. I will try the joystick calibration option you suggested as well. I've not ever said that FSUIPC is causing the problem. However, it is FSUIPC that isn't working. The helicopter works just fine when the axis is controlled by FSX. I'm sure your program is excellent. Many people like it. I've certainly had wonderful advantage from it with all the other payware I've used that utilizes it. However, the tone of your support is making me regret my purchase. I suppose I'm just not used to being treated as if I am stupid, and accused of doing things I have not done and ignoring things I have not ignored.
  11. I did in fact ensure I had no conflicting assignments. And I haven't "newly connected" anything, although I will be sure to keep that issue in mind. And I'm doing what you are asking as I understand what you are asking, and will continue to do so. There is no single throttle axis assigned on this controller, but I checked all other controllers as well (a joystick, pedals, and trim wheel). There were no assignments to any axis on any controller for the single Throttle axis or any throttle axis. I can take pictures of all of them if you would like. But, with what you said in mind, I looked at buttons as well, and found that there were settings for throttle (increase quickly and decrease quickly) for "mouse look" on the scroll wheel. Lord knows how those got there, as I certainly didn't do that. Perhaps they are default. There was also a throttle decrease quickly (default=F2) assigned to a button on the CH quadrant. I deleted those assignments, restarted FSX and checked to make sure they were still not assigned, and then tried the helicopter again. That didn't make any difference. I trust you that something in FSX is controlling the single throttle axis, and that this is causing the problem, however only for this one aircraft so far, but I can't for the life of me see what it is since nothing is assigned to it in FSX. Would it be helpful to look at my controls.ini? I copied the log from when I restarted FSX to check, but it doesn't seem to have logged any control inputs, although I was making them. If you could tell me how to ensure I get the kind of log you need, I will try to get it: ********* FSUIPC4, Version 4.853 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=62FC0000 User Name="Phil Hopkins" User Addr="hopkinsp@southwestern.edu" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 406 System time = 10/10/2012 12:02:03 406 FLT path = "C:\Users\Phil\Documents\Flight Simulator X Files\" 437 Trying to connect to SimConnect Acc/SP2 Oct07 ... 437 FS path = "D:\MyGames\FSX\" 702 LogOptions=00000000 00000001 702 Wind smoothing fix is fully installed 702 G3D.DLL fix attempt installed ok 702 SimConnect_Open succeeded: waiting to check version okay 702 Trying to use SimConnect Acc/SP2 Oct07 4321 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 4321 Initialising SimConnect data requests now 4321 FSUIPC Menu entry added 4352 D:\MyGames\FSX\FLIGHTS\OTHER\FLTSIM.FLT 4352 D:\MyGames\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 54413 D:\MyGames\FSX\SimObjects\Rotorcraft\DodoSim_206_FSX_LowSkid\DodoSim206FSX_lowskid.AIR 117375 System time = 10/10/2012 12:04:00, Simulator time = 12:02:07 (20:02Z) 117437 Aircraft="Dodosim 206 FSX RAN N17-025" 118904 Starting everything now ... 118919 LUA.0: Starting... 118951 LUA.0: Done. 120011 Advanced Weather Interface Enabled 314404 Sim stopped: average frame rate for last 196 secs = 69.2 fps 405540 Sim stopped: average frame rate for last 63 secs = 72.4 fps 408582 Weather Mode now = Theme 408582 C:\Users\Phil\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
  12. Yes, you did say that, but you also said to check the logging tab and I wasn't sure whether logging was happening unless I clicked something. I did disable my two throttle axes in FSX. I've seen plenty of information both here and in the lua script itself that makes this clear. As I said, I'm am reading the instructions and trying my best to follow them. I have a Ph.D. and am not unfamiliar with reading technical instructions. I clearly understand that FSX and FSUIPC cannot be controlling the same axis or button at the same time. I also believe I understand I don't have to fully disable a controller in FSX in order to assign some of its axes in FSUIPC. Perhaps I am mistaken about that. But I checked in FSX yet again to triple check that the two throttle axes are not being controlled by the sim: As you'll see here, there is no setting on this controller or any other for Throttle 1 or Throttle 2 (X and Y axis). There is for X and Y rotation, which are two different axes on the controller. So, I do not see how FSX is trying to control those two axes. I'll trust you that the log says they are. Or perhaps the log says that other axes on the same controller are being controlled by FSX and I need to disable that whole controller in FSX. I would prefer not to do that, but will, I suppose, if I have to. I realize that you've been doing this a long time, and that you are intimately familiar with this program. I am not. I am trying to read everything provided by you to figure out what the problem is, but have not been able to do so, and that is why I am writing here.
  13. I remarked those lines, although I think the SyncSlope settings were done after I first noticed this issue. There was no change in behavior. I enabled logging and then advanced and retarded the throttle four times, and then moved it and stopped it a bit. I think this is the log that was made. Hope there's something in here that is helpful : ********* FSUIPC4, Version 4.853 by Pete Dowson ********* User Name="Phil Hopkins" User Addr="hopkinsp@southwestern.edu" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 1681113 System time = 10/10/2012 09:23:35, Simulator time = 09:19:41 (17:19Z) [Continuation log requested by user] Running inside FSX on Windows 7 Module base=635C0000 1681113 LogOptions changed, now 50000000 00000001 1681363 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1681363 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 1681363 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1681363 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1681363 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1681535 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1681535 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -165 (0xffffff5b) AXIS_ELEVATOR_SET 1681535 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1681535 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1681535 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1681691 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1681691 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -165 (0xffffff5b) AXIS_ELEVATOR_SET 1681691 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1681691 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1681691 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1681878 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1681878 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 1681878 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1681878 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1681878 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1681878 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 130 (0x00000082) THROTTLE1_SET
  14. I'm happy to paste in the .ini (below) but I figured pictures of my settings would be more informative than me trying to describe them and you could see what they are easily. No, I'm not confusing myself. And it's completely regular. I've tried quite a number of times, and there is never a departure. Moving Axis#X always triggers Axis#Y and moving Axis#Y always triggers Axis#X. If I open up FSUIPC and move axis #X, axis#Y appears in the windows and moving axis#Y changes the values. Moving axis#Y always makes axis#X appear in the windows and moving axis#X after that changes the values. The changes are smooth, without any appearance of jitter (in other words, the values change smoothly and do not change after I stop moving the axis....it's a fairly new quadrant). This seems to have no effect on operation in the sim except for possibly the Dodo. Here's the .ini. I'll try the other things you suggest when I get home from work. I am reading the manual, but don't always understand its instructions. The interface is not always intuitive, but I'm working at it. ---------- [General] UpdatedByVersion=4853 History=YAM4VJNVSVU9HAIOXG9UB AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=Yes WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No OOMcheck=Yes InitDelayDevicesToo=No MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=Yes EnableMouseLook=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 1=CH Pro Pedals USB 1.GUID={3F04E780-F054-11E0-8005-444553540000} 2=CH Throttle Quadrant USB 2.GUID={42699650-F054-11E0-8008-444553540000} 3=Pro Flight Cessna Trim Wheel 3.GUID={A2BCFFB0-624B-11E1-8001-444553540000} 0=T.16000M 0.GUID={4A54B3D0-31DE-11DF-8001-444553540000} [WideServer] WideFSenabled=Yes [sounds] Path=D:\MyGames\FSX\Sound\ Device1=Primary Sound Driver Device2=Headphones (High Definition Audio Device) Device3=Digital Audio (S/PDIF) (High Definition Audio Device) Device4=Speakers (High Definition Audio Device) Device5=Digital Audio (HDMI) (High Definition Audio Device) [Window.VAFS Message:] Docked=405, 3449, 3514, 2428 [buttons] ButtonRepeat=20,10 1=P2,14,CL2:T,2 2=P2,12,CL2:T,1 3=H2,3,K45,8 [MacroFiles] 1=4X_DA20-100 2=Meggitt2100 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [LuaFiles] 1=PMDG_J41_CP 2=ThrottleManager [Profile.J41] 1=PMDG Jetstream 41 Origin Pacific [Keys.J41] 1=74,11,L1:R,0 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Throttle1=-16384,-512,512,16383/32 Throttle2=-16384,-512,512,16383/32 SyncSlopeThrottle2=20/21,41/41,63/63,71/71,92/91,101/100,117/115 MapThr12to34=Yes [Auto] 2=Lua ThrottleManager [Axes] 0=2X,256,D,9,0,0,0 1=2Y,256,D,10,0,0,0
  15. What appears to be happening is that a signal is sent when the axis is moved to set the power corresponding to the amount of movement but then when the axis stops moving, a signal is sent to set the power to 0. This results in the power jumping around while moving the axis (which it shouldn't, since moving the axis should result in a smooth application of power) and then down to 0 again (actually 30 % on the gauge, which is zero power input) when I stop moving the axis, always ending with the power at 0. I'm assigning the axis in FSUIPC as I said, and I have deleted that axis in FSX. I have "Send direct to FSUIPC" option checked. Here's my settings: I'm using 4.853. I just bought it a few weeks ago. I've tried different settings in FSUIPC. The response is always the same. So far, it is specific to this helicopter, but I haven't been able to find the problem occurring for anyone else using FSUIPC and the Dodosim, and I have found info on the internet where people are using FSUIPC and this aircraft and not having any problems, so I think this is a problem with my specific install, and since the Dodosim works perfectly (and always has) with FSX controlling the throttle axis, I think it must be something I'm doing wrong in FSUIPC. And there is a weirdness that I'll explain now, but the thing is that all my other aircraft work perfectly fine, including the Huey helicopter (I don't have a lot of helicopters). The weirdness is that when I open up FSUIPC and click on the Axis Assignment, it's usually not blank. Instead it usually says this: I've not assigned this axis, and don't know what Axis# R even is. If I close it and open again, it sometimes says the same thing except Axis# V or Z. This may simply indicate that FSUIPC is registering one of my other axes as having moved. The really weird part is that if I open FSUIPC and the Joy# and Axis# fields are blank, and I move Axis X (Throttle 1), then it puts Axis#Y in the fields and registers the movement of that axis (Throttle 2). If I move Axis Y, it puts Axis# X in the fields and registers the movement of Axis X. If I move any other axis on my 6 axis CH quadrant (none of which I've assigned in FSUIPC) when the fields are blank, then it registers Axis# X, usually, but sometimes axis# Y. If I hit rescan, it then registers whichever axis (X or Y I move correctly, although sometimes I have to hit rescan several times as it cycles through Axis# R or U or Z or whatever first. So, I think something is not right here, but I followed the steps from both the User Guide and PilotJohn's instructions for his Lua script exactly.
  16. I'm a new user of the registered version of FSUIPC. I've set up my throttles (and only my two throttle levers on my CH quadrant) through FSUIPC, deleting the assignments in FSX for those two levers. I did so in order to use the wonderful lua script by pilotjohn for reverse thrust provided here on the forum in user contributions. That works like a charm. I calibrated my two throttle axes as per the instructions in the user guide. Throttles work fine in all aircraft I have used so far, with the exception of the Dodo helicopter. In helicopters, throttle control in the aircraft is usually assigned to prop pitch, and the actual throttle axis controls the "collective." This works fine in my Aerosoft Huey, just as it should, but in the Dodo, trying to control the collective with the throttle axis produces very strange behavior. The power needle jumps around as I move the axis and the helicopter tries to lift off, but as I stop moving the throttle axis, the power drops to zero. This never happened when throttle axes were assigned in FSX. It appears that there is something being recognized when I move the throttle (collective), but something is not right. I can make the helicopter take off by constantly moving the throttle axis up near the top of its range, and I can make the helicopter descend again by constantly moving the throttle axis near the bottom of its range. In other words, by constantly jiggling the axis, I appear to be sending signals to the sim that the Dodo recognizes. But as soon as I stop moving the axis at any point in its range, the signals seem to stop and the power returns to idle. I'm really hoping there is a way to resolve this issue with the Dodo. I've searched and can't find any info on others having this problem. I would hate to have to revert to FSX control, since the lua script for reverse thrust is a god-send for my turbo-props. But I can't give up flying the Dodo!
  17. Just came across this, and gave it a try. Fan----tastic! Finally, reverse thrust that works individually for each throttle and is infinitely adjustable! Thanks so much for this script!
×
×
  • 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.