Pete Dowson

FSUIPC 4.968 is now released. Pete

FSUIPC 5.101g is now released in the Download Links subforum. Pete

FSUIPC 5.101g is now released in the Download Links subforum. Pete

FSUIPC 5.101g is ready to download, in the Download Links, for your kind attention. I'm pretty sure the offset writing problem is fixed, but the VRI (part of COM) and HID (ditto), and EXT library functions have had revisions needing testing. I should be able to test the latter two, the VRI / COM parts should be well tested by your VRI implemetation. Pete

For LINDA and VRi you will need to update FSUIPC5 to version 5.101g which I'm uploading imminently -- check the Download Links subforum in about 30 minutes. The VRi facilities used by LINDA's Lua plug-ins have been extensively revised to handle 64-bit "handles" separately (Lua cannot cope correctly), so the facility needs testing. Feedback welcome, please. Pete

No, there's no specific information about that in those documents. I will respond to such questions, of course. I was only responding to your comment that you "didn't know about the documents in that folder" in response to another poster suggesting that you read them. Sorry if you really meant that you knew about the documents but didn't know they explained tranferring from one sim to another. Pete

5.101g will be released shortly, with several problems relating to Joystick Scanning (see other threads) and fixed for LINDA an other offset using programs, plus VRi support (untested -- released for VRi users to test and report). If you're hoping I can diagnose PMDG problems I'm afraid you are mistaken. At present that's between PMDG and L-M, because I cannot debug PMDG software or what it is getting so wrong from SimConnect, which I assume is the common factor. Pete

They are listed, with information about where they are placed, in the Installation and Registration guide, the document included in the main FSUIPC install download ZIP! I suppose you didn't read that either? :-( Pete

This is the same problem reported in the LINDA thread and which has taken quite a lot of work to isolate. It should be fixed in the next interim update (5.101g), probably this afternoon. Please check the Download Links subforum tomorrow. Sorry, what is your problem with that "Running in" line? It looks correct. The information logged there is what is received from PP3D after FSUIPC successfully connects. Pete

If your Registration was for "WideFS7" (i.e. with FSX or P3D), then, yes. I assume you mean WideClient, on the client PC? If so, yes. I've investigated things like this. It all depends on the drivers in that PC -- and the crash is actually in the driver. Without notice it just makes the device handle invalid. The crash is invariably in the driver itself. I never managed to solve it (it has been the same for nearly 17 years). Best not to change the hardware configuration whilst things are using it. Pete

Only one such device is listed (joy ID 1). It's the letter assignment which goes wrong. And I don't thoink it's a new problem. Thomas managed to isolate this problem on a different device altogether and in FSUIPC4. It is caused by there being a space at the end of the OEMname for the device in the Registry. That name is used in the INI file, but spaces at the ends of parameters effectively don't exist, so every time FSUIPC obeys the "AutoAssignLetters=Yes" request it sees that it is a different device. This seems quite a rare occurrence -- you are only the second person to repprot it, including Thomas. Setting that parameter should stop it, but version 5.101g, being released soon (probably this afternoon, as an Interim DLL only update, will fix it in any case. Keep an eye on the Download Links subforum. Pete

That's an intention, for future independence, but the current methods should work completely with FSUIPC. However: You will probably need 5.101g, an interim update I will hopefully be releasing this afternoon. It should fix problems with some types of "offset" writing -- ones which could especially affect the PFCMCP. Please see the thread about LINDA for more details on this. It's been a complex process to resolve. Pete

Have a look at the business of tillers/steering in the documentation. I am sure searching on some word like that will find the explanation for you. There's also an INI file parameter to control its operation (MaxSteerSpeed). Pete

Sorry, no. I can't keep track of folks with specific problems. If this thread is only about this problem I will probably post a note here, but otherwise please just check the "download Links subforum above. And it will initially be an "interim" release -- no installer, just the DLL which you copy to your sim's Modules folder. Oh, the version for FSX/P3D3 will be 4.968. Sorry, I think I mistyprd it above. Pete

Well , I could reproduce it with a release-compiled version, but not the debug-compiled version, which is worrying. And because I had little access to proper debugging facilities then it took a while to narrow down, mainly using logging in narrower and narrower areas. I found that a flag I was testing was somehow being set. I though this must be because it was being trampled on by something, so I moved it somewhere else completely, to no avail. I reprogrammed what the flag was being used for, and now it all works okay. But I am a little worried that I've simply hidden another problem by doing this. More checks tomorrow. Pete

It is due to the this odd device:609 Product= UMDF Virtual hidmini device Product string 609 Manufacturer= UMDF Virtual hidmini device Manufacturer string 609 Serial Number= UMDF Virtual hidmini device Serial Number string 609 Vendor=BEEF, Product=FEED (Version 1.1) which is hanging when asked for details. You can either disable it in Windows Device Manager, or wait for FSUIPC 4.968 which will be released in the next two days with that fixed. Pete

Or you can use FSUIPC and not PMDG. Though most folks seem to be finding workarounbds, to do with the order in which you load aircraft. Even I can do that here. Pete

Sterring Set is an FS contorl, it is NOT the FSUIPC tiller control. For that you have to use the "Direct To FSUIPC" mode of assignment. FSUIPC is working fine from what you say. You are just misunderstand some of its advanced functions. It most certainly isn't anything t do with axis responsiveness. Pete

There's no way I can deal with the PMDH 747 problems. I don't have PMDG source fgiles. Please refer to PMDG. Pete

No. There's no new purchase necessary. If you have WideFS7 registration for FSX or P3D already, you can use that. Pete

Good. But with the latedt FSUIPC5 updates (5.101d or later) that certainly should not have been necessary. Pete

Yes, but the 64 bit version of GFdev.DLL is not ready yet and isn't included. It would probably be part of their DLL, with full documentation as before. Don't worry. I'm in touch with GoFlight and they will advise me when it is ready. Pete

Strange indeed! BUT I think I now have a clue about that. I've managed to repro it, but ONLY WITH A RELEASE VERSION! Of course, for testing I need to use a Debug version, because that way I can set breakpoints and do tracing and so on. So I never tried with the compiled test version!!! Now it gets difficult. I have to work out what actual code difference is doing it! Pete

Yes, my error. Don't worry. The difference is only in the JoyLetters assignments, a minor change. Pete

How long do I need to let it run? It's been going 750 seconds now (over 12 minutes) with no sign of any errors! :-( Win10 next ... Pete