Jump to content

mbucholski

Members
  • Content Count

    109
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

9 Neutral

About mbucholski

  • Rank
    Eastern Forehand
  • Birthday 04/07/1993

Contact Methods

  • MSN
    mati_11@msn.com
  • Website URL
    http://www.pl-vacc.org/
  • ICQ
    0
  • Yahoo
    mbucholski
  • Skype
    mateuszbucholski

Profile Information

  • Gender
    Male
  • Location
    The Netherlands, Poland

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes
  1. You can assign the hat switch via FSUIPC. It doesn't work as smooth though. Space bar will have to be INOP. Side note, I run with controls enabled in FSX, as it doesn't really matter with FSUIPC assignments and doesn't give you above hiccups. I have my hat switch assigned both in FSX and FSUIPC - you can easily see when the input dropout occurs.
  2. No issues with FSX and Vista, been running this config for 1,5 year.
  3. After all this time, I'm pretty convinced the problem is in the kernel and there isn't much we can do. We're destined to either use FSUIPC or loose input unless MS shows some effort and interest.
  4. That's quite a drastic solution if I understand correctly, but glad it works for you.
  5. Nobody really knows how our simming environment will act under Win 8.1, and concerns have already been voiced that FSX fails to run under the public beta of it (see http://forum.avsim.net/forum/590-win8-os-forum/).
  6. It's probably a coincidence. I don't use REX and still had(have?) this problem. The unusual and tricky thing here is that you have to use FSX for quite a few hours (I'd say 20-30) before you can accurately asses whether this issue is still there - I had weeks when everything worked just fine and then joystick started disappearing again, out of the blue.
  7. In minus: throttle #2 is unresponsive in the NGX. In plus: I didn't lose controls after a couple of hours in MD11. All in all - FSUIPC looks promising. :rolleyes:
  8. Update: It turns out that DINPUT8.dll was the culprit in FSUIPC not recognising any joystick input. I deleted the file from FSX main directory and at least I can now assign controls via FSUIPC.
  9. Yep. That's the answer. It doesn't recognize it at all? Even with FSX controllers disabled and all the axes and buttons set in FSUIPC? Or it does recognize the joystick and then you lose control of it? When I try to assign a button or axis it doesn't recognise any movement or press. Joystick is working and enabled in FSX at that time. I haven't tried disabling it.
  10. Well, in my case fsuipc doesn't even recognise joystick inputs in Windows 8. Wysłane z mojego GT-I9100
  11. Sadly, after some test flying I can say that the "background processes" trick doesn't work.
  12. Click on the Advanced tab. It looks like this - http://www.thewindowsplanet.com/wp-content/uploads/2010/03/PerformanceOptionsChangeVirtualRAM.jpg Choose background services.
  13. Oops, something went wrong there. This should work - http://www.eightforums.com/tutorials/5657-visual-effects-adjust-windows-8-a.html
  14. You can find instructions here - http://www.eightforums.com/tutorials/5657-visual-effects-adjust-windows-8-a.html. When you get to the Performance Options window (last picture), click Advanced and there it is.
×
×
  • Create New...