Pete Dowson

It cannot be fixed in any "final version" if you go away and don't bother to help. I am trying to work out a way of getting more information, but it will involve you downloading additional versions, testing them, and showing me the results. I cannot fix it otherwise!! Pete

You are still using 5.10, that's why! Try 5.101 which was released to fix this! If it is okay in FSX and P3D3 then you are out of date with FSUIPC there too!!! The equivalent of FSUIPC 5.1 for those is 4.967 and behaves identically. The fix will be in 4.968, probably tomorrow. Pete

You odn't get ANY download from SimMarket, They do provide a link, but that points back here. All my software, includining interim updates like 5.101, is available in the Download Links subforum above, and has been for many many years. Anyway, I was more concerned with you using 4.964 on P3D3 when that's been superseded by major new versions several times over months! Pete

I see you are still using the original release of FSUIPC, from last Thursday. 5.10. It might be a good idea to at least change to 5.101. I'm working on 5.102. Oh deal. you are using 4.964, a pretty old one, on P3D3. The joystick scanning is completely differnt in that one. The equivalent to FSUIPC5.1 is 4.967, the currently suppoted version. Please try not to use unsupported versions. Pete

Are you saying they actually work (i.e. cange the actual AP) till then? I'm checking. Looks like those have never been directly writeable. Seems a flag s being lost or not tested correctly. It will be fixed. Pete

Yes, but strangely, as well as being listed as a Keyboard, following the entry which states that, there are listed 8 or 9 other uses with the same identification. One of those looks like a joystick type to directinput, somehow (though I don't see how or why). Strange. Never seen anything like that. I doubt that it's related to the problem, but if you have simple wired keyboard you could substitude temporarily it would be a useful test. Pete

Well, thanks for the thought. But I never expected to still be working on it some 19 years after I started. I'm 74 years old this year and hoping to retire one day, sooner than later I hope. Pete

Okay, good. That explains the short Joystick Scan. I wonder, though, what the device with this data is: Vendor=8087, Product=0A1E (Version 2.0) This must somehow have shown up as a Joystick Type device in DirectInput. I could do with a HidScanner log please. Get HidScanner.exe from the "Useful Additional Programs" thread in "Download Links" subforum, put it on the desktop, double click it, then show me the Log it produces. Thanks.

I think i went to 12 for 3308 because I did think, early last year, that the DTG 64bit version of FSX would be ready long before P3D 64 bit. So, yes, I think I'll stick tothat. 3124, however, is calculated from the real version number of P3D, and it actually should be reading 40 at present. I've no idea how it gets to 51. I'm investigating. [LATER] Aaaarggghhh! Somehow it got the Version reading mixed up -- the 51 you are getting is the FSUIPC version number (from 5.1xx)! Duh! :-( Fixing now. Pete

Ah, now that log IS different. Your earlier log was NOT from a crashed P3D. This new log terminates early on, after a very very short Joystick scan: 93 ---------------------- Joystick Device Scan ----------------------- 93 Product= <not readable at this time: maybe device disconnected?> 93 Vendor=8087, Product=0A1E (Version 2.0) 93 ------------------------------------------------------------------- What joystick type devices do you have connected? Once I have narrowed down the place where it stops I can add more detailed logging ot identidy it exactly. It's an iterative process and I need your help. I am still hoping for corroborative log information from Navigation! It certainly won't be very soon at all unless you help. Where's your LOG and INI files with 5.101a? The process of nailing this will be me getting information from you then asking you to try things. If nobody is going to help it won't get fixed. i cannot fix things here without help when there's no problem here. And as you say, there seems to just the two of you! Thanks, Pete

That's interesting, and the opposite of what i get! But then the problem it gives me is that it hangs P3D4, completely. Ah well ... hopefully PMDg will track it down. I think they need to call in L-M's help, as I did last week -- they resolved by weird baffling problem within hours. They'd have to be able to reproduce it, though, and it seems it isn't universal. Pete

FSUIPC merely relays the error number it receives and the description from the SimConnect SDK. I'm not sure why you are getting those. Are they definitely with an aircraft which features and autopilot with those features? The more important matter is whether those offsets are actually working for you. Maybe P3D in their infinite wisdom have not enabled those SimVars for writing as they were before. If so I'd have to intercept them and send the approriate Events (controls) instead, aaa much messier proposition. Of ourse. All the missing bits were targetted to be completed before the end of the week, but there has been a deluge of problems which I'd not really expected. I must resolve problems before dealing with facilities. Keep tabs on the release notice. I'd like to get it done. Pete

4.968 is in the works at this very moment and should be released very soon, maybe even tomorrow. Pete

It isn't too late to change this. I think it's a result of the internal referencing of the difference sims. I can make 3308 give 9 or 10, whichever is next, and 3124 give 4x as you expect. They were both probably oversights in any case, with rather more things occupying my mind. I doubt if anyone else is affected yet. Version 5.102 will be released as soon as i've resolved a couple more problems. Shall i "fix" it in that release? Or just document the anomalies? Pete

Yes. I think you only read the last part of my last message. This would be useful please, as in the first part of that message: Now could you remove one of those at a time, so I can see which action of the three is causing PMDG grief, please? That was referring to the three lines you added. Thanks, Pete

As yet, despite my requests, I have no actual FSUIPC.LOG for this problem. I also need the Windows crash details please. See previous message in this thread. Thank you! Pete

There will be crash details in the Windows Event Viewer, Application Logs. I need those details please. Also please show me the FSUIPC5.LOG file from the P3D4 Modules folder (not the Install log), and also the FSUIPC5.INI file. Thank you, Pete

Great! Now could you remove one of those at a time, so I can see which action of the three is causing PMDG grief, please? That's strange it is the ther way around here! This seems to be reminiscent of similar PMDG loading problems in FSX in the past, unless my memory is failing me. All your information will be useful to PMDG, so please don't forget to send the details to them too. Thanks, Pete

Odd. I've changed nothing else. I'll check. It is very difficult without any suitable devices. So is this happening with all buttons with default actions? And only buttons, nothing else? If it is alll buttons and nothing else it narrows it down well -- i should be able to track it down by simulation of the button press. Pete

The INI file is one. but the DLL is the program itself, which of course I have already -- I wrote it!!! The most important file is still not being supplied. if an INI file exists then a LOG will exist too: FSUIPC5.LOG. Why can you not supply that? The INI file is just the default. So it is fine. No, please, the LOG!!! Pete

Interesting that Wi7 results are different -- something certainly to report to PMDg. I've just found that the "NoWeatherAtAll" setting doesn't do anything in FSUIPC5. I'm fixing that, and also adding another: NoPanelsAccess=Yes which prevents FSUIPC accessing the P3D4 PANELS.DLL functions to read and write L:Vars. This action, along with Weather and AITraffic amounts to all the "extra" things,, on top of just waiting for SimConnect to supply data for the Offsets, that FSUIPC does, at least when not registered. When registered, of course, it also scans joysticks and keypresses. Version 5.102 (which has some fixes too in the Joystick Scanning) will replace the full 5.10 installer later today. Please try that with both the two parameters mentioned above AND this new one for panels access. Pete

Well, I've done some more tests here. This is on my Win7 development PC: 1. If I load up my normal default, a 738 at EGLL, then when I subsequently load the PMDG 747, it reults in a black screen solid hang in P3D4, needing Task Manager to terminate it. 2. If instead I select the 747 at the initial P3D4 menu, it loads okay, no problems detected AND it does this whether or not FSUIPC is installed or not, and unregistered or registered – and with no special eliminations needed. 3. With the 747 loaded as above, I selected an innocuous aircraft (Piper Club, as it happens), then the 747 again ... it loaded okay again. 4. So, I loaded my normal default 738 (the ProSim model, with no cockpit, as it happens). THEN back to the 747 .... again, all working! Just to check whether something had changed in the 747 files by getting it fully loaded and working, I then did an extra test: 5. After all the above, If I close P3D4 the restart it and load up my normal default (the 738 at EGLL), then when I subsequently load the PMDG 747, it works – no hang in a black screen. I don’t know what can be done with this information, but I’m seeing that it is all okay here providing it is first loaded once as the first selected aircraft. This seems to put something right so that it works fine on all subsequent loads. Of course, the original symptom here is nothing like those reported by your other users – it was definitely a solid hang with a black screen. [LATER] Unfortunately, the result 5 above is inconsistent. It worked fine on two P3D4 restarts, but on the third, some time later, I got my usual black screen hang when changing from my normal aircraft to the 747. Pete

There is a way of fooling applications which read the details from FSUIPC offsets into thinking the FS version is something different. You need a little Lua plug-in like this: -- Loop forever while 1 do ipc.writeStruct(0x0024, "1UW", 0x3308, "1UW", 2, "1UW", 8) -- Sleep for 50 mSecs so the update gets done roughly 20 times per second ipc.sleep(50) end Offset 3308 == 8 means "FSX". Change the 8 to whatever might make those programs work. Pete

Please, try adding the following to the FSUIPC5.INI file [General] section: NoWeatherAtAll=Yes ProvideAIdata=No then see if the 747 is okay. These parameters eliminate two main requests from P3D. For an unregistered FSUIPC5, which therefore does not scan joysticks or buttons, the only other part I can really eliminate as a test is the L:Var access into PNELS.DLL. I wil add another parameter for that and advise here, in this thread. But please try the above in any case. Pete

Ah, good! I shall tidy it up and release it properly as 5.102 after I've tested a few other things. I shall also make the same corrections to FSUIPC4 and release 4.968, Thank you for the quick turn-around in testing! Pete