Jump to content

DirectX adapter for Brunner FFB Joystick ready


Recommended Posts

  • 1 month later...
On 5/7/2021 at 10:20 PM, Chuls said:

that's great. I was not sure at all it would but glad that fixed what you were seeing in DCS. I hope I'm not jinxing it now 😛

 

Hi Chuls, I went for the Arduino and encountered a problem during installation. First and foremost, in BrunnerDX, I need to manually select my COM port (doesn't auto detect), and then, when I flash the Arduino, at the end of the process, I get a issue saying:

 

14:06:23:094 Difference encountered during verification!

 

It says it two times.

 

Do you know what the problem could be?

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

The installation worked fine for me. 
 

 


Edited by Lynchsl62

PC: 9980XE @ 64GB RAM /2080Ti, Samsung C49RG90

Joystick bases: VKB GFIII, FSSB R3L, Brunner CLS-E, Virpil Mongoos CM2

Joystick grips: Realsimulator (F-18CGRH, F-16SGRH-CE), VKB (MCG Pro, F-14, KG-12), Virpil Warbrd

Throttles: Virpil CM2, Kantorrin,

Other: TrackIR, TM MFDx2 (Cubesim Screenx2), Virpil Control Panel 1

Link to comment
Share on other sites

For completenes this is the log I get when I upload firmware, just for your reference. Hpoe you get it to work as it makes the Brunner worthwhile in DCS:

 

2021/06/23 18:42:41.401 Starting ArduinoSketchUploader...
2021/06/23 18:42:41.401 Starting upload process for file 'C:\Program Files (x86)\jmriego\BrunnerDX.Setup\Fino.ino.hex'.
2021/06/23 18:42:41.401 Establishing memory block contents...
2021/06/23 18:42:41.401 Opening serial port COM8 - baudrate 57600
2021/06/23 18:42:41.401 Executing Post Open behavior (ArduinoUploader.BootloaderProgrammers.ResetBehavior.ResetThrough1200BpsBehavior)...
2021/06/23 18:42:41.401 Issuing forced 1200bps reset...
2021/06/23 18:42:41.417 T+0 - Port not found
2021/06/23 18:42:41.542 T+100 - Port not found
2021/06/23 18:42:41.651 T+200 - Port not found
2021/06/23 18:42:41.756 T+300 - Port not found
2021/06/23 18:42:41.877 T+400 - Port not found
2021/06/23 18:42:41.991 T+500 - Port found: COM3
2021/06/23 18:42:41.991 Establishing sync...
2021/06/23 18:42:41.991 Sync established.
2021/06/23 18:42:41.991 Checking device signature...
2021/06/23 18:42:42.033 Device signature checked.
2021/06/23 18:42:42.033 Initializing device...
2021/06/23 18:42:42.076 Software identifier: 'CATERIN'
2021/06/23 18:42:42.107 Software Version: 1.0
2021/06/23 18:42:42.138 Programmer type: S.
2021/06/23 18:42:42.168 Block support - buffer size 128 bytes.
2021/06/23 18:42:42.206 Supported devices: 68.
2021/06/23 18:42:42.206 Selecting device type '68'...
2021/06/23 18:42:42.246 Device initialized.
2021/06/23 18:42:42.246 Enabling programming mode on the device...
2021/06/23 18:42:42.286 Programming mode enabled.
2021/06/23 18:42:42.286 Programming device...
2021/06/23 18:42:42.286 Preparing to write 19954 bytes...
2021/06/23 18:42:42.286 Flash page size: 128.
2021/06/23 18:42:53.596 19954 bytes written to flash memory!
2021/06/23 18:42:53.596 Device programmed.
2021/06/23 18:42:53.596 Verifying program...
2021/06/23 18:42:53.596 Preparing to verify 19954 bytes...
2021/06/23 18:42:53.596 Flash page size: 128.
2021/06/23 18:43:03.890 19954 bytes verified!
2021/06/23 18:43:03.890 Verified program!
2021/06/23 18:43:03.890 Leaving programming mode...
2021/06/23 18:43:03.953 Left programming mode!
2021/06/23 18:43:03.953 Closing COM3...
2021/06/23 18:43:03.953 Waiting for virtual port COM3 to disappear...
2021/06/23 18:43:03.953 T+0 - Port still present...
2021/06/23 18:43:04.062 T+100 - Port still present...
2021/06/23 18:43:04.172 T+200 - Port still present...
2021/06/23 18:43:04.281 T+300 - Port still present...
2021/06/23 18:43:04.390 T+400 - Port still present...
2021/06/23 18:43:04.492 T+500 - Port disappeared: COM3!
2021/06/23 18:43:04.492 All done, shutting down!
2021/06/23 18:43:04.492 Uploaded to Arduino. Please click on 'Detect Ports' just in case the Arduino device has changed ports
2021/06/23 18:43:20.879 Trying to connect to CLS2Sim in 127.0.0.1:15090
2021/06/23 18:43:20.895 Waiting for device...
2021/06/23 18:43:20.895 Connected to device
2021/06/23 18:43:20.895 Checking Arduino Firmware version
2021/06/23 18:43:21.004 Arduino sketch version is v2.4.0
2021/06/23 18:43:29.860 Trying to connect to CLS2Sim in 127.0.0.1:15090
2021/06/23 18:43:29.860 Waiting for device...
2021/06/23 18:43:29.860 Connected to device
2021/06/23 18:43:29.860 Checking Arduino Firmware version
2021/06/23 18:43:29.970 Arduino sketch version is v2.4.0

 

PC: 9980XE @ 64GB RAM /2080Ti, Samsung C49RG90

Joystick bases: VKB GFIII, FSSB R3L, Brunner CLS-E, Virpil Mongoos CM2

Joystick grips: Realsimulator (F-18CGRH, F-16SGRH-CE), VKB (MCG Pro, F-14, KG-12), Virpil Warbrd

Throttles: Virpil CM2, Kantorrin,

Other: TrackIR, TM MFDx2 (Cubesim Screenx2), Virpil Control Panel 1

Link to comment
Share on other sites

This is the extract from mine. I really got no idea what's up yo. Why does mine check so many ports, compared to yours? I hope it's not a problem with running it on USB 3.0 or with 3.0 cable... I tried around other USB-ports and nada, same thing.

 

2021/06/23 19:52:47.698 Init
2021/06/23 19:52:48.085 You have the latest version
2021/06/23 19:52:52.250 Starting ArduinoSketchUploader...
2021/06/23 19:52:52.250 Starting upload process for file 'F:\BrunnerDX\Fino.ino.hex'.
2021/06/23 19:52:52.270 Establishing memory block contents...
2021/06/23 19:52:52.283 Opening serial port COM6 - baudrate 57600
2021/06/23 19:52:52.283 Executing Post Open behavior (ArduinoUploader.BootloaderProgrammers.ResetBehavior.ResetThrough1200BpsBehavior)...
2021/06/23 19:52:52.283 Issuing forced 1200bps reset...
2021/06/23 19:52:52.300 T+0 - Port not found
2021/06/23 19:52:52.403 T+100 - Port not found
2021/06/23 19:52:52.515 T+200 - Port not found
2021/06/23 19:52:52.627 T+300 - Port not found
2021/06/23 19:52:52.738 T+400 - Port not found
2021/06/23 19:52:52.847 T+500 - Port found: COM5
2021/06/23 19:52:52.847 Establishing sync...
2021/06/23 19:52:52.847 Sync established.
2021/06/23 19:52:52.847 Checking device signature...
2021/06/23 19:52:52.879 Device signature checked.
2021/06/23 19:52:52.879 Initializing device...
2021/06/23 19:52:52.907 Software identifier: 'CATERIN'
2021/06/23 19:52:52.940 Software Version: 1.0
2021/06/23 19:52:52.971 Programmer type: S.
2021/06/23 19:52:53.003 Block support - buffer size 128 bytes.
2021/06/23 19:52:53.035 Supported devices: 68.
2021/06/23 19:52:53.035 Selecting device type '68'...
2021/06/23 19:52:53.064 Device initialized.
2021/06/23 19:52:53.064 Enabling programming mode on the device...
2021/06/23 19:52:53.094 Programming mode enabled.
2021/06/23 19:52:53.094 Programming device...
2021/06/23 19:52:53.094 Preparing to write 19954 bytes...
2021/06/23 19:52:53.094 Flash page size: 128.
2021/06/23 19:53:02.829 19954 bytes written to flash memory!
2021/06/23 19:53:02.829 Device programmed.
2021/06/23 19:53:02.829 Verifying program...
2021/06/23 19:53:02.829 Preparing to verify 19954 bytes...
2021/06/23 19:53:02.829 Flash page size: 128.
2021/06/23 19:53:11.916 Expected: A5-91-25-91-35-91-45-91-55-91-A6-F3-EF-01-0E-94-9B-22-FE-01-97-01-A8-01-DA-94-69-F7-DF-90-EF-90-FF-90-0F-91-1F-91-CF-91-DF-91-08-95-DB-01-8F-93-9F-93-0E-94-47-22-BF-91-AF-91-A2-9F-80-0D-91-1D-A3-9F-90-0D-B2-9F-90-0D-11-24-08-95-AA-1B-BB-1B-51-E1-07-C0-AA-1F-BB-1F-A6-17-B7-07-10-F0-A6-1B-B7-0B-88-1F-99-1F-5A-95-A9-F7-80-95-90-95-BC-01-CD-01-08-95-97-FB-07-2E-16-F4-00-94-07-D0-77-FD.
Read after write: FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF
2021/06/23 19:53:11.916 Closing COM5...
2021/06/23 19:53:11.916 Waiting for virtual port COM5 to disappear...
2021/06/23 19:53:11.916 T+0 - Port still present...
2021/06/23 19:53:12.027 T+100 - Port still present...
2021/06/23 19:53:12.137 T+200 - Port still present...
2021/06/23 19:53:12.247 T+300 - Port still present...
2021/06/23 19:53:12.354 T+400 - Port still present...
2021/06/23 19:53:12.466 T+500 - Port still present...
2021/06/23 19:53:12.578 T+600 - Port still present...
2021/06/23 19:53:12.688 T+700 - Port still present...
2021/06/23 19:53:12.797 T+800 - Port still present...
2021/06/23 19:53:12.907 T+900 - Port still present...
2021/06/23 19:53:13.016 T+1000 - Port still present...
2021/06/23 19:53:13.126 T+1100 - Port still present...
2021/06/23 19:53:13.234 T+1200 - Port still present...
2021/06/23 19:53:13.341 T+1300 - Port still present...
2021/06/23 19:53:13.451 T+1400 - Port still present...
2021/06/23 19:53:13.561 T+1500 - Port still present...
2021/06/23 19:53:13.672 T+1600 - Port still present...
2021/06/23 19:53:13.782 T+1700 - Port still present...
2021/06/23 19:53:13.891 T+1800 - Port still present...
2021/06/23 19:53:14.002 T+1900 - Port still present...
2021/06/23 19:53:14.113 T+2000 - Port still present...
2021/06/23 19:53:14.224 T+2100 - Port still present...
2021/06/23 19:53:14.336 T+2200 - Port still present...
2021/06/23 19:53:14.445 T+2300 - Port still present...
2021/06/23 19:53:14.557 T+2400 - Port still present...
2021/06/23 19:53:14.667 T+2500 - Port still present...
2021/06/23 19:53:14.778 T+2600 - Port still present...
2021/06/23 19:53:14.890 T+2700 - Port still present...
2021/06/23 19:53:15.000 T+2800 - Port still present...
2021/06/23 19:53:15.109 T+2900 - Port still present...
2021/06/23 19:53:15.221 T+3000 - Port still present...
2021/06/23 19:53:15.331 T+3100 - Port still present...
2021/06/23 19:53:15.443 T+3200 - Port still present...
2021/06/23 19:53:15.553 T+3300 - Port still present...
2021/06/23 19:53:15.664 T+3400 - Port still present...
2021/06/23 19:53:15.776 T+3500 - Port still present...
2021/06/23 19:53:15.884 T+3600 - Port still present...
2021/06/23 19:53:15.994 T+3700 - Port still present...
2021/06/23 19:53:16.102 T+3800 - Port still present...
2021/06/23 19:53:16.214 T+3900 - Port still present...
2021/06/23 19:53:16.324 T+4000 - Port still present...
2021/06/23 19:53:16.435 T+4100 - Port still present...
2021/06/23 19:53:16.547 T+4200 - Port still present...
2021/06/23 19:53:16.658 T+4300 - Port still present...
2021/06/23 19:53:16.768 T+4400 - Port still present...
2021/06/23 19:53:16.879 T+4500 - Port still present...
2021/06/23 19:53:16.990 T+4600 - Port still present...
2021/06/23 19:53:17.101 T+4700 - Port still present...
2021/06/23 19:53:17.212 T+4800 - Port still present...
2021/06/23 19:53:17.322 T+4900 - Port still present...
2021/06/23 19:53:17.431 T+5000 - Port still present...
2021/06/23 19:53:17.541 T+5100 - Port still present...
2021/06/23 19:53:17.649 T+5200 - Port still present...
2021/06/23 19:53:17.760 T+5300 - Port still present...
2021/06/23 19:53:17.872 T+5400 - Port still present...
2021/06/23 19:53:17.982 T+5500 - Port still present...
2021/06/23 19:53:18.092 T+5600 - Port still present...
2021/06/23 19:53:18.202 T+5700 - Port still present...
2021/06/23 19:53:18.310 T+5800 - Port still present...
2021/06/23 19:53:18.422 T+5900 - Port still present...
2021/06/23 19:53:18.534 T+6000 - Port still present...
2021/06/23 19:53:18.644 T+6100 - Port still present...
2021/06/23 19:53:18.755 T+6200 - Port still present...
2021/06/23 19:53:18.866 T+6300 - Port still present...
2021/06/23 19:53:18.976 T+6400 - Port still present...
2021/06/23 19:53:19.086 T+6500 - Port still present...
2021/06/23 19:53:19.196 T+6600 - Port still present...
2021/06/23 19:53:19.307 T+6700 - Port still present...
2021/06/23 19:53:19.418 T+6800 - Port still present...
2021/06/23 19:53:19.528 T+6900 - Port still present...
2021/06/23 19:53:19.637 T+7000 - Port still present...
2021/06/23 19:53:19.749 T+7100 - Port still present...
2021/06/23 19:53:19.861 T+7200 - Port still present...
2021/06/23 19:53:19.972 T+7300 - Port disappeared: COM5!
2021/06/23 19:53:19.972 Difference encountered during verification!
2021/06/23 19:53:19.972 Difference encountered during verification!
 

 

 

 

For some reason, our logs differ. I am curious what this is:

 

2021/06/23 19:53:11.916 Expected: A5-91-25-91-35-91-45-91-55-91-A6-F3-EF-01-0E-94-9B-22-FE-01-97-01-A8-01-DA-94-69-F7-DF-90-EF-90-FF-90-0F-91-1F-91-CF-91-DF-91-08-95-DB-01-8F-93-9F-93-0E-94-47-22-BF-91-AF-91-A2-9F-80-0D-91-1D-A3-9F-90-0D-B2-9F-90-0D-11-24-08-95-AA-1B-BB-1B-51-E1-07-C0-AA-1F-BB-1F-A6-17-B7-07-10-F0-A6-1B-B7-0B-88-1F-99-1F-5A-95-A9-F7-80-95-90-95-BC-01-CD-01-08-95-97-FB-07-2E-16-F4-00-94-07-D0-77-FD.
Read after write: FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF

 

Also, why does it check so many ports on my side?


Edited by zerO_crash

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

It looks as though during the verification process at 19:53:02.829 there is a discrepancy between what is uploaded and what should be uploaded, and the characters FF-FF are what is loaded. At this stage that is about as far as I can help. I have my Arduino on USB 3 Powered Hub so don’t believe that is an issue, but perhaps connect it to a motherboard USB to see if that help.

PC: 9980XE @ 64GB RAM /2080Ti, Samsung C49RG90

Joystick bases: VKB GFIII, FSSB R3L, Brunner CLS-E, Virpil Mongoos CM2

Joystick grips: Realsimulator (F-18CGRH, F-16SGRH-CE), VKB (MCG Pro, F-14, KG-12), Virpil Warbrd

Throttles: Virpil CM2, Kantorrin,

Other: TrackIR, TM MFDx2 (Cubesim Screenx2), Virpil Control Panel 1

Link to comment
Share on other sites

Tried both already brother, I did both a USB 2.0 on the motherboard (right now it's connected to a 3.0 at the front of the computer), and initially I tried my power hub (USB 3.0 and separate power cable). No luck.

 

I also notice that the problem starts here:

 

2021/06/23 19:53:02.829 Preparing to verify 19954 bytes...

 

For some reason, it won't verify all the files. I just cannot understand how it's being flashed one sketch, but saves a different one...

 

Do I need to hold the reset button on the Arduino while it's being flashed in the BrunnerDX software?


Edited by zerO_crash

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

There is no need to touch the Arduino at all during the flash - mine is somewhere behind the PC. However it may be worthwhile to perform a factory reset if that is possible 

PC: 9980XE @ 64GB RAM /2080Ti, Samsung C49RG90

Joystick bases: VKB GFIII, FSSB R3L, Brunner CLS-E, Virpil Mongoos CM2

Joystick grips: Realsimulator (F-18CGRH, F-16SGRH-CE), VKB (MCG Pro, F-14, KG-12), Virpil Warbrd

Throttles: Virpil CM2, Kantorrin,

Other: TrackIR, TM MFDx2 (Cubesim Screenx2), Virpil Control Panel 1

Link to comment
Share on other sites

Just now, Lynchsl62 said:

There is no need to touch the Arduino at all during the flash - mine is somewhere behind the PC. However it may be worthwhile to perform a factory reset if that is possible 

 

Been doing that the whole day, since when my Arduino is being flashed from BrunnerDX, and it fails, the respective COM (6) disappears. Therefore, if I want to do anything with the Arduino, even use IDE, I need to factory flash it.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Suggest to try another PC with a fresh download of the BrunnerDX, then if that fails I suspect the Arduino is bad, hopefully you can return it

PC: 9980XE @ 64GB RAM /2080Ti, Samsung C49RG90

Joystick bases: VKB GFIII, FSSB R3L, Brunner CLS-E, Virpil Mongoos CM2

Joystick grips: Realsimulator (F-18CGRH, F-16SGRH-CE), VKB (MCG Pro, F-14, KG-12), Virpil Warbrd

Throttles: Virpil CM2, Kantorrin,

Other: TrackIR, TM MFDx2 (Cubesim Screenx2), Virpil Control Panel 1

Link to comment
Share on other sites

hi! I checked again the logs and I think I figured out something new. After uploading the code to the Arduino it complains that

avrdude: verification error, first mismatch at byte 0x4a80


That hexadecimal number is 19072 in decimal. I'd say that part of the memory is not working correctly. I found another sketch that is almost as big as this program at 19960 bytes, which should be enough to fail in your Arduino
Examples>GSM>Tools>GSmScanNetworks

 

If you try to upload that one it should give you the same error. Anyway, let's hope after you get the replacement it all works fine for you!

Link to comment
Share on other sites

54 minutes ago, Chuls said:

hi! I checked again the logs and I think I figured out something new. After uploading the code to the Arduino it complains that


avrdude: verification error, first mismatch at byte 0x4a80


That hexadecimal number is 19072 in decimal. I'd say that part of the memory is not working correctly. I found another sketch that is almost as big as this program at 19960 bytes, which should be enough to fail in your Arduino
Examples>GSM>Tools>GSmScanNetworks

 

If you try to upload that one it should give you the same error. Anyway, let's hope after you get the replacement it all works fine for you!

 

I wrote in Discord, but yeah, I got the replacement and the installation was successful through BrunnerDX! Apparently it was a faulty Arduino! It works now perfectly 😉 Thx again for help.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Sadly though, I still have the issue with overcorrection. There is something seriously wrong with the trimmer function in DCS. When I used the Hardware trim-only, everything was good and reacted realistic. Using the trim-keybinding in DCS, boom, overcorrection and bumps. Does this even work correctly for anyone with FFB and trim-keybinding in DCS? Say Ka50 for example?

 

- Can vjoy still be installed, or do I need to remove it so as not to interfere?

 

- Which unit should axis be bound to: my stick, Arduino or vjoy?

 

It seems really weird to me, because I don't get any cannon rumble effects. I only get the effects that I was getting with CLS2Sim. I see that the stick is limp before jumping into an aircraft, after which when I do, the stick energizes and goes to the correct position. Still, I am lacking some of the old "overdone" effects on the stick.


Edited by zerO_crash

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I don't know a lot about DCS but you can install vjoy and it would have no effect on anything.
You should bind the axis to the Arduino if you are using BrunnerDX, but if you are not I think the stick or vjoy would be the same for CLS2Sim

Link to comment
Share on other sites

Ive been thinking about doing my own FFB using motor controllers or possibly some servo motors but wasnt sure if i could do the directX ffb stuff. Would you mind if i had a look at your Ard file?  

1080 ti, i7700k 5ghz, 16gb 3600 cl14 ddr4 oc

Link to comment
Share on other sites

On 6/25/2021 at 10:12 PM, Chuls said:

I don't know a lot about DCS but you can install vjoy and it would have no effect on anything.
You should bind the axis to the Arduino if you are using BrunnerDX, but if you are not I think the stick or vjoy would be the same for CLS2Sim

 

Gotcha 👍

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

  • 2 months later...

Hi,

 

I tried using BrunnerDX and all went well except two things:

 

- Because I have both the Brunner CLS-E FORCE FEEDBACK JOYSTICK and the CLS-E MK II RUDDER WITH TOE BRAKES and there seems to be no feature to control the rudder through BrunnerDX I loose FFB in the rudder axis.

 

- Second, there is not much force increase with airspeed increase (tested in the P-51) but I guess that’s a DCS feature that may not be so well implemented… or it is as is.

 

Other than these two issues (maybe just one) BruunerDX works very well and the biggest plus (vs CL2SIM) is the working trims with the corresponding stick movement (the hardware trim from CL2SIM is a not so practical workaround because the simulated trim in DCS won’t move).

 

Cheers!!!

Link to comment
Share on other sites

Hey Chuls, any chance of having spring force hold the stick centered, unless you have an aircraft model loaded?  Since I use an extension, mine always falls to the side after I connect CLS2.

 

i9 12900k @ 4.9ghz, 32gb RAM

Nvidia RTX 3090

Windows 11 x64

Valve Index

Brunner CLS-E w/RS F16GRH, Virpil TCS Rotor Plus Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v1

Link to comment
Share on other sites

On 6/24/2021 at 4:48 AM, zerO_crash said:

Sadly though, I still have the issue with overcorrection. There is something seriously wrong with the trimmer function in DCS.

 

Are you by chance using any curve on your joystick axis?

I have MSFF2 and if I have any roll or pitch curve, the trimmer doesn't work right. I have to run zero curve on both FFB joystick axis.

Link to comment
Share on other sites

21 hours ago, Aries144 said:

Are you by chance using any curve on your joystick axis?

I have MSFF2 and if I have any roll or pitch curve, the trimmer doesn't work right. I have to run zero curve on both FFB joystick axis.

 

Negative, I have never used curves, as it makes the control non-linear. It does not replicate real controls. 

 

With that said, this is a specific issue with Ka50 trimming. It has been reported before, and is scheduled for fixing with BS3.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

  • 2 weeks later...
On 9/18/2021 at 6:30 PM, Shrimp said:

Hi,

 

I tried using BrunnerDX and all went well except two things:

 

- Because I have both the Brunner CLS-E FORCE FEEDBACK JOYSTICK and the CLS-E MK II RUDDER WITH TOE BRAKES and there seems to be no feature to control the rudder through BrunnerDX I loose FFB in the rudder axis.

 

- Second, there is not much force increase with airspeed increase (tested in the P-51) but I guess that’s a DCS feature that may not be so well implemented… or it is as is.

 

Other than these two issues (maybe just one) BruunerDX works very well and the biggest plus (vs CL2SIM) is the working trims with the corresponding stick movement (the hardware trim from CL2SIM is a not so practical workaround because the simulated trim in DCS won’t move).

 

Cheers!!!

 

Sorry everyone! I've been busy moving countries now and it will be a while before I can use my Brunner, but I can start coding and looking at things.

 

I'm afraid there's not too much I can do about the P-51 airspeed forces. That's something that depends on the developer for that plane. The best I can probably do is add force sliders so you can modify different forces in different ways (for example force spring differently than force damper). But that would just be a plain force multiplier for the spring effect, wouldn't know anything about current airspood.

I can write a small document explaining how to do this manually by modifying the Arduino code just for testing. Then if you think it's helpful I'll add a proper menu to BrunnerDX so you can edit on the fly.

 

On 9/20/2021 at 2:52 PM, heloguy said:

Hey Chuls, any chance of having spring force hold the stick centered, unless you have an aircraft model loaded?  Since I use an extension, mine always falls to the side after I connect CLS2.

Sure! I'll have a look at it. It's definitely possible but I'm going to need some help in testing it until I can access my Brunner again

Link to comment
Share on other sites

2 hours ago, Chuls said:

Sure! I'll have a look at it. It's definitely possible but I'm going to need some help in testing it until I can access my Brunner again

I can help with that.

 

i9 12900k @ 4.9ghz, 32gb RAM

Nvidia RTX 3090

Windows 11 x64

Valve Index

Brunner CLS-E w/RS F16GRH, Virpil TCS Rotor Plus Collective, BRD F1 Pedals, WH Throttle, FSSB R3 w/WH Grip, PointCTRL v1

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...