zerO_crash

No worries, much of what you write is indeed true. I find it fascinating to see how the controls are solved on the "other" side. To be honest, I was quite surprised when I saw that the Apache has a force-trim release (i.e. trim) on the upper hat switch on the cyclic. From eastern helicopters, it would be much more natural for me to have the force trim where the flare dispense button is. I am quite sure that it´s a good design too, but its the little differences that make it interesting. The nice effect of that is having attitude-hold and altitude-hold on the same hat, and the respective disengage. I wonder though how natural having a trim button in that position is, when doing a prolonged flight. Even the trim logic seems quite similar in many cases, the difference being in the level of advancement, sophistication, automation and ultimately the methodology as set by the aircraft designers and the mission it is made for. What I cannot find in this helicopter is the engine trim switch. In the eastern aircraft, it´s located on the collective, and gives you the ability to, for a lack of a better word, trim the engine RPM up or down such that you can pull more or less AoA with the collective without demanding as much power from the engines. Does Apache not have anything like that?

If the helicopter isn´t trimmed within 3km/h, then the AP could start to overcorrect itself leading to a pendulum-effect. It will straighten out over time, but it´s not the real way of doing it. Within 20% of the cyclic´s position, the AP handles everything. The reason why you really want to trim the cyclic to hover before engaging auto-hover, is to have a smooth engagement of auto-hover as well as giving the AP the biggest playfield of the 20% authority that it has across x and y.

It´s important to mention that this is a efficient way for trimming with the typical flight-gear people fly DCS with. Otherwise IRL, and with a FFB joystick (like my Brunner CLS-E), the "recommended" way of trimming the Ka50 (or any Russian helicopter) is clicking for the reasons explained below (G-forces would make you susceptible to overcorrecting): Not really into western aircraft, but I wouldn´t be surprised if that was the case for Apache too.

This option should be in, if even for us who actually have the ability to simulate those switches on our pedals.

There seems to be the same bug with Mi24 that Mi8 had back in the day: This is literally the same issue, and it occurs if one doesn´t hold the trigger through the whole sequence, instead rapid fires. I´ve seen this now many times with both S-5s and S-8s. I can provide a track if needed.

Yeah I know about it, but this is a FFB force-trim issue. It’s likely that it needs a separate solution.

I seem to have a FFB-issue specifically with the Hind. Sometimes when I trim in the Hind using the trimmer button, I will get a weird feedback bug where the stick applies full force from one of the sides. It’s easy to replicate, basically use the click-trim method and click the trim often. It’s really weird, and doesn’t happen in any of the other helicopters or planes.

Gotcha

Thanks, will try

Well, I got it to work, but it is definately not working as it should. One just has to live with the bumps, when using click-trimmer. Those should not be there when trimming with a FFB-stick. I really hope someone from ED could just give me a straight answer whether the “bumps” and “overcorrecting” that I describe, ocurring with click-trimming, are supposed to be there? If not, then if a fix for this will come? I would also kindly ask to consider helping support the Brunner, beacuse this is a fantastic stick that shines really only in DCS, with these flight- and system-models.

I got my Arduino and went on with BrunnerDX. Sadly, I still get the issue with overcorrection. Both with FFB on and default trim, and FFB off and “Stick without springs and FFB”. In order to ensure what I mean, try to see if you have the behaviour from the picture. I am really not sure what does that, but it is an issue, both with FFB on and off. Regardless of the trim settings. @BIGNEWY Is this issue that I’m talking about, specifically for all helicopters in DCS, something that is reported? I am also missing some FFB effects, like the cannon rumble. I have tried Ka50 and Su27 and had no such rumble. Otherwise over-G effects work, with buffeting and otherwise shaking due to atmospheric- and weather-effects.

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.

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.

Mi24 is simply amazing, definately a work of art! Fantastic work as always ED

All my other computers are Macs. I tried reinstalling BrunnerDX and no luck. I might have to RMA this one, if I don't manage to solve it.

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.

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?

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?

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?

Precisely that

Ah gotcha brother, if it worked, I’d be in heaven. Sadly it requires the Arduino fix. My two gripes with that are: a) It’s not vanilla, little maintenance, but not standard. Not a fan of mods for aestethics and sometimes unexplained bugs. b) Some of the effects in the original FFB were overdone. As much as I like feeling a cannon shoot, it isn’t supposed to vibrate the stick. Sadly on e.g. Ka50 it’s overdone. I suspect that might be the difference in our results. You use Arduino fix heloguy, I don’t. But the overcorrection kicking in when not using FFB in DCS and “Stick without springs and ffb” just doesn’t make sense… Atm. I cannot use trim in DCS. It works so far, but it is far from perfect. That’s interesting. But with that in mind, I don’t get why the FFB-effects would be gone if Brunner uses telemetry (which I know it does)? I tested WWII aircraft and L-39/Mig21Bis. No luck there. My Jetseat did work though. CLS2Sim has to be used before in the mode of HID-device. Now it has a beta DCS-mode. It should support DCS in the basic way for sure. Much has changed, improved, with them and DCS-support over the past 2-3 years.

Indeed, but remember that the operator only has the simple sight for firing. The foldable fixed sight. I, as a pilot, use the fixed sight myself for firing any weapons, primarily because I got a good eye for predicting trajectory and also simplicity. Ease of use during combat. For sure there isn’t anything more advanced in the operator’s seat than fixed sight. You’ll have to get used to it mate.

Mig-21Bis doesn't have an ammo counter. But that's beside the point. I believe I read that those counters are work-in-progress. Don't worry, they will come, but right now ED has more pressing issues and bugs to fix.

Ok, I tried it. With: - FFB off - Trimmer mode - Stick without springs or FFB - Bound DCS trim-button (Mi8/Mi24/Ka50) to the same that I have Hardware trim on in CLS2Sim (they are not interfering with each other, tested it) I get no FFB-effects on my Brunner, which is a must with WWII and planes with hydraulic-controls. I surprisingly still get FFB with my Jetseat, which is nice. However, with "Stick without springs and FFB", I get overcorrection when trimming. The overcorrection is a surprise considering FFB is off and the trimmer mode selected. This just doesn't work. I really hope that ED can come up with a solution to have FFB on, and allow a trim mode that only updates AP without the overcorrection. The Brunner is such a fantastic piece of hardware, professional hardware, that it's a pleasure and joy to fly with it.