Blazkovitch

I think there's a false assumption that 2FA is about stopping abuse of multiple accounts for trials. It's not. It can't be. It doesn't work like that. It requires the clock on your desktop to be accurate so no more going back in time to prolong the trial. But the risk of abusing multiple accounts ia still there. This, in turn, can be mitigated by using a hardware-based checksum.

Well then.. maybe Wine is not perfect for a 24/7 server... although I've seen too many DCS restart scripts to be 100% sure But seriously: my VM is rather small - 8GB of RAM - and the server is only restarted when DCS or Linux must be patched. The crashes are not often (haven't seen them recently) but I'm not monitoring the process in any meaningful way.

@BIGNEWY is someone looking into this issue? It's still ocurring.

I'm currently running a wine-based DCS server on Linode but it's mainly for me and whoever wants to fly with me so nothing heavy I'm using Ubuntu 22.04.3 and wine-8.0.2. I'm using following overrides: WINEDLLOVERRIDES='wbemprox=n;riched20=n' and everything seems to be working fine (apart from the usual - I think - dcs crashes).

For TEDAC or in general? For TEDAC make sure that triggers are treated as buttons or on split axis which can be mapped by Joystick Gremlin. Otherwise you won't be able to simultanously lase and fire. I'm using 8BitDo Ultimate Bluetooth with beta firrmware that allows me to switch from XInput to DInput. It's pretty good, uses hall sensors and is somewhat programmable with a desktop application.

Well.. only the sim crowd needs this kind of functionality and pads are usually not considered a sim-grade equipment so I somewhat understand simpler functionality On the other hand I'm pretty sure that you could do all that if given enough access to the firmware. You can set customizable dead-zones and assign macros to specific buttons so adding curves and analog-to-button mapping is just few lines of code away. Especially if you consider that beta-firmware already does that (more or less) for triggers. My only complaint is that the P1/P2 buttons are momentary-only (they do not register a continous button-press) and you cannot create layers with P1/P2 acting as modifiers. I even dropped an email to 8bitdo support and they said that they will consider adding these features but we all know how long it usually takes

It's a different pad so YMMV but I used 8BitDo's software because 3rd party software (e.g. vjoy or UCR) is buggy as hell and it crashed quite often when doing more complicated stuff. Also, the axis splitting is complicated because windows treats both triggers to be on the same axis so you cannot pull both at the same time so I decided to not use the 1st stage triggers. P1/P2 are programmable which means that the DCS won't see them as separate buttons unless you assign them to a macro (e.g. diagonal D-Pad) in a profile. I don't know why the mini-buttons are not working.

Recently I bought a 8BitDo Ultimate Bluetooth Controller and with either bluetooth connection or beta firmware for dongle it works pretty well. Bluetooth/beta fw is required to use triggers as buttons instead of a shared axis - I wanted to lase while firing Hellfires. You can also use 8BitDo software to map P1/P2 buttons to diagonal D-Pad (up-left and down-right).

Please, please, please publish your reshade settings together with the mod Pieknie prosimy!

Issue is still present in the latest patch. Can we get any update?

Check if you have "sync cockpit controls with HOTAS controls at mission start" turned off.