Pete Dowson

Well the first two are wrong. You need \\ for every single \ as that character is an 'escape' character, used to insert things like returns and tabs etc (\r = return, \n = new line, \\ = \ etc. Standard in many programming languages including Lua. In the other two you suddenly decided to use \\ instead of \, so I think you really knew this. In the third one the EXT_MIN and EXT_CLOSE should be in "". Did you create a folder named DOS in C and put "StartDCS.bat" into it? Because that's what you show in the last two. Why "DOS"? Did you mean "DCS"? I think you need to be a lot more careful what you type. Is is not like errors in emails and messages which people can still understand. Computers are basically stupid. You must be 100% exact. Also, the "error" number being returned should be used to see what error might be indicated. Log the value by ipc.log("ext.shell returned error = " .. error) Pete

Care to share more details so others can do this, please? Pete

Thank you for this feedback! Good also to know you have it fixed. Pete

You most certainly are! Those are OUTPUTS, from the aircraft, TO those FSUIPC offsets (647F 6480), for displays in cockpits. And they have to be enabled in the INI for the aircraft, as described at the beginning of the .h file. They are all read only. As I said, all the added controls are listed at the END of the .h document in the SDK. Do not mix up "controls" (which are actions) with "offsets" (which hold data). Sorry, there's no way I can be more specific. I don't have or use any PMDG aircraft. BTW, what on earth do you mean by this Where do you see an "offset" to put it into? You should be assigning to <custom control>, as I said. no "offset" comes into it. Pete

The 9 x86) is wrong, again. EXT_HIDE works on Windows and may not work with Batch files, which operate via the DOS-type Command line interface Pete

As I said "Run" (and "RunIf", as documented, is a version of Run) cannot create a process from a BAT file. You must use the shell facility, as I also said! In any case, you seem to have tped "9" instead of " (" in the path (AND you repeated it in the last line!). Please do check your own typing. Why are you trying to run ipcDebug.lua? Pete

Yes. Using the list at the end of that .h file you need to compute the "custom control" number. Just add the base to the additional number given for the control. You assign to <custom control> in FSUIPC, using that number. The parameter for the control is another matter. Some just seem to use zero or non-zero, for a simple off/on action, others need a value derived from Windows' mouse operations. PMDG didn't exactly make it very user friendly I'm afraid, and the list will be different for different aircraft (737, 747, 777). Pete

Well, yes ... but FSUIPC does first try to see if it can change it into a UNC path (one usable over the Network). If it can it will change the path part to suit. But if not (as in your examples), the Logged and 0130 offset version is exactly as received. Even it can match a shared folder, to create a UNC path, it doesn't touch the rest of the filename -- except to add an N to the end if the name ends in .PL. (I think this was because of some earlier bug in FS). I can esily extend that fix by appending PLN or .PLN as necessary if there's no .PL either, including the period only if there isn't one. I'll implement it here so it will be included in the next FSUIPC4 and FSUIPC5 update, whenever (I'd rather not release an update with only that change). No, P3D3 and P3D4 have the same for 1JY2. I don't think they've changed any of the airport BGLs. I'll report the bug to L-M. Maybe they'll fix it in a P3D4 update. Pete

I was puzzled when I first saw this, so I checked. There is no "path" function in the ext library. Not sure how you invented that. The ext.run function simple takes a complete pathname, so the path itself is part of that. The other thing is that you can't use ext.run for a batch file. It creates a process with the program name given. So, to execute a batch file you'd need to ext.run the command line program, command.exe, and give the BAT file name as a parameter after the /c. Instead of ext.run you should use ext.shell, which "shells" the command you give out to the Windows shell mechanism, which can execute most things. This won't give you a handle on the process you are restarting, of course. You'd need to "run" the Dolby Cockpit Sounds program directly for that, after presumably closing or killing it. Pete

You should use the PMDG dedicated control numbers for all that. There's a lit in the .h file you can find in the SDK folder for the installed aircraft. Yes, of course. Please look at the right-hand side of the Axis assignments tab in FSUIPC Options. Check the User guide, Axis Assignments chapter. I think the part about that area starts at page 44 (but that depends on which edition you have). Pete

You can't do that directly, only via Lua. You can assign buttons to any Lua file placed ito the Modules folder. Pete

This is covered in some detail in the FSUIPC User guide. Check the Contents, near the front. There's an entry under "joystick Calibration" called "Calibrating flaps with specific detentes". Just reverse it (REV) before calibrating. Have you actually looked at the Calibration tab? Again, this is what the REVerse checkbox is for! Do that BEFORE calibrating. Please do refer to the FSUIPC documentation. It is all there. Pete

Sorry, to be clear: the yoke inputs are working and affect the aircraft flight, but the visual yoke on screen doesn't move? If so, which aircraft it this with? Does it happen with a default aircraft? Are you assigning in FSUIPC, and if so, in which way -- to FS or to FSUIPC calibration? Yes, of course. It is the User manual which you were advised to refer to by the Installation and Registration guide! You will find all FSUIPC documentation in the FSUIPC Documents folder, inside the Modules folder. Pete

Hmm. Strange. I'll check my processing of the Plan filename. But I know it does not normally remove the extension, so there's no need for it to search for a period. The FSUIPC log file will show the Plan name as received direct from SimConnect. What does that show? If SimConnect does this, then all I could do is check for a .PLN ending and add this if it isn't there. This might be the only solution for FSX and FSX-SE (and probably P3Dv1-3) as those sims are unlikely to be fixed (and anyway, they'd probably say don't put periods into flight/plan names). Of course the quick interim solution would be to save the flight or plan with a name without the period. Is your program (sorry, I don't know what it is) generating the plan automatically? I wonder if Flights with such names also suffer. Pete

I think WidevieW connects multiple PCs all running Flight Sim. rom your description you are only running FS on one PC, so really WidevieW has no use. FSC can connect from a networked PC not running FS, via WideFS, not WidevieW! BTW you posted EXACTLY the same message twice, in two threads. I've deleted the duplicate. Pete

Er, wait a minute. Are you actually saying that you are assigning an Engine Start button, and it saves and reloads next time? Yet you say "still no storage of my button commands"!??? If that is the case, then there just MUST be more files in the Modules folder -- FSUIPC5.LOG and FSUIPC5.INI. I now get the feeling you are looking in the wrong place. Try starting Explorer "as administrator (a right-button option) before looking. Maybe you are looking at only what Windows thinks you should be allowed to look at. (One of the big penalties of having P3D installed in its default location, "Program files". That is very much over-protected against us users. I never install any flight simulator in the place it wants to go. my P3D4 is in E:\Prepar3D v4, and my P3D3, P3D2 and FSX, similarly installed in simple folders outside of the system driver (C:) altogether. Pete

You must set the minimum value numerically less than the maximum. In ALL calibration tabs, values increase from left to right. -1 is less than +1. If you want it the other way around, just set REV to reverse the axis first. This has ALWAYS been the case in all versions of FSUIPC since Calibration facilities were added, before FS2004 days. BTW the currenly supported version of FSUIPC is 5.121a. Version 5.12 is out of date. Pete

If it isn't FSUIPC5.DLL then FSUIPC5 cannot be loaded and run, as that is where it has to be. I've no idea what a "words data file" is, sorry. Nor a "DLL data file". I'm pretty sure that by default Windows will label FSUIPC5.DLL as a "DLL file". But unfortunately all those labels can be changed by any program which thinks it can use them! That is what it is important to change the Explorer option as I said (this is also strongly recommended in the FSUIPC User guide). As I said, change the Explorer options so that it doesn't hide things from you! In windows 10 this is by: File -> Change folder and search options -> View -> uncheck the option "Hide extensions for known file types". Pete

I assume "FSUIPC5" is actually "FSUIPC5.DLL". Best to change folder properties in Explorer to stope hiding known extensions from you. Otherwise the DLL, LOG and INI files are all likely to look indistinguishable to you. Is that for "Everyone"? So they were not ticked before? If they weren't already ticked then something is going wrong with the Installer. Maybe it cannot set the permissions AFTER the Modules folder is created, but it should be able to. I need to know these things, please? With those ticks added for "Everyone", and running P3D again, do you now get an INI and LOG file? Also, if you've now changed them, best to re-run the FSUIPC5 installer. You could also try (a) running P3D4 "as administator", or (b) deleting the complete Modules folder and re-running the 5.121a Installer to re-create it. Pete

Well, that is sometimes easier to accomplish with several wave files, edited to have the levels needed, but the Lua sound facilities do have a volume capability (also a directional one, for a quad sound system), which always worked with FSX and P3D3. Not sure yet about P3D4 as I've not tried all the options yet. Pete

Yes, you can do all that with a Lua plug-in. You can read and check things like speed and flap settings and play already existing sounds (WAV files) via Sound library functions. Please take a look at the Lua library document in your FSUIPC Documents folder (in the Modules folder). Alternatively, if ProSimAudio can do the job given the right triggers, then you could using a Lua plug in to read the speed value, and set flags in user offsets (any of 66C0-66FF) which are then assigned as triggers in ProSim. Pete

With 5.121a there should be no problem with FSUIPC being able to write to the P3D Modules folder, because that installer will have set the appropriate permissions. This needs checking, please, because it worries me that you aren't getting things saved. Could you please find the P3D Modules folder and tell me what files are listed inside that folder? Just use Windows Explorer for this, as usual. If you can, it would also be very helpful if you could check the folder permissions, because if they are not being set correctly it would be a serious Installer problem for me to fix. To check Permissions, do this: 1. In Windows Explorer RIGHT click on the P3D modules folder, 2. Select "Properties" down at the bottom of the popup list. 3, You'll see a dialogue window called "Modules Properties". It has 5 tabs I think. 4. Select the "Security" tab. This will display a two part window. 5. Look at the list at the top. there should be an entry labelled "Everyone". Select it. 6. Then in the lower list all the first 6 entries should be ticked. 7. That's it. Just click Cancel to exit. Please tell me if this is hard to do, or if anything doesn't look like what I said. Thanks, Pete

Well, thanks for the sarcasm, but what on Earth do you find aggressive about it? I just asked where you got FSUIPC from, because I don't understand how you could do so without seeing the details for purchasing registration. And the rest is all factual and intended to be helpful! I do my utmost to help everyone who asks for it and it takes most of my time. I am also disabled, and getting too old for this sort of treatment (74+). I cannot see how I deserved it in this case. :-( Pete

There is absolutely no difference whatsoever in a "full" and free" version The difference is only made by whether you register it or not, and to register it you have to purchase a registration. How did you find and download FSUIPC? All the places I know of tell you where to go to purchase a registration -- on SimMarket. Judy go there and click search. This information is also shown in the FSUIPC documentation, installed by the FSUIPC Installer in your FSUIPC Documents folder (within the FS Modules folder). Pete

Can you please confirm that you are using the latest version of FSUIPC (5.121a) ? Because he problem you are talking about was known on Windows 10 systems where folks made the mistke of letting P3D install into the Program Files folders. That problem was fixed, at least in all test so far. If you don't know what version you are using i suggest you download it again and re-run the installer. Not at all. Maybe English is not so familiar to you? "Files" are items which go into "Folders". The term "folder" describes itself really, a place into which you fold things. Pete