Frost_rus

Hi again. A couple more things to the knowledge base. Long story, see TLDR below. I initially connected the sensor with the resoldered cable, and it seemed to work (checked in Windows device test tool). But I had no time to actually play. Tried it in DCS after a couple weeks and found that it starts working properly but after a few minutes starts to "jump" again. Just a bit at first, then more and more, and after a few more minutes - completely stops working. Immediate device reconnect didn't help but letting throttle rest disconnected for a few minutes brought it to working state. And it kept working again for 2-5 minutes I thought that maybe my soldered cable still had loose connection, so ordered one more 5pin cable (Molex with proper pinout this time). Replacing the cable didn't change anything. I tried to use all USB ports, flashing original and patched firmware, recalibrating - same result. Original sensor had no issues, as well as other throttle axes and buttons. Same results in MSFS. Then I tried to run hardware stress test (FurMark + CPU-Z) and figured out that the sensor stops working properly when the system is under heavy load. Actually, if only CPU or GPU alone is at 100% utilization - everything was fine, but issue starts under full load. As soon as I stop benchmarks (or DCS/MSFS) it gets back to a normal state after a few minutes. For reference, the hardware is ZOTAC RTX 4090 / MSI MPG B650 Edge / Ryzen 7600X / Corsair RM1000x Shift. I suppose, the motherboard is relatively low-end and has issues under load. Or PSU issues (less likely). Most likely something was wrong with USB voltage under load. I also found that sensor axes do not work completely (even in idle mode) when I connect the device using USB extender, while everything else worked fine (including original sensor). So maybe it requires more stable voltage than other parts of the throttle. TLDR: at final I connected the throttle via externally powered docking station (Thinkpad, USB-C), run stress test and DCS and it seems to work. At least, no issues after 20 minutes (and before that it started to fail after 2-5 minutes). Will fly for a few hours this weekend to ensure it works stable with the dock. Hope that will help if anyone else have same issues Update: I can confirm. Was flying DCS for a few hours - no issues anymore, while using the dock station

Ok, I can confirm it was a damaged cable. After a couple days it stopped working again. Disassembled the throttle, reconnected the cable, it started to work, still unstable. Then a new 5pin cable arrived. The problem was that the cable I ordered had reversed pinout. So I had to cut all wires (except the middle one) and reconnect them as needed (1st to 5th, 2nd to 4th). I'm not good at soldering, so initially it was also jumping. Now soldered again and it finally works as expected. I hope soldered wires won't break super soon maybe I'll order one more cable, with correct pin out this time. TLDR: if ministick response is unstable (does not work, or "jumping") it is most likely a cable. Even when it seems to be ok. Most likely, some wire was a bit damaged, and its resistance was higher or it was loosing continuity randomly

Correct, cleared windows calibration and run calibration tool from https://deltasimelectronics.com/pages/install-instructions I have only tested it using standard windows device settings window. I'll check later if it affects real usage scenarios in DCS. +also ordered molex 10cm cable, just in case.

wow, today I did what you suggested, and it works! Thank you again! I have no idea what I did wrong last time (as far as I remember, already tried these steps yesterday). The only thing now is when I slowly move mini stick, the cursor starts to "shake" and "jump" to 0 and back to real values in some positions (both in v23 and v100, and after recalibration). I still suspect it may be one of 5 pin cable wires a bit loose. So I'll try another one. These ones should fit, right? https://www.digikey.com/en/products/detail/adafruit-industries-llc/4925/14291408 or 0151340500 Molex | Cable Assemblies | DigiKey

Ok, will try tomorrow and then let you know. Thanks

Hi @Deltaalphalima1 I just got my slew upgrade (order #9603), installed it, and have the same issue. Click works fine, but X/Y axes do not work. Tried both TM v23 and Deltasim v100 firmware. Updated firmware with both old and new mini sticks installed Cleared windows calibration and used TM calibration tool (v1.07). Tried to swap 5pin cable ends - same result. Slew axes work when I connect original sensor and recalibrate. Cable continuity looks good (checked with ohm meter), but maybe I should still try another cable to be 100% sure? What else can I do to troubleshoot? (I'm using Win 11 22H2 if it matters) Thank you, Andrey

Guys, correct me if I'm wrong (that are my thoughts after some reading... but I never tried DCS with any VR): 1. new Oculus Quest 2 requires better hardware than Rift S due to higher native resolution. But the result quality is worse (because it uses USB and compression instead of DP) 2. Rift S requires ~2x multisampling to make picture "OK" (but still not ideal). And new high resolution headsets (like Reverb G2) will work with 1x. But Rift S is still better if you don't have high end GPU 3. Reverb G2 will be much much better then current "G1". But G1 is better than Rift S / Cosmos / Odyssey 4. Having a laptop with i7-9700F / 64RAM / RTX2070 (laptop version, closer to desktop 2060 in terms of performance) - Rift S is the only option that will work with reasonable FPS To be clear: I'm not interested in competitive multiplayer (dis)/advantages (that was ages ago). Single player only, but I still want to be able to read gauges / HUD text in VR.

Даёшь ИРК канал. Можно в принципе и на сайт прилепить java клиент с подключением к соответствующему ирку. Поверьте, это только плюс, есть положительный опыт работы с ИРК в подобных условиях (с другой игрой)

Ripcord, с вами лучше общаться по-русски или in english?

Пока это технический эфир. Но вообще да, если зайдёте в лобби - регулярно можно увидеть сервер. Об официальном запуске (с новой кампанией и фишками) будет объявлено дополнительно.

Забавное наблюдение. Посмотрите на строку браузера http://www.games.1c.ru/lockon_hr2/?type=news lockon_hr2 В реестре кстати кроме раздела flamming cliffs можно найти раздел hot rocks Видимо, старое рабочее название проекта?

В первую очередь смотри на стабильность канала. Нужно, чтобы в режиме 24/7 при полной загрузке не начинались потери пакетов и прыжки задержки. Ну а сама ширина канала... с разумным запасом можно рассчитывать на комфортную игру 8 человек.

Кстати. А где лежит EULA применительно к ГС2? При установке даже нет стандартного экрана "я согласен" :)

Кстати, очень эффективна порою система votekick Можно сделать в ротаторе

Проблема есть, подтверждаю. Но предложенные варианты - это утопия. Даже в сетевых играх с многомиллионной аудиторией подобного не делается. Единственное - это если клиент будет передавать некий хэш своего ключика - то есть банить аккаунты. Тем не менее полностью поддержу добавление в wishlist любых новых средств для ограничения доступа к серверу.