John Dowson

Didn't you just try it as it was first? I left all your settings, just removed the duplicates. There is only one setting in the ini not assigned to a controller, which was this one: 1=P0,8,C66506,14401 -{PANEL_ID_TOGGLE}- What do you mean 'nothing works'? From the log file you posted, I can see your buttons being pressed and the controls sent (although this was with your original ini), e.g: 152781 [Buttons] 47=R2,3,C65615,0 152781 Repeating flag set: bRef=0, Joy=2, Btn=3 (RepeatDelayCtr=1) 152781 FS Control Sent: Ctrl=65615, Param=0 ELEV_TRIM_UP 152781 *** EVENT: Cntrl= 65615 (0x0001004f), Param= 0 (0x00000000) ELEV_TRIM_UP No, this is not possible. I am sure many people use FSUIPC gear toggle over the years (including me!) and this would surly have been reported before if it was an issue. Your problem lies elsewhere. I also confused by this, as you previously said 'nothing works', whereas this implies things were working until you applied the gear toggle. Which is it? There is no difference between FSUIPC5 and FSUIPC6 in this area.Check that you have controllers disabled (in both sims). I also see that you are auto-starting a lua file relating to your gears: 141672 LUA.0: beginning "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\Get_Gear_Height.lua" Try removing this for the time being.. So, I suggest you try the following: - remove the auto-start of the lua - remove all FSUIPC logging except 'Events (non-axis controls)' and 'buttons and switches' - check various button assignments using a default aircraft - let me know of any issues and re-post your .log and .ini John P.S. If your issue is related to the auto-started lua, it could be related to the problem reported in this thread. You could download and try the dll posted there - forget this for now. The fix there is for lua key events, not buttons.

Think we've found the issue. Can you try the following dll please (v6.0.10b): FSUIPC6.dll

Did you run P3D at least once before trying to install FSUIPC6? Do you have an install log - if so, please post that. If it can't find P3D, it means that the registry entries are not there. Try uninstalling and re-installing the P3D client. Then run P3D once, and close it down before trying to install FSUIPC6. John

@duyvh0309 We have now added facilities for this. Could you try the following dll please (v6.0.10a): FSUIPC6.dll There are facilities to create menus either via lua facilities or offsets: LUA FACILITIES ipc.SetMenu or ipc.setmenu(title, prompt, table_of_items) Prompt can be omitted for black in that space Title and prompt can be omitted for blank in both spaces The table of items is a Lua table with up to 10 entries. event.MenuSelect or event.menuselect(result, "function_name") or event.menuselect("function_name") With the former you can have a different function for each result. In both cases the result is supplied to the function which is declared as function function_name(result) The result is 1 - 9 for items 1-9 selected 0 for item 0 (10) selected -1 for Menu Removed -2 for Menu replaced (eg by another Lua -- all use the same ID) -3 for menu timed out (not likely -- no timeout facility offered. -4 for something else (not just "queued" or "displayed" -- not reported. OFFSETS: 5100 - 51FF: write menu tests here, up to 256 bytes including final terminator. Each string terminated by zero byte. First string = Title Second string = Prompt Then up to 10 more strings. The text (no item numbers) of item 1-9 and 0. Limited to 256 bytes altogether. Write 0 to byte 5100 to close it unanswered. Results: 0 is written by FSUIPC to Byte 5100 when selection is made or other things happen. The selection is written to Byte 5101. Here are a couple of scripts we have used to test this: menuViaOffsets.luamenu.lua

Sorry, but I don't understand this... What values are you actually writing to offsets 05EB and 05ED? As the documentation states, the speed is controlled by the values that you write there, from -127 (fast forward/left) to +127 (fast backward/right) for offsets 05EB and 05ED (vertical & forward/backward) and 0-32767 for 05E8 (vertical rate). John P.S. Try logging offsets 05EB, 05ED and 05E8 from the FSUIPC logging tab to see what they contain.

You can assign to the Situation Save control. This is the same as using the default P3D key ; (semi-colon). There is also an Auto-save Toggle control, which you can use to toggle auto-save on/off once it has been enabled from the AutoSave panel. John

Hi Dane, looks like your devices GUIDs have changed for some reason - have you had a windows update or re-install? Anyway, can you try the attached ini: FSUIPC6.ini I have tried to keep most of your settings, but you should review them. Cheers, John

We have an alpha version of FSUIPC for MSFS (FSUIPC7) which has been released to third party devs who have access to MSFS Alpha. Still a lot to do though, and we're a bit surprised that the release is so soon. We're currently getting very little feedback from Asobo on the SimConnect facilities, and there is still no documentation on key event/control names. I'll post an update when we get more information (or a documented SDK) from Asobo/Microsoft. Cheers, John

Here's v6.0.8 which you can use while we investigate this: John FSUIPC6.dll

First, you posted in the Download Links sub-forum (where it states: NOT for support requests). I have moved your post for you. If you check your FSUIPC documents folder, there should be a controls list document. For the master battery, there is Toggle Master Battery. As this is a toggle, you could also add an offset condition for offset 281C (Master Battery Switch) so that the control is only sent when needed - see the Advanced User Guide for this. John

Try pressing the 'Ignore Axis' button. This will ignore the input from that axis (until you close the FSUIPC UI) to allow your other axes to be seen.

Please update to the latest version, v6.0.9. There was an update in v6.0.8 for P3Dv5 Active Sky compatibility - see John

Yes of course - was thinking of the wrong installer. Sorry about that.

Let me know your FSUIPC4 order details (order number + date of purchase) and I'll check them for you. Please don't post your key! WideFS registration is always optional, so you should leave that blank. John

Just do that! Whats the problem?

Hi Rob, the centre wheel for 'mouse move' seems to work as always (i.e. moving eyepoint forwards/backwards - I don't have sideways/left/right on my mouse wheel). This is the same in P3Dv4 (latest hotfix) and P3Dv5. The difference between v4 and v5 seems to be the way the FSUIPC controls 'mouse look on', 'mouse look off', and 'mouse look toggle' work with 'mouse look'. This is what is toggled when you press the middle mouse button/wheel. When you do this (or assign those controls to the space bar, overriding the default P3D space bar control of mouse look) the view pans strangely and is hard to control. I suggest you avoid these controls for now, and use the default P3D control of the space bar for this. With P3Dv5, there is also a new option to 'Enable Advanced Mouse Controls' (under 'Other Controls') which now allows you to use the mouse with having other controllers disabled. Note that if using FSUIPC mouse move/look controls, then this should be disabled (and vica-versa) - i.e. choose one. Did you try using the P3Dv5 advanced mouse features? For me, the eyepoint controls work but the right-click mouse move functions don't seem to work - I get a cross-hair cursor but no movement. So there seems to be a strange issue with mouse-look panning, but only when using the FSUIPC 'mouse look' controls in P3Dv5. This is certainly due to changes in P3Dv5, but I will look at this in more detail at some point, when time permits, but I'm afraid that this could take quite some time as there is quite a bit of work on at the moment. John

First, you posted in the FAQ sub-forum which is NOT for support requests (as it states!). I have moved your post for you, but please try and post in the correct forum in future. The facilities to load and run additional programs are only available in a licensed/registered version of FSUIPC. License are only available from SimMarket. See https://secure.simmarket.com/pete-dowson-fsuipc4.phtml. You can still download and install FSUIPC, which would give you access to the documentation, which you can use to decide if you want to purchase a license or not. You can download from here: FSUIPC 4.975. John

If you have a license for FSUIPC5, you will automatically get the reduced/discount price of 9.99 + taxes for FSUIPC6 when you check-out your purchase in SimMarket (assuming you purchase from the same account). John

Thats strange. If it hasn't been created, then most likely FSX is crashing before FSUIPC is loaded. You shouldn't remove the original as that is the one thats copied back - you need to remove the one from the same folder as the FSX.cfg file, as I said. Maybe, and probably FSUIPC as well. Your install log file would help with this. Thats probably a good idea. Remember to run FSX at least once before attempting to install FSUIPC. Check or post your FSUIPC install log after you install. There should be a copy in the folder that contains the installer, as well as in your FSX Modules folder. You should also try running FSX again after you have installed FSUIPC, to see if your problem persists or if its starts correctly and you have FSUIPC in the Add-ons menu. Cheers, John

Thanks Alje. I'd forgotten about this problem....I've now made a note and will look into it. I think I'll remove the check on the previous version anyway. This prevents you from rolling back your installation, which it shouldn't really - If you want to install an older version, it shouldn't stop you (but maybe give you a warning). Cheers, John

Whatever devices you have attached shouldn't make any difference to the initial state of the aircraft. FSUIPC only re-acts on changes, not the initial state of your devices buttons/switches. Did you try with your device disconnected? I suspect the problem would be the same. If so, I would suspect that it is either related to the aircraft (do you use accusim or related software?), or software that you have installed for that device. I can't se how this can be anything to do with FSUIPC. Your logs don't even show this device - the only device FSUIPC sees is a 'SideWinder Precision 2 Joystick'. You have a profile called 'Honecomb Yoke', but this is empty! Maybe you have additional software installed for your Yoke that is taking control of this device? John

It could be due to a corrupt weather file. You can try adding the following line to the [General] section of your FSUIPC4.ini file to temporarily disable weather facilities: NoWeatherAtAll=Yes If it works with that, you have a corrupt weather file. The only way then to correct the issue is to delete the weather files (.WX) from your Flight Simulator X Files folder in your Documents, and the wxstationlist.bin from the same folder as the FSX.CFG file. The WX files are simply where FS saves the current weather with its Flights, and the WXstationList.bin file will be rebuilt on the next P3D load. If thats not your issue, could you post your FSUIPC4.log and .ini files (from your Modules folder). John

I don't have FS9 so cannot check, but I assume the provided license details work both in FSUIPC3 and the installer. Could you check the contents of your FSUIPC3.key file (located in your FS9 Modules folder). It should contain: [User] Name=free userAddress=fsuipc@free.comFSUIPC=Y8ZG SUWH TIQ2WideFS=IUT7 DBMK 1EU1 If the contents match, could you post your FSUIPC.log file, as well as your installation log. John

You can download the installer here: http://fsuipc.simflight.com/beta/FSUIPC6.zip Extract the contents of the zip file. Once you do that, there will be three files - an Installation and Registration guide, the installer and a text file for recent changes. Open and read the Installation guide. Then run the installer and follow the instructions. You can download and install without purchasing a license, but if you do this you will not have access to the registered options. If you decide to buy a license, you need to re-run the installer to activate the license. John

Thanks Adrem, thats what I thought. Just waiting for the ini and log files from @yen eb to see what his problem could be.