Jump to content
The simFlight Network Forums

cellular55

Members
  • Posts

    303
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by cellular55

  1. Hi, VRSIM is the VRInsight tool that discovers the devices (like as the initial tool SerialFP2) I have updated WIN10, but this almost one month ago and until few days ago I did not have any trouble. The strange is that some few times the devices are seen, but most of the times no. In the log I have attached it seems that the COM ports are opened but there are some strange messages about the disconnection/the lost of VRSim.exe The two devices are on COM5 and COM6 (and that is visible also in the WIN CP) In FSUIPC I have: [VRInsight] 1=COM6, COM3 2=COM5, COM7 and in VSPE the pairs: COM2 <=> COM3 COM4 <=> COM7 Thanks Joe
  2. Hi, since some days I'm facing issues connecting 2 VRI devices (MCP and CDU I) using VRSIM and VSPE Those were running correctly until some weeks ago, now even if connected and having changed nothing in the config, the devices are most of the times not found and not properly running (other few times they connect and run normally). It seems a sort of random issue. Do you have any idea about what could be the trouble. Attached the FSUIPC extended log. I'm using P3D 4.5 Hot Fix 3 and FSUIPC 6.0.8. Thanks and Kind Regards Joe FSUIPC6.log
  3. Hi, thanks a lot for the advise. I will wait for the fix. KR Joe
  4. HI, I'm trying to use the offset in one app I'm building to manage the PMDG 747 v3. It seems that the offsets listed in the documentation to manage Landing Lights (6506) and Taxi Lights (6510) are not set as expected. Also using the FSUIP logging when I turn on or off the lights the value for these offsets is always 0. Most of other offsets seems to be fine. Suggestion about how is possible to solve this issue? Thanks and KR Joe
  5. Hi, thinking to buy this bird, I would ask if SDK or offsets (to use with FSUIPC) are present. Thanks and KR Joe
  6. Hi Peter, I had finally time to test and I can confirm that doing what you suggested allows to solve the issue and have all program running without any problem. Thanks and KR Joe
  7. Hi, is there a way to execute the programs listed in the 'Programs' section as Administrator? Since when I have installed Win10 no one of them runs correctly as it's required to have them launched as admin. Thanks and KR Joe
  8. Hi, thanks a lot for the reply. Thanks to that i have solved the issue and adjusted the assignments... I have to check the rudder: I should not have throttle control there To delete the trim have I to remove these lines? L=Pro Flight Cessna Trim Wheel L.GUID={4F45C0A0-7B6A-11E6-8001-444553540000} K=<< MISSING JOTSTICK >> Thanks and KR Joe
  9. Sorry I forgot a file.. attached here FSUIPC5.JoyScan.csv
  10. Hi John, thanks for the prompt reply. Attached the file, in the mean time I will llok at the manual. KR Joe FSUIPC5_log.txt fsuipc5.ini
  11. Hi, planning to install P3D 5 I have updated Windows 7 with Windows 10- Everything seems to be fine with the exception of Joy names in FSUIP5.ini. Joys names have been messed up: buttons that were mapped on a device are now mapped on another and so on (I have 4 of them so really a mess). Is there a way to easily map all them to the original situation? Thanks and kind regards Joe
  12. Hi, thanks, but it seems that is not the right way. Reading that offset I get the FSUIPC log if I am showing it on the screen, but not the msg of the CDU KR Joe
  13. Hi, is there a way to read the CDUs MSG of PMDG 777X? I have found the var and the offset to intercept if a MSG is present, but not how to read the real content. Thanks and KR Joe
  14. Hi Pete, Thanks a lot!!!!! Always a great support. Joe
  15. Hi Pete, thanks for the usual fast replay! I have already filled also the Project Magenta offsets and I'm already using multiple values for several used offsets. Main new purpose for the request is that i would try to experiment and use D70 offset (I would build automated cockpit for aircrafts not using offsets/controls, but local variables) and I see that for that i need space for at least one Double/Float offset. To have an additional space of 64 bytes could be perfect. Thanks again Joe
  16. Hi, for some apps I have written I'm using for my purposes all the available free offsets between 66C0 - 66FF adressess. Are there some other possible offset addresses that can be used for general purposes? Thanks and KR Joe
  17. Hi, Thanks a lot for the support and help!!!!! KR Joe
  18. Hi, I have just realized that I'm no more able to have on the P3D screen the values of the offsets I have selected in the logging screen of FSUIPC. As usual I have flegged the FS Window check bos , but the values are not showed. Any possible reason for that? I use P3D 4.51 and FSUIPC 5.152. Thanks and Kind Regards Joe
  19. Hi Pete, sorry to have bothered you for a stupid my mistake: I was forgetting that I had already programmed those buttons in the FSUIPC profile for my PMDG737. It is evident that the profile was utilised and the new general asignment was not considered. Sorry again and kind regards Joe
  20. Hi, attached another log where appears more clear that the button is intercepted but is still executing the original PMDG control for the L1 button of the CDU instead the change of the ofset that I have forced in FSUIPC. FSUIPC5.log
  21. Hi Pete, Correct. What I have done: I have created on VSPE the pair COM2 - COM3 After the launch of P3D I have launched the VRSIM (and also tried launching the old SerialPF2). The CDU device appears on COM6. i activate the VRInsight driver (With the VRInsight profile keymap of the loaded aircraft) In FSUIPC i click the button I want to be assigned to set the offset 66EA to 1 and define the assignment like I do normally buttons on other devices. I do not know if this is important, but the joystick name and number button are shown in FSUIPC only when I activate the function FMC/CDU on the VRInsight device (clicking on the EXEC button of the device) After that when I click the button the screen of the VRINsight device changes but the offset is still at 0. As asked attached the log Thanks for the support Joe FSUIPC.log
  22. Hi, I'm trying to use the VRInsight CDU Device with FSUIPC to set values of some offsets (i.e 66EA set to 1). For that I have followed the instructions in the advanced manual using VSPE. Even if seems that everything is OK and I see the joystick buttons enumerated in the FSUIPC interface, the value of the offset is not changing. Below the log entries that I think could be useful : VRI port 1 "COM6" opened (this is the port appearing in the VR software: VRI or SerialPF2) 1435 VRI driver port 1 "COM3" also opened (this is the port part of the pair in VSPE: COM2, COM3) ..... ...... 171195 VRI COM6 <--- CMDRST [to Device] 171398 VRI COM6 <--- CMDCON [to Device] 171429 VRI COM3 <--- CMDCON [to VRI Driver] 171585 VRI COM6 <--- CMDFUN [to Device] 171601 VRI CDU ("CDU") detected on port COM6 171601 VRI COM3 <--- CMDCDU [to VRI Driver] 171803 VRI COM6 <--- CMDVER [to Device] 171850 VRI COM3 <--- CMD2.520 [to VRI Driver] 189432 WRITE0[4616] 330A, 2 bytes: D2 07 .. 192942 Deactivated for PID=2072, "explorer.exe" 197668 ### Mode is NORMAL ... .... 206202 VRI command CDUR4C0 trapped as Joy 266 Btn 3 Toggle ( device button clicked to try to set to 1 the offset 66EA) 229571 VRI command CDUR4C0 trapped as Joy 266 Btn 3 Toggle 230148 VRI command CDUR4C0 trapped as Joy 266 Btn 3 Toggle 230694 VRI command CDUR4C0 trapped as Joy 266 Btn 3 Toggle 231131 VRI command CDUR4C0 trapped as Joy 266 Btn 3 Toggle 231567 VRI command CDUR4C0 trapped as Joy 266 Btn 3 Toggle What am I missing or eventually is not possible to address offsets valus in this way? Thanks and Kind Regards Joe
  23. Hi Pete, yes.. all the HUBs are powered. I think taht is a problem of some connector entries: more or less the devices going disconnected are the same. Unplagging and repulugging they get back the connection. and yes .. you are right: I do not know how Windows manages that, but I have noticed that If I add a new device (even if not related to P3D) and I change the HUB connector entry of one P3D device the GUIDs change (I did that adding those lights). KR Joe
  24. Hi Pete, I will try to explain a little more and in detail. The devices are identical in the sense that the issue occurrs always on the devices on the USB HUBs. No problem with the joke, rudder pedals and the two serial devices (MCP and CDU). Issue1: Device disconnected If I launch P3D no checking before if all the devices installed on different USB HUBs are connected and one of them is disconnected (may be the connectors on hubs are not so good) I do not have only the command disappearing on the disconnected devices, but its commands move on another device connected on another Hub substituting the original assignment. In this case I have found that is enough to close P3D and relaunch it being sure that all the connections are ok (I have written a tool to check that) and everything is back to nornal. Issue 2: Adding new connection on HUB This is an issue stranger and harder as the only solution I have found until now is to manually reassign the commands on the impacted devices as they were before. This occurred for example when I added, through one existing HUB, some LED lights to illuminate the cockpit devices: after that, commands on two devices (one on the same HUB where I installed the light and another on a differen HUB) were swapped. Hope this helps to clarify. KR Joe P.S. Yes.. I disconnected the Cessna wheel and did not update the conf file
×
×
  • 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.