Pete Dowson

Best to enable the joy letters facility so that FSUIPC can identify them by name in future. Pete

I didn't event think they sent the keys in emails. I've never had any key from SimMarket (or Aerosoft for that matter) via email. I've always had to go to my account and look at the order information, where all such information is stored. And I buy a lot of stuff from both SimMarket and Aerosoft. Pete

Er, yes, and it didn't really need hundreds of examples! Didn't you see any of these lines? SendKeyToFS(00020078=[ctl+F9], KEYDOWN) ctr=0 Guess what that means? As far as FSUIPC is concerned, the key combo was sent. Of course, after that who knows what happened to it? What did you expect to happen? Pete

Can you show a picture of that options window just before you click OK? Well, yes, there's nothing appearing in your INI file for such changes. Does it record other changes? Try assigning a keystroke in 'Keys" for instance, then see if it got added. If not, perhaps you are getting the file from the wrong place, or it is protected (read only)? Pete

But as I said, you actually have NOT done this. The assignment would have othjerwise been written to the INI file when you "OK"d out of the FSUIPC settings. It cannot register inputs from axes which are not assigned. I keep saying this. We are going in circles! Pete

I'm still none the wiser. Sounds like a word processor. You still haven't assigned anything to joystick D, the MFG Crosswind V2. And you STILL haven't deleted those assignments to your removed device B! This is the THIRD time I've advised you to do that! Look, these are your axis assignments: [Axes] 4=BX,1,F,66387,0,0,0 5=BY,1,F,66388,0,0,0 6=BR,1,F,65764,0,0,0 0=AX,1,F,L74:V,0,0,0 -{ TO SIM: LuaValue TDC_CursorX }- 1=AY,1,F,L75:V,0,0,0 -{ TO SIM: LuaValue TDC_CursorY }- 2=AZ,1,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }- 3=AR,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }- 7=CX,69,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- 8=CY,1,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- I see the missing D.GUID line has mysteriously re-appeared, so it is detected correctly: [JoyNames] AutoAssignLetters=Yes A=Throttle - HOTAS Warthog A.GUID={C4782260-0FDE-11E2-8002-444553540000} C=Joystick - HOTAS Warthog C.GUID={C4778620-0FDE-11E2-8001-444553540000} D=MFG Crosswind V2 D.GUID={D156B4E0-397B-11E6-8001-444553540000} 0=MFG Crosswind V2 0.GUID={D156B4E0-397B-11E6-8001-444553540000} 1=Throttle - HOTAS Warthog 1.GUID={C4782260-0FDE-11E2-8002-444553540000} 2=Joystick - HOTAS Warthog 2.GUID={C4778620-0FDE-11E2-8001-444553540000} Pete

But the calibration tab cannot actually tell WHERE the rudder control messages it intercepts come from, FSUIPC's or P3D's assignments! It traps those messages FROM FS, no matter who sent them. I think you need to show me the INI file again, because the only assignment you had to rudder there was to a rudder set no longer connected. That alone could interfere, but I'd hope you'd deleted those lines by now as I've said (twice). What does the calibration tab show for IN and OUT for the rudder? What's "SS"? Pete

I see. That ecplains it. There is no "assignment" possible in "Joystick Calibration". It's only calibration of axes already assigned! That's the whole point. You can assign anywhere. FSUIPC assignments are done in the Axes tab! That is evidently why you have to assign in FS instead! I find it puzzling that you do not seem to know this yet your INI file shows that you HAVE made FSUIPC axis assignments before! Quite a lot in fact, and several very sophisticated ones: 0=CX,69,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- 1=CY,1,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 2=AX,1,F,L74:V,0,0,0 -{ TO SIM: LuaValue TDC_CursorX }- 3=AY,1,F,L75:V,0,0,0 -{ TO SIM: LuaValue TDC_CursorY }- 7=AZ,1,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }- 8=AR,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }- No, not true. Only when ASSIGNING in FSUIPC. It doesn't matter where you assign, but do NOT mix up FSUIPC assignment and FSUIPC assignment. If you do decide to assign in FSUIPC (as you already have for many, as shown above), be sure to disable controllers in FS/P3D Just delete the lines I showed in my previous reply, EXACTLY as I suggested there! That's why I gave you those instructions. Er .. once as a Joystick and once as a Throttle. It evidently presents itself to Windows as two devices. Or don't you have both parts? Surely you do, because you've already somehow made FSUIPC assignments to the Joystick part: 0=CX,69,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- 1=CY,1,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- and FOUR assignments to the Throttle part: 2=AX,1,F,L74:V,0,0,0 -{ TO SIM: LuaValue TDC_CursorX }- 3=AY,1,F,L75:V,0,0,0 -{ TO SIM: LuaValue TDC_CursorY }- 7=AZ,1,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }- 8=AR,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }- Are you saying you did all this without knowing what you were doing, or did someone else do it for you? I just can't understand how you thought you could calibrate unassigned axes. I wouldn't worry about that. The GUID is only used to differentiate between two or more devices with te same name. The GUID is always unique. You've only got one "MFG Crosswind V2". Pete

That version is not supported. The currently supported version is 4.955c. Sorry, how do you "attempt to connect"? And what is "msg#2>"? So what do you expect it to connect to? What are you running on the client PC (the one NOT running FS) apart from FSC? How do you expect it to connect with no software to do so? Why didn't you read my last reply, and in particular the part " ... WideClient.EXE which is "installed" by simply putting it somewhere convenient on the Client PC -- i.e. the Networked PC, not the FS one. " No nothing you've told me so far makes sense. Sorry. Please PLEASE do read at least some of the WideFS documentation supplied! Pete

Need more information: 1. What does the FSUIPC4.LOG show in the early section, where it logs the devices it scanned? 2. Can you describe more exactly what you mean by "unable to calibrate"? Please note that Calibration in FSUIPC is completely independent from Assignment: it doesn't matter WHERE you assign, in FSUIPC or in FS/P3D, now even how. The calibration works on the FS controls you assign to, not on the joystick inputs. From the INI file I see: B=Saitek Pro Flight Combat Rudder Pedals << MISSING JOYSTICK >> B.GUID={C478E5B0-0FDE-11E2-8004-444553540000} A missing set of rudder pedals, yet you have assignments to it: 4=BX,1,F,66387,0,0,0 5=BY,1,F,66388,0,0,0 6=BR,1,F,65764,0,0,0 Now I don't know if this will make a difference, but if I were you I'd delete all 5 of those lines. I also only see: D=MFG Crosswind V2 2=MFG Crosswind V2 2.GUID={D156B4E0-397B-11E6-8001-444553540000} which is odd as there should also be: D.GUID={D156B4E0-397B-11E6-8001-444553540000} Since you have "AutoAssignLetters=Yes" set, it should have made that line as well -- or have you edited it? I casn't think of any reaon for it not to have completed this itself as it is done part and parcel with the creation of the D=MFG Crosswind V2 line. I don't see any assignment to device D in your INI. So maybe that's the problem? No assignment at all, no calibration. Even assignment in FS would allow calibration. Pete

"Lua KillAll" would look for a Lua plug-in called KillAll.lua and run it. I've no idea what that Lua contains as I've never seen one named that way, but if you really need to Kill all running plug-ins then you'd either need to invoke a macro which executes the LuaKillAll control. or, yes, usa a plug-in to send that control in the KillAll plug-in, i.e. using: ipc.control(1084) (The 1084 is from the list of FSUIPC additional control numbers in the Advanced Users guide). Mind you, I've not tried it and I'm not quite sure what would happen if a Lua plug-in tried to murder itself in such a fashion. However, all profile-specific Lua plug-ins are automatically closed when you change profiles, so this action is only really acting on plug-ins loaded by the generic [Auto] section. This line is interesting: I'd like to see the LuaFiles list, to see what entry 22 is -- I assume it is KillAll as well, but then I don't understand why there's no space in the FSUIPC-added annotation between "Lua" and "KillAll". It's definitely a Lua "Run" assignment as shown by the 'R'. Here's my entry for the keypress I use to kill all plug-ins: 2=49,24,1084,0 -{tab+1: Press=LuaKillAll }- Pete

If the virtual joystick buttons are those provided by FSUIPC, then, yes, to assign them he'd need FSUIPC registered. However, he also says: So where are those already assigned? Pete

I really don't know. With FSUIPC you can assign to buttons and switches if those buttons and switches are recognised as normal joystick type buttons and switches (up to 32 on each device, with up to 16 devices). I don't know if the Saitek Panel is a Windows-recognised joystick. If it is you should be able to see this in FS assignments itself. Do you? Is it shown in Windows Game Controllers, and if so does it detect the buttons and switches? I don't know SPAD either. You might want to ask in whatever forum SPAD is supported. Pete

Oh dear. It's an assignable control, called LuaKillAll, and, just like Lua, LuaKill, LuaSet,, LuaClear, LuaToggle and LuaValue, it is clearly listed in the assignable controls drop down for Keys and Buttons. As stated in the Installation and Registration document, found in the FSUIPC download ZIP, the FSUIPC Lua documentation is in your FSUIPC Documents folder (inside the FS Modules folder). Have you never looked there? The information about the added controls is provided on the very first page, the introductory part entitled "What is provided in FSUIPC for Lua programming". Pete

I just checked, and, in fact, if you try to read an L:var which doesn't exist you actually get zero, not "nil" -- there's an error in my code there, which I will correct in the next FSUIPC update. Currently you can only check whether it exists or not by using n = ipc.getLvarId("name") which will return nil if it doesn't exist. But from what you say, the "nil" error you are getting is because it thinks the function you are calling doesn't exist. There's no library called "pic", so that could be one reason -- or is that another autocorrection gone wrong? Also is isn't "readLVar" but "readLvar" -- another autocorrection? Surely not? Lua is case sensitive -- every character must be correctly upper or lower case. If you really are using ipc.readLvar then I think you need LINDA support. I don't know what it is doing to get that screwed up, I don't know it at all I'm afraid. BTW use the built-in FSUIPC assignable control "List local panel variables" to get a list of all the valid L:vars for the current aircraft, and their current values. Pete

Please ALWAYS post questions or support requests to the Support Forum, unless very specifically concerned with mentions in the SunForum, in which case they should be appended to the relevant tab. BTW I assume you mean "ipc.readLvar" not "ipc.readvar", which doesn't exist. ;-) This sentence seems to finish rather abruptly. Did you trace with LINDA? Why? Where does LINDA come into it? Did you try tracing using the facilities in FSUIPC? No, there is no "stripping out" of anything at all. And names with spaces in a certainly okay -- one of the default FSX ones is "L:EFIS Mode", and the default FSX 738 actually features as many as 31 different ones with embedded spaces -- and they all work fine. Pete

Yes of course. As listed on the first page of the Lua Plug-ins document, there's an assignable FSUIPC control called "LuaKill" exactly for this purpose. There#s even one called LuaKillAll to kill all running plugins. You can start then with the Lua control as well of course. The Auto loading facility is really just making use of this. Pete

Sorry, what has WideFS got to do with it? Evidently you did not uninstall v3 properly. And why on Earth did you install v3 into a folder called Prepar3D v2? Yes, I gave you exactly the solution in my previous message. did you not read it? Pete

It is n't relevant -- the point is they must be run in the same way. Not really as I asked. I said to close P3D first. Good. Saves you going to their support forums. Pete

And a good job too, because you appear to be using P3D version 2.5 but the Registry says it is version 3. see this part of the Log: You have registry entries for both versions 2 and 3 pointing to the same place, and version 3 being the more recent naturally FSUIPC installs for that! This part shows that in fact the Prepar3D.EXE file is version 2.5. How did this mess get made? What did you do? The only solution to the mess is to use the Registry Editor (RegEdit) to delete the key: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Such a mix up will be certain to get other add-on installers doing odd things too! Pete

Leave it to its default setting normally. It's only to stop a loop developing when the add-on aircraft itself uses those controls, which very few do these days. How are you detecting this? In the calibration tab? What throttle assignments do you have? Where and what to? Perhaps you need to show me more of the INI file, not just two lines. Note that some of the PMDG aircraft do not like FSUIPC calibration at all. Pete

I've checked here to see what I do in my cockpit programming. I do send keypresses to select GSX and ProATC/X menu items, and they work fine, with the numbers 0-9. I just have a separate button to invoke the menu then the normal choice 0-9 on other buttons (these are actually on a touch screen using the Button Screen facilities in WideFS). If the original sequence you programmed didn't work then either you have something wrong there, or it needs some delay between the key presses. (I wouldn't be surprised if that isn't the case at least after the Ctrl+F12 to allow the menu to be created -- SimConnect probably misses the choices thereafter). To check the former possibility, please show me the [Buttons] section of the FSUIPC4.INI file which you edited. To handle the latter isn't possible with only assignments I'm afraid -- although it might be worth sending the "Ctrl+F12" on the press and the 5, 1 on the Release. If that doesn't work then the only way would be to use a Lua plug-in to send the keypresses, and instigate that by your button. Pete

There is no difference to the interface FSUIPC presents to applications whether it is running in FSX, FSX-SE or P3D (or even FS98, FS2000, FS20002, CFS1 or CFS2)! Maybe those programs check whethe rit is FSX or P3D and make their own decision, but this is unusual, and all the programs I know which use FSUIPC run fine independently on whether it is with FSX or P3D. There are NOT two versions, "free" and otherwise. It is identical. The only things purchasing it gives you are the User Facilities. Registration enables those which are otherwise locked. I think you need to contact Support for those two programs. Oh, and make sure you are not running P3D "as administrator" and those programs not, or vice versa, because programs of different privilege levels can't talk to each other. If you want me to check FSUIPC is running okay you need to find the FSUIPC4.log file in the P3D Modules folder, and paste its contents here. Please close P3D first. Pete

This is an install problem normally caused by the inability to find the Prepar3D.CFG file. Full details of what happened are in the FSUIPC4 Install.log file, which you can find either in the P3D Modules folder, or in the same place as you ran the Installer. That cannot be anything to do with FSUIPC, because if it couldn't add itself to the DLL.XML file, it wouldn't even be loaded. FSUIPC touches nothing else but the DLL.XML and the files it places in the Modules folder which it creates itself. What do you mean by "any more"? Are you saying you had installed it and had it working before? You just said this was all fresh "yesterday"? Of course, if FSUIPC is not being loaded then it cannot add itself to the menu system. Find the Install log and paste its contents into a message here. I'm out all day but I'll get to it when I return later this evening. Pete

I'm still confused, but never mind. I can't help anyway. But you also said, just before: So you already knew it couldn't be Win10 itself!? No need to reply. The repeated contradictions confused me, but it doesn't change my conclusions. Pete