|
Post by jules gabriel on Feb 28, 2019 10:37:16 GMT
Dear mister Eizikovich.
I would like to know if you are the right owner of the Vjoy driver.
Or maybe it's Heasolft. I'm confused about it. Please give me more info about the licence thanks. Sincerely yours.
|
|
|
Post by Shaul (Admin) on Feb 28, 2019 14:57:08 GMT
I'm the owner of vJoy. Home page is: vjoystick.sourceforge.net/site/It is open source, free to use code. You may use it as-is or modify it if you please. Acknowledging my efforts will be nice but not mandatory. Shaul Eizikovich
|
|
|
Post by jules gabriel on Feb 28, 2019 16:29:16 GMT
Dear mister Eizikovich. Thank you for your attention. The reason I am asking is that I found two similar vjoy drivers on the internet. In property,one has your full contact information and the other has the information of the person mentioned above. Before using the driver I wanted to know who is the rightful copyright owner. If Headsoft used your Vjoy driver source to make a software or you did use their source to make your. Please accept, Mister Eizikovich, my very best regards.
|
|
|
Post by Shaul (Admin) on Feb 28, 2019 19:19:14 GMT
Neither copied. We worked in paralel. It is sheer coincidence.
|
|
|
Post by jules gabriel on Mar 2, 2019 11:41:18 GMT
Dear mister Eizikovich. Did you buy a Kernel-mode code signing certificate or used a open-source one?. Apropos: "Starting with new installations of Windows 10, version 1607, the previously defined driver signing rules will be enforced by the Operating System, and Windows 10, version 1607 will not load any new kernel mode drivers which are not signed by the Dev Portal. OS signing enforcement is only for new OS installations; systems upgraded from an earlier OS to Windows 10, version 1607 will not be affected by this change." My best regards.
|
|
|
Post by Shaul (Admin) on Mar 2, 2019 14:23:51 GMT
I did buy a Kernel-mode code signing certificate. It worked well until the last (1809 ?) version then I'm told it broke. The price of a certificate and the bureaucracy involved made me decide to finally stop developing vJoy. In addition, a better and a more generic project by Nefarius (such as this github.com/ViGEm)is in development.
|
|
evilc
New Member
Posts: 32
|
Post by evilc on Mar 8, 2019 20:39:15 GMT
Shaul, is that really the main reason? I am pretty sure Nefarius would let you use his, he started a company, so can meet requirements for getting own cert. He currently has no real plans to integrate DirectInput emulation into ViGEm, and I am sure there are people who would pitch in - we've got quite the nice community going, centered around the Discord Channel Please consider coming back?
|
|
|
Post by dantman on Mar 9, 2019 15:13:39 GMT
That is an interesting idea to continue making vJoy available.
Right now ViGEm doesn't have any support for non-gamepad devices so if you need to act like a HOTAS there is no option other than vJoy.
|
|
|
Post by Shaul (Admin) on Mar 10, 2019 19:13:23 GMT
Hi Evilc, Glad to see you here. Well, there are several reasons to my reluctance to carry on with vJoy. I have been on this for over a decade. At this point I lost interest in this project. I would be happy to assist people by answering a question here and there, but createing a new developmet and testing environments is too much work for me. Anyone can take the project from here or perhaps rewrite it using the most modern technics that weren't available back then. I've still here to try to help whenever I can.
|
|