Went to fire up Joystick Curves this morning as part of the same Elite: Dangerous startup sequence I've been doing for the last 6 years and got the following message ..
It turns out the software performs a "necessary update check" every time it starts and attempts to access a manifest file at www.xedocproject.com (I never knew this).
Unfortunately if you go to www.xedocproject.com you now get ..
So xedocproject's account has been suspended and now we can't use Joystick Curves anymore!
That's an absolute disaster as all of my analog bindings rely on the software's virtual joystick driver to make my twitchy HOTAS inputs manageable.
Has anyone got any thoughts/suggestions? Is it possible to somehow hack the software to bypass the update check? Or could we somehow spoof the URL it tries to get the manifest from?
For now I've created a new bindings file which uses the raw joystick inputs. You can do this by making a copy of the ".binds" file with your control bindings, changing the PresetName on line 2 and then doing a global replace of ..
.. for whatever your original joystick input device was called, for example ..
FIXED
1) run a command prompt as Administrator (you can get an option to do this by finding the shortcut to Command Prompt in your start menu and right-clicking on it)
2) cd \windows\system32\drivers\etc
3) start wordpad hosts
That will edit your hosts file where you can specify IP addresses for specific host names (people often use this file to block spam sites).
4) Add the following line to the end of that file:
127.0.0.1 is a special IP address that refers to your local machine (often referred to as localhost)
5) Save the file and then reboot your PC.
JoystickCurves should now startup normally (it will try to access www.xedocproject.com, get no response and give up trying).
Alternative solution: dev build of JoystickCurves by @dr_chef which doesn't include the installer/updater stuff.
forums.frontier.co.uk

It turns out the software performs a "necessary update check" every time it starts and attempts to access a manifest file at www.xedocproject.com (I never knew this).
Unfortunately if you go to www.xedocproject.com you now get ..

So xedocproject's account has been suspended and now we can't use Joystick Curves anymore!
That's an absolute disaster as all of my analog bindings rely on the software's virtual joystick driver to make my twitchy HOTAS inputs manageable.
Has anyone got any thoughts/suggestions? Is it possible to somehow hack the software to bypass the update check? Or could we somehow spoof the URL it tries to get the manifest from?
For now I've created a new bindings file which uses the raw joystick inputs. You can do this by making a copy of the ".binds" file with your control bindings, changing the PresetName on line 2 and then doing a global replace of ..
Device="FEEDFACE" DeviceIndex="0"
.. for whatever your original joystick input device was called, for example ..
Device="ThrustMasterHOTAS4"
FIXED
1) run a command prompt as Administrator (you can get an option to do this by finding the shortcut to Command Prompt in your start menu and right-clicking on it)
2) cd \windows\system32\drivers\etc
3) start wordpad hosts
That will edit your hosts file where you can specify IP addresses for specific host names (people often use this file to block spam sites).
4) Add the following line to the end of that file:
127.0.0.1 www.xedocproject.com
127.0.0.1 is a special IP address that refers to your local machine (often referred to as localhost)
5) Save the file and then reboot your PC.
JoystickCurves should now startup normally (it will try to access www.xedocproject.com, get no response and give up trying).
Alternative solution: dev build of JoystickCurves by @dr_chef which doesn't include the installer/updater stuff.
Joystick Curves utility no longer works - xedocproject account suspended! [SOLVED]
Went to fire up Joystick Curves this morning as part of the same Elite: Dangerous startup sequence I've been doing for the last 6 years and got the following message .. It turns out the software performs a "necessary update check" every time it starts and attempts to access a manifest file at...
Last edited: