Pete Dowson

Well, that version of the manual dates to the first release ever of P3D (4.0), and the first of FSUIPC5. So I don't know how long ago you got your FSUIPC5, but if it was later than June 2017 it must have been from some unauthorised site. But there were major changes in P3D between 4.0 and 4.4, and even more major changes in FSUIPC5 as features missing in the first release were added. The User Guide itself may not have changed substantially, but other parts of the supplied documentation did, as well of course as FSUIPC5 itself. Pete

That was the first issue when P3D4 was first released. Are you still using P3D4.0? The only currently supported version of FSUIPC5 is version 5.15, and that needs at least P3D version 4.1. The current version of P3D is 4.4! The FSUIPC documentation supplied is listed in the Installation document included in the download ZIP, and that also tells you where to find it all -- in "FSUIPC Documents", a sub-folder in the P3D Modules folder. You really do need to check that you are using a current and supported version before posting support questions. Please see the Announements sub-forum above. Pete

No waste. It reminded me to revise / clean up / unpin my original notices here, posted when the main Lorby program was certainly needed! Pete

The current version of MakeRunways does NOT use the Lorby AddonOrganiser, but a special program provided by Lorby which is in the ZIP and must be installed alongside MakeRwys. As stated in the MakeRwys README document also supplied in the ZIP: NOTE for Prepar3D versions 3 and 4 Those Prepar3D version 3 and 4 scenery installs abiding by the new L-M system for add-ons will NOT be seen by MakeRunways unless you copy the LorbySceneryExport program from the ZIP into the Prepar3D folder, to sit beside MakeRwys.exe. I'm demoting this thread from being pinned and removing the earlier entries because the instructions in the package are those which need to be followed (as is the case with most packages). Pete

PFCP3D.DLL was my early thoughts on the name for PFCcom64.dll (the serial port version). This was because the FSX one was called PFCFSX.DLL. Could you tell me in which manual, exactly, you see that reference? In the FSUIPC5 User Guide the references on Page 23 are correct. There is one which needs updating on page 39. There's also one needing updating on page 18 in the FSUIPC5 Advanced User's manual. I will correct those references. (Neither say "forthcoming"). Anyway, PFC Hid equipment needs PFChid.DLL (32-bit) or PFChid64.dll (64 bit). Pete

Not via FSUIPC offsets, no, sorry. I doubt if there's any way to do it by program -- same goes for pretty much all the P3D user interface settings. Pete

What version of FS or P3D? How many cores do you have on your Processor? Are they all enabled for the Sim (i.e. no "AffinityMask"? FSUIPC does everything it can to get things running, but it will always give the flight sim priority. It would not be right for FSUIPC to make the Simulation performance worse. The whole point of flight simulation is to simulate smooth flight, after all! Whichever works best for you. For the fps, check the offsets list -- it is there. I don't recall the actuall address. It isn't a plain number, you have to divide it into another number. Details are in the offsets list in your FSUIPC Documents folder. Best to adjust your sim settings so that frame rates never go below 20 fps. After all, below that it isn't a good experience, is it? Pete

No! For FSUIPC5 and P3D4 you need the 64-bit version, PFChid64.dll! That's because it is NOT a joystick type device, and needs a proper HID driver. And that is where PFChid64.DLL comes in! Please read my previous sentence, just above. Pete

PFCHid64. The PFCCom versions are for the serial port devices, hence the "COM" in the name. "HID" in the Hid version names says it's for the HID (=USB Human Interface Device) version. The main DOWSON page on www.schiratti.com/Dowson does tell you: PFCHID 1.49 PFChid.DLL and includes PFChid64 for P3D4 An add-on for FSUIPC3, FSUIPC4 or FSUIPC5 to drive PFC's modern USB HID devices June 12th 2017 (1.04 MB) and it is also listed in the Docnload Links subforum above, thus: Pete

That's odd. You are right, it no longer restores the file! That's annoying. I shall have to copy it across in FSUIPC then,, not just delete the existing one. But I've been running P3D4.4 here on two PCs and with FSUIPC all through the Beta period and now with the release version, and no CTDs. Also, if this were a general problem I would expect many more reports, because every 4.4 user running FSUIPC would get the same CTD. Nevertheless, it seems wrong for P3d4.4 not to do this basic task. I wonder if that also applies to the Scenery.cfg file. It's always copied its default into the ProgramData if there isn't one already there. BTW you can run with "NoWeatherAtAll=Yes" set with no adverse effects unless you are using an add-on which reads or sets weather through FSUIPC. Pete

The weather folder isn't involved. The wxstationlist.bin file is in the same folder as your Prepar3D.CFG file -- i.e. your AppData\Roaming P3D4 folder. You can safely delete that (if FSUIPC hasn't already done it for you). P3D restores it from the original one, which isn't changed, and it is that which is in the Weather folder. But the corruption may be in one or more of the .WX type files in your P3D documents folder, among the saved scenarios. If you use a weather program like Active Sky you can safely remove all those in any case, as whatever weather they supply will be overridden by the weather program settings. Otherwise just move them out temporarily as a test. Pete

Sorry, you said FSUIPC sees all the axes with the software running. I don't see how a refund can be justified just because you have something wrong. Have you asked Saitek for a refund for your X56? There are plenty of users with X56 which have no problems, and FSUIPC is using all standard Windows DirectInput methods. It knows nothing specifically about any joystick devices, it merely gets values through standard Windows facilities. Pete

This is almost always due to a corrupted weather file -- either a .WX file or the wxstationlist.bin file. Unfortunately, when Simconnect is asked to supply weather inforamtion to FSUIPC (one of the dirst thing it does after the scenario is loaded), it reads these binary files which do not have any checks built in, and obeys them. The log shows nothing else wrong. Oddly you have no (recognised) joystick type devices at all. The event details from Windows Event Viewer might be the most informative, but I don't seem to have anything which will open "evtx" files. Could you simple grab the text from the event viewer instead, and paste it in a message please? The INI file has almost no settings in any case. And what do you mean "no luck"? It is an ordinary text file and easily deleted if you want to revert to default, which it almost is in any case. If you want to check whether or not it is down to corrupted weather files you can try adding NoWeatherAtAll=Yes to the [General] section of the INI file. Or to check for other things which FSUIPC might do before you are "ready to fly" (which things are precious few) you could rename the FSUIPC5.KEY file, rendering it unregistered. Pete

Just "an amendment"? I feel your ability to determine what's changed from "looking at coding" is rather suspect! It was actually several months solid work (more than full time) -- but that was only the start. Then taking advantage of P3D developments as they occur, and for an indefinite time -- till FSUIPC6 (another 12 years hence for all I know -- but more likely till some serious revision like P3D5). Without such invstment in time the product would stagnate and be less worthy than I'd like it to be, not taking advantage of deleopments in the sim program and the interfaces added (such as in the PDK for P3D -- only Simconnect was in use before). On top of all that there's the time for Support work which has been almost full time right since FSUIPC1 back in 1998. (FSUIPC was completely free for the first 6 years. It was a hobby. I only had to start charging when my software business stopped earning. In the lhe little time left over I do try to have an occasional fly -- after all it was my hobby in the first place, and I think i ought to try to indulge a little at my age of 75. That an an occasional holiday of course. But as I said, it is your choice. It is what is is. If you feel cheated and that I am ripping you off, just don't but it. Actually -- please don't buy it! I'd rather not have a customer than an unhappy grouchy one! Pete

FSUIPC5 was a lot of work, and continues to be so with the ongoing development of P3D4. And it was the first new payware product from me in all the years since FSX was first released, in late 2005. FSUIPC4 was maintained, developed and supported for 12 years all for the one-off purchase price. But just don't buy FSUIPC5 if you think it isn't worth it to you. It's easy enough, No point in posting such an odd message. (And I've never heard of Olaf. He probably knows nothing about the subject). Pete

Have you tried COM1 transmit select and COM2 transmit select? Note that I doubt that any PMDG Boeing model will respond to the built-in FS controls.. They have their own systems, with the controls listed in the 2.h" type document in the aircraft's SDK folder. Look at the list at the end. You have to calculate the control number (just adding two numbers together), then assign by selecting <Custom control> (first in the list) and entering the calculated number. Pete

I think in was added in P3D later -- 4.2 with errors, fixed to indicate clearance in 4.3. Sorry, this should really be mentioned in the Lua PDF. I obviously thought no one would stick with such an old version of P3D4. I'll amend it for the next update. I can very strongly recommend P3D4.4. Excellent version, very robust, good performance, outstanding graphics. Pete

Which version of P3D4? Your script is working fine here. Maybe add a log entry when you invoke the event.textmenu function, just to check that your Lua is really running. To check that the facility is working add the following lines to the [General] section of FSIOPC5.INI: Debug=Please TestOptions=X8000 This will give entries for menus like this (this is a test menu only): 1498655 ### TEXT: 512 (Menu) From SimC, Duration 0.00, Flags 00000000, Len=81 1498655 SimConnect Text Menu 1498655 Choose which item: 1498655 Item #1 1498655 Item #2 1498655 Item #3 1498655 Item #4 1498655 Item #5 1498655 ***DISP*** Text/menu type 2 broadcast 1498655 TextMenu Displayed That last line is from your script. When I selected an item from the menu I got this logged: 1578262 ### TEXT_DESTROY: 512 (Menu) Result: 2, Flags 00000000 1578262 ***DISP*** Text/menu type 2 clear broadcast 1578262 LUA.0: Menu Opened so it gets called then, too, when the menu is cleared. Pete

You have some extra characters in your code, non-ASCII ones I think -- one character or more after the last ). Delete the line completely and re-type it. BTW you realise that using 0 to don't just get Menus, you also get Text Messages. For menus only you need 2. Pete

There's nothing to check "GSX menu" specifically. You just use event.textmenu and receive the text from whatever menu there is, when it displays. event.textmenu in the event library descriptions. It's been in there for a long time, but enhanced for P3D4 since FSUIPC 5.13. So I'm not sure what the "last version" you refer to is? Note that there are minor updates in the document in the 5.15 release too, but please check the first paragraph of the document It should say "(for FSUIPC5, version 5.15 and later, ...". The first day of the 5.15 release actually had the previous versions of the documents installed, for the very latest you'd need to clear your cache (F5 I think) and download again. But this is not necessary for this facility. Pete

Well, not really the right place as SimConnect.xml isn't used by FSUIPC or WideFS. The right place is probably the SimConnect SDK reference. But here's my FSX one which you can use: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <Address>192.168.0.170</Address> <MaxClients>64</MaxClients> <Port></Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Address>192.168.0.170</Address> <MaxClients>64</MaxClients> <Port></Port> <Scope>local</Scope> </SimConnect.Comm> </SimBase.Document> You'll need to change the two Address>192.168.0.170</Address> lines to contain your FSX PC's IP Address. Pete

Ah, yes. You can certainly get prblems with those adapters. I never found one which was good enough, and I went through quite a few makes. I use serial port PCI or PCI Express cards, plugged into the PC motherboard. Brainbox ones are excellent -- I have one in every PC to which I need to connect serial port devices (and I have quite a few). See: http://www.brainboxes.com/pci-express-serial-cards for PCI Express cards, and http://www.brainboxes.com/pci-serial-cards for ordinary PCI slots. You need the type to fit whatever spare slots you have. Pete

That latter point is even more reason why I think you need Saitek support to deal with this. Because nothing you've said makes sense if the X56 is a proper working device. There are so many of those (and the similar X55) in usuccessful use with FSUIPC -- with or without the Saitek software -- that your symptoms can only suggest a bad device, or faulty USB hardware on your PC. Pete

The keycodes supported are Windows keycodes. There are lists of all those I knew of at the time of first publication in the FSUIPC Advanced Users Guide, but for the full current list look here: ttps://docs.microsoft.com/en-us/windows/desktop/inputdev/virtual-key-codes There are special built-in controls for the Squawbox3 PTT ON and PTT OFF functions which also apply to roger Wilco and Advanced Voice Client. I don't know if iVAP bothered to follow those standards. You'd need to ask them. See the section Additional "FS" Controls added by FSUIPC in the Advanced user's guide. Only if VPilot implemented an FSUIPC interface and such an offset. Youd need to ask them. I don't use vPilot and know nothing about it. I really can't support other folks' software. You really need to talk to them. Pete

Sorry, but I do not know CPFlight equipment. If that unit looks like a Joystick type device, then, yes, FSUIPC should be able to see its buttons and axes natively. If it is recognised by Windows as a USB HID device then you could read the values by using a Lua plug-in which used the com library HID functions (there's a HID demo plug-in provided in the FSUIPC documents folder). In all other cases the answer is probably no -- you'd need to write a driver. I really think your question should be directed to CPflight. Ask them if the button and knob details can be read by programs other than theirs. Pete