nephilimborn

Very good point SharpeXB, it is what looked into first. No warning lights on the MB nor the GPU (sense pins), also have been very careful do adjust the Asus anti-card-sag strut to mitigate any PCIE slot contact issues. A fried power connection sound like nightgmare to deal with! I have inspected the power connector at the card and at the PSU, luckily i have not had this occur however it seems to be constantly reported on NorthridgeFix youtube channel. HI BitMaster, i had no idea DCS could be run with the Proton overlay! Does Nvidea release reliable Linux driver updates?

Hi kksnowbear, Rig is a custom build from a pretty reputable vendor here is Melbourne Australia (scorptec - have had dealings with them for many years). Apologies, i should have provided the additional details Deepcool LT720 Premium Liquid CPU Cooler, 360mm Radiator G.Skill Ripjaws V 32GB (2x16GB) PC4-28800 (3600MHz) DDR4 Gigabyte Z690 AORUS ELITE AX DDR4 MB When i was getting WHEA errors early on, i brought the system back to their support dept and they ran a number of stress tests over a few days - identifying a possible bad GPU (which they RMA'd on my behalf) and defective RAM (what is with quality control and consumer parts these days?!?!?). PSU tested fine at that time (GPU is connected via the 12VHPWR cable as supplied by the MSI PSU). I agree with you, also do not immediately think this is a GPU fault. I also do not think this is a 12VHPWR cable issue (sense wire LEDs on the GPU do not indicate a delivery power issue), and i am certain the strut is correctly placed and preventing slot contact issues. The MotherBoard status lights are normal when this occurs as well. No Corsair software either, seems that software was causing similar issues for people awhile back. I use (and trust) Remi Mercier's FanControl (github) for all heat mgt and avoid any control software from gigabyte, asus, corsair, etc. Although i do launch (and subsequently terminate) Asus GPU Tweak III to disable fan control and set the GPU power level to 95%. I had HWINFO logging all voltages and temps to SSD for inspection after crash, also set set process priority for HWINFO & FanControl (using Process Lasso Pro) to above normal. I previously ran GPU + CPU stress testing using 3DMark (paid version) and others (OCCT, Cinebench, etc), however i could never trigger the black screen of death. It is really weird and almost at times seems at times to trigger at GPU load transition (e.g. High to Low; e.g. after a few seconds in DCS cockpit -to- mission briefing); however, crashing also occurs that is in no way related to what seems to be a load transition scenario. You have motivated and encouraged me to get off my lazy ass properly test this with another GPU - i have a RTX 3080 in another older system that i could swap into my DCS rig for a time. I am honestly gratefully for all the time and effort everyone has put into responding to this thread!!! I opened the forum today and was so happy to see so many responses! Going to read+respond to following posts. Thank you kksnowbear!

NOTE: I do not believe this is a DCS defect, however this behaviour commonly occurs when in DCS Problem At least twice a week (at times much more - i play DCS every evening) and within the first 15minutes of a SPlayer VR DCS session the following has been occurring over the last year - Black Screen, Fans 100 percent, hard-reset or power-cycle is the only option to restart (12VHPWR sense pin LED indicates normal signal) History I first encountered this issues last year with a new gaming rig however windows event viewer was reporting WHEA errors - in response i RMA'd the 4090 which turned out to have bad capacitors. About 3 months after installing the new 4090, i again started to encounter the same behaviour with similar frequency and symptoms. Just prior to black screen event, the Windows Event viewer reported the nebulous and useless Event ID 56 ACPI 2. I was able to eliminate this event from being reported by Windows by setting NVCPL to prefer max performance and restart (no fast start) PC prior to any DCS session. Over the last 10months i have tried many settings to resolve or at least minimize (see below). Currently the Windows Event Viewer reports (albeit with a timestamp nowhere near the black screen event) \Device\Video3 UCodeReset TDR occurred on GPID: 100. What i have tried to solve or at least mitigate Variations of this behaviour is littered en mass in forums across the internet (NVidia, Reddit, Overclock.net, etc.); as such and as expected with anything on the internet, the unstructured responses, recommendations, etc wildly vary from moronic, insulting, helpful. There is of course no systemic solution as influencing hardware, software, OS & BIOS configuration varies materially enough that a resolution for one particular person's ecosystem does not work for others. Removed all useless bloatware e.g. gamebars, overlays, RGB crap software, razer trash, armoury crate toiletware, ... NVCleanStall 552.44 driver; Disable Telemetry, disabled NVIDIA HD Audio Device sleep timer, enable Msg Sig Interrupts (default, High Priority) BIOS, Disable PCIe Native Power Management & ASPM, Enable Resizeable BAR, power limits set to Intel spec for 13700K Windows 10: Disabled hardware accelerated GPU scheduling, Disable PCIe link Power Management, TDR delay to 15seconds, no fast start on boot NVCPL: Neg Load Bias Allow, Prefer Max Performance NOTE: Have not tried the more controversial settings such as turning off C-State in BIOS Power Supply: MSI MPG A1000G PCIE5 (12VHPWR) GPU: ASUS TUF RTX 4090 GAMING w/ latest (23-2-22) VGA Bios. I use the anti-sag adjustable support brace (although a stupid design by asus) to help support the card and (hopefully) avoid slot contact issues that might lead to the behaviour i am experiencing. AC Power: I don't use my UPS as it is only 900Watt, instead using a high quality monster power surge protector. Not sure how sensitive the MSI power supply is to voltage variations (while under higher than normal load) in wall power? I do, of course, actively profile and log all relevant sensors via HWINFO and i use the Remi Mercier's FanControl (github) for all heat mgt. Nothing recorded is ever out of temp, voltage, etc bounds for any measured component when the black screen occurs At my wits end with this and truly hoping i don't have to RMA my 4090 again.

Good advice, thank you! This actually did happen to me as i did not wait the 4seconds between Jester ack and when the tanks actually drop.

Hi all, Rookie mistake on my part as i am new to the Jester feature (previous experience is airframes without second-seat/RIO). During the Iranian reactor strike mission (Persian gulf map) i noticed that i was unable to release bombs (CCIP mode) even though the MK-8x ground munition was indicated in the Jester ground attack menu context. Turns out i had jettisoned fuel tanks just before the IP which apparently changes the munition; had to re-select the ground attack munition in order to attack the target reactor...took me a couple runs to realise.

Just started a few days ago with the F-14 module; this was happening to me as well on landing, never considered that i was wrecking the tires on take off but that was what was happening. I added manuever flaps, lower throttle, and more aggressive rotation and during take-off and no more flat tires! Thank you all that contributed to this thread, much appreciated!

This post is for entertainment purposes more so than a visual bug report...this crewman must have been stuck on the runway when i was taking off and got attached to the left wing ... disappeared after a dive bombing run

same here...i have a fair bit of experience tuning the MT DCS VR experience (process lasso, oculus debug tools, etc) and cannot tune my way out of this stutter fest. My rig is a 13th gen intel + 4090...i play a number of airframes + campaigns on the V2.0 map and this is the only campaign with this issue. It is unfortunate as i really like the target rich and active theatre of war. Please note that this is not a complaint levelled at the campaign developer, I never regret campaign purchases as i am grateful for the content and will always support campaign devs, just disappointed.

same here

About 50% through the campaign; absolutely love the radio transmission content, historical attention to detail, and campaign mission implementation. Avoiding any spoilers, i captured (attached screenshot) a rather surprising collision event - nice touch Refected Sims!

I was experiencing the same immersion breaking audio issues with quest 3 over link cable; previously i had mitigated this by increasing the bitrate to 800 and dedicating a processor core to the audiodg.exe (process lasso process cpu-affinity settings). Recently i decided to give up on sending compressed audio to the headset over the link cable and instead use wireless headphones over pc audio by disabling both "Computer Audio in VR" and "VR Audio in Desktop" within the Oculus pc app settings. This did the trick for me and i no longer experience the issue. It is painfully apparent that meta does not give a sh*t about their pcvr customer base and does not invest in fixing systemic issues with the pc link.

Just chiming in to also state how impressed i am by your campaigns (Blue Nosed Bastards, Debden Eagles, Wolfpack) and that the tireless support you provide for your content does not go unnoticed. My warbird flight & combat skills leave A LOT to be desired, and as such mission 1 of Debden eagles was beyond my ability (esp in VR), however your mission encouraged me to treat it as a challenge that would eventually improve my gameplay; which it did as i was eventually able to successfully complete the mission (albeit over a fair period and without a competitive score). Anyway, just wanted to add some good noise to the forums and take the opportunity to express gratitude for both your content and support of that content. Just as you motivated me to pick up the P-51 airframe from my P-47 campaign (Wolfpack) experience, you have also motivated me to pick up the F-14 airframe so that i can experience your content for that airframe. All the best and very much looking forward to more content from ReflectedSims!

No mods nor open composite...agree with you that wired is likely the best option; TBH i am not sure why i am even wasting time with this; my original intent was curiosity with HEVC 10bit compression over 150Mbps however i am certainly not interested in compression artefacts nor any additional load on the 4090.

I am having a similar issue with VDXR; using the shortcut approach is the only way for me to launch MT exe however it never loads (black loading screen). It should not matter to MT as VDXR is simply another OpenXR runtime i guess. Not sure if this exacerbates the issue some people are having with the MT version requiring the use of process lasso (P-cores only and hyper threading disabled)? Only way i can get MT version to work is via the Oculus link cable approach unfortunately.

VDesktop streamer app changes the OpenXR runtime to VDXR. Kill the VD Streamer App then navigate to the Oculus desktop app and change the active OpenXR runtime back to Oculus (see attachment)

I was also having difficulty with avoiding the manpad whilst rolling into a ccip release. Many thanks for the suggestions Badger 633, the 13000feet release tactic worked for me. Had this campaign in my library for awhile and finally got around to playing it. I am about 70% through and having immersive fun, another great job by Badger 633; IMHO not as good as the Persian Lion campaigns but still a well crafted campaign. Nice touch with the airport debris in Mission 4.

The B1-B in Mission 4 is a nice touch! Make sure to call-in & watch the carpet-bombing run on the helo airbase.

Sofar the campaign seems to find a good balance; Incirlik air base (esp with many mission-active airframes) and the Syria map however will always be a drain on perf regardless. My rig is a 4090+13thgen I7, 32gb ram, openXR Quest2(asw off, 120hz forced 60fps 1.7x render resolution, max dcs settings); if i turn off the mirrors i can just get frame times that result in 55 to 60 fps (as long as its not raining that is)

Thank you Looking Glass for publishing this campaign. IMHO this finds a great balance between immersion and insulation from DCS game breaking releases. I am only 3 missions but having a blast playing. I have played through all F/A-18 campaigns (excepting Rising Squall which i cannot stand) and this is sofar the most fun i have had; this easily compares with Rise of the Persion Lion. I look forward to playing the remainder of the missions as well as any future content. Also many thanks for tirelessly responding to the sim-gamer feedback in these forums; i play in VR so the labels make all the difference during AGM.

Many thanks; that is very helpful technical advice! I was able to mitigate this (happens rarely now) by deleting the contents of the metashaders2 and fxo directories

Similar issue here; MT never fully loads; sometimes a brief window of access presents (between hour glass icon) and i am able to select a function such as campaign but after that it is in a constant state of loading. Have to go back ST which tanks perf on intensive loads such as with supercarrier. i don't mind the increased load time; would be happy if it at least worked as it did with the previous openbeta release. Happy to post my dcs log file if that helps any diag. DCS Module: F/18 module, Super Carrier 4090, I7 (13th gen), 32GB Ram, Quest2 (OpenXR)

Experiencing the same issue with Mission 8; Pistol 36 does not show up to waypoint 3

Hi All, Just joined as i am fairly new to DCS (about 3months and only a couple of hundred VR hours of playtime). I am really grateful for all the content (missions, helpful advice) on this forum and thought I would share a controller profile and accompanying kneeboard that has been working well for me in VR. This is specific to the VKB Gladiator flight stick and the Virpal CM3 Throttle. Any feedback is greatly appreciated! Many thanks for the content and very helpful instruction and advice! DCS Layout v1.pptx