lester

That's unfortunately v1 version of the cable which is not available anymore. v2 costs $185.90 in the official US HP Parts Store.

Problem is in WMR for SteamVR. Solved here:

And the problem is gone for me too after switching to the lkg_release of the WMR for SteamVR: tried both missions where I had it before. Thanks again cptmrcalm!

Thank you so much for the research! I'll try to rollback WMR for SteamVR to the lkg_release a bit later today and return back with the results.

Looks like I have similar issue: I got this SteamVR critical error first time on October 8 too. Didn't change anything either. I suspected SteamVR update.

I'm getting SteamVR error during night mission in a Hornet with Supercarrier I never had any problems with before. I initially thought that it might be a mission specific thing when I played Raven One: Dominant Fury mission but then I started getting it every time I play my custom Case 3 Recovery mission in a Hornet with Supercarrier at night I never had any issues with before SteamVR was updated. It starts with some stutters and fails some time into the mission on my way to the marshal stack or when I'm in the marshal stack and look at the carrier direction. SteamVR fails with critical error, but DCS process itself still stays alive. I didn't have this problem in other missions. Update: Turned out I'm observing serious stuttering in other missions too and I also got this error in the F-14A Refueling mission. I guess with SC and/or clouds it's just heavier. fpsVR doesn't show anything different from what I had before. Now I realize that it might be my personal thing, but I noticed another user reported similar error on the Spanish sub-forum: I'm sure it's SteamVR-related issue, but it would be nice to know if anyone else experienced it and are there any specific conditions. SteamVR 1.24.6 DCS 2.7.18.30765 NVidia GTX 3090 (tried both most recent 522.25 and older 516.94 versions) i7-10700K HP Reverb G2 Windows 10 P.S. I know about OpenXR and will try to switch eventually.

Sorry for the English here. I'm experiencing exactly the same issue (it's consistent and occurs after some time into the mission). It looks like something is broken with the current SteamVR release (I'm on 1.24.6). I initially thought that it might be related to the specific mission in campaign I played: but then I got it in my own custom mission I played without any problems for ages. May I ask: when you encountered this error, did your mission involve Supercarrier module and was it a night mission? ¡Gracias! UPDATE: Problem is in WMR for SteamVR. Solved here:

I'm also getting error on Mission 08 in VR, tried 4 times already: 3 times when I was close to the WP1 at the assigned altitude, 1 time on my way to the WP1 (i.e. very early in the mission). What's interesting though is that in my case it's SteamVR crashing, DCS process itself stays alive. DCS: 2.7.18.30765 SteamVR: 1.24.6 UPDATE: In my case the problem was in WMR for SteamVR update. Solved here:

You were really lucky with that. I'm also out of warranty (I own it ~ 1.5 years) and tried both to chat and call HP Support and the only option they had for me is to buy a new cable (V2), which costs $185.00 (completely new headset now costs $399.00). Luckily I haven't observed the issue I had anymore: several pixel-wide colored vertical lines at the edges on the right LCD screen only, but if it happens again I'd rather go with the new headset.

Just flew this mission this night. I didn't have any issues with ICLS. One issue I experienced though is that during startup on the carrier, it was a moment as if entire ship leaned aside or small instant earthquake happened and it cost me broken landing gear (just in case: I removed wheel chokes right after the mission start), had to restart. On restart this event happened again, but this time with no damaging consequences.

ОФФТОП: Да, но это не то... Хочется фулл фиделити Игла (не Страйк) от ED (ноющим голосом).

F-15C фулл фиделити

На левом MFD выбираю HAD, на правом TGP. Когда радар системы ПВО становится виден на HAD, навожу на него курсор и "выбираю" его нажатием TMS вверх. При этом TGP на правом MFD переключается на примерный район местоположения системы ПВО. Записал трек, вроде сошелся. viper_had_tgp_switch2.trk

А разве HAD позволяет установить точные координаты источника излучения? Насколько я понимаю, выбрав эмиттер на HAD, можно направить другой сенсор (например TGP) на примерный район его расположения и провести доразведку, затем, найдя нужную цель, например создать маркпойнт с TGP как источник координат (создается как стирпойнты с 26 по 30, на которые можно потом переключиться).

Thank you for reply. Yeah there's a designation on the SA page of the Hornet (and iirc DCS Viper had the same feature for air-to-air from the very early stages). It would be interesting to know whether it's possible to actually transmit your designation point to your flight members in the Hornet (so it becomes for example one of their markpoints) though.

Sorry if it was asked already: in the Viper it's possible to share your target/steerpoint from TGP/HAS/HAD with the flight members via Link16 by pressing IFF UP button, then it becomes available for them as a steerpoint from 500 and up. I'm curious if something similar exists / is planned for the Hornet? Thanks

Хотел бы еще узнать: у Вайпера есть возможность транслировать свою SPI/Steerpoint членам звена по Link 16 нажатием IFF UP. Насколько я понимаю, у Хорнета дожна быть доступна схожая функциональность, будет ли она реализована? И еще один вопрос, планируется ли реализация процедуры BORESIGHT для Мавериков на Хорнете как у Вайпера?

Хотел бы узнать, насколько далеко в приоритетах добавление возможности отображения MGRS координат на TGP Вайпера? UPD: Мэтт ответил, что в реальной жизни MGRS координаты не отображаются на TGP Вайпера, вопрос снят.

Почему я просил уточнить: действительно, несколько апдейтов назад устойчивость по тангажу при дозаправке ухудшилась и об этом несколько раз писали в англоязычной части форума, однако в крайнем и предыдущем патчах это вроде бы пофиксили (хотя, возможно, по-прежнему WIP): https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.15.26783/ https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.16.27869/ Как по мне, субъективно дозаправляться после крайних двух патчей стало легче, до этого Вайпер был очень чувствителен по тангажу.

Хотел уточнить, это по прежнему наблюдается на крайней OB?

ЕМНИП в ночное время надо выключить/включить внешнее освещение (Exterior Lights Master Switch ON/OFF), чтобы дать сигнал шутеру

Я правильно понимаю, что на видео Maverick автоматически наводится на цель (режим slave) на маршрутную точку (WPDSG) или с помощью какого-либо сенсора (радар, ИЛС итд)? В таком случае, для ручного наведения ГСН сейчас нужно нажать кнопку сброса целеуказания (NWS/Undesignate). Цитата из анлийской версии мануала: Не уверен, что русская версия мануала обновлена, т.к. там по прежнему написано: Также обсуждалось на англоязычной части форума:

I just finished the mission, it's a DCS bug indeed and very annoying. What I did eventually is found coordinates of the Tartus (which is inside of the WALL SOCKET box) on the F10 map (LALT+Y to change format) and updated the WP2 coordinates with it. IIRC had to do that couple of times as after Peter is found, Knight gives reference to another ship from WP2 (which again might have been already incorrectly overwritten by RADAR/ATFLIR at this point).

I just finished the mission, dropped Rockeye in front of the ship (in order to avoid hitting it) in CCIP mode, definitely changed VT (but don't recall was it 1200 or 1500) and Olive reported that ship stopped after cluster munitions exploded over the water ahead of the ship.

Насколько я понимаю, на текущий момент данная компания/команда отложила все эти планы в "долгий ящик", поэтому темы скрыли и откроют если будет какой-то прогресс. Рассматриваются также и другие варианты (но для ED думаю все упирается в весьма ограниченные ресурсы/приоритеты).