Pete Dowson

There is code in FSUIPC to improve performance on all axes (and using 0BDC is treating Flaps as an axis -- it uses the Flaps_Set control) by eliminating successive identical settings. Otherwise these can arise in profusion by things like the scaling and smoothing and slopes changes performed in FSUIPC's calibration. If you only use 0BDC, or only assign Flaps as an axis, there's never a problem, but in this case there is because of the mixing of methods. The same would apply to throttles, spoilers, ailerons, elevators, rudders, mixtures, prop pitches, and brakes.. It has always been this way. I could probably change it for offset writes (as opposed to axis inputs) by deliberately overwriting the last saved value which the "efficiency code" is checking against. This shouldn't be difficult, but it isn't something I can do till I get back from my holiday which starts early tomorrow. I'm back on the 12th April. I wonder why he's writing to 0BDC in any case? One way around it is to write a different value first, eg. 1 then 0. That works fine. Let me know if you think I should change the code as above. Not sure how easy it is, and, as I say, I couldn't look till mid-April. Pete

FSUIPC is unlikely to help if your joystick keeps disappearing! Sounds like you need to turn off USB power management in Windows'' Device Manager. Pete

It isn't a single green line if you include new lines in the text, just like Radar Contact. There is no facility exactly like the Lua facilities which you can use from an external application program. You can invoke a Lua program instead from an application program. Otherwise you would need to use SimConnect directly. Pete

In the [Auto] section? Remove the space.You must get the name right. it needs to be 1= LUA DynamicFriction You misunderstand. It doesn't create that because you add another line saying 1=Lua DynamicFriction. The complete [LuaFiles] section is always made and contains a list of ALL the Lua files in your FSUIPC Modules folder. It is nothing whatsoever with anything else you do, all you have to do is put Lua files into the Modules folder. The lines in there are needed to enable button and axis assignments to Lua programs, they don't affect any Lua commands elsewhere, such as in the [Auto] section. In that case there is no such file in your Modules folder! Pete

Okay. tested and working: in P3D3.2, using FSUIPC 4.949k (the latest interim update released on Sunday), I assigned a button to Ctr+Shift+Z, which is assigned by default in P3D to "altitude bug set". That worked fine. Then, again in FSUIPC, I assigned that keypress to "Sound toggle" (so it would be obvious to me when it worked). It did work -- the button toggles the sound. Then, just to be really sure, I unassigned the keypress in FSUIPC and reassigned Ctrl+Shift+Z to Sound on/off in P3D instead. Again the button worked fine, toggling the sound. So, it seems P3D3.2 is fine. There's either something wrong with your assignments, or with the PMDG add-on. Pete

Er ... to which facility in Lua are you referring? The ipc.display one? I've already given you the equivalent offsets for an external program. What is confusing you? Pete

That's not a good check. Didn't you enable Button/Key logging and check in the log that the keypress in being sent okay? FSUIPC doesn't "talk" to PMDG. Key presses are just sent to the main FS Window, effectively emulating the keyboard. And this is the same on all FSUIPC versions and with all Flight Sims. If the keypress is being sent (and I thought you would have checked this), then it sounds like something it intercepting this in P3D, or causing it to be ignored. Why this should happen when keypresses are sent by program instead of from the real keyboard I don't know, but they are distinguishable if something really wants to. Earlier you said Are you talking there also about assignments to key presses, or to controls? If keypresses, then it definitely seems the key combination you are having trouble with is being singled out. Is it possible to reassign to a different one? If it affects all assignments to keys, and you didn't have this problem in P3D3.1, then something has obviously gone wrong in P3D3.2. I am checking here now (but not with PMDG aircraft, as I have none). Pete

What is actually calling your "start_pump_check" function? Much better and more efficient than a loop, you should use event.offset for the offset(s) you are monitoring, and have that call the function. It provides the offset address and current value as parameters, so the code becomes very lean. For intermittent events for which where is no specific event function, you would use event.timer (with, for instance, 10000 for 10 seconds) to cal a function at intervals. But that wouldn't apply for this case if you are monitoring offsets. Pete

You do NOT add any lines to [LuaFiles]. That section is created automatically by FSUIPC based on the Lua files it finds in the Modules folder. You must NEVER edit it. It is not a user area! If your Modules file contains the Lua program and you want it loading automatically you need an [Auto] section containing 1=Lua DynamicFriction BTW reinstalling FSUIPC does not disturb ANY files you have created or added, it merely updates the DLL and the stuff in the FSUIPC Documents subfolder. Pete

Yes, those are they. You get multiline by including new line codes embedded in the text, i.e. "\n", or returns, "\r". Hotkeys for answers are set in the table at offset 3210. Instructions are in the main "FSUIPC for Programmers" document. Pete

What "two offset"? Do you mean for messages, 3380 ad 32FA? Pete

No. And FSUIPC isn't treating it any differently. But I suspect most PMDG 777 users would be assigning direct to the <custom control> facility, using the PMDG published control numbers for these things. (See the 777 SDK folder, the .h file lists them all, after the data listing). Pete

4.858 is old and unsupported. You do not install a "registered version", you install the only version, and you may or may not register it as you wish. You can install new versions at any time without re-registering. Why don't you know? You must always install the latest version if you want any support. FSUIPC4 currently supports FSX, FSX-SE, P3D1.4, P3D2, and P3D3 up to P3D3.2. No, you purchased FSUIPC4, not a specific version of FSUIPC4! Pete

You have two AllowShutdown parameters. Only one will be read, possibly the first, maybe the second. I don't know how Windows behaves when you have duplicate keys -- you should only have one. WideClient will try to run those three programs when the connection is up and running. Same there for that one program, assuming "notepad.exe" is in the same folder as WideClient, because you've not given a path. And there is no parameter "AppsOnly" for AllowShutdown, it is "AppOnly". Why? There's almost never a need for that. You mean the "AllowShutdown=AppOnly" action? You need to specify that if you want that. Pete

Well, I think so. I suppose it's okay if you never want anything else on it. You'd need to run regedit and delete these two keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 The FSUIPC4.LOG looks fine, except that you made it extremely long by enabling weather logging. Why did you do that? Anyway, your ACARS program should work. maybe it doesn't like the version of FS? Isn't there any support for it? You should uninstall old versions properly first, not just delete them. Pete

Not the same. The FSUIPC facilities for Lua plug-ins provide display facilities using a similarly transparent (and undockable) window (ipc.display and others), where you can display a list of choices and detect keyboard responses, and there's also the ipc.ask facility which is similar and collects its own typed and visible response which could be more than just a detected keypress. The display facilities can be used from an application program via offsets. That's the way the Radar Contact menu system works, for instance. It registers hotkeys with FSUIPC for the responses. Pete

That's the Install log. That just shows you installed it okay. the run time log is called "FSUIPC4.LOG", as I said. However, the installer log does show up some bad things in your Registry. For instance it says you have an FSX installed in D:\FSX. If that's no longer true, why does it say that. Did you delete FSX without actually uninstalling it? The Registry also says you have a Prepar3D version 2 installed in P:\Prepar3D, but that too seems wrong. What have you done there? The system appears to be in a mess! I see you have version 3 of Prepar3D in the root drive P:\. Was that intentional? It is very unusual. Pete

Show me a complete FSUIPC4.LOG from the P3D Modules folder. Close P3D first. Paste the log into a message here. Have you bought WideFS as well? Do you run This ACARS program on a different PC? If not,WideFS is not relevant. Most FSUIPC client applications don't even need FSUIPC to be registered, as the program access for applications is free for users, always has been. Pete

Pictures aren't really needed, just the numbers. Looking at the calibration values you've set: Aileron=-16380,-3118,512,16380 Elevator=-16380,0,0,16380 Rudder=-16380,0,128,16380 you really haven't allowed much leeway in the centre (none for elevators!) for normal and likely variations in the actual axis centres. You've also not allowed ANY slack at the extremes. normally needed to ensure that you have the full range available on the aircraft. I have always found that the values supplied by most joysticks vary a bit - humidity, temperature and other factors affect the resistance in the pots used. Optical ones may not suffer so much,. On top of this. the centering action is often by a spring or piece of elastic not an actual detente, so its position on the pot will vary. I've always calibrated centre by not omly moving the yoke to both sides of its sprung centre, but turning it to the extremes each way too and letting go -- often it ends up different depending on which side you took it. Note that you can lessen the bad effects of being a little off-centre by using one of the calibration slopes with a flattened centre. Pete

First, please note that not only have you posted almost the same message twice (why not just edit the earlier one?), you have added your messages to a thread entitled "FSUIPC and P3D v32 crashing", when your question is most certainly not at all related to this particular subject. By posting in a different thread you miss the possibility of someone who could actually help you noticing and actually doing so. You should post it as a new thread with an appropriate title, such as "CH yoke and pedals not working in Windows 10, please help". I'm afraid I most certainly cannot help. To start with I don't have Windows 10 and most certainly don't intend to update to it, and I don't have any CH products. I'm sure someone who has both might be able to help. All I can note for you is that if Windows doesn't see them properly, such that you can calibrate them, and P3D doesn't either, then FSUIPC is most unlikely to also as it uses the same standard DirectInput methods. But surely you must have tried them in FSUIPC? You say you have it but haven't installed it. Why not? Why ask without even trying? Incidentally, for P3D3.2 you need at least version 4.949h, and there's a version 4.949k available too now which would be better. See the Download Links subforum. One other hint -- try posting the question, properly entitled, in the P3D forum on AVSIM, and also at ch-hangar where there is specialist assistance with CH products.(http://www.ch-hangar.com/forum/). Pete

If you've no need of the user facilities in FSUIPC then you only need purchase a key for WideFS. Pete DOwson

The first test isn't whether there's an INI file or a LOG file, but whether there's an FSUIPC entry in the Add-Ons dropdown. Is there or not? Why are you first only looking at files? FSUIPC is controlled primarily through the in-program menu and dialogues. Pete

No FSUIPC in the Add-Ons menu drop down either? If not then FSUIPC is not being loaded. This looks like the reason: Do you see, the entry just before FSUIPC is different from all the others? What are all those "!--" parts doing there? Your DLL.XML file is corrupt. I suggest you delete the whole section for as_connect -- i.e. this part: <Launch.Addon>--> <!--<Name>as_connect</Name>--> <!--<Disabled>False</Disabled>--> <!--<Path>as_srv\as_btstrp.dll</Path>--> <!--</Launch.Addon> Then retry. You'll probably need to reinstall ASN to get its as_connect entry restored. Pete

FSUIPC cannot lose or change the calibration values you've set, assuming you set them in FSUIPC. Perhasp you've created a Profile for a particular aircraft and ave not assigned others to it yet? I really can't help with the scant information you've provided. I would need to see your settings -- you can paste the INI file from the Modules folder here, and tell me which aircaft it is you have problems with. What does "current FSUIPC" mean? Please ALWAYS state version numbers. Anyway, if it isn't at least 4.949h (and preferably 4.949i, the current interim update in the Download Links subforum), please update and try again first. Pete

WHERE did you download it from, please? There are only two valid sources, and they've not changed since 2003. One is the same one linked to by the purchase page on SiMarket, which is www.schiratti.com/dowson. The other in in the Download Links subforum here, where you've come! In fact there's usually a more up to date interim release here too. Why did you Google it when I told you in my reply above? Did you not even both to read it all? How did you miss this bit? There is a lot of information about supported versions, and links to downloads, in the SubForums here. Please use them. Pete