cellular55

Hi, I show the FPS through a networked app I wrote that uses Wideclient 7.14a and FSUIPC 5.124a on P3D 4.2 with the option UsePDK=Yes. I can confirm that the FPS shown are correct. KR Joe

Great! So something is moving.. I will wait for the new version. Thanks and kind regards Joe

Hi Peter, any new about this or idea by L-M when this will be possible again? Thanks in advance and kind regards Joe

Hi, if you go around only a little in the forum you will see that FSUIPC 5.123 causes issue with P3D42. For the moment, until Peter is back, you can try using FSUIPC 5.122. KR Joe

Hi Peter, thanks a lot for the prompt reply as usual. Let hope this will be solved soon. Kind Regards Joe

Hi Peter, I would know if with FSUIPC5 (ver 5.122a) there are limitations for the use of the 'event.textmenu' in LUA scripts. In fact I definitevely moved from FSX to P3Dv41, but a lua using that instruction (to have HIfi AS and GSX messages shown through Widefs to another PC and not in the simulator) correctly running in FSX is no more running in P3D (the messages are shown in the simulator and not intercepted by the LUA). I have in my FSUIPC.ini the line NewInterceptTextMenu=Yes and the log related the LUA under Widefs is only reporting that the LUA is normally launched and running. Thanks in advance and Kind regards Joe

Hi Peter, sorry.. it was my mistake. I was convinced to have cleand all the P3D control settings for all my devices, but it was not true: I had some doubled axis assignments (FSUPC and P3D controls) and those did the mess. Sorry to have bothered you with a not issue. KR Joe

Hi Peter, I'm facing issue to have the controls managed through axis in FSUIP5 and P3D41. I have reproduced all the contriols I normally use in FSX with FSUIPC in P3D. Everythinh works correctly with the exception of the axis (flaps, rudder, aileron, elevator, etc) even if all the assignments are the same between the two versions, the devices are detected in FSUIPC and are correctly reproduced in the FSUIP5 interface. I'm using P3D4 v1 and FSUIPC 5.122A. Attached my FSUIPC5.INI Thanks and best regards Joe FSUIPC5.ini

Hi Peter, as usual you were right: I have not still understood what I was originally doing wrong, but rewriting that app piece now things are working as expected. Also about the 2nd point you are right.. but you know.. as you more eat as much more you would eat :) By the way I solved the problem reading the AI table to get the info related the flight number. Thanks again Joe

HI Peter, the offsets work great, only issue is that I have to store them in a file written with a LUA becasue, very strange, I'm not able to read them as all the other offsets im my app (I use the SDK for VB). In that case the resut is always 0. A last question: is there a way to translate the FSUIPC_ID of the aircraft in its tailname (airliner/flight number)? Thanks again Joe

Hi Peter, thanks a lot!!!! I will check the new offsets... and have a great trip in USA :) Joe

Hi Peter, do you think could be possible now to have what I asked some months ago? Thanks in advance Joe

Hi Peter, the set PMDG737offsets=Yes did the trick.. everything is ok on FSX and P3D now. Thanks a lot Joe

Hi Peter, yes.. effectively the issue on FSX started when I downloaded the last update of PMDG. In P3D I am using FSUIPC 5.103e. Joe

Hi, It seems that gthe offset 65A7 related to Parkinng Brakes on PMDG 737NGX (FSX and P3D) is no more active. Can you confirm: If so is there another possible related offset? Thanks and best regards Joe

Hi, i had the same issue with PMDG 737NGX and P3D v 3.4 I was able to load it only after to have loaded in the start screen another plane. KR Joe

Hi Peter, I just did the test.. all my devices are seen by FSUIPC and properly running. Below the attached files As usual your support is simply more than fantastic! Thanks a lot!!!! KR Joe FSUIPC5.log FSUIPC5.JoyScan.csv

Hi Peter, at work now.. I will try this evening when back at home. KR Joe

Hi Peter, I have downloaded the new version, attached the files. Hope this helps more. KR Joe FSUIPC5.ini FSUIPC5.log FSUIPC5.JoyScan.csv

Hi Peter, thanks for your support. Attached the files. As you said this version is not solving the issue, but strangely one (out of 4 VRInsight devices) now seems to be ok. Other three and the second Saitek quadrant are still ko. KR Joe FSUIPC5.ini FSUIPC5.log FSUIPC5.JoyScan.csv

Hi Peter, I have found a more recent version of FSUIPC4 that I had installed before FSUIPC4.976. It's FSUIPC4966c and that runs also well. It seems that the problem on FSX started with the last version. KR Joe

Hi Peter, the point was always related the VRInsight trouble. Things are worst than expected: in fact to execute what you asked I have installed FSUIPC4.976 (before I think I had FSUIPC4962a.. last version availbale in my FSUIPC download archive) and now the issue is the same on FSX and P3Dv4: no one of the VRInsight device and 1 of the 2 Saitek quadrants are usable on both simulators. (: Attached what you asked in term of files. Reinstalling FSUIPC4962a, FSX is still running well. KR Joe FSUIPC5.JoyScan.csv FSUIPC5.log FSUIPC4.JoyScan.csv FSUIPC4.log

Hi Peter, attached here the file FSUIPC5.JoyScan.csv. KR Joe FSUIPC5.JoyScan.csv

Hi Peter, for sure I can volunteer to do tests. In FSUIPC4 no problems at all with those devices that are treated like 'USB pad'. They appear also in the FSUIPC5.ini, but with << MISSING JOYSTICK >> close to them No problem at all for the memory.. it was only my curiosity and thrill looking eventually for the first time more than 2gb available in a simulator :) KR Joe

Same here: only one quadrant is recognized, in FSUIP5.ini this is te section related the Joystick: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Rudder Pedals 0.GUID={28EBBAA0-829A-11E5-800C-444553540000} A=Saitek Pro Flight Rudder Pedals A.GUID={28EBBAA0-829A-11E5-800C-444553540000} E=usb pad << MISSING JOYSTICK >> E.GUID={28EBBAA0-829A-11E5-8002-444553540000} F=usb pad << MISSING JOYSTICK >> F.GUID={28EBBAA0-829A-11E5-8003-444553540000} G=usb pad << MISSING JOYSTICK >> G.GUID={28EBBAA0-829A-11E5-8004-444553540000} 4=usb pad 4.GUID={28EBBAA0-829A-11E5-8001-444553540000} H=usb pad H.GUID={28EBBAA0-829A-11E5-8001-444553540000} 5=Saitek Pro Flight Yoke 5.GUID={28EBBAA0-829A-11E5-800D-444553540000} C=Saitek Pro Flight Yoke C.GUID={28EBBAA0-829A-11E5-800D-444553540000} B=Saitek Pro Flight Quadrant << MISSING JOYSTICK >> B.GUID={28EBBAA0-829A-11E5-800E-444553540000} 7=Saitek Pro Flight Quadrant 7.GUID={28EBBAA0-829A-11E5-800F-444553540000} D=Saitek Pro Flight Quadrant D.GUID={28EBBAA0-829A-11E5-800F-444553540000} 8=Pro Flight Cessna Trim Wheel 8.GUID={4F45C0A0-7B6A-11E6-8001-444553540000} L=Pro Flight Cessna Trim Wheel L.GUID={4F45C0A0-7B6A-11E6-8001-444553540000} K=<< MISSING JOYSTICK >> On of the Quadrants is in teh list, but with the << MISSING JOYSTICK >> the others not recognized are VRInsight switchwes (I have opened another topic for that KR Joe