Pete Dowson

Do you think so? think about my situation: 600 scenery layers at last count (and the additions over the default are ONLY for Europe, as I fly no where else at present). If I need to re-order sceneries for some reason, like conflicts, or bleed throughs, or whatever, it is now much more complicated. Even just to elimiate some, maybe for a test or maybe to try a different version from another supplier, becomes more difficult. You have to try and find the things first, then work out how to disable what! I like things to be kept simple and self-contained. This new system, which is apparently applied to P3D3 too, is just too complex for my tastes. And what is worse intriduces even more Unicode and XML files, the latter being the most verbose and error prone format ever desgned. The files are far bigger than they need to be and one little error in the format anywhere renders it all useless. Maybe when my successor takes over the reins, as and when (and who), they will think differently. I'm rooted in the basic computing eras -- started as a test programmer on Leo III's back in 1963. For me even Windows is too complex, too far removed from the nitty-gritty or what computers are. ;-) Pete

ProSim drives some things directly. You'd need to check. Yes, you buy "WideFS7" to get the REgistration key to unlock WideFS. You download the WideFS7 pakage, or just the WideClient from the Download Links subforum for use on your client PCs. You only need FSUIPC on the P3D PC. Pete

In the Download Links subforum. It won't be on the Schiratti page until Mr. Schiratti decides to put it there. This Forum and it's subforums is really where all my things are provided. Pete

It isn't an 'update' but a new 64-bit version, for P3D4 only. And installation and use for application programs has always been free. You can download it, install it, read the documentation, but for User Facilities you have to purchase a key. Unfortunately the purchase page at SimMarket appears not to be ready yet, but i'm sure it won't be long ... If you don't already use WideFS then why now? If you do already use WideFS then you can register it with the same details in the 5.1 installer and continue using the WideClient you already have. Pryr

As I said, remind me if you see nothing here by the end of next week. Pete

It is very easy. Load the aircraft and select profile mode then the Profile name from the list. Easy. Not at present. Enhancements will have to wait. There are still a lot of things missing which need doing (see Announcements subforum). I'll be tied up with all that for some time. And I've still got support work to do, and a familty. One day I might even be able to fly myself! Remind me in a few weeks. Pete

YOU WERE IN THE WRONG FORUM! MAKE SURE YOU CHECK WHERE YOU ARE PSTING! You are clearly making a mistake then, or the date on your PC is wrong. why is the order many months old. Have you waited all this time? If not how have you lost your KEY file? didn't you back it up as instructed? Pete

Sorry, I've got far too much to do as it is. And it has little to do with Simconnect. Aircraft DLLs are intimately tied into many parts of the sim, and rarely if at all Simconnect. Pitch your suggestion elsewhere please. Pete

I have no idea. I'm in deep technical discussions and exchanges with L-M. Pete

They are all positive. "negative" ones would have numbers like 255 to 248 or less. Quite honestly, if PFC are still making new products and expecting me to support them in FS then they should at least tell me about them and possible compensate me.I did get some hardware from them for my earlier work, but nothing now for many years. They only seem to care about X-Plane these days. Maybe you should appeal to them. i don't like to let folks down but they do trade on my good will, and i wouldn't mind if I wasn't so busyn(I do wish P3D had never been invented. FSX-SE was bad enough. FSX could have subsided nicely by now)). i wasn't planning to be still doing this stuff at age 74 and I'd like to get time to fly my own cockpit occasionally -- something I last did way back in April. So,sorry, I don't think enhancements to PFCHid are likely. I'll check what is happening with the multiple values returned, next week, but nothing more. Pete

FSUIPC links directly into the SimConnect part of P3D, no need for any external Simconnect DLLs. In any case P3D has never installed any specific SimConnect DLLs, at least not since P3Dv1 perhaps. Currently it isn't worth anyone else getting frustrted by this 100% consistent crash in Win10. L-M are involved. i'll keep pressing them. Pete

Well, I see the 255 (-1) returns for one direction, and either 1 or sometimes 2 -7, presumably from when you turn it fast in the other director, but no -ve equivaluents (254 - 248, say. did you run it fast both ways? I can see that the HDG macro is invoked for anything other that 1 or 255. So i'm thinking the original spec didn't mention anything about multipl counts. And I would certainly have noticed when I had a RIC. How old is your unit? They might have improved it and revised the firmware. I'm going to have to find the original specifications for the PFC protocol. And I may have to ask PFC to supply these again, or, better, updated ones, because it was many years ago that I dealt with any of this and it was all on another PC. I have some archives and I might be able to find them, but it could take a while. I'll make a note to get back to you when I can, probably next week. Put a reminder in this thread if I haven't got back before the end of next week. Pete

Check with default aircraft. Same or not? What did you assign the flap buttons to, and where? If the flap handle moves but the gauge doesn't then this usually means you have no hydraulic pressure (depending on the aircraft). Did you start the engines and set all the overhead switches correctly? Pete

Offsets don't move about. What are you comparing with? Which offsets? If you means these: Offset Type of data Remark 3358 U32 Saitek Radio panel offset address 335C U32 Saitek Multi Panel offset address 3360 U32 Saitek Switches Panel offset address Then they are the virtual button offsets, designed to be seen in FSUIPC's Buttons & Switches tab. They've never changed, they are exactly as documented in the offsets lists. Pete

Ah, yes, sorry. So you did. But that takes me back to my first comment, that if the hardware sends the same thing for a fast turn as it does for a slow one, naturally the same action will be triggered. I think I need the log to show me what is coming from the hardware. Let me see ... ... Yes. Use LogComms=Yes LogData=Yes LogDecode=Yes in the INI. Run it but only use the knob in question. Turn it slowly both ways, then wait a while 9so i can see a gap in log times) and turn it fast each way. [LATER] Actuallly, having a quick look at the code, the unit sould be indicating fast in the data it sends. There are time constraints. the code ifnores a "slow" withing 110 mSecs of a fast -- probably to stop that odd 1 being added when you stop turning. Maybe you aren't turning it fast enough for the hardware to indicate it? Pete

Can you show me a log or anything? It is a long time since i had any access to such hardware and the software itself is pretty old now. I will try to help, but it may take some time with some revision necessary and so much else going on at present. Show me a log and the macro file and i'll try to fit you in. I do try to deal with support questions within a short space of time but I cannot guarantee it. I really need more technical inforamation. If there is a documented facility for this then I'm positive that it used to work. Have you checked that your PFCHid is up to date, for instance? Isn't that what there's also Hdg> and Hdg< I can't imaginre you are the first user with such needs. You say Hdg> and Hdg< don't work as advertised. Do they do nothing? Pete

I had on of those when I had a PFC console. Really? I think the fast/slow rotation system was dependent on an appropriate indication from the device. i don't recall it being based on internal timings of changes in the DLL itself. Perhaps the hardware is not capable of that? Pete

Yes, I see it -- I just updated Addom Manager to check. Well, if GSX runs all I need to do now is convert my PFCFSX.DLL and PFCHid.DLLs, and wait for AS16 for P3D4, and I can run my cockpit with all accessories okay***! (I'm using Windows 7, which is no problem for P3D4 -- but Win10 problems are delaying my release of FSUIPC5). *** Excepting not at present being able to move the GSX and ProATC/X menus into the screen in my cockpit. I need an extra facility in P3D4 for that, pending L-M implementation. Pete

Whether internal or external, we all use SimConnect for the interface into P3D. So, do you have GSX running? With or without a BGLMANX.DLL loaded? Have they done away with BGLMANX.DLL and made its code run elsewhere, rather than convert it to 64-bit? Pete

As in FSX and P3D1-3, it's only ever added by some add-ons which want it there, FSUIPC probably being the most common. The Modules folder was where most previous versions of FS stored their own DLLs, and it was the only place you could put add-on DLLs to get them loaded in the days before imConnect and DLL.XML. Pete

I run the main ProSim EXE on a client PC. I have a copy of the FS PC too, but only for the database update when I add scenery. I do run ProSimMCP on the FS PC, because otherwise the slight delay in controlling by A/P can induce instability, expecially if you ever use 2X, 4. You should refer to the ProSimForum really. I'm sure you'll get more definitive help there. That's where I go for help. Pete

I don't know. I'll try it here. [LATER] No ... same problem. It's something to do with P3D's use of .NET Framework (which FSUIPC has nothing to do with). I'm trying to find out why it loads okay without FSUIPC but not with. Of course FSUIPc makes it work quire a lot (via SimConnect), so there's a lot of things to eliminate. I'm adding lots of logging to find out which. Pete

Sorry, there's no way I'm going to embark on an Android or IOS version of WideClient. I've got far too much on as it is. Pete

Yes, of course. The whole point of FSUIPC is that cross-platform compatibility -- right through since FS98 days. Pete

Does it need one of my PFC DLLs too? Because I've got to convert those to 64-bit when I'm satsfied that FSUIPC5 iss bulletproof, which it seems not to be yet, at least on Win10 (it is okay on Win7). The problems I'm having sem very closely related to those others are havong, as in the L-M support forum. So I might have to await an L-M fix. Other bits like the 64-bit versions of PFCFSX.DLL and PFCHid.DLL will have to follow, later. No timescale until I know FSUIPC is fully ok. Pete