vgbaron

Success. I played around with Joyid and moved both the stick and throttle down. I now have two of EACH listed but it works. Just a wild guess, but using USBDeview, it shows dual entries for the stick and throttle - listed as HID and BULK, I'm guessing that is in the registry and fsuipc picks it up. Let's see if the settings stick! Thanx for the help Pete! Vic

Yes, I saw the two stick also. Got no errors,etc. I'll clean it up and try joyid and see what happens. Just to clarify, I am ABLE to program the stick but not the throttle. Thanx, Vic

Hi Pete - Running P3D 3.3.5 under W10 Pro 1511 with version 4955g I have ch yoke, ch throttle quadrant, ch rudders and Saitek x55 Rhino Stick & Throttle connected. Fsuipc sees all connected devices and I can program all EXCEPT the x-55 Throttle. When I move the throttle or press a button - nothing happens in FSUIPC window. Any movement from other items including x55 stick gets readings displayed. The X55 is two units, each with it's own USB connector. I have tried moving the around to different USB ports with same result. Downloaded and installed latest (9/15) drivers from Saitek. The x55 throttle is recognized within P3D and the axis can be calibrated. Log attached - you'll see where I unplugged the throttle and put it in a different port - FSUIPC sees that - just apparently not getting a signal. Any insights other than going back to W7? Thanx, Vic FSUIPC4.log FSUIPC4.ini

Thanx Pete! :cool:

LOL! Because I'm one of those that actually READ TFM! I tend to scan the docs first, then focus on specific areas later at the flight system. I'll just have to wait until I get home. Go fly and enjoy! Vic

Would it not also be beneficial to have the document in the DOCUMENTATION section of this website so one could read it should they ot have access to their FSX/P3D install? Vic

Pete - In the changes for 4.942 is says to get further information from a separate document " Profiles in Separate Files". It's probably right in front of me but I can not locate it. I have not run the 4.942 installer but looked in the documentation area here. Thanx, Vic

Thanx Pete, I'll look at that option. I am using offset 024C Type S32 with FS WIndow checked - the resulting remaining VAS is the display I was speaking of. Thanx again! Vic

Is it possible to save the size and position of the VAS logging window in P3D2.5. It always starts with the green bar across the screen and I must resize and move it. Thanx, Vic

Rob Ainscough has stated that the FSUIPC version he is using is working as expected with 2.4. Vic

Whatever - it works as expected and shows 4.926b. Thanx again Pete and best wishes of the holiday season to you and your family.. Vic

n o - UAC is disabled and I have ownership of all the FSX folders - I'll do it again when I get home. Vic

properties say 4.927b maybe I've mislead here - installed 4927b by deleting OLD 4921 and copy I forgot I had my earlier INI file created by 4921 - started FSX - worked - module showed 4.921 changed the ini to the current one which says "modified by 4926" - and FSX crash I have to go to work now but I'll look at the ini files altho I probably wouldn't see the problem. Vic

Thank you Pete - sorry for the trouble! I'll d/l and report back. Vic EDIT: No joy - tried an earlier ini file - works fine - current - no only question - when fsuipc opens in fsx is still shows version 4.921 dated sept. V

Hi Pete - All has been well up until this version: Start FSX as usual get an error about FSUIPC.DLL (fsuipc_err.jpg) - I ignore the error and continue to load FSX - FSX crashes with err.txt. I use ASN but uninstalled that and still get error. Rebooted - tried several earlier versions of FSUIPC going back to 4.90 with same result. log cuts out at trying to connect to simconnect - Any thoughts? Any other documents you need? Thanx, Vic Edit: Tried a few more things. Uninstalled ASN completely Restored just the MODULES folder from an earlier backup ( it was FSUIPC V4.921) FSX ran fine! Install ASN FSX Fine Install4.927a crash restore MODULES fsx fine. HTH, vic fsuipc_err.zip

Reread the docs again - it's clearly stated. The fault is with the reader. Thanx Pete! Vic

Worked for me! Vic

Read the docs and the extra supplied re the Beaver - understand the concept but still a tad confused. In my setup I have, [Profile.Twin_Piston] 1=Beech Baron 58 Paint1 2=Cessna 310 BB 3DAnalog 3=Cessna 310 N5225J 4=Cessna 310 N5077J 5=Douglas DC-3 Paint2 6=Cessna 310 Song3 freeradio 7=Cessna 310 SB freeradio following that are the buttons.twin piston, axes.twin piston, etc If I understand correctly then, instead of lumping those a/c under twin piston, I should create a separate profile for each a/c which would then include all the paints. Vic

Hi Pete - Thanx for the quick response. As is quite often the case, the problem was hardware - the nut behind the keyboard. AS I slept on it, I realized that I had NOT double checked the key assignments within P3D. Yup! I had missed deleting the landing lights toggle. Corrected that and all is well. Sorry to take up your time. Should have done that first. I think at the time I was setting it all up, it was easier to enter the keypress than scroll down the list to find landing lights. :) I guess I'll have to dig in the docs again - don't follow you on that feature. edit - Read the docs and the extra supplied re the Beaver - understand the concept but still a tad confused. In my setup I have, [Profile.Twin_Piston] 1=Beech Baron 58 Paint1 2=Cessna 310 BB 3DAnalog 3=Cessna 310 N5225J 4=Cessna 310 N5077J 5=Douglas DC-3 Paint2 6=Cessna 310 Song3 freeradio 7=Cessna 310 SB freeradio following that are the buttons.twin piston, axes.twin piston, etc If I understand correctly then, instead of lumping those a/c under twin piston, I should create a separate profile for each a/c which would then include all the paints. Vic

Hey Pete - Trying to track this down - Had my CH Throttle Quadrant set up in FSUIPC running under FSX, P3D 1.4. with no problems. Deleted FSX & 1.4 and installed P3D2 and your latest for it, copied the fsuipc.ini file settings, etc. All the Axis work just fine on the aircraft but I've run into a problem. I have a button on the TQ mapped to send a CTRL L to toggle landing lights. Loaded the Mooney Acclaim and also one of the P-38's that are default in P3D. Pressing the switch caused a brief busy icon from the mouse but did not toggle the lights. Also tried setting it up as a FSX command - Toggle Landing Lights - still didn't work. interesting in that if I look in the VC and press CTRL L on the keyboard, the visible switch moves and the lights toggle. Set up FSUIPC to send CTRL L - nothing moves. As I said - this happens on the two a/c I tested. I will check others if you wish. The ini file and log is attached. Thanx, Vic uploads.zip

I didn't bother to check the log after I restored the original - basically - FSX didn't crash. Replaced "k" again - FSX crashed. However - I must apologize for sending you down a wild goose chase - the problem is NOT yours but is specific to something that I have done to my system, which at the moment is proprietary. Had no idea it would affect FSX. Any others users with crashes, etc would have absolutely NO relationship to my problem. Again. my sincere apologies - I should have caught this myself before posting. Vic

pete - Windows7 64 Still crash after trust established prior version works fine will try 4.859k when I get home. Thanx! Vic

4859j failing System is FSX/Acceleration ( I have p3d on a different system - new fsuipc works fine there) - install and add PatchSIM1friction=yes in [general] section. Start FSX - get trusted module request - FSX load fails with error Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: FSUIPC4.dll Fault Module Version: 4.8.5.9 Fault Module Timestamp: 50c070d4 Exception Code: c0000005 Exception Offset: 0001c4b3 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 logfile: ********* FSUIPC4, Version 4.859j by Pete Dowson ********* Running inside FSX on Windows 7 Module base=68900000 User Name="victor baron" User Addr="vgbaron@hotmail.com" FSUIPC4 Key is provided WideFS7 Key is provided 16 System time = 06/12/2012 17:27:28 16 FLT UNC path = "\\BLAZER\Users\Vic\Documents\Flight Simulator X Files\" 16 Hook Error: can't find .37 in SIM1.dll 16 Hook Error: can't find .37 in VISUALFX.dll 47 Trying to connect to SimConnect Acc/SP2 Oct07 ... 47 FS UNC path = "F:\FSX\" 265 LogOptions=00000000 00000001 edit: sim1.dll dated 9/26/2007 4:09PM 869kb - visualfx.dll dated 9/26/2007 4:08PM 200kb Thanx, Vic

Thanx for refreshing my memory on that Bob! That's what I did before (at your suggestion!) Now mixing the edited standard.xml with FSUIPC seems an interesting approach, I'll dig in to that some more. BTW, thanx to FSUIPC I finally found a use for the paddles on the Ch Eclipse Yoke - programmed them for Zoom + and Zoom - for quick adjustments. Nice! Vic

that's why I don't unplug devices unless I must. So as long as the INI file is intact, FSUIPC will do it's thing. That's what I expected but the SimS docuemnt threw me a curve and haviong had the GUID issues in the past I made an erroneous connection. Now to get to the programming...... Thanx again Pete! Vic