117 replies to this topic

[MentalPatient]

Hi, this program sounds great but I have one question. Does it support absolute movement rather than the default movement a joystick typically gives, as absolute movement is more appropriate for mechwarrior games. Thanks.

[MustrumRidcully]

evilC, on 23 January 2013 - 11:19 PM, said:

Unfortunately, yes.

You will probably never have a way around this, unless you get yourself or the driver certified. That will probably be out of the scope of a one-man project.

Which is a pretty amazing one, I think. I don't use joysticks, but this seems pretty cool.

[F lan Ker]

S!

Good show EvilC

[evilC]

von Pilsner, on 11 April 2013 - 01:12 PM, said:

In my setup I had to change the joystick curve from a linear one:


To a nice gentle curve...


Perhaps EvilC could make a linear/Log checkbox for the axis (would require a recalibration if checked/unchecked).

Assuming that controller.AimingX and controller.AimingY is a value from 0-255
and axisx and axisy are what the program outputs/uses

Here is the code snippet that worked for me...

   xaxis = (127-controller.AimingX);
   xaxis = ((-1*xaxis)*xaxis);
   if (controller.AimingX >= 128)
   {
	xaxis = xaxis*(-1);
   }
 
   yaxis = (127-controller.AimingY);
   yaxis = ((-1*yaxis)*yaxis);
   if (controller.AimingY >= 128)
   {
	yaxis = yaxis*(-1);
   }

Just a simple adjustment of the axis value to x^2 gives much more control in the middle of the stick and still allows full speed movement when the stick is near its maximum range. The downside is that since I do not scale the values back down a recalibration is required.

I just happened to notice this old post, must have slipped past me...

The second graph looks odd - it ignores values over a certain max or just reports them as 100%?
Whatever, this is basically what UJR's "Sensitivity" option does. It adjusts the curve such that max values are returned for a partial deflection.
Furthermore, it only ever reports the same max as you would see with a normal mapping, so no recalibration is required.

Edited by evilC, 12 July 2013 - 11:13 AM.

[evilC]

New versions up.

Hadn't updated in a while, but there are various ways of mapping the hat switches, plus profile support.

[Hammerhai]

Evilc,
had a go at installing ujr but got the following error

missing comma at line 356 in vjoylib.ahk
Syntax looks correct to me.
Can you help?

Here is the offending line, but most likely the glitch is further up

VJoy_init(id := 1) {

Edited by Hammerhai, 16 September 2013 - 08:48 AM.

[Hammerhai]

Nvm, fixed it
It should read
Vjoy_init( id = 1){
iow an equals sign
As far as I can tell. Pls check. I am a Spectrum Man, and I miss my Highsoft Pascal right now... So EASY

[evilC]

Hmm, what version of AHK do you have?
There should be nothing wrong in vjoylib.ahk - I did not even write that code and I certainly have not changed it.

The only thing that I can guess is wrong is you do not have AHK_L, instead some other fork of AHK maybe.

[Hammerhai]

One of those things then.
I do indeed run ahk_l, so that is not the problem.
All I can say is that changing the line in the above way allows ujr to run, and I have gotten it to work in MW4 that way.
Personally, that is where it stays for me. Some things are not meant to be known by man and all that (cue H P Lovecraft voice here).

Demons exist, and they possess computers nowadays, I learnt that a while ago, when trying to resolve incompatibilities

[evilC]

I have asked the author of vjoylib.ahk if he knows what could be the issue with that line.

It shouldn't be a big issue though.

:= is AHK syntax for "Use C-like assignment"

a = b assigns the string "b" to var a
a := b is assigning variable b to a
a := "b" assigns the string "b" to var a.

id := 1 assigns the integer 1 to var id
id = 1 assigns the string "1" to var id

so they are kind of similar, and as long as anything examines id does not care if it is a sting or an int, then it should be the same thing.

[Enderman]

I always get the follwing error:
[VJoy_DeviceEr] Device 1 is not ready

when trying to assign a virtual joystick, how can this be fixed?

[evilC]

Enderman, on 21 September 2013 - 04:44 AM, said:

I always get the follwing error:
[VJoy_DeviceEr] Device 1 is not ready

when trying to assign a virtual joystick, how can this be fixed?

Does the vJoy feeder demo work? Have you enabled the virtual joystick?
Did you use the right vjoy? (sourceforge-shaul not headsoft)

[evilC]

I have been thinking about a UJR update / rewrite for a while, and I think I may bite the bullet pretty soon.

If you use UJR and have any niggles with the current version, or suggestions for the new version, I urge you to reply to my post on my google groups forum.

[evilC]

UJR 5.0 is out!

[SaltBeef]

Sounds like you have to be a C++ programmer to get the stick to work, turn most guys off quick. I did manage to get my old microsoft precision pro-joystick to work after tweeking only issue was that the r-z torso twist was way too slow not sure how to speed it up , ( faster with a mouse ) Up down ( forward back on stick was too slow also ) made it hard to hit and track targets all of the button mappings worked. Too bad I loved my old force feedback joystick.

[evilC]

I am thinking about trying to get crowdfunding going to get the vJoy driver signed, so that Test Mode is no longer required under 64-bit windows.

If you are interested in helping, please make a post on the vJoy forum.

[evilC]

The maker of the jVoy virtual joystick code that UJR uses is trying to raise some cash to get the driver signed (So Test Mode is no longer needed).
If you are feeling at all generous, please pop over here and pop a little in the donate jar - our target is about $180.

[evilC]

A new version has been rolled out, 5.3

PLEASE NOTE: If you use the "axis merging" feature, the way axes are merged has been changed - please see the changelog.

The new method is much more intuitive to set up.

Also, movement of merged axes should be smoother.

[CyBerkut]

I got an email that vJoy is now signed.

It looks like it installed properly.

[Loc Nar]

Great news, gonna give it another go now. Hopefully ditching Saitek's SST will make my USB's stop catching full blown a i d s as soon as I add Ts3 to the mix >_>

I'm suspect of SST because my problem always begins with my rudder pedals glitching, leaving me in a constant turn until I unplug them. Then all my USB's go out and ts3 proceeds to spam uncontrolled (digitally generated) beeps like some kind of robotic Tourettes fit into the channel till I literally pull the plug on my whole computer.

It disables all interface ability (no mouseclicks even if mouse x/y works, no enter button, no way to affect/pull up menus...). It's beyond annoying, and if anyone has any similar experiences or insight I'd love to hear about it. In the meantime I'm giving this another go since I've long wanted to use merged axes on my pedals but have never bothered to really do it.

Edited by Loc Nar, 27 December 2013 - 04:12 PM.