Testing with the FFBeast

[fdamstra]

Certainly not one of the controllers on the supported list, but I was curious if I could get the FFBeast to work and get some minor effects in ED.

I've taken the default settings.json and updated it with the GUID and Name:

  "Devices": [
    {
      "ProductGuid": "58f9045b-0000-0000-0000-504944564944",
      "ProductName": "FFBeast(Joystick)",

      "StatusEvents": [
        {
          "Event": "Status.Docked:True",
          "ForceFile": "Dock.ffe",
          "Duration": 2000
        },
...

It looks like it detects it on startup, but then fails to initialize ... something. Here's the output of running it from cmd on a windows 11 system:

C:\EDForceFeedback>EDForceFeedback.exe
DeviceName: Mouse: ProductGuid 6f1d2b60-d5a0-11cf-bfc7-444553540000
DeviceName: Keyboard: ProductGuid 6f1d2b61-d5a0-11cf-bfc7-444553540000
DeviceName: Stream Deck XL: ProductGuid 006c0fd9-0000-0000-0000-504944564944
DeviceName: 3Dconnexion KMJ Emulator: ProductGuid 046dbeef-0000-0000-0000-504944564944
DeviceName: Programmable Hotkeys: ProductGuid 508106a3-0000-0000-0000-504944564944
DeviceName: USB Audio Device: ProductGuid 00140d8c-0000-0000-0000-504944564944
DeviceName: SpaceMouse Compact: ProductGuid c635256f-0000-0000-0000-504944564944
DeviceName: Wireless Controller: ProductGuid 09cc054c-0000-0000-0000-504944564944
DeviceName: FFBeast(Joystick): ProductGuid 58f9045b-0000-0000-0000-504944564944
Found Joystick/Gamepad FFBeast(Joystick)
Effect available GUID_ConstantForce
Effect available GUID_RampForce
Effect available GUID_Square
Effect available GUID_Sine
Effect available GUID_Triangle
Effect available GUID_SawtoothUp
Effect available GUID_SawtoothDown
Effect available GUID_Spring
Effect available GUID_Damper
Effect available GUID_Inertia
Effect available GUID_Friction
File Effect available Cargo.ffe
File Effect available Dock.ffe
File Effect available Gear.ffe
File Effect available Hardpoints.ffe
File Effect available Landed.ffe
File Effect available Vibrate.ffe
File Effect available VibrateSide.ffe


***********************************************************************************

 Unable to access window handle.  Do not run EDForceFeedback.exe in a console window.

***********************************************************************************



Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at EliteAPI.EliteDangerousAPI.Start(Boolean runRichPresence)
   at Journals.Client.Initialize(Settings settings) in F:\workspace\elite\EDForceFeedback\Journals\Client.cs:line 44
   at EDForceFeedback.Program.<Main>d__0.MoveNext() in F:\workspace\elite\EDForceFeedback\EDForceFeedback\Program.cs:line 20
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at EDForceFeedback.Program.<Main>(String[] _)

Let me know if you have any suggestions. It's not clear to me what it's erroring out on, especially since I don't have an F: drive.

[bobhelander]

I have not tested on Windows 11 but I have to make sure that you have not attempted to run this from the command line.

---

Unable to access window handle. Do not run EDForceFeedback.exe in a console window.

---

This error displays because the force feedback libraries were written over 20 years ago. The library requires a parent window handle. The program attempts to create a parent window when the program is double clicked from the explorer. It does not create a window when it runs from another window like the command line.

For debugging purposes, the F: drive references are the source file location when the program is compiled.

Please let me know if this does not resolve your issue.

Bob

[fdamstra]

Sorry, I thought this was being more actively maintained from the dates on the files and some of the issues reported. Didn't realize it was using 20 year old libraries.

FWIW, I still get the "Unable to access window handle" when I start from explorer. Running it as administrator seems to get rid of that, but the Null Reference still occurs.

I tried compatibility mode to windows 7 and windows 8, as well, but no luck. Thanks anyway!