Ppjoy Error Installing New Device Drivers Windows 10
Eugene Aubry
Help me for ppjoy. I can't use only when the W7 64bit is on test mode. When deactivate test mode show this error .Can't open the ppjoy device driver .Please install ppjoybus.sys first. The error is the certificate of the driver. But i try to install that in manual. But any solution in this way. I try to remove the watarmark, but not solution. Why in my system there is this problem?
I read on support PPjoy. It's run only with test mode. But in the video it's deactivate the test mode. Any people use ppjoy with normal mode. I don't want use test mode. Or i see beta 5 or final release of A10C to use wit faketrackIR or freetrack with any trackir fixer.
Is there any way to see or match the axis definitions on the three programs? In FTNI the values are displayed as you can see below (X, Y, Z, rotX, rotY and rotZ). It would be great to be able to read the values in ppjoy and DCS to see which axis correspond to which of the others, in other words if for instance a change in the rotX value in FTNI create changes in X Rotation in ppjoy.
I tried following Daniels walktrough but ended up having to start over in the DCS axis settings, choosing one axis at a time until they all matched. Perhaps this was casued by some snafu from me, but still annoying. I just noticed that Daniels instructions for setting up ppjoy has rotational axis first, then the non-rotational ones. Again, I have no clue to if this is right or wrong, but seeing that FTNI at least displays the non-rotational ones on the left and the rotational ones on the right got me thinking that Im not sure that the axis are mapped correctly. The original post also have the axis the other way around in ppjoy (hope Im making some sense).
After doing this one evening everything was wrong the next evening. Perhaps due to removing the USB connector for the webcam? I think this happened after I switched from a webcam to the PS3 eye. Had to start all over again. :(
To put it another way, when figuring which axis to choose in the DCS axis settings, is there a faster way than choosing one, then starting up a mission (I use a training mission), see if the virtual and real head movements match, end the mission, go to options, rinse and repeat?
Cannot zoom in/out in the cockpit by the keyboard anymore. Using keypad 0 to see instrument panel. Joystick hat switch stopped to. A little slow to move view from one side to another. No up/down movement.
Strange. I have Win7 64-bit and FC2 32-bit. But my trackirfixer fixed that newinput.dll. Please check if there is some misconfiguration in TracknoIR because the fixed dll is working fine with freetrack that I am using.
WARNING: Windows Vista 7 & 8 64Bit Users will have to disable Driver Signature Enforcment for this Workaround. If you are not comfortable with that DO NOT try this. In general it shouldn't be a problem but you still need to disable a SECURITY FEATURE which makes your PC more vulnerable. You have been warned!
I wanted to try out playing KSP with a Joystick, a trusty, few years old Saitek one. But what i discovered was that it wasn't exactly behaving right. My spacecraft always wanted to move somewhere and the throttle, which i bound to the slider, could only be set between like 10% and 60%. What was happening was: The Joystick was not calibrated properly. So i recalibrated it with the Windows calibration tool but nothing changed. Even weirder: It worked perfectly fine in other games.
For some stupid reason Unity uses Raw-Input. I've seen many Unity-developers complain about it in forums. It's pretty ridicculous. But this is why Joysticks in KSP (which uses Unity) are never properly calibrated.
Unfortunately this is not being developed any longer and i haven't found any "official" sources where you can still get it. But this tutorial here has a link to the download: =PPJoy_for_using_multiple_joysticks
The PPJoy setup will PERMANENTLY disable driver signing and does not reenable it when you uninstall it. To reenable it yourself, open a CMD as Administrator and type (without ") "bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS" and then "bcdedit -set TESTSIGNING OFF"
4) Open KSP, go to settings and set the Joystick commands using your physical Joystick (Don't worry if they are named the same as before. You are actually using the Virtual Joystick. No idea why the name doesn't change)
Good post. I ran into the exact same issues as you did when I tried to use my Sidewinder 2 and came to roughly the same solution as well (my problems and solutions are documented here: -What-s-the-best-way-to-set-up-a-Joystick-for-this-game).
After messing around some, I found that GlovePIE is actually a little more flexible than PPJoy's Joystick Remixer. Both are good solutions depending on what kind of control stick you have though. Again, good guide either way. It's important to get this info out there to people with these problems!
Oh, nice! I had to unplug my Logitech G940 stick/throttles/rudder setup because Unity doesn't read it correctly, and pull my old Sidewinder out of the basement for KSP. I'll have to see if this fixes the problem...
It works with anything. You can also use your keyboard or mouse with it. For example: You press "E" and PPJoy presses Button 1 on the Virtual Joystick. Although that may not be very useful in this case.
GlovePIE uses PPJoy as far as i know and you can do much more things with it. I think you can even program Joystick macros right? It seems though their site was hacked and nobody cares about fixing it. Who knows what happened to the GlovePIE binaries hosted there :S. But you can get it from 3rd party download sites. Just google "GlovePIE 0.45". That's the newest version afaik. Here for example: -0.30_174835.html
The important part is the ID field. The virtual stick is registered as my "first" joystick by default, and my real one second. So joy0.0 refers to the X-axis of my virtual stick, and joy1.0 would refer to the X-axis of the real one. So if you're having problems making things map in-game, go into the config file and try changing stuff manually and see if that helps.
Also note that the second number in the joyx.y pair depends on how you set up your virtual joystick's axes. By default it has 8 axes, but I set mine up to just have the same 4 that my real joystick does.
Assuming your Virtual Joystick really works properly you might try another program that comes with PPJoy called "Keyboard Joystick". It does the same thing as the Joystick remixer, but uses the keyboard instead. Just for configuring KSP.
3) Press WINDOWS+R and type "joy.cpl" and enter. Do you see both your real Joystick and the Virtual one there? Select the virtual joystick, click "Properties" and then go to the "Test" tab. Move your real Joystick around and press a few buttons. Do they all work? If yes, then the Virtual Joystick does really work properly and I'm out of ideas. :S
I am having the same issues. I opened the mixer, set up a basic joystick: x and y axis, z rotation (the twist of the stick), and button for each button. No hat since I can't figure out what that'd be.... but I left it out out of simplicity. I saved the .ini as ppjoyff2.ini so I could relaod it anytime and loaded up KSP. I went into settings and tried to map the axes out in "Staging". Instead of saying "Sidewinder FF 2" on the button, it had a kind of garbage. So I figured it was reading from PPJoy now. I loaded up a simple plane to test the joystick with and none of the axes worked properly. They behaved as if nothing had changed. Am I missing something?
EDIT: If the driver signing is disabled, what is the best way to tell? If I did the joy.cpl and ran the test and configuring of the PPJoy1 virtual device using my Sidewinder... is that a good indication that the driver signing is disabled? If so, then I am still having issues. Not sure what to do at this point, either. However, if driver signing might still be enabled I will go that route... but I think it's off.
I wanted to note that I'm using Universal Joystick Remapper (which leverages vJoy instead of PPJoy) because I've gotten the impression that it has been actively in development. For the most part I'm happy with it, easy to use. Still requires Test Mode. Does everything I need it to do (merge pedals into single axes, easily invert axes, change axis ids on the fly, and utilize/simplify multiple joysticks).
My 1st issue was to get my racing pedals to map the Clutch and Accelerator to one axis for use as a Rudder. This has been done now and UJR w/ vJoy made that easier than what I had been trying with PPJoy and GlovePie (not to mention that PPJoy stopped successfully installing, even in test mode, for some reason).
My 3rd issue is going to be that these ids seem to get all mix'n'matched when you unplug and replug in joysticks...I have quite a few that I change for racing, flying, controller-pad for action, etc...so this is going to be a problem. I could probably see if I can get everything onto the virtual joystick and somehow keep it's id as 0...but I'm not sure that covers everything. Unity could really use a huge boost here...
4th issue is pretty silly? Once I get these joysticks working, there isn't a follow mode while in atmosphere? So I'll have to take my hand off the stick to turn my view so I can follow a plane? I haven't gotten to this point so perhaps the answer is really simple and I've just overlooked it. If other's have ideas... EDIT: Nevermind, chase camera view works just fine. For some reason it wasn't working the way I had previously experienced but that must have been a mistake on my part, everything works as expected.
3. KSP still seems to get confused (though I still think I could find a way to force a consistent joystick ID and that should solve the issue) BUT, for the most part this is easily resolved. Often I can even solve the problem by just changing some of the associated Joystick/Axes IDs in UJR and that'll get them back inline with KSP.
I have the same problem and the POV is not working here too. I'll try to fix it up and post here if I'm lucky, no promises anyway... I really can't believe using a joystick with this game is such a PIA.
b37509886e