Muas

Hi. I'm going through something similar - except I don't plan to tear my PC apart (I hope :? ) I'm still a bit knew to FSUIPC, installed it about 3 weeks, and lately I've been suffering from FSX hangs, followed by the fatal FS error mesage and prompt to address it to MS. I mean, lately, more and more often, and now it happens everytime I run whatever mission. Lets review what I did: 1) Installed FSUIPC and start configuring it. Cool program. 2) I started configuring it storing settings by aircraft. General assignmets for prop/turboprops; specific assignments for jets. 3) I noticed a hang once in a while. Didn't bother with it too much, there was no consistency - I couldn't recreate them, so I thought "if this is real, it will reveal itself sooner or later, too soon to trace it yet". 4) I continued configuring aircraft, this time assingning specific flap settings for each airliner, and yes, I was using the "Send to FSUIPC calibration" option, more and more, I just thought it was the best way to do it. Hangs become consistent. "Its time to sort this out". 5) I just made one test: disabled the FSUIPC.dll manualy. I didn't uninstall anything - just disabled FSUIPC from running on FSX load up. 6) FSX run ok, no more hangs. Enabled FSUIPC to load again. Hangs about five minutes from mission start, everytime. Disabled again - no hangs. I'm having 3 days out of town work, and was wondering what to do next - sometimes its better do nothing and sleep a bit on the subject than start messing around without a clue. Then I made my mind about my next step: I'd clean up the FSUIPC ini file and start configuring axes again from the start. I was sure FSUIPC was pushing hard on something my rig couldn't cope with. Then I started reading this thread. In fact I started to read it earlier but when I reach the memory testing part, I thought "forget it, I aint got time to that, maybe I'll quit on FSUIPC instead". But I decided to read further on a few days later, till I reached the axes assignment option, then I thought "of course, my hangs grew up as I was using that option more and more, so that must be it!". So, I'll be back to my PC before the weekend. I'll disable that "send to FSUIPC calibration" and start testing from there. I'll report back then. Thanks for continuing this discussion, it probably saved some people lot of trouble (including me I guess).

Ok, maybe you're right; but it shure reads Logitech, Thrustmaster and Saitek input devices. Of course the 112 buttons are the sum of all: 64 (pushbuttons) + 32 (16 two way toggles) + 16 (4 four way rotaries, normal and fast operation CW and CCW) = 112 (total) Plus an 8 way hatswitch and 8 analogue axes. I'll sent you the manual via pm.

I'm afraid that is not the case. The MJoy Mapper does exactly the same as the "Buttons" tab on the FSUIPC, except that it can read up to 112 buttons from any device (not only the MJoy16 card), and translate it to keyboard strokes, and with advanced features like key action hold, repeat, press, release, and also macro key sequences (like we can with FSUIPC but only by editing the config file manualy). I don't know how MJoy mapper does the button state reading, and I'm afraid I won't get support for it anymore. Anyway, I'll keep using it as I've been doing in the past. The only drawback is I can't assign buttons higher than 32 directly to commands; instead I map them to keyboard keys on the MJoy mapper and then assign those keys to commands using FSUIPC. Regards.

The MJoy Mapper just translates joystick button presses to keyboard key presses, and reads all the 112 buttons provided by the MJoy16 card. That's all I know about it. Let's clear out this first: I'm not complaining about FSUIPC capablilities; I'm just asking for help to get advantage of all my card potential, so, I do not avoid to answer questions - I answer them the better I can, I'm not a pc hardware buider nor a software programmer and I have very limited knoledge on pc operating systems. I'm the one interested on this subject, so I'd appreciate your help. I would do so, but I'm afraid I'm unable to do that. I don't know how to write such driver. Thanks for the advice.

Neither the Windows joystick interface nor DirectInput can cope with that, so how are you reading them in Windows? If you have your own driver it must have a non-standard API, so how on Earth could FSUIPC handle it? It only knows DirectInput and the main joy API. The only way I can read the 70 buttons is by using MJoy Mapper, which is a mapping software developed specially for the MJoy16 card. Now if it uses a non standard API, I don't know. I just thought, if it can handle more than 32 buttons, why shouldn't FSUIPC be up to it? The EPIC card had up to 512 buttons. It looked like 16 joysticks to Windows. 16 x 32 = 512. How are you currently getting 70 buttons read on one joystick via a standard Windows interface?? Same answer as above - by the MJoy Mapper. Is there a way I can use a similar solution like the Epic to get may 112 buttons to be recognized by FSUIPC?

Hello everyone. I have my own custom built cockpit console based on the MJoy16 input card, including pushbuttons, toggles, rotaries, trim thumbwheels, etc., to control all the FSX switching. It works perfectly, although I need some extra software like key mappers (I gotta use two!), and a simconnect module I put together myself for that "left out of FS user interface" commands. I recently bought FSUIPC4 and finnaly understand the huge capabilities of this module, so I'm trying to get to do all the "interfacing" to get read of all the key mappers and get a few extras like ailleron and rudder trim (these, I got them are already working :wink: ). As I passed my eyes through thr documentation I realized it can only recognize up to 32 buttons + plus POV, even if it isn't using direct X. My cockpit solution doesn't rely on multiple cards with up to 32 buttons; instead, its a one card solution with up to 112 buttons! That's my main problem here, cause I'm using something like 70 buttons. My question is: is there a way to get FSUIPC to recognize more than 32 buttons per joystick card? Thanks in advance.