LabFaca Posted November 26, 2018 Report Share Posted November 26, 2018 Dear Sirs, I assemble a simulation setup with Sismo panels and commands based on a BU836A board. Currently Windows 7 Professional, FSX SE, Prosim 1.56B and FSUIPC4, Version 4.974 are used as software. It had the BU836A board disabled in FSX and the analog axes calibrated by the "FSUIPC Calibration". At first it worked without problems. Last week I noticed that when the prosim is activated, the commands coming from the BU836 Card are recognized by FSUIPC4, but stop being forwarded to FSX. If you enable the recognition of the BU836 Card in FSX, the commands work. I tested it with a Microsoft Joystick instead of the BU836 Card and the result does not change. I tested the BU836 Card on another CPU with a unique Microsoft FSX in conjunction with FSUIPC4 and ProSim and the Set works through the "FSUIPC Calibration" Option and disabled the Joystick in FSX. I made an installation of the operating system, FSX, FSUIPC and ProSim, with the minimum resources needed to test the commands (in conjunction with the Microsoft Joystick) and the result remains the same. The new installation decided to carry out, as in the former had performed several experiments with other applications and had even installed the Elise-NG Fly Software and had doubts if there was something interfering in the operation of the simulation setup. Attached are the logs generated by the software that I installed after the last installation. I've also activated some more logging options. I will post this question also in the ProSim support forum, but I would like to hear from you about what might have happened and if there is something to be corrected, as I may have changed some configuration. Appreciate your attention. Best Regards Maury Maia FSUIPC4 Install.log FSUIPC4.DLL FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log FSUIPC4_prev.log SimConnect0.Log WideServer.log WideServer0.log (PS)config.xml (PS)log.txt (PS)rlm1202.dll (FSXSE)dll.xml Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 26, 2018 Report Share Posted November 26, 2018 1 hour ago, LabFaca said: I tested it with a Microsoft Joystick instead of the BU836 Card and the result does not change. The files you attached (and you should not really send me my own DLL!) show only a Microsoft SideWinder attached, which is recognised properly, and you have just one assignment for it, the elevator, assigned "Direct to FSUIPC": [JoyNames] AutoAssignLetters=No 0=SideWinder Precision 2 Joystick 0.GUID={357959C0-EF44-11E8-8003-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=0Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- You have no buttons assigned and no other axes. The log confirms this device was seen, and subsequently you moved the axis and the movements were also seen and acted upon: 202 ---------------------- Joystick Device Scan ----------------------- 218 Product= SideWinder Precision 2 Joystick 218 Manufacturer= Microsoft 218 Vendor=045E, Product=0038 (Version 1.8) 218 GUIDs returned for product: VID_045E&PID_0038: 218 GUID= {357959C0-EF44-11E8-8003-444553540000} 218 Details: Btns=8, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X255,Y255,Z255 218 ------------------------------------------------------------------- 218 Device acquired for use: 218 Joystick ID = 0 (Registry okay) 218 0=SideWinder Precision 2 Joystick 218 0.GUID={357959C0-EF44-11E8-8003-444553540000} 234 ------------------------------------------------------------------- 18517 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -8639 (0xffffde41) AXIS_ELEVATOR_SET 18579 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -11676 (0xffffd264) AXIS_ELEVATOR_SET 18642 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -10496 (0xffffd700) AXIS_ELEVATOR_SET 18704 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -7447 (0xffffe2e9) AXIS_ELEVATOR_SET 18767 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -3295 (0xfffff321) AXIS_ELEVATOR_SET 18829 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -96 (0xffffffa0) AXIS_ELEVATOR_SET 18891 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 3419 (0x00000d5b) AXIS_ELEVATOR_SET 18954 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 6965 (0x00001b35) AXIS_ELEVATOR_SET 19016 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 10047 (0x0000273f) AXIS_ELEVATOR_SET 19079 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 12433 (0x00003091) AXIS_ELEVATOR_SET 19141 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 14429 (0x0000385d) AXIS_ELEVATOR_SET 19203 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 15346 (0x00003bf2) AXIS_ELEVATOR_SET 19266 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 15768 (0x00003d98) AXIS_ELEVATOR_SET 19328 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 15478 (0x00003c76) AXIS_ELEVATOR_SET 19328 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 14905 (0x00003a39) AXIS_ELEVATOR_SET 19391 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 14170 (0x0000375a) AXIS_ELEVATOR_SET 19453 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 11633 (0x00002d71) AXIS_ELEVATOR_SET So what really is the problem? You don't really seem to have described it. Pete Link to comment Share on other sites More sharing options...
LabFaca Posted November 26, 2018 Author Report Share Posted November 26, 2018 Dear Mr. Dowson, The first set of logs was generated after the full reinstallation of all software relevant to the situation.I only left the "SideWinder Precision 2" connected and only one axis (elevator) for testing purposes. When the prosim is activated, FSX no longer receives information about the position of the elevator, and when ProSim is disabled, FSX will receive the information normally. The axis related to the elevator was moved from the activation of the FSX, through the activation of the ProSim and its disengagement and shutdown of the FSX. During the period that the prosim is active, if we enable the reading of the joystick in FSX, without going through the FSUIPC4, there is no problem. I've attached a new log, without the DLL, and without the SimConnect log, the problem may be clearer. Best regards Maury Maia FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log FSUIPC4_prev.log WideServer.log Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 26, 2018 Report Share Posted November 26, 2018 12 minutes ago, LabFaca said: When the prosim is activated, FSX no longer receives information about the position of the elevator, and when ProSim is disabled, FSX will receive the information normally. Ah, so this is not an FSUIPC question, but a ProSim one! I use ProSim 2.08 at present, and that works for me with the main control axes assigned in FSUIPC, not in ProSim. But that it because my controls are PFC serial port ones and not seen by ProSim. I think ProSim folks do advise that you assign and calibrate in ProSim itself. 15 minutes ago, LabFaca said: I've attached a new log, without the DLL, and without the SimConnect log, the problem may be clearer. I don't really want to look at logs which are clearly not really relevant when you've already identified your problem. However, a brief glance shows it to be virtually identical to the previous one, so my previous comments apply. It is perfectly possible for any FSUIPC application to prevent control axis inputs reaching the Sim. This is done by systems programs like ProSim in order to properly simulate the various subsystems. If you think this is not operating correctly in ProSim, then it is to their Forum you need to report. Pete Link to comment Share on other sites More sharing options...
LabFaca Posted November 26, 2018 Author Report Share Posted November 26, 2018 Thanks! Maury Link to comment Share on other sites More sharing options...
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