Jump to content
The simFlight Network Forums

sfox72

Members
  • Posts

    16
  • Joined

  • Last visited

sfox72's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi, I'm using the RP48 roatary knobs for example to set ND range and mode. This is working fine but I have noticed the the command assigned to rotary knob is executed only at every second tick/notch of the knob. Is there where to change this behaviour to one tick/notch? Regards Stefan
  2. Hi Pete, I have installed the update and cleaned the fsuipc.ini. Have not noticed any problems with the default, so in my point of view 3.962 seems to be fine on my system. If there are any problems i will notice you. Thank you and best regards Stefan
  3. Whilst you were assigning? Or calibrating? The code does not operate in flight modes, as I say, only in the options. I have upgraded FSUIPC and checked if there where any new settings to do. So I have opened any tab to check, but I have not changed or clicked any option. After closing FSUIPC I have done my IFR-Setup for a flight. After the the aircraft startup I have noticed that the complete axis for my joysticks are dead, so I was thinking that some hardware is broken. This happened twice plus searching for hardware problems makes two hours ;-) In my point of view there should be something that says that XYZ is disabled bacause of the timeout.
  4. Hi Pete, thank you for the fast response. 40ms is definitely not working, so I have choosen 50ms. Currently I'm not using the CH control Manager, but I can install that if CH has 64-bit drivers. I was thinking that there is a permanent check, because the rudder pedals has disconnected after I have redone the axis assignment and calibration. All axis where fine and shortly after closing the FSUIPC-dialog the rudder was dead again. My setup: Intel E6800@GHz, 8GB Ram, NVidia 280GTX, WinXP 64Bit SP2 USB: 1x T.16000M 1x CH PRO PEDALS USB 1x Saitek Pro Flight Yoke 1x GoFlight GF-TQ6 Throttle System 2x GoFlight RP48 2x GoFlight P8 2x GoFight GF-166 1x GoFlight MCP 1x GoFlight LGT 1x TrackIR v4 1x Mouse 1x Keyboard The system is stable, I have no problems with bluescreens, freezes or temperature. Let me check if there is suitable driver for CH and then I will retest again. Best Regards Stefan
  5. Hi Pete, I have to use 50 as timeout because my "CH PRO PEDALS USB" stops working with a smaller value, the "Saitek Pro Flight Yoke" works well with 20, OS is XP 64Bit. I'm not really happy with this feature, for me there is a chance that if 50 is not small enough, maybe one of my usb-controls stops working in flight. I'm using 9 different USB-Controls so there might be a chance that the USB-Stuff (hardware, driver) has a problem and FSUIPC turns of the temporary faulty device inflight. Is there a way to turn off this feature completely? Please note that I really think that FSUIPC is one of the most important and best addons for the FS, but I do not like that FSUIPC makes the decision to turn off hardware devices without my confirmation. Today I have lost 2 hours to find out that I have no hardware problems, FSUIPC has turned off the stuff without any notificaion. Best Regards Stefan
  6. Hi Pete, you are right, after placing the dll in the modules folder I was able to use Goflight also with FSX. I have have testet my FS2004 setup again, for this purpose I have to use "C:\WINDOWS\SysWOW64", no other directory is working for me. Anyway, all is working fine now. Thank you again for support Stefan
  7. Hi Pete, I have no idea currently, it's an fresh installation of XP. But trouble seems to be ongoing: I have installed FSX and found out the same problem. Is there any extra dll to copy? Best Regards Stefan
  8. Hi Pete, with your help I was able to get the GoFlight modules running: The trick is to place the GFDev.dll here: "C:\WINDOWS\SysWOW64". First I have tried this directory "C:\WINDOWS\system32", but this is not working. I think this has something to do with 32/64Bit versions of the libraries. Thank you for your fast response on sorting this out :-) Best Regards Stefan
  9. Hi, I would like to use FSUIPC 3.93 on XP 64Bit to capture GoFlight buttons and knobs. Before I have testet Windows 7 64Bit and this was working fine. For various reasons I prefere XP 64Bit, but FSUIPC does not recognize any modules. The modules are working fine, is there any trick to get them work with FSUIPC? Best Regards Stefan
  10. Hi Pete, http://squawkbox.ca/doc/sdk/fsuipc.php was the perfect tip. I'm sorry for not reading the docs from the SB-site first. Perfect support as always! Regards Stefan
  11. Hi, is there any way to read (and set) the state of the (Vatsim) SquawkBox Transponder? Rgeards Stefan
  12. public void setButton(int joystick, int button) { // joystick 64-72 // button 0-31 joystick -= 64; int offset = 0x3340 + (joystick * 4) + (button / 8); byte[] data = new byte[1]; fsuipc_wrapper.ReadData(offset, 1, data); data[0] = (byte) (data[0] | 1 << (button % 8)); fsuipc_wrapper.WriteData(offset, 1, data); } Based on your comments I have rewritten the code and it's working really fine! :-) It was not clear for me that I have no exclusive area to write the buttons. I will keep this in mind. Thank you for support! Stefan
  13. If somebody would like to trigger the virtual buttons with the Java-API, this works: public void setButton(int joystick, int button) { // joystick 64-72 // button 0-31 byte[] data = new byte[36]; joystick -= 64; int offset = joystick * 4; data[((button) / 8) + offset] = (byte) Math.pow(2, button % 8); fsuipc_wrapper.WriteData(0x3340, 36, data); }
  14. Hi Pete, have managed the virtual buttons, problem is solved! :-) Regards Stefan
  15. Hi Pete, this is exact the same I want to do and also I agree that macros could be different on each computer. Currently it's not clear for me how to operate these virtual buttons, but I will try to find out. Thank you for support Stefan
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.