Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't work on Freespace 2 (tested only to single game) #27

Open
luca2125 opened this issue Mar 20, 2020 · 10 comments
Open

Don't work on Freespace 2 (tested only to single game) #27

luca2125 opened this issue Mar 20, 2020 · 10 comments

Comments

@luca2125
Copy link

Hi,

I confirm that not work on freespace 2.

Just copied dll and ini file on exe game folder.

There is a way to fix ?

@briankendall
Copy link
Owner

@luca2125 Try following the instructions to install devreorder system-wide. That may be necessary in order for it to affect Freespace 2.

@luca2125
Copy link
Author

luca2125 commented Mar 20, 2020

ok, I ask another question:

There are other games like xwing alliance, that work good with devorder.

In my case (and I' don't think to be the only one) I use it with vjoy becouse most games don't support multiple controllers.

The problem is that if all work and the game point to vjoy I can use multiple controllers in one, but I lose the force feedback.

My question is:

Is possible redirect all force feedback data to a different device (for example add a new section "Force Feedback priority" on ini file) ?

This can be very useful for my opinion ...

@briankendall
Copy link
Owner

@luca2125 Such a thing might be possible but is outside of the scope of devreorder. Are you transferring button presses from another physical controller to a vJoy device?

@luca2125
Copy link
Author

luca2125 commented Mar 24, 2020

yes, exactly.

I have 3 devices: cloche (with force feedback), throttle and pedals, all merged in only one virtual device (vjoy). This work ok, but the system see vjoy as ffb device with the final result to cut all force feedback effects becouse vjoy don't send the ffb to real device (in my case ms sidewinder force feedback 2).

For my opnion can be useful if is possible add a new section "Force Feedback priority" on ini file, or a section "Force Feedback redirect to device:".

I' aready known that is not exaclty the scope of devreorder, but I think can be a step up to solve other problems that within it is not easy to solve.

@briankendall
Copy link
Owner

@luca2125 I think the correct answer here is for vJoy to send force feedback to the physical device. And from some searching around it looks like it does support that. Check out the vJoy forums and search for thread about force feedback to see if you can find something that works for you. I haven't looked into it closely but I see some people there trying to do something similar to you, and it looks like there may be software that can do what you want.

@luca2125
Copy link
Author

hi briankendall,

thank you for your replay, I use vjoy from several years.

vjoy support force feedback but it is a great downside, becouse vjoy don't pass the ffb packets to real device, but you need to re-create artificially all ffb packets and apart the fact that it is very difficult to do it, you never get the some result, becouse you can only simulate it (to be honest I don't have expecience to do it).

Theorically the best solution can be hide the force feedback support to vjoy, but unfortunatenly vjoy don't offer this option, you can only disable the force feedback but all games still see vjoy as "force feedback device", this is the problem.

The trusted sign certificate of the vjoy developer is expired, and the developer was stopped the support.

Another possible but very hard solution can be hook vjoy in some way, but I don't know if it is really possible or not.

However if you have some idea, I'am very happy if you can share it.

thank you in advance

@briankendall
Copy link
Owner

@luca2125 Okay, I have a better idea now of what the issue is. It's too bad vJoy is no longer being supported as it is an excellent tool that I rely on daily. I would consider making a contribution to it to fix the bug where disabling force feedback for a vJoy device does not stop it from reporting itself as being force feedback capable, but I don't have a paid license to visual studio and cannot sign drivers. (Of course it is possible to disable the driver signing requirement, but it's not ideal.)

As for devreorder, I don't think it's actually possible to have DirectInput use different orders for button / axis input and force feedback. However it might be possible for devreorder to alter certain devices so that they report that they do not support force feedback. It sounds like that would solve your issue. Am I correct?

@luca2125
Copy link
Author

hi briankendall,

This is optimal solution, for my opinion. If you can add a section like for example:

"Force Feedback hide support"

for included devices (for example vjoy) this solve the problem.

If you can do it will be a great solution.

@briankendall
Copy link
Owner

Okay well I can't promise if and when I'll get around to adding that, but if I find some time I'll see if I can hack it in. Hopefully it won't be too difficult.

@luca2125
Copy link
Author

thank you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants