Jump to content
The simFlight Network Forums

metzgergva

Members
  • Posts

    186
  • Joined

  • Last visited

  • Days Won

    1

metzgergva last won the day on December 16 2023

metzgergva had the most liked content!

About metzgergva

  • Birthday 10/03/1953

Profile Information

  • Gender
    Male
  • Location
    Gland, Switzerland
  • Interests
    aviation, flightsimulation

metzgergva's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

2

Reputation

  1. Hi, I would like to understand the specific differences between the two possibilities to assign a throttle axis to a hardware lever. I used to use "Throttle1", but learned in the documentation about "Axis Throttle 1" as the more modern way? Before I change my various assignments, i would like to understand if it is worth the effort. Thank you
  2. Hello Peter, I have checked the registry and the cause is that I had decided to use the same folder name F:\P3D for the install of Version 2 than what was used for my install of V1.4. This is not the default name, but I did not expect to cause problems. I do not recall if ....\P3D was the default root folder for V1.4.
  3. Thank you ver much Pete for finding the problem. Though I actually did use the uninstall function to delete P3DV1.4, this may not have cleaned up the registry properly. But now I know where to look due to your valuable help. Thank you!
  4. Everthing runs correctly. I do not get an error message when it istalls the FSX version, then when it tries to install into P3D 1.4, I get the expected message as I don't have that installed. When it tries to install into P3D it works, never the less this error message appears. Maybe this has something to do with the location and folder I use. P3D is installed in F:\P3D\. I paste the whole log file now: Installer for FSUIPC4.DLL version 4.924a Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\ESP Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" ... >>> OK! FOUND Prepar3D! <<< ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... =========================================================== INSTALLATION FOR FSX: SetupPath="D:\FSX\" Checking version of the FSX EXE: ... Version 10.0.61472.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:\FSX\Modules\FSUIPC4.DLL ... Version 4.924a found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "D:\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Alexander M. Metzger\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Alexander M. Metzger\AppData\Roaming" Found FSX.CFG in "C:\Users\Alexander M. Metzger\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 ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. 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\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 "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay =========================================================== INSTALLATION FOR Prepar3D: SetupPath="F:\P3D" Checking version of the Prepar3D EXE: ... Version 2.0.9448.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) 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:\P3D\Modules\FSUIPC4.DLL ... Version 4.924a found. Prepar3D Modules folder already exists. Okay -- installed FSUIPC4 into "F:\P3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Alexander M. Metzger\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one Looking in "C:\Users\Alexander M. Metzger\AppData\Roaming" ... No Prepar3D.CFG there 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\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. =========================================================== INSTALLATION FOR Prepar3D v2: SetupPath="F:\P3D\" Checking version of the Prepar3D v2 EXE: ... Version 2.0.9448.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) 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:\P3D\Modules\FSUIPC4.DLL ... Version 4.924a found. Prepar3D v2 Modules folder already exists. Okay -- installed FSUIPC4 into "F:\P3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Alexander M. Metzger\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one Looking in "C:\Users\Alexander M. Metzger\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Alexander M. Metzger\AppData\Roaming\Lockheed Martin\Prepar3D v2\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\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\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 "SimConnectP3D2.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 "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay =========================================================== All installer tasks completed. Registration check for FSUIPC4 was successful! (result code 00) *************** End of Install Log ***************
  5. Hello Peter, I reopen the threat on an error message that I get when I install the latest version (just like the ones before). See attached screenshot Here ist the P3DV2 part of the install.log INSTALLATION FOR Prepar3D v2: SetupPath="F:\P3D\" Checking version of the Prepar3D v2 EXE: ... Version 2.0.9448.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) 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:\P3D\Modules\FSUIPC4.DLL ... Version 4.924a found. Prepar3D v2 Modules folder already exists. Okay -- installed FSUIPC4 into "F:\P3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Alexander M. Metzger\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one Looking in "C:\Users\Alexander M. Metzger\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Alexander M. Metzger\AppData\Roaming\Lockheed Martin\Prepar3D v2\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\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\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 "SimConnectP3D2.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 "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay =========================================================== All installer tasks completed. Registration check for FSUIPC4 was successful! (result code 00)
  6. Hi, I could overcome the problem of the wrong sequencing when switching from OFF to RIGHT to LEFT to BOTH and the engine dying from RIGHT to LEFT by activating the repeat function on the LEFT position. By that the "delayed" OFF from releasing the RIGHT button is immediately overwritten by the repeated LEFT command. Thanks again!
  7. Thank you Pete. Need to check if this is the same behaviour on all four switches and then will check your suggestion on "Compound button conditions".
  8. Sorry it took some time to check things out. My magneto switch has closed contacts for position Right-Left-Both and no contact for Off. I have turned magneto switch engine 1 in the following sequence: BOTH-LEFT-RIGHT-OFF-RIGHT-LEFT-BOTH The USB interface is "Joystick 0" and the buttons are: BOTH = Button 0 LEFT = Button 21 RIGHT = Button 20 OFF = Button not assigned So I checked the logging and this is the content: I added comments in color as the first part seem to work correct but switching back from OFF to BOTH there are actions missing and in wrong sequence??? The engine died during the secon phase. ********* FSUIPC4, Version 4.853 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=667B0000 User Name="Alexander M. Metzger" User Addr="alexander@metzgergva.de" FSUIPC4 Key is provided WideFS7 Key is provided 593 System time = 23/04/2013 21:51:00 624 FLT UNC path = "\\AMM4\Users\Alexander M. Metzger\Documents\Flight Simulator X Files\" 655 Trying to connect to SimConnect Acc/SP2 Oct07 ... 655 FS UNC path = "\\AMM4\FSX\" 905 LogOptions=00000000 00000001 905 Wind smoothing fix is fully installed 905 G3D.DLL fix attempt installed ok 905 SimConnect_Open succeeded: waiting to check version okay 905 Trying to use SimConnect Acc/SP2 Oct07 13946 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 13946 Initialising SimConnect data requests now 13946 FSUIPC Menu entry added 13993 \\AMM4\Users\Alexander M. Metzger\Documents\Flight Simulator X Files\LSGG_HP-RWY05.FLT 13993 \\AMM4\FSX\SimObjects\Airplanes\Lockheed_L1049_SCFA\L1049_v2.7_sim.AIR 15350 System time = 23/04/2013 21:51:15, Simulator time = 11:47:36 (09:47Z) 15350 Aircraft="Lockheed C-121C SCFA Breitling" 48407 Starting everything now ... 48407 Using "C:\Program Files (x86)\GoFlight\GFDEV.DLL", version 2.2.1.0 48407 GoFlight GF46 detected: 1 device 48423 AES Link established 49608 Advanced Weather Interface Enabled 134551 LogOptions changed, now 40000000 00000001 140760 Button changed: bRef=0, Joy=0, Btn=0, Released ==>BOTH released 140853 Button changed: bRef=0, Joy=0, Btn=21, Pressed ==>LEFT active 140853 [buttons] 30=P0,21,C65929,0 140853 FS Control Sent: Ctrl=65929, Param=0 142398 Button changed: bRef=0, Joy=0, Btn=21, Released ==>LEFT released 142398 Button changed: bRef=0, Joy=0, Btn=20, Pressed ==>RIGHT active 142398 [buttons] 42=P0,20,C65928,0 142398 FS Control Sent: Ctrl=65928, Param=0 143646 Button changed: bRef=0, Joy=0, Btn=20, Released ==>RIGHT released (switching to OFF) 146157 Button changed: bRef=0, Joy=0, Btn=20, Pressed ==>RIGHT active (switching from OFF to RIGHT) 146157 [buttons] 42=P0,20,C65928,0 146157 FS Control Sent: Ctrl=65928, Param=0 147452 Button changed: bRef=0, Joy=0, Btn=21, Pressed ==>LEFT active (now this is strange as RIGHT release should have come first but shows up later) 147452 [buttons] 30=P0,21,C65929,0 147452 FS Control Sent: Ctrl=65929, Param=0 147452 Button changed: bRef=0, Joy=0, Btn=20, Released ==>RIGHT released (RIGHT active is missing in sequence) 148778 Button changed: bRef=0, Joy=0, Btn=0, Pressed ==>BOTH active 148778 [buttons] 29=P0,0,C65930,0 148778 FS Control Sent: Ctrl=65930, Param=0 148778 Button changed: bRef=0, Joy=0, Btn=21, Released ==>LEFT released (this should have come when switching from LEFT to RIGHT higher up and RIGHT active is missing at all) 199759 Sim stopped: average frame rate for last 63 secs = 57.8 fps 205375 LogOptions changed, now 00000000 00000001 228495 System time = 23/04/2013 21:54:48, Simulator time = 11:49:00 (09:49Z) 228495 *** FSUIPC log file being closed Average frame rate for running time of 81 secs = 56.9 fps G3D fix: Passes 9941, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 205 Allocs, 205 Freed ********* FSUIPC Log file closed ***********
  9. Thank you Peter for your support. I will check this out on my side too. If these errounous sequences occur, it will be a challenge to find a way to get it right. As said, on the default DC-3 I have seen the same than in my Constellation Sim. We'll find it.
  10. I have veryfied a couple of times what showes in FSUIPC when I actuate the switch. I have not looked into lgging. My un derstanding is that the switch is working like a regular switch, so that the contact is closed when in the LEFT, RIGHT, BOTH position. But I can veryfy that in the controls setup of the USB digital card. Will look into this next weekend. Thank you for the tip!
  11. Hello Pete. Setup is FSX PC for running FSX and a slave PC for running the gauges and switches in the panel. FSUIPC4, Version 4.853 I have an original rotary magneto switch for each engine (4). The position clockwise is OFF-RIGHT-LEFT-BOTH (which is a bit strange I know) . As the OFF position is not a contact, I have tried the following assignment for engine 1 when controll is pressed: BOTH - MAGNETO1 BOTH LEFT - MAGNETO1 LEFT RIGHT - MAGNETO1 RIGHT In addition on RIGHT - MAGNETO1 OFF when releasing the button, so that when I go to OFF the engine would die, and when I go to LEFT the MAGNETO1 OFF command will be immediately overwritten bei MAGNETO1 LEFT and the engine should continue to run. Now unfortunately whenever I go on position RIGHT, the engine dies. So I have deleted the additional assignment, but it does not help. If I go from BOTH to LEFT the engine continues and I can see in the original FSX engine panel that the switch there is switching correctly to LEFT. Once I go further to RIGHT, the engine dies and I can see that in the orignal panel the magneto switch jumps to OFF. So I thought maybe a problem with that aircraft panel and loaded the default DC-3 and same result: Selecting MAGNETO to RIGHT the magneto switch in the panell changes to OFF. This is the same for all 4 engines (2 on DC-3). Hope you have an idea where to look for the solution.
  12. Thank you Pete for those hints. As a developer, I try to live with the standards that FS provides and your FSUIPC was considered as a standard for me. I try to avoid to use specific settings that the user of the aircraft don't have or would be complicated for them. On top all this all will cause much more support. Nevertheless I will try the first option with the button assignment and see if that helps. Just by using your described example values I should get a much finer resolution (0.1° vs 0.6° based on a total +/-15° deflection - more just looks bad on the trim flap) and I can post that in the aircraft user manual if users have a problem with the trim control speed. I belive the whole thing comes from internal cycle calculation in FS which with the new powerful computers just run faster. I can see that the single step did not change and on my slow laptop it is still ok but on the high speed PC the trim just runs too fast. W'll see what is the best solution. Edit: I have implemented the trim as per your instructions and it works now perfectly. I used 128/16383 as parameter to have a really nice running electrical trim, Advantage is it keeps the speed and does not accelerate further the longer you press. Great! Thanks!
  13. Well than I need to look for that. Just giving the recomendation to hav "Fix control acceleration" set to ON helped me through the years when people were complaining about electrical trim responsiveness of "my" planes. Explaining them the proposed option might be more difficult, but I will check it out. Thank you for your very quick response.
  14. "Fix control acceleration" was used by me all times as it slowed down the repeat rate for example on elevator trim. I'm using a CH yoke. FS internal smallest trim step is 0.6° and by playing with the total degrees for trim tarvel, it was possible to adjust trim travel time within certain limits and meeting electrical trim specs on aircrafts. Now since I'm on a newer computer and Win7, I see that it is basically impossible with the trim acceleration in Fs9 or FSX set to medium (the position always used) to get a single click movement. Switching Fix control acceleration on or off just does not have an influence anymore. Is it something eliminated by chance? And could it brought back into life?
×
×
  • 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.