cellular55

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

Hi Peter, I have just registered FSUIPC5 and I have some troubles: - for buttons and switches I am using several VRInsight Multi and Tack and Toggle switches: they do not appear in FSUIPC5. I think that this is due to what you have mentioned in the announcement about VRInsight devices. when do you think that the problem will be solved? - I was curious to see the amount of memory available in P3Dv4., but it sems that the Offset 24C (I was using before) is no more operative: it shows 0. Thanks and KR Joe

For sure I will compete to be the first purchasing it :)

Hi Peter, thanks a lot for your availabilty, I will remind you the point at the end of the month. By the way.. have a great holiday Joe

Hi Peter, I'm using the new offsetsthat show the distance of the closest AI aircraft(ground or airborne) in one my app. Those are running very well (thank for that),. I was wondering if could be possible to have two more offsets (at lest for the airborne AI) showing the altitude and the headinbg of the closest airborne AI aircraft (avoiding to read the full AI table to obtain those info). Thanks a lot Joe

Hi Peter, as promised to let you know that after to have applied your JoyNames section everything was ok and I was able to install and properly run the new FSUIPC version. Once more thanks a lot for your support KR Joe

Hi Peter, thanks... and my keyboard must have a problem between 3 and 4 keys (version is 4.958) :) I will let you know when I will have adjusted the Ini.file section. KR Joe

Hi Peter, it seems really a mess :) Only some explanations respect the cockpit configuration: One Saitek quadrant is used for spoilers and engines, I use the other for flaps and parking brakes The Saitek pedals should be the only device configured as rudder The Cessna trim wheel is connected, but not yet configured The USB Pads are a mix of VRInsight Panels and one Saitek Multi switch (it is configured to use FSUIPC macros associated to keys) The profiles are used and running: I have those files in a directory called Profiles (attached the example config related to PMDG 737NGX) Can appear strange, but with 3.958 everything is correctly running (until the 4.961 I never faced errors) Next week when I will have enough time I will try to put some order here using your suggestions Thanks Joe PMDG.ini

Hi Peter, my mistake: I was installing 4.961 from 4.958. Yes.. I have several devices for my home cockpit and yes I use the joy letters. Attached my FSUIPC.INI: when I install 4.961 even if the ini is not changed almost all of buttons and switches do not run. KR Joe FSUIPC4.ini

Hi, i tried to install (more than one time) the new version (4.6.1) from the version 4.5.8, but with that version I always loose all my joysticks, buttons assignments. To restore them I had to go back to the previous installed version: that fixed the issue. Apparently with the new version the assignments are in the FSUIP.INI file, but are not running. Attached the log after the 4.6.1 installation Thanks and kind regards Joe FSUIPC4 -461.log

Hi Peter, thanks for the usual prompt reply. I will do what you suggest, and in case of reoccurence I will send all the possible info. Thanks again and kind regards Joe

Hi, I'm experiencing several crash also after few minutes of flight with the message that it was caused by FSUIPC (still more often when I tried to install the newest P3D version). I'm using FSUIPC 4.957, log attached. Suggestion on the possible cause? Thanks and KR Joe FSUIPC4.log

Hi, issue solved: I forgot to set the EnableDataBroadcast option KR Joe

Hi Peter, I' m trying to use on PMDG 737NGX in P3D v3 the same offsets I'm using in FSX but without any success. Is there another offset list that should be used? Thanks in advance for the support and best regards Joe

Hi Peter, even after more than 30 mins after I have shut down P3D I see it in the list of processes yet: I think is some add-on I have. I will do some more tests and checks and i will let you know. Joe

Hi Peter, you are right! I have noticed that when shut down the new version of P3D it remains still active in the processes list and I have to manually close it. I will open a topic on the P3D forum about that. Joe

Hi Peter, thanks. Only another possible issue: if I close FSX and P3D and the restart them I get the following message: 'There seems to be duplicate copies of FSUIPC installed, or another running still in memory! Please remove older copies! Never simply rename modules, move them OUT of the Modules folder! If there are no duplicates please use Task Manager to check that the' I do not have any duplictaed or renamed FSUIPC.DLL and going in the task manager no multiple FSUIPC instances result running. Joe

Hi Peter. here the FSUIPC.INI and the PMDG Macro for which error comments are reported. Comments seem to be referred to parts of the macro considering keyboard strokes and not mouse clicks. The other macro mentioned (WX) is effectively not existing. BR Joe FSUIPC4.ini PMDG.MCRO

Hi Peter, as usual your support is more than fantastic: that dll solved the issue for FSX and P3D!!! A last question: why in the .INI file I get the 'unknown macro' mark even if the macro with that name is existing? Thanks a lot once more. Joe

Hi Peter, attached the FSUIPC.INI after the attempt to run FSX/P3D after the reinstallation of version 4.9.5.5. The default aircraft loaded at FSX start does not use any profile, by the way I attach ini file related PMDG that is the aircraft I use more. BR Joe FSUIPC4.ini PMDG.ini FSUIPC4.ini

Hi, after the 4.9.4.8 I tried with the 4.9.5.3 with the same type of issue. I was hoping that the new version was solving it. Attached the 2 FSUIPC.INI BR Joe FSUIPC4.ini FSUIPC4.ini