JB77W Posted October 21, 2020 Report Posted October 21, 2020 Hi, New user to FSUIPC and flight simulation. Thanks for a great product and support. I apologise in advance for my unfamiliarity with a lot of the technical computer terms as it's a very steep learning curve. I have consulted the forums and various tutorials but am unable to find a resolution to my issue. Windows 10 new build PC LINDA 3.2.6 for P3D 64-bit FSUIPC 6.1.0 Registered Module PMDG 777 version 1.5a P3D v4.5.14.3 PMDG 777X VRinsight MCP Combo II Boeing, Flightsim PM 777 V2 Throttle quadrant. I have been trying to assign and calibrate the Flightsim PM throttle quadrant. The issues I have had are as follows: When trying to calibrate the separate throttle per engine, throttle 2 assigns fine and moves through the full range of values from -16231 to 16375. Throttle 1 detects the max and fully closed throttle values but does not incrementally change up or down? I have tried this numerous times and the throttle unit itself tests fine using the windows calibration software. Throttle 2 operates normally in the aircraft where 1 does not move at all. When trying to assign the individual detents for the 777 flap, FSUIPC will set flaps up, detent 1, detent 2 and flap 30, but will not allow me to assign the range for the other detents. When trying to replicate this issue to describe for this email, the flap lever is now not recognising any movement of the flap lever to the various detents and their corresponding values. I would appreciate any advice you can provide to resolve these issues. Thanks, John Barwood FSUIPC6.JoyScan.csv FSUIPC6.log
Pete Dowson Posted October 21, 2020 Report Posted October 21, 2020 34 minutes ago, JB77W said: When trying to calibrate the separate throttle per engine, throttle 2 assigns fine and moves through the full range of values from -16231 to 16375. Throttle 1 detects the max and fully closed throttle values but does not incrementally change up or down? I have tried this numerous times and the throttle unit itself tests fine using the windows calibration software. This is a problem mostly experienced by Saitek Throttle users, but can occur with others. It's a bad registration by Windows. Please see this thread in the FAQ subforum: Fixing problems with 50% (or digital on/off) action with Saitek levers 36 minutes ago, JB77W said: When trying to assign the individual detents for the 777 flap, FSUIPC will set flaps up, detent 1, detent 2 and flap 30, but will not allow me to assign the range for the other detents. Is this with the 777 loaded? If so, how many flap positions does FSUIPC display in the field "No. of detentes"? It gets this information from SimConnect for the specific aircraft when it is loaded. I see you are using LINDA, and the Log is almost all LINDA -- stuff I've no knowledge of at all. You may need LINDA support as I don't know what it might be doing. Pete
JB77W Posted October 21, 2020 Author Report Posted October 21, 2020 Hi Pete, Thanks for the quick reply. That's great i'll follow that fix, thank you. Yes, correct with the 777 loaded. The detents displayed in FSUIPC is correct at 7 with the loaded PMDG 777. I have already started a topic on Linda's support regarding the issues i'm having. Appreciate your help John
Pete Dowson Posted October 21, 2020 Report Posted October 21, 2020 39 minutes ago, JB77W said: Yes, correct with the 777 loaded. The detents displayed in FSUIPC is correct at 7 with the loaded PMDG 777. So I'm sure FSUIPC will allow you to set 7 zones. It is that count it uses. Perhaps you need to explain why you cannot in more detail? Without worrying about the detentes, can you achieve all of the positions by moving the lever. or not? Pete
JB77W Posted October 21, 2020 Author Report Posted October 21, 2020 Hi Pete, I followed the fix. It worked.....until I activated the reverse thrust lever which i think is button 5 and the neither the no.1 throttle lever or reverser lever will work. Each time I go back and change the registry it keeps reverting if I do this. The file appears to be VID_06A3 in the HKEY_Current_User. John
Pete Dowson Posted October 21, 2020 Report Posted October 21, 2020 12 minutes ago, JB77W said: .until I activated the reverse thrust lever which i think is button 5 and the neither the no.1 throttle lever or reverser lever will work. Each time I go back and change the registry it keeps reverting if I do this. Sorry, I've no idea how it is possible for the registry to be changed just by pressing a button. That is surely impossible, unless LINDA is doing it -- as i said I have no idea what LINDA does. Note, however, that PMDG aircraft do not like calibrated axis inputs. they seem to intercept the axis inputs at a conflicting level. Also, most folks with PMDG aircraft find the reversers only work correctly using THROTTLEn DECR assignments, repeating on a button, rather than any type of axis input. 16 minutes ago, JB77W said: The file appears to be VID_06A3 in the HKEY_Current_User. But according to your log you have these assignable devices: 94 Product= T.A320 Pilot 94 Manufacturer= Thrustmaster 94 Serial Number= 1 94 Vendor=044F, Product=0405 (Version 2.0) 94 GUIDs returned for product: VID_044F&PID_0405: 94 GUID= {E4093CE0-F8D3-11EA-8001-444553540000} 94 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 94 Product= T-Pendular-Rudder 94 Manufacturer= Thrustmaster 94 Vendor=044F, Product=B68F (Version 1.16) 94 GUIDs returned for product: VID_044F&PID_B68F: 94 GUID= {DED9A120-F76A-11EA-8002-444553540000} 94 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z65535 94 Product= Alpha Flight Controls 94 Manufacturer= Honeycomb Aeronautical 94 Serial Number= 6D323C1325153B00 94 Vendor=294B, Product=1900 (Version 0.33) 94 GUIDs returned for product: VID_294B&PID_1900: 94 GUID= {DED97A10-F76A-11EA-8001-444553540000} 94 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0 94 Product= BU0836-LC Interface 94 Manufacturer= Leo Bodnar Electronics 94 Serial Number= BZ0498 94 Vendor=16C0, Product=05B7 (Version 1.39) 94 GUIDs returned for product: VID_16C0&PID_05B7: 94 GUID= {A506C460-138E-11EB-8001-444553540000} 94 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U4095,V4095,X0,Y0,Z4095 See that none of the devices assignable in FSUIPC have a VID (Vendor ID) of 06A3 !!! Pete
JB77W Posted October 21, 2020 Author Report Posted October 21, 2020 7 minutes ago, Pete Dowson said: Sorry, I've no idea how it is possible for the registry to be changed just by pressing a button. That is surely impossible, unless LINDA is doing it -- as i said I have no idea what LINDA does. Note, however, that PMDG aircraft do not like calibrated axis inputs. they seem to intercept the axis inputs at a conflicting level. Also, most folks with PMDG aircraft find the reversers only work correctly using THROTTLEn DECR assignments, repeating on a button, rather than any type of axis input. But according to your log you have these assignable devices: 94 Product= T.A320 Pilot 94 Manufacturer= Thrustmaster 94 Serial Number= 1 94 Vendor=044F, Product=0405 (Version 2.0) 94 GUIDs returned for product: VID_044F&PID_0405: 94 GUID= {E4093CE0-F8D3-11EA-8001-444553540000} 94 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 94 Product= T-Pendular-Rudder 94 Manufacturer= Thrustmaster 94 Vendor=044F, Product=B68F (Version 1.16) 94 GUIDs returned for product: VID_044F&PID_B68F: 94 GUID= {DED9A120-F76A-11EA-8002-444553540000} 94 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z65535 94 Product= Alpha Flight Controls 94 Manufacturer= Honeycomb Aeronautical 94 Serial Number= 6D323C1325153B00 94 Vendor=294B, Product=1900 (Version 0.33) 94 GUIDs returned for product: VID_294B&PID_1900: 94 GUID= {DED97A10-F76A-11EA-8001-444553540000} 94 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0 94 Product= BU0836-LC Interface 94 Manufacturer= Leo Bodnar Electronics 94 Serial Number= BZ0498 94 Vendor=16C0, Product=05B7 (Version 1.39) 94 GUIDs returned for product: VID_16C0&PID_05B7: 94 GUID= {A506C460-138E-11EB-8001-444553540000} 94 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U4095,V4095,X0,Y0,Z4095 See that none of the devices assignable in FSUIPC have a VID (Vendor ID) of 06A3 !!! Pete I'm totally confused. The only other things that connect via USB, I don't believe would be assignable in FSUIPC. Any ideas where to go from here? John
Pete Dowson Posted October 21, 2020 Report Posted October 21, 2020 1 hour ago, JB77W said: I'm totally confused Why is that? Which of the above devices is actually your throttle? Couldn't you locate the correct entry in the Registry? 1 hour ago, JB77W said: The only other things that connect via USB, I don't believe would be assignable in FSUIPC. The only things which are assignable in FSUIPC are those listed in the log, see above, and in the INI file (which would be the same). Show me the INI file so I can se which of those you are using as Throttle in your assignments. Vendor 06A3 is Saitek. You have no Saitek devices listed as being connected! Pete
JB77W Posted October 22, 2020 Author Report Posted October 22, 2020 10 hours ago, Pete Dowson said: Why is that? Which of the above devices is actually your throttle? Couldn't you locate the correct entry in the Registry? The only things which are assignable in FSUIPC are those listed in the log, see above, and in the INI file (which would be the same). Show me the INI file so I can se which of those you are using as Throttle in your assignments. Vendor 06A3 is Saitek. You have no Saitek devices listed as being connected! Pete The BU0836-LC interface is the throttle. I have located the correct entry for this in both the Current User registry and Local Machine registry. The INI file is attached as requested. I previously used 2 saitek quadrants for testing but am not using them anymore. I have tried to delete the saitek drivers but unsure whether I have deleted them all. No Saitek devices have been connected since these issues occurred. Thanks for your help. John FSUIPC6.ini
JB77W Posted October 22, 2020 Author Report Posted October 22, 2020 Hi Pete, I have tested the throttle today and it works fine in P3D v4 with the QW787. I do not encounter the same issue with no.1 throttle and reverser. Not sure if this helps! John
Pete Dowson Posted October 22, 2020 Report Posted October 22, 2020 7 hours ago, JB77W said: The BU0836-LC interface is the throttle. It's very unusual for Bodnar devices to have anything wrong with the axis Registrations. 1 hour ago, JB77W said: I have tested the throttle today and it works fine in P3D v4 with the QW787. I do not encounter the same issue with no.1 throttle and reverser. So it's your PMDG configuring which doesn't suit their methods. Looking at the INI file, I see that you have set calibration for every axis, but have not actually calibrated any of them -- the values for calibration are all defaulted! So why bother? The assignments for the 777 are very strange indeed. You have multiple different (conflicting) assignments to both THROTTLE 1 and THROTTLE2 -- TWO to Thr 2 both on the Bodnar, THREE to throttle 1, one on the Bodnar, two on an unconnected device 2. [Axes.PMDG 777] RangeRepeatRate=100=1X,256,F,65821,0,0,0 -{ TO SIM: THROTTLE2_SET }- 1=1Y,256,D,12,0,0,0 -{ DIRECT: Throttle4 }- 2=1Z,256,F,65698,0,0,0 -{ TO SIM: FLAPS_SET }- 3=1R,256,D,22,0,0,0 -{ DIRECT: Spoilers }-4=1U,256,D,10,0,0,0 -{ DIRECT: Throttle2 }-5=1V,29151,D,9,0,0,0 -{ DIRECT: Throttle1 }- 6=1T,256,F,65760,0,0,0 -{ TO SIM: FLAPS_DETENTS_SET }- 7=2X,256,D,22,0,0,0 -{ DIRECT: Spoilers }-8=2Y,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }- 9=2Z,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- You've no FSUIPC assignments to ailerons and elevators, so I assume those are assigned in P3D. You likely have conflicting assignments if you haven't disabled controllers in P3D. either use FSUIPC or P3D for assignments, not both. mixing always gives problems! With PMDG aircraft it is best to use only the FS controls, AXIS_XXXX_SET, and not calibrating. Otherwise your results will not be completely predictable. If I were you i'd delete the PMDG 777 profile settings and do them again, trying to stick to those methods known to work with PMDG aircraft. There's been plenty written about this, especially here in the Forum. Pete
JB77W Posted October 23, 2020 Author Report Posted October 23, 2020 Hi Pete, That is strange. I will follow your suggestion and delete the 777 profile settings and start over. Is the easiest way to delete the INI file? Excuse my ignorance but can you elaborate a little on the FS controls AXIS_XXXX_SET? If you could point me in the right direction for discussions around this matter for PMDG aircraft, it would be much appreciated. In addition, I have been getting a strange message after I start P3Dv4. A popup box appears with "FSUIPC PROBLEM! The text is There seems to be duplicate copies of FSUIPC installed, or another running still in memory! This is probably because a previous Sim session did not terminate it properly. Use the windows task manager to check for this in its process list". When I go to the task manager processes, there's no FSUIPC listed? After clicking ok, there is another popup "SODE Warning...Another SODE process is still running in the background. Please kill the process in task manager and restart the sim". Thanks for your help. John
Pete Dowson Posted October 23, 2020 Report Posted October 23, 2020 10 hours ago, JB77W said: Excuse my ignorance but can you elaborate a little on the FS controls AXIS_XXXX_SET? If you could point me in the right direction for discussions around this matter for PMDG aircraft, it would be much appreciated. The PMDG coding appears to do things similar to FSUIPC, intercepting the regular Sim Controls (the ones the sim would assign if you used those) at a high level. FSUIPC offers those same controls for assignment (AXIS .... SET) and will send them to the Sim the same as if you'd assigned them in the Sim. So both parties should be happy. The problem then comes if you set calibration in FSUIPC. Then FSUIPC also traps the control it has sent, and puts it through the calibration to emerge changed accordingly, and that changes value it then sent f to the Sim at a different level. The two values processed for the same control can therefore conflict. Because of this, generally folks using PMDG aircraft are encouraged to assign all flight controls only to the FS "AXIS ..." controls and not calibrate. I know some folks have found ways through this restriction, but in general that's how you should start. Make sure everything works correctly that way before attempting things like calibration. For reversers, PMDG aircraft work best with button for "THROTTLE DECR", as I think you have. You could try the FSUIPC Reverser but just make sure you get the main controls working correctly first. Not sure what discussions you expect to have with PMDG. They usually don't want to know, just advising folks not to use FSUIPC. Pete
John Dowson Posted October 23, 2020 Report Posted October 23, 2020 10 hours ago, JB77W said: In addition, I have been getting a strange message after I start P3Dv4. A popup box appears with "FSUIPC PROBLEM! The text is There seems to be duplicate copies of FSUIPC installed, or another running still in memory! This is probably because a previous Sim session did not terminate it properly. Use the windows task manager to check for this in its process list". When I go to the task manager processes, there's no FSUIPC listed? Are you using the dll.xml install method (and not the add-on.xml method)? I ask as this is normally due to the dll method being used, with two entries for FSUIPC6. There was an issue with an earlier version of FSUIPC6 (before 6.0.8 I think) that failed to remove this entry in certain situations. Even though this has been corrected in the later installer, there can still be issues. Check your dll.xml file under ...\AppData\Roaming\Lockheed Martin\Prepar3D v5, and if there are two entries, remove one. If you are using the add-on.xml method, check that file (if it exits) to make sure that there are no entries for FSUIPC6. John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now