Pete Dowson

I've looked at PFCHid and the PFC protocol for encoders. As far as I can see, the protocol says you might get the number of steps (i.e. the 1, 2, 3, or 255, 254, 253 for -ve) and/or a "fast" flag, indicating it is being turned fast. For macros, my code seems not to handle both more than 1 step AND the "fast flag", if they both occur. I need to know if you get the fast flag, so I've modified the code a little to check that and use > or < if it is set irrespective of the number of steps returned. Download this update please: http://fsuipc.simflight.com/beta/PFChid148_TEST.zip If this works, well and good. If not then I guess I'll need to determine "fast" from the number of steps. In that case you'll need to do more experiments with logging enabled, please. You'll need to determine how many steps should be needed to make a > or < selection. (After all 2 or 3 may just be the result of you turning a little too far -- it would be irritating not to be able to get +1 or -1 changes). I think all the users of the RIC and the heading knob in the past must have either been using standard Heading gauges, which would be handled without a macro, or were quite happy without the "fast" entries. Because PFCHid has been around like this for about 12-13 years! Let me know please. I'm working on the 64-bit conversion now and would obviously like whatever fix seems best in both versions. Pete

The correct place to obtain FSUIPC5 is in the Download Links subforum, here in SimFlight. That other link you have found: actually does point to the same release. ALL my releases are found here, in SimFlight (and even the pointers over on the Schiratti "Dowson" page point back here). Just because the word "beta" is in the path name doesn't mean they are Betas. I orinally had no control over that part of the pathname -- the area provided for me to place the files was named by SimFlight back in the days when Enrico Schiratti hosted the main releases and I just provided updates and Beta copies here. Now, however, all my work is hosted here. No, no need. If the above link is the one you used, the it is okay. It is not a Beta. Pete

You allready supplied the Install log, and I certainly didn't need pictures of anything!. Your DLL.XML already has many entries. How come? Are all those DLLs ready for P3D4 already? Look: <Launch.Addon> <Name>IvAp</Name> <Disabled>False</Disabled> <Path>D:\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path> <Commandline/> </Launch.Addon> <Launch.Addon> <Name>FSTramp</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>F:\FSTramp\FSTramp.dll</Path> </Launch.Addon> <Launch.Addon> <Name>VAInterface</Name> <Disabled>False</Disabled> <Path>Modules\VAInterface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>Air Manager</Name> <Disabled>False</Disabled> <Path>F:\Prepar3D v4\Modules\Air Manager\AirManager.dll</Path> </Launch.Addon There's a > missing at the end of that last line above. That will certainly make the DLL.XML file fail to load FSUIPC. My installer would not have removed that -- it must have been a bad file beforehand. There's also an extra unwanted line after that missing >: </Launch.Addon> So, at least two faults in the file before the added FSUIPC entry. Also I am pretty sure few if any of those are 64-bit DLLs which can be properly loaded and run in P3Dv4. Have you just copied your P3Dv3 (or, worse, FSX) DLL.XML across? You cannot do that! DLL's are run inside the P3D process, and must be 64-bit versions for P3Dv4! Try removing the DLL.XML file and re-running the FSUIPC4 installer. Pete

There's no "Beta" version you can download. What are you downloading? No. I think I caught SimMarket on the hop by releasing so quickly. You cannot, yet. And certainly not in some sort of illegal downloaded "Beta". I don't do public releases of Beta versions. Pete

That's okay. That's only a precaution in any case. The installer normally copes without worrying about that. It would be useful for me to see that, please. Also, can you check the Modules folder in P3D4. Is there an FSUIPC5.LOG file there? If so, I need to see that. Pete

Oh, that must be a mistake by SimMarket. I think they have problems setting up the sales page at present, and it seems forgot to remove the references they put in ready. You'll be able to buy it at the same time as every one else, when SimMarket are ready. I obviously took them by surprise by my early release of FSUIPC4. Pete

Yes of course. Have you not seen the User Guide yet? It even has pictures of them. Not until you register, then everything in your INI will work again. Pete

You mean in P3D4? In the Settings - Controls section? I don't remember off hand, but it is there somewhere, because I disabled it myslef last week. Keep looking. L-M have moved things around a little. If you get stuck, ask in the P3D Frukm over in AVSIM or on the L-M forums. I'm taking s little break. I'm going a bit dizzy here. Pete

You mean the "pay booth" at SimMarket I think! It isn't an "upgrade" -- you use the same installed version of FSUIPC5 and simply register it. What page are you trying to go to to get an error 404? No links to the payment page are available until the page actually exists. Pete

Well, I have many applcations using offsets and working well. There's no change in this interface. I really don't know which offsets he thinks are "missing" (by which I assume he must mean "don't work"?). If he or you would like to tell me which, I can easily test them here. Offsets are never actually "missing" -- the offset number is simple a value between 0000 and FFFF (0 and 65535 in decimal), and that range is always the same. Maybe he is saying P3D is not responding to the throttle changes. that is a different matter. Why don't yo enable Offset Write and the two Event logging options, and see for yourself. Pete

The FSUIPC5 application interface is no different that that for FSUIPC4 (or FSUIPC3 for that matter), so I see no reason why it should not work. Haven't you tried it? Pete

Offset access for applications does not depend on registration. Button and Switch assignments are nothing to do with "offsets" but are part of the facilities in the Registered install. Sorry, I don't really know how much ProSim uses FSUIPC. On my own system ALL of the ProSim assignments are via FSUIPC offsets because my hardware drivers are not ones recognised by ProSim, but ones I wrote myself. I assumed ProSim used SimConnect for most of its interaction with FS. From the sound of it you won't have any difference whether you register FSUIPC5 or not. Maybe you need to ask more questions in the ProSim Forums? Pete

Sorry, there was no offense taken. I would just like to save folks the time and trouble to post pictures which are provided in any case. My replies are not just for the poster -- I'm trying to help others help themselves. If the Forum were the only reference I'd understand the need for all these basic clarifications, but it isn't. Pete

Apparently they are dependent on someone or something in the USA, and they ot it's not awake yet. They apologise for the delay. Pete

Why post pictures here when you can see these in the FSUIPC5 documentation? Didn't you look at all? The ZIP file you downloaded includes a guide to installation, which tells you what documents are installed and where to find them. Then, within the first few pages of the User Guide, it shows you precisely the same picture as you posted first, above! (The Logging tab picture is of course shown in the Logging section). It would have been much easier for you just to look, wouldn't it, than go to the trouble of doing screen grabs etc? :-( Pete

Unfortunately it seems SimMarket aren't quite ready yet with their sales page. I thought I was late releasing FSUIPC5 on Thursday instead of Tuesday. I supplied Simarket details last weekend and apologised to them be being late with the program! I'm talking again with them now.

This IS the Support Forum! You are posting in it!!!! It's the starred thread within 3 or 4 threads of this thread!! [LATER] I've pinned it now so it's at the very top of the Forum. I'm sure you can manage to find your way there!

Mouse look is okya. Mouse macros are a totally different thing. see the documentation please. Pete

Why do you want to convert LINDA to 64 bit? Does it have modules (other than Lua plug-ins) which run inside P3Dv4? External processes can remain 32-bit. No! The external interface has to be the same. DWORDs are 32 bits, and the pointer is used only locally to the calling program so it doean't matter to FSUIPC. It is a pointer for the linked LIB (if this is used) to use to store the data when it is returned. It doesn't feature in the interchange. It would be a 64-bit pointer if you recompile the LIB to 64-bit for a 64-bit program. but why bother? Try my existing TraficLook and WeatherSet programs, which just use the standard FSUIPC SDK-provided data. There's no 64-bit version of the SDK. I don't think it is needed. There's no reason for most utilities to move to 64 bit. Pete

You can have FSUIPC installed in any number of sims-- FSUIPC3 in FS2004, FSUIPC4 in FSX, FSX-SE, P3Dv2, P3Dv4, and now FSUIPC5 in P3Dv4. Once installed, FSUIPC is just another part of the simulator. I don't know when SimMarket will be ready. Last I heard they said "tomorrow" (i.e Friday). Pete

NO! No need to uninstall anything! You just can't run two flight sims at the same time, that's all. Their idenntifying window names will clash. They probably won't run at the same time in any case, with one of them saying "another ... already running" or similar! This is nothing to do with FSUIPC. The sims are all sepaarate and you can swap between them as you wish, but by stopping one and starting another. Nothing related to FSUIPC. Pete

It just won't install in anything but P3Dv4, so you don't need to worry about "excluisveness"! Pete

FSUIPC5 is a 64-bit version for P3D4 only! You stay wilth FSUIPC4 on FSX-SE (4.967 just released today also). FSX-SE is a 32-bit program! Pete

Just copy it over and rename it FSUIPC5.INI. No version numbers to edit -- those are written by FSUIPC each time in any case, for information. Also copy any Macro files and Lua modules you use -- but remember, mouse macros aren't supported (yet). Hopefully they will one day -- dependent upon L-M. Pete

No conflict. P3D3 and P3D4 (and P3D1 and P3d2 and FSX and FSX-SE and FS2004 etc etc) are different products, entirely separate except that you can only run one of them at a time on one PC (due to Window name constraints). Pete