Pete Dowson

Ah. So you don't select the App you want first? Just enter the code and it automatically gets the right App? That's all new to me. Thanks. I'll try it. Pete

Wow! Well done! I hope you've not lost the use of anything? Keyboard, mouse, all okay? Meanwhile, for everyone else with the problem, please try FSUIPC5101d_TEST.zip still with these lines added to the[General] section of the FSUIPC5.INI file: Debug=Please LogExtras=x200000 and please show me the Log file after, no matter what the result. Pete

Where have you been? FSUIPC5 was released last Thursday and is sold by SimMarket since last Saturday. There are already updates in the Download Links subforum and there will be more this week as it develops. BTW you posted your question in the FAQ subforum, which is NOT a support forum but a repository for information. Please use this, the Support Forum. Pete

Thanks. Bed time here -- I'll catch up in the morning. I sent an email saying I couldn't find any "Redeem" button, BTW. So if I need to go that way i'll have to pay. Pete

Not two with the same name though -- you can't have two files withthe same name in the same folder. Windows won't allow it. I assume you renamed one. The Sim isn't loading it, FSUIPC loads any it recognises as being suported by its facilities. Good. Thakns for testing. I'll be rleeasin this formally, along with PFChid64.dll for P3D4 and PFCcom64.dll also for P3D4 withing the next day or tow. The P3D4 versions need FSUIPC 5.102 which isn't quite there yet. Pete

But we are trying ot work out what is wrong. you only need to disable FSUIPC if you want to load without it -- just rename the FSUIPC4.DLL, for example. Data files can't stop anything running. It makes no sense to start again from scratch every time I ask you to do a test. Well, it is detected by DirectInput and shows in the Registry. Check in the Windows device manager. Pete

Does the IN value arriving from the axis in the Axis Assignment tab change when you move it? Does the IN value change on the Calibrations tab for the rudder change when you move it? It certainly shows an Inocming value in the pic you posted. And you seem to have calibrated it okay. Are you using a default or add-on aircraft? Have you tried assigning to the more usual FS control, the Axis rudder set one in the FS contorls assignment dopdown? Have you also assigned the FSUIPC steering tiller? If so, when you are on the ground and at slow speeds the tiller controls the rudder -- the rudder takes over graduakky as you speed up. This is an FSUIPC facility. See the documentation. You could also have tested the detection and operation in FSUIPC of that axis by assigning to somethhing you evidently trust in any case, such as the ailerons, just as a test of course. BTW I've just tested the twist axis on the X-55 stick, and is detected and operates just fine. In fact unless there's a fault in the device itself, or with its Windows calibration, there's no way one out of all the axes on a particular device cannot be detected -- all of them are returned in one data block, every time (along with the button states). Pete

Why? Did you delete it? If there's no FSUIPC5.INI then you've NEVER used FSUIPC in that folder, in that sim! Not unsuccseeful in any case. More information: 94 Usage=12, UsagePage=1, =Flight Mode Switch 94 Error 50 [00000032] returned on HidD_GetProductString: (\\?\hid#intc816&col02#3&36a7043c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}) 94 Product= <not readable at this time: maybe device disconnected?> 94 Vendor=8087, Product=0A1E (Version 2.0) 219 ------------------------------------------------------------------- 219 ****** Registry scanning: VID=8087, PID=0A1E ****** 219 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_8087&PID_0A1E\Calibration\0" 219 ... and a "GUID" value 219 GUID= {55BAE820-FF5E-11E6-8007-444553540000} 219 NB: not valid for this device according to GetConfig! So, the device you have connected is a "Flight Mode Switch". FSUIPC assumes you might want to program such a thing in a flighjt sim. I suppose you know what this iss? Pete

Ah. Joy B axis R. Right. So the problem is? It looks okay in the pix. Pete

Yes, thank you. this is actually the same problem as already covered at length in another thread (with a misleading title, unfortunately, "FSUIPC REG not working". But ytou're the first to confrm what some of the other logs had indicated -- that it's related to the joystick scan and what happens when there aren't any. Therefore, i would be grateful if you could do another pair of tests, the same as those you have posted, but first add the following two lines to the [General] section of the FSUIPC5.INI file: Debug=Please LogExtras=x200000 This will log the scanning in more detail. Please sohw me the resulting logs. Odd that I have three PCs here running P3D4 yet cannot reproduce this. Thank you, Pete

To all those with this problem, please try 5.101c in which I have restricted the choice of device made during the JoyStick Scanning. I'm not sure I'm in the right area yet (pending fuller logging information), but maybe it will help. FSUIPC5101c_TEST.zip Just put the DLL from that Zip into your P3D4 modules folder. Before running, please do add these lines to the [General] section of the FSUIPC5.INI file: Debug=Please LogExtras=x200000 and after the run, succssful or not, please show me the usual three files: FSUIPC5.INI FSUIPC5.LOG FSUIPC5.Joyscan.csv all from the Modules folder. Thanks Pete

You are serious misreading what I said!. Please PLEASE read it again please: These are logging options, in the INI, to get me more information!!! They will never appear in any logs! They are Parameters in the INI file, as it clearly says! :-( Pete

Please refer to the thread someehere near here with LINDA in the title. This is an already reported problem which is being looked at. Please keep an eye on that other thread for progress. Pete

Thank you. Those will be concerned with the P3D assignments. I don't think those are relevant here. Pete

So do i have to keep switching things on and off for 5 minutes, or are you saying these write problems occur on their own, with no attempts being made to write? If so, then this is different to what is reported for LINDA. Pete

The log shows that only the X-55 Throttle and X-55 Stick are connected and in the Rergistry. They would be seen in the FSUIPC menu as joysticks A and B respectively, as labelled here, in your INI file: [JoyNames] AutoAssignLetters=Yes 0=Saitek Pro Flight X-55 Rhino Throttle 0.GUID={304AE990-CD37-11E6-8006-444553540000} A=Saitek Pro Flight X-55 Rhino Throttle A.GUID={304AE990-CD37-11E6-8006-444553540000} 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={304B5EC0-CD37-11E6-8007-444553540000} B=Saitek Pro Flight X-55 Rhino Stick B.GUID={304B5EC0-CD37-11E6-8007-444553540000} There's no sign of any pedals at all, anywhere. So how do you determine that "it detects the rudder axis"? Pete

THIS is my website. If you mean the Schiratti "Dowson" page, that is a private site run by Enrico Schiratti. I keep asking him to update it -- I don't think he's even updated it for FSUIPC5 and P3D4 yet. :-( The download place (and in fact where the links on the Schiratti page point) is here, in the Download Links sunforum. That is under my controls and is the ONLY place which is complete and up to date. There are other subforums you should probably tkenote of too. Even the links on SimMarket point here. I understand that, but unless I build Internet access into FSUIPC (and have it permanently sitting in FS address space?) there's no way. I am very reluctant to add any Internet Access at all to FSUIPC. And in any case, many folks keep their FS PCs internet free. Pete

So is the App doing writes repeatedly, without having to operate switches on its display? Okay. Thank you very much! Pete

It is not anything wrong you are doing. There are other confirmations, and I can see what is happening from the logs. I just don't understand why, and I need to reproduce it here so I can track it down. I think you posted without reading the preceding messages. I'll reproducce part where I was appealing to you for help in reproducing it, here: Yes, this is because the TestOptions parameter added does a write test on all of the variables during FSUIPC initialisatin. Don't worry about those now, the info was for me. 179406 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF 179406 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF 179406 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON 179406 SimWrite[145]: 0804="AUTOPILOT BACKCOURSE HOLD", DDef=00000007, Ref=3880, Size=4 [flt=0.000000, int=0, 0x00000000] 179406 Exception 20 "DATA_ERROR", Ref 3880, Index param 1 on write SetData for "AUTOPILOT BACKCOURSE HOLD" 179406 SimWrite[132]: 07D0="AUTOPILOT ALTITUDE LOCK", DDef=00000007, Ref=3881, Size=4 [flt=0.000000, int=0, 0x00000000] 179406 Exception 20 "DATA_ERROR", Ref 3881, Index param 1 on write SetData for "AUTOPILOT ALTITUDE LOCK" Something really strange is occurring. It is quite happily sending events for the assorted AP offsets you are writing, and then, suddenly, switches to the SimVar writing -- to non-writeable SimVars (as determined, in fact, by the initialisation test. I now need to find out why this is occurring. Corruption of the tables in memory? Nothing actually writes to those decode tables in my code, at least nothing programmed. I think I'll have to write a Lua plug-in to do something like what you are doing. Writing of, what, 8 or so AP switches up to 20 times per second? I don't suppose you have a simpe (not needing LINDA) plug-in which can do that, and which gives the same symptoms on your System, have you? If not, it might speed things up if you could make one, test that it fails, then let me use it do I can debug the issue here. Thanks, Pete

Please, anyone suffering form this problem, I still need more information. All the logs so far supplied show no joysticks connected, but Direct Input returning a non-joystick instead -- for some reason I can't fathom. However, this doesn't appear to be the direct cause of the crash. I think it must proceed to the next phase which invoves checking the Registry for the deice(s) already identified and trying to work out if they are suitable. To see how far that gets, to determine what is going on, I need logs with Debug=Please LogExtras=x200000 added to the [General] section of the FSUIPC5.INI. Please also check whether a partial FSUIPC5.JoyScan.csv file is produced. The first part may be. If it is there I need to see that too. Thanks, Pete

Well, it doesn't bother me in any case. I only installed it to see if I could identify the FSUIPC/747 conflict, but I don't get one. I don't actually use any PMDG aircraft and this one will be uninstalled. As for a target environmnet. Win10 is certainly more likely to be best as I'm sure hardly anyone stuck with the buggy Win8. I like Win7 Pro, the best O/S Microsoft ever came up with. Win7 Pro 64 is on all of my PCs (8 of them, 6 used for the cockpit alone). I have an old laptop still on Vista (ugh, but there's no later screen driver for it), and a Surface Pro 4 on Win10 (updating again, massively, as I type). Pete

Not that it's relevant, but my development system is Win7 Pro 64. I used the current VS15 compiler system with the libraries set the same as P3D4 and the target set to Win10. Pete

None of that should be relevant. In fact the DirectInput function I'm using should only tell me about connected joystick type devices, nothing else. Pete

I've added to the Win7 count. But I have the same problem if I load the 747 later, with or without FSUIPC. It also loads okay as first aircraft, from the Scenario menu, again with or without FSUIPC. Pete

So far all the logs I've seen for this problem have shown no joysticks, so it looked the common factor. So, can you show me you log with the joystick previous connected, please? With the DEbug=Please etc options added to the INI. BTW I've now tested on a Microsoft Surface Pro 4 on Win10 with no joystick devices, and I get no problems. So it isn't something in Win10 specifically. Pete