Pete Dowson

It's not only there, in profiles Any comment put right at the end will be lost. The last part must be the automatic annotation. Add your comments to the line before the annotation, thus: 19 = P3,8, K118,8 ; FLAPS DOWN - {Key press: F7} - The system is designed so you can add comments before the file is actually used and the annotation added. Incidentally, F7 is assigned by default to "Flaps Inc". It is F8 which is "Flaps Down". Also, it would be more efficient to assign to the actual Flaps Inc control. By assigning to the key you are telling the Sim to look up that key assignment and then use that same control. And also, then, the annotation would tell you what the control was and save you the trouble of putting comments in. Pete

You are making a mistake then. All three parts must be correct and exact: Name, Email and Key. Cut and paste from the original registration details from SimConnect. Pete

The Bodnar board is recognise, with and X and Y axis connected: 812 Product= BU0836A Interface 812 Manufacturer= Leo Bodnar 812 Serial Number= BY0C28 812 Vendor=16C0, Product=05BA (Version 1.38) 812 GUIDs returned for product: VID_16C0&PID_05BA: 812 GUID= {41C9B2E0-C1F4-11EA-8001-444553540000} 812 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4095,Y4095,Z0 It is assigned ID 6: 843 Device acquired for use: 843 Joystick ID = 6 (Registry okay) 843 6=BU0836 Interface 843 6.GUID={39B97A80-9FC5-11E7-8001-444553540000} And there are no conflicts on this ID, so it must surely work ok. There are other problems though. There two have the same ID (0) assigned: 827 Device acquired for use: 827 Joystick ID = 0 (Registry okay) 827 0=T.16000M 827 0.GUID={58FEFF80-FAE9-11E7-8002-444553540000} 843 Device acquired for use: 843 Joystick ID = 0 (Registry okay) 843 0=MFG Crosswind V2 843 0.GUID={58FEFF80-FAE9-11E7-8002-444553540000} and so do these two (ID 3) 843 Device acquired for use: 843 Joystick ID = 3 (Registry fixed) 843 3=Flight Yoke System 843 3.GUID={A969C360-7F30-11EA-8001-444553540000} 843 Device acquired for use: 843 Joystick ID = 3 (Registry okay) 843 3=MFG Crosswind V2 843 3.GUID={A969C360-7F30-11EA-8001-444553540000} You say you used JoyIDs to sort things out. What exactly did you do in JoyIDs? Of your "two" Crosswinds I'd guess that, from the assignments you have, historically ID 3 is the correct one, though that does give the worst results in the Joyscan. I've no idea how the registry got into such a mess with that device. I suggest that you find its entry in the Windows device manager and uninstall it there, along with any driver software it says is installed, then unplug the device and reboot the PC. Then plug the device in and see if the registry entries have sorted themselves out. But the Bodnar board should certainly be recognised as device 6 with an X and Y axes. This shows definitely okay. BTW you are using FSUIPC 4.974, which is out of date. Please update to 4.975a. Pete

Just changing UseProfiles=Yes to UseProfiles=Files is enough. Next time FSUIPC runs it will make the files. But, as documented, there must not be a "Profiles" subfolder already, or it assumes the conversion has already been done. The conversion is only done once. Please see the document in your FSUIPC6 Documents folder entitled "Profiles in Separate Files". It explains it all in more detail than I can here! Pete

Profiles work fine without that, but sometimes it helps having separate files for each profile rather than in one large INI gile. Changing the parameter will make files for each Profile you have already created. The Profiles folder is created as a sub-folder in the FSUIPC6.DLL folder, the place you selected for it when you installed it. If you do not remember where you installed FSUIPC then you can use a button in the Logging tab in FSUIPC Options to open the folder for you in Explorer. Pete

Not really, as your FSUIPC4.LOG is from a good session. The previous (last crashed) log would have been more informative. However, from the Windows crash data it would appear that the problem was due to some corruption in memory. The first was in ATC.DLL and the second in AI_PLAYER.DLL, and assuming that it isn't a corrupt install of FSX the most likely problem was corruption due the SimConnect loading bad weather data. Maybe the FSUIPC update has caused a slightly different memory arrangement, so something more innocuous is corrupted. Or maybe your deletion of the weather files paid off this time. Pete

P3D5, like FSX and all the P3D versions before it, by default have a specific axis value which Arms the spoiler. Nothing less than that does anything -- the spoiler/speedbrake remains down and disarmed. The internal range for the axis is 0-4799 spoilers off/disarmed, 4800 Armed. Then about 5600 (representing a minimum 7%) to 16383 fully deployed ground speedbrake. These numbers are what you'd see if you monitored offset 0BD0. FSUIPC calibration provides the minimum value , a zone you can set for "Arm" (which FSUIPC automatically converts to the Armed value needed) then the full movement to the maximum. Please just follow the numbered steps to calibration in the FSUIPC User Guide (page 42). You'll note in Step 6 that you calibrate a zone for the "centre" or "arm" for spoiler, as specifically mentioned. That zone cane be wherever you like. In my case I use a PFC throttle quadrant which has the Arm position specifically marked, so i calibrate to that position. Check your assignments and calibrations. It only takes one of your many controls to be wrongly assigned or have poor calibration. Check that you are disabling controllers in P3D also. Pete

YOU POSTED THIS TO A REFERENCE SUBFORUM CLEARLY MARKED, IN RED Not for support requests Please do look at where you are posting. You are lucky I saw this and moved it to the correct Support Forum! I use many Bodnar boards with no difficulty, so it must be a configuration issue. Did you check that it is seen by Windows, and have you calibrated the axes in Windows first? I can't help without some information. Please show me the following files, all provided in your FS Modules folder: FSUIPC4.INI FSUIPC4.log FSUIPC4 JoyScan.csv Pete

But FSUIPC supports Profiles automatically loaded for each aircraft or type of aircraft, as needed, and with all standard keys and buttons defined outside of profiles for availability with all. I still don't see any advantage of using something more restrictive. Pete

Yes, I've seen. Hopefully L-M will address the matter then. Pete

Okay, that's good. Well, evidently that driver is stopping the buttons being seen by FSUIPC. So why not stop using it, and just use FSUIPC? Seems to be the answer, no? Pete

You added this to a thread in the reference section "FAQ". I know that thread may well be relevant, but so we can deal with it as a support query i've moved it here. Well, in that case we need the CTD details, please, from the Windows Event Viewer. Paster a copy here. It's easy to cut the details from the Event Viewer display options. We also need to see the last FSUIPC4 Log you got from FSUIPC. It'll be in the Modules folder. Try with FSXWX disabled AND, before starting FSX, again deleting the wxstationlist.bin and all of the .wx files. After all, it does seem mighty suspicious that it started when you started using that program. Pete

Maybe the search does not search everywhere. I use a freeware program called "Everything", and run it 'as administrator' so it can access all folders. Otherwise, if you did search everywhere, I think you must have some anti-virus checker which for some reason takes exception to the file. Perhaps try after temporarily disabling it. Pete

I'm not completely sure what you mean. There are offset controls which you can assign to a key or buttons press, yes. You can have a button do as many things at the same time as you want to, but to do this you'd need to edit the settings in the INI file -- you can't do it directly in the Options interface -- that is, unless it is okay to assign one thing when the button is pressed and another when it is released so allowing two actions on the one button. Editing the INI file for multiple actions on a button press is documented in the Advanced Users guide. Ah, so "Thrustmaster Combined" is the name for a specific control device, not a term for some software way of lumping several Thrustmast devices together. as it sounds! I see it is recognised by FSUIPC. But by this statement: do you mean that FSUIPC sees the button presses but not the axes on the same device? Because if it is a standard USB HID Game Controller that doesn't make sense unless some driver is causing that problem. I get the feeling that I still don't understand exactly what your problem is. Pete

I think you need to uninstall thrust master software if you want to assign in FSUIPC. if the axes are getting through to the sim then you should be able to calibrate in FSUIPC. Pete

Sorry, I've no idea what a "target script" is, nor what "thrustmaster combined" is, but my guess is that it's some program or driver which takes control of your device and therefore stops FSUIPC seeing it. This may be a question for the Thrustmaster forum. Pete

No. WideFS is only to support FSUIPC applications on a PC not running a flight sim. WidevieW is not supported here, it isn't our product, so for details about setting that up you'll need to find its Forum. Sorry. Pete

Do you not see the information "The Advanced User’s guide gives a list of keycodes and shifts." in the Lua librarry documentation for ipc.keypress? Pete

It looks to me like it was downloaded quite quickly (it's a small package). Have you looked in your Downloads folder or wherever you have things set to download to? Note the notification which appears briefly at the bottom left of the screen. Maybe you are not used to seeing such fast downloads because you normally download somewhat larger files? I suggest you search your system for "MakeRwys.zip" as I expect you've actually downloaded it several times already. I didn't notice which browser you were using, so i don't know if it applies to yours, but in Chrome (the browser I use) one of the options it provides is to display a window called "Downloads" which displays a history of the downloads you've done (and any underway or pending). Check yours. Pete

I clicked on it and MakeRwys.zip downloaded okay. What do you mean by "the page refreshed"? The link most certainly refers to the ZIP file in which we supply MakeRwys. And it is the same as the one you quoted (from "Useful additional Programs") and the same as the one on FSUIPC.com. In fact it is the only MakeRwys ZIP there is. So I've no idea what your system is doing. Maybe it would be quite useful to understand what you actually mean by a page "refreshing". Pete

MOVED FROM "ANNOUNCEMENTS" SUBFORUM! Please ALWAYS look where you are posting support questions if you really want a reply! The subforums are for reference not support. Please look at the existing threads on this subject. Pete

We won't be adding it to the documentation. I've done some tests here on P3Dv5 with some default panels, and it doesn't work. in fact it can hang P3D completely. The function will probably be removed in future updates of FSUIPC6. If a reliable way of doing it by program is ever found then we'll look at adding it when time permits. If it works with FSUIPC4 on FSX or P3D1-3 then by all means go ahead and use it. We won't be changing FSUIPC4. Pete

Okay, I found the undock function. It is in the Lua ext library, so it is x = ext.undock("name") Somehow it missed being added to the Lua library documentation! Very strange. Sorry about that. It needs testing on P3D though -- I think that code dates to 2011. Maybe it wasn't added because it doesn't really fit. the "ext" library is all about external processes, not child windows of the simulator. Maybe it should be in the ipc library after all, as I seem to have originally proposed. I'll discuss it with John before firming it via documentation. The name is the title of the docked window. You'd need to undock it manually to see the title in its title bar if you don't know it already.If the window is found, x is non-zero, if x is zero it means the Window couldn't be found. Pete

It might work using the documented codes -- keycode 13, shift code 16. But as it says, the Alt key might instead or as well invoke the menu. Okay, I'll take a look. see if it helps me remember how to do it. Back 9 years ago it was likely via a hack into FS code. I'm not doing that any more. Pete

Note that some switches in the default 737 don't really do anything as they are for subsystems which aren't implemented. All FSX controls assignable in FSUIPC are listed in the document saying it's a list of controls in your FSUIPC documents folder. Have you looked? Note also that the control name assigned by Microsoft is often not the name you would see on the cockpit. You have to use some intelligence to work some out. One way is to enable FSUIPC Event logging, and the Console Log (so you can see results on screen immediately), then operate each switch, button and knob in turn and see what control is generated. I don't know any like that (though I admit I've never used the default 737 with cockpit controls, only Project Magenta and ProSim models), but you can assign to both press and release for any button or switch, and you can have multiple actions on either by editing the settings in the FSUIPC4 INI file -- as described in the Advanced Users document. Pete