Search the Community

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.

Next product from Total Controls has been revealed: The Total Controls Eject Handle! It will fit every module with an ejection seat in DCS and BMS. It is plug and play and will give three pulses in one pull. Base will be slightly larger on production unit. It will be 40x130 mm. Designed to fit an aluminum T-profile 80x40 mm. Base height 85 mm. Total height about 300 mm. Handle is adjustable. Preorders will go live soon.

I am having some trouble setting up my interceptor pedals with DCS, and I am wondering if I am doing something wrong. Here is my setup: VPC button panel VPC CM3 base w/ Warthog stick VPC CM3 throttle Wingwing PTO2 Winwing MIP (VR) VPC Interceptor pedals Everything is working fine in DCS, except for the rudder pedals. For some reason it is not showing up in the upper columns in the controls binding menu. All devices have been calibrated. Weirdly the pedals are showing up in the VPC software, I see all the axis inputs are correct, but not showing up in DCS. I have a lot of devices (not including keyboard and mice), is it possible I reached a devices limit in DCS??? I don't think my issue is hardware caused because I can see the rudder pedals working properly in the VPC software. Any other idea? Thanks

DISCLAIMER: My wife built my computer (laugh it up, chuckles) and I am computer illiterate, so any delays in my responses are because my dumb ass will need to parse everything through her. From what I can tell I may need more RAM (?), but I would like to pick your brains before investing into a solution that may be a dead end. The problem: Horrible FPS drops and stuttering on large/populated single player missions. Down to like ~7 FPS at times. Otherwise she runs OK. I badly want to buy a the Channel map, but am worried it would be a waste if I can't get Normandy to even run smooth. Attempts (futile) at resolution: - Played with all in game settings (water, heat blur, MSAA, SSAA, Shadows, SSLR, Lens Effects, Clutter, Trees, etc...). The only things I refuse to do are screw with textures and the overall "prettiness" of the game. - played with every setting in my Radeon panel. - tried every trick in the book that google, and this forum, suggested (override application settings, played with MSAA, messed with anisotropic filtering, messed with Vsync, etc...) Compy stats: CPU: AMD Ryzen 5 3600X 6-core Motherboard: B450 Gaming Plus Max (MS-7B86) Ram: 16 GB SSD GPU: AMD Radeon RX 5700 XT OS: Windows 10 Thanks for any and all input. It is very appreciated. I can (probly) afford to resolve the issue because apparently my computer is decent, but I can't afford to blow money needlessly.

Hi, I'm not active here, but I took a lot of info from your posts, in order to do this small project so I'd like to share the result. Essentially what I started out to do is turn a CH Pro Throttle game port version into a USB throttle. The Ch Pro Throttle comes with one low-ohm poti for the throttle axis. Four dedicated buttons and four digital four-way hats make for 20 buttons, which are wired into a button matrix. In a first step I took an arduino sparkfun pro micro and the MMjoy firmware. I wired up the button matrix, liberally reusing the available cables and connectors. The poti also needed some rewiring, as the gameport joystick "protocol" is just wired to read resistance of an analogue axis poti, while the arduino already expects a voltage divider setup. Now since I really enjoy the AV8B I decided to add more potis to the throttle grip. And, to my demise, I found @rel4y's excellent Playstation thumbstick mod 3D printed parts, which replace the index finger 4-way hat with 2 analogue axes and a push button; which is really nice for the TDC slew and TDC down/action part of a HOTAS. You already see that I was quickly running out of arduino inputs. Therefore I decided to use an MCP-3208 ADC to digitize all 5 analogue axes. This required me to put a static resistor into the voltage divider of the slider axis, to reduce the charge going into the ADC at each sampling interval. I know my mechanical skills are crude, please bear with me. After some hours of soldering and grinding I now have this nice USB throttle, and still 3 analogue axes and 3 buttons not used in hardware. Also when I'm grown up I maybe use some shift registers to put even more buttons.

Hello kind pilots, here is my probelm... So I will write down all of my components right here: CPU ---> Intel Core I7 8700K 3.70 GHz (https://www.amazon.com/Intel-i7-8700K-Desktop-Processor-Unlocked/dp/B07598VZR8/ref=sr_1_4?dchild=1&hvadid=77790517240465&hvbmt=bb&hvdev=c&hvqmt=b&keywords=core+i7+9700k&qid=1623684884&sr=8-4) GPU ---> GeForce GTX 1080 GAMING X 8G (https://www.msi.com/Graphics-Card/support/GeForce-GTX-1080-GAMING-X-8G.html) RAM---> HyperX Fury 16GB (2 x 8GB) DDR4 2133MHz DRAM (https://www.newegg.com/hyperx-16gb-288-pin-ddr4-sdram/p/N82E16820104674?Description=16gb ram hyperx&cm_re=16gb_ram hyperx-_-20-104-674-_-Product) Motherboard ---> MSI Z370 A PRO (https://www.msi.com/Motherboard/Z370-A-PRO) Tell me if you want the rest of it but I think it's what you have to know. So here is my problem, I began to play dcs some time ago and didn't really have problems with anything, it was all running great at high settings but as the updates went to come I incountered this issue... I am lagging a lot and what I mean by lagging is a frozen screen for multiple secconds, sometimes long enough to make me crash my plane while I can't do anything... It is very annoying and happens mainly when I'm close to other players. So I don't know if it's a computer hardware problem. I lowered my settings, but it still lags, and the game runs just fine in solo with even higher settings. Is it maybe my RAM ? I have 16go and I saw that the recommended config was with 16go ram (they are maybe talking about playing in solo, right ?). When I checked the benchmarks while playing I didn't get much higher than 14go so I don't know... If the RAM wasn't the problem then I thought: maybe my connection is. I did mulltiple speedtests and always got similar results which are 45 Mbps in download and 20Mbps in upload. Are these numbers too low(maybe the upload in particular). I don't know what I can do more, maybe I should reinstall DCS ? I also checked if it was running in all of the logical processors but it already was, so no problem there... I'll try to lower my settings even more than what it is now but I find it weird that with this config it has that much of a problem running it in multiplayer but again maybe it's not my config, (it runs perfectly in solo with heavy missions)... Thank you for hellping me out...

Hello all, My brother've been having some serious issues with DCS for a long time time now, and I just had the idea to share it with you too, maybe someone can help. The issue is very simple, and a lot of people with cheaper PC's suffer with it. It's the high RAM usage. We tested this for a few months now, and this is what he's been experiencing: His game crashes after 10-15 minutes of playing on Caucasus map in multiplayer because he used all of his RAM. At this stage usually his whole PC shuts down, in a better case only DCS, maybe Discord too. I experimented with his settings to lower it to the most minimum settings that I can, but this didn't seem to extend his playtime. I also told him the obvious to close any programs running in the background that are not necessary, this only had a very minor impact of things. Here is his PC specs: ASUS Prime H310 M-E 2.0 Intel(R) i5-9600K 16GB DDR4 RAM running at 2400MHz RTX 3050 OC I know that 16GB's of RAM is not enough for DCS to comfortably run, but the strange thing is that I had the almost EXACT SAME PC config as he, but with a 6 gig GTX 1060 and never crashed the game because of not enough RAM. Here are his settings he's having now: I'm open to any ideas, and thank you all in advance.

Ma cazzo avevo scritto un poema per descrive il tutto (perdendo un sacco di tempo) e alla fine mi publica solo le foto?!?!?! Vabbe ora non ho certo tempo per riscrivere tutto!!!!! E adesso manco più le foto.... UPDATE... ci riprovo.... Allora mi è finalmente arrivato il collettivo in oggetto... Alla dogana hanno aperto tutto (forse pensavano che contrabbandavo tecnologia militare cinese....) Il montaggio è stata abbastanza facile, soprattutto perché avevo visto un video molto ben fatto su YouTube. Ho scelto il modello desktop perchè si adatta perfettamente alla mia situazione... ARGHHHH NOOOO E’ MALEDETTO STO POST…. Avevo riscritto quasi tutto e per sbaglio per spostarmi su un altra pagina ho fatto lo swipe indietro perdendo NUOVAMENTE TUTTO!!!!!!!!!!!!!!! A sto punto BASTA…. (Poi tanto forse delle mie impressioni su sto collettivo vi frega il giusto……)

Hi friends! I want to know if is there any place to share projects to build in home? I am starting this topic with the intention to share my projet in the future and colaborate with community's projects. I am doing this display with arduino leonardo and a 9,7 hdmi display. The bezel will be backlighted too, so it start from a white material, receive paint and translucent label. I am also working in a force feedback control with 775 dc motors, arduino and optical encoder. you can see a planetary to colect three motors torque in the image above The flight control project will contemplate, ailerons and elevators controls, also rudder.

Servus, Mein Warthog Throttle von TM funktioniert plötzlich nicht mehr. Also keine Reaktion beim einstecken seitens PC oder throttle. - alle USB Ports ausprobiert - am Kabel rumgewackelt - Aufgeschraubt (innen sieht alles gut aus - soweit ich das beurteilen kann) Hat jemand schonmal sowas gehabt? Evtl ein Wackelkontakt? Hat jemand Erfahrung mit dem Support von TM? grüße

This is for fellow simmer pilots who are seeking something more serious than regular gaming chairs and racing seats. Hopefully also for DIY enthusiasts who find the NACES too time-consuming to work out. Despite the broad selection of DIY materials and tools, the construct of this seat presents quite a challenge to work on by hand. Unlike the ACES II which is mostly sheet metal. The Martin Baker NACES is a combination of both solid chunks and thin pieces of metal, plastic and organic materials, each requiring its best suited means of fabrication. Take the seat bucket side wall above, a piece of thick aluminum plate needs to be milled down before it's bent to the right angles on a multi-ton bending machine. Screw holes are then tapped and had right lengths of steel thread inserts planted within. Cloth had to be selected with the right texture and color which closely match that of the real seat cushions. Sourcing straps of the right texture is another difficult task. Once the fabrics and filling foam are ready, it takes industrial grade cutting, forming and sewing equipment to piece them together. Snap buttons have to be riveted in place before the back cushions can be filled and closed up. Spring loaded harness retractors are customized with the designated model of straps. Velcros need to be sewn onto certain sections of straps so they can be secured or detached from the headrest, which by itself, is a dense foam that requires a special process to manufacture. Sheet metal is used throughout the seat. Large sheets of aluminum are laser cut, riveted with clinch nuts or threaded studs and bent into 3D shapes as designed. The different metal pieces are then joined together with various types of rivets, forming very robust assemblies. Another way of forming sheet metal is stamping. The back pad, seat pan and the top cover of the chute container are stamped out of steel sheets between custom made molds with tons of force from a hydraulic press. The result after thorough powder coating in matte black. Rubber has proven to be another difficult material to work with in a home DIY setting. Getting the helical color patterns to match the crisscross texture isn't good enough, the colors have to stick and endure sustained use of the ejection handle. Besides individual parts and stiff assemblies, the seat also depends on a collection of moving mechanisms to function. In a real jet, the pilot needs to adjust his sitting position in order to get the correct line of sight. This is achieved through the seat bucket actuator. A 2000N electric cylinder is incorporated in the main structure just for this purpose. The cylinder runs on 24V DC power, preferably with a 5Amp max capacity. The power supply is sourced separately, while a section of power cable is supplied with the seat. It comes with a pair of circular plugs which mate with the receptacles behind the seat. Height adjustment is commanded through the flip of a toggle switch mounted on the left of the seat bucket. The retractors for shoulder straps are spring loaded and can actually pull back on the straps. They are not actively actuated by default though. Kinematic models are used to verify the movement of each mechanism before finalizing the design of linkages and handles. The resistance of the shoulder harness control handle is adjustable through a screw cap on the top. All the handles are operable and internally linked to optional electronics. You can even actuate the sears and have the spring loaded plungers pull out. Check the following video for how they work: When it comes to the ejection handle, I feel your pain in making the repetitive Ctrl+E work with DIY electronics. Sometimes a few extra line of code is enough to hinder the progress by days for the lack of required experience. As much as we love Arduino, we prefer to build every PCB in our products on our own. That means we design all the PCB's for ourselves, and write all the firmware for ourselves. PCB assemblies are then made by professional plants to ensure proper quality. The switch box on the left side distributes 24V power directly through output cables. Some analog electronic tricks are used on the PCB to tap into that same 24V output without frying up chips, while allowing the firmware to determine whether and which way each of the toggles are flipped. Writing firmware from scratch allows us to make the seat show up on the computer as anything we want. In this case, it appears as a generic game controller with a number of buttons. The following video demonstrates how these buttons can be configured in DCS World: If you find it pointless to assign exactly the same virtual handle functions in game to the physical handles on the seat, you're welcome to get creative and find other uses for them, at the end of the day, they are only generic buttons. Bear in mind the ejection handle is the special one, it is hardwired to trigger three quick and consecutive button strokes to activate the ejection process in game. All possible scenarios such as pulling or pushing a handle from its resting state, or quickly switching it on and off are anticipated while coding the firmware. Noise from snapping mechanical contacts is also properly debounced to eliminate runaway issues in all branches of program execution. This seat is now on sale for $2,890 at our official site: https://www.neoengress.com/naces-ejection-seat . There're a bunch of other cool stuff on other pages to indulge your curiosity if it's new to you. The USB interface, switches and signal cabling requires an additional $360. If anyone is interested in this product, please feel free to write to us at info@neoengress.com for more information, because currently it's the only way to place orders.

I hope you like watching the Su-25T go on a tiny mission... Can I land it? Any questions, please ask. This was a really interesting project. It's just for fun and to see if it would be possible

I bought a Leap Motion hand tracking device, and tried it out in DCS VR. The experience was not very great. Even though the tracking works fine in the Leap Motion App, my hands are all kinds of crooked in VR. My Fingers do weird stuff in DCS, even though they show up correctly in Leap Motion. And even worse is the pointing in DCS. The cursor doesn't go where your finger points, it is very awkwardly positioned, I had to twist my hand way left, and way down, so the cursor went somewhat in the right position. It seems to point from the middle of your hand, not the finger, which is very annoying. And it wiggles around so much, it is almost impossible to hit buttons precisely. Additionally, my hands disappear regularly in VR, without moving them. I have to move around my hands to get them to be tracked again. All of these Problems are non-existent in the Leap Motion Control Panel I also tried the "Fingers" app, that is supposed to emulate a mouse cursor by pointing your finger, but it also tracks your whole hand, not your finger, so I have to move my hand around in a very awkward manner to point where I want. I tried different tracking modes in leap motion, desktop, screen mounted and headset mounted, but nothing seems to improve the tracking. I am very disappointed with the implementation of Leap Motion in DCS. The Leap Motion Tracking itself is very good, but in DCS it is very very bad. Which is a shame, since finger pointing in DCS would be VERY beneficial for VR.

I am wondering that an environment is running two GPUs, and would DCS have any benefit with both GPUs? Thanks.

RealSimulator Hardware Introducing the new FSSB-R3L MKII “ULTRA”. This force-sensing flight control system allows you to connect any of the Realsimulator or Thrustmaster grips, and it represents the same displacement and feeling of a real F-16 flight stick. It delivers the same amazing precision and smoothness, found in a real Viper. Based on its professional force sensor technology, it is in use with prestigious organizations like the US Navy test pilot school, Australian Royal Air Force test pilot school, French test pilot school, and others. Since the launch in 2006 of the R1 and R2 bases, which were the first force sensor bases available for the simulation game market, the development and manufacturing of these high-grade force flight controllers has evolved over the past 16 years. This new Realsimulator device has been tested by a beta group of real test pilots and simulation enthusiasts to tune the feel of the new FSSB R3 MKII “ULTRA”. They have confirmed that the new sensor base is smoother and more precise. We encourage you to check it out for yourselves on the Realsimulator website https://realsimulator.com Bye Phant

I have done several performance tests of my newest hardware and compared them with each other. I have used DCS World 2.8.3.38090 Open Beta with Single Thread ST and Multiple Threads MT with an Instant Mission: AH-64D, map "Marianas" - Battle for Saipan: Dawn Invasion" After starting the mission, I have pressed OK, then [Right-STRG + Break/Pause] for two times (for displaying the frame rate) and then I have pressed the space bar. Directly after that I have checked the frame rate. I know that my graphic settings are very hard.....: null All CPUs as well as GPUs are slightly overclocked, except the CPU Intel I5-13500. Here are the results, including the fps / framerates in DCS World with ST and MT: Here as a table: 4K performance comparison between four of my computers Type Description CPU GPU RAM DCS World Battle for Saipan – Dawn Invasion Time Spy Time Spy Extreme Port Royal ST MT Total Graphics Score CPU Score PC Self build Intel i7-12700KF (12 Cores, 25MB Cache) RTX 4090 24GB GDDR6X 64 DDR5-6000 84 98 („GPU-Bound“) 31977 37570 17394 16227 27128 PC Self build Intel i5-13500 (14 Cores, 24 MB Cache) RTX 3080 LHR 10GB GDDR6 32 DDR5-4800 48 58 („GPU-Bound“) 17325 17624 15810 8406 11529 PC Self build Intel i7-2600k @ 4.5 Ghz (4 Cores, 8MB Cache) RTX 2080 Ti 11GB GDDR6 16 DDR3-1600 21 38 (fast changes between „CPU-“ and „GPU-bound“) 9996 14096 3775 4506 8941 Notebook Alienware 17 R5 Intel i7-8750H (6 Cores, 8MB Cache, up to 3.9GHz with Turbo Boost) GTX 1070 OC 8GB GDDR5 32 DDR4-2666 6 7 („GPU-Bound“) 4404 4459 4118 1815 1030

Hi, I'd like to try DCS in VR but I had some feedback from friends telling me that some headsets that don't have a very good pixel density make it difficult to read what's on the MFDs etc. Is it the case with the Reverb G2 ? (I'm thinking of getting this one) Also, still about the Reverb G2, does it give you the horse blinders effect or is the fov wide enough ? And finally, using a G2 with a 3080Ti, flying above Syria with all settings cranked up to the max, not CPU bottlenecked or out of RAM so the GPU can use its full power, how many fps can I realistically expect in average? Finally, what's the compatibility of it and DCS ? Is it quite plug and play or does it need another software to fine tune a ton of settings (like a TrackIR) ? Thanks!

I'm in the process of expanding the drive and need to replace the 1TB SSD with a 4TB. Will the certificates of my modules be affected? What do I have to do beforehand? Many Thanks in Advance

Hello, after my glorious throttle mod I also came across a quite dirty but cheap CH Combat Stick game port version... So I made a plan to turn it into USB using once more the MMJoy arduino path. I took an arduino sparkfun pro micro and the MMjoy firmware, another MCP-3208 ADC for the stick axes and wired up everything in the base. While in the CH Pro Throttle game port version the poti had idk like 100 Ohms or something and needed an additional resistor before the MCP-3208 input to keep it from freaking out, the Combat Stick came with high resistance potis (100k?) and that way was ready out of the box for the modding. Meanwhile I also took apart the grip, and threw all the plastic pieces into the dishwasher (ymmv) to remove ten years of somebody else's palm sweat and grease residue (eew). I think that's the early version of a Combat Stick as the gimbal springs are tiny. In the original setup, the 14 or so grip buttons are all wired down into the base individually; I decided to use an array of shift registers in the grip to reduce the length of the wiring significantly. So after all this, a mere 5 wires (VCC, GND, DATA, CS and CLK) were left, plus one empty I was too lazy to pull out of the cable assembly. Note I marked which colour means what on the base before closing it, and of course not without testing everything with the help of some cheap breakout 74HC165 shift registers and a breadboard. Also note the mega unprofessional use of red/black wire for ground and white/black for VCC For the grip, the Combat Stick I had came with two hats and two buttons at the top thumb area (trim, sensor select, pickle and perhaps sensor select down for the AV8BNA), and a single button on the thumbrest halfway down the stick. On the box, there is a version pictured that has one of the hat switches in that position, and the button moved up to the main area. Now I still had a spare hat switch from my CH Pro Throttle, the index finger one to be precise, which I had replaced with an analogue stick mod by the mighty @rel4y. I decided that this needs to go into the thumbrest, increasing the actual number of buttons on the stick to 17. It required some grinding to fit into the button well, as the Throttle variant came with a square PCB while the CH Fighterstick variant that fits the same spot does not have a PCB but directly connects the microswitches. The rest is exactly fitting, including the little notch that prevents the hat switch from turning in its round socket. I tried fitting 3 x 74HC165 shift register breakout boards in, plus the necessary pullup resistor networks - which had to be SIL because my SMD soldering capability is not existing. Of course I failed miserably, but I came across a very nice 3 x 4021 shift register SMD setup on ebay classifieds. And, shame on me, until I read his name on the PCB when it arrived yesterday, I had failed to realize that the guy selling it was in fact our very own @rel4y. Hi mate, thank you for doing this! From then on everything was really just plug-and-play, also switching from 74HC165 to 4021 shift registers was as easy as 1 2 3. Cramming all that into the stick handle was still a nightmare, but at that point I could also no longer be asked to reduce the truly excessive wire lengths. To make everything fit, also around all the different studs and screw wells, I had to bend one of the pin header arrangements on the shift registers to 90 degrees inwards, but then *** ta-daaaa *** everything closed nicely, snapped into place and works like a charm. The only thing now is, I am missing a rudder axis dearly, especially for the half-helicopter AV8BNA. Perhaps that's my next mod? Who knows

While moving either of the dual throttles the other throttle moves a little when the throttle pass the other and a clicking sound occurs. Would've shown better with a non-handheld steady camera. Looks, sounds worse in reality than on video. Does anybody else's throttle act and sound like this? It's disturbing because I think it is new. I fear maybe the friction mechanism starts to break down. Throttle is 4 months old.

Hello, I'd like to share a project I'm working on that is fully detailed on Github. Compact input controller with 19 switches and 4 rotary encoders. Functions as a joystick in DCS, so it's easy to map controls. Supports DCS-BIOS for more advanced control mapping. Overall, it provides up to 120 control inputs via a 3-way mode switch. I find it to be a great addition in VR. After developing some muscle memory, it feels relatively natural to locate controls for startup, navigation and weapons. The project includes 3D models, schematics and arduino source code. If you'd like to help with the development of this, such as adding DCS-BIOS scripted controls or some other idea for VR input, I'd love to hear from you.

would an rtx 2070 super be suitable for dcs vr and if not are there any better ones at an affordable price? (sub 600 euro) thanks!

Hello DCS community... May I please request some assistance from anyone who has an idea about VR - 'Blue Screen of Death issues'...? Any ideas or help would be greatly appreciated. In short, I'm trying to troubleshoot the reason why using my Reverb G2 causes the dreaded 'Blue Screen of Death' 99% of the time I use it with DCS (and I think any other title). It can be 3 minutes after commencing a flight / mission, or 20 minutes - the timing is random. *** Further to that, I can be playing using the monitor (2D), and if the Reverb is simply plugged in (Display Port, USB 3 & Power Adapter) even without WMR & Steam VR running, then DCS will still BSOD at any random time after starting to play *** SYMPTOM: - Blue Screen of Death with varying error messages, causing a reboot of the PC - Timing can be at any stage of gameplay (2 minutes or 30 minutes) - I can play DCS all day long using the Monitor, but if the Reverb is plugged in & idle in the background (even without WMR or Steam VR running) I'll still get the BSOD after a random amount of time BASIC SYSTEM SPECS: - i7 8700k - water cooled - 32G 3600Mhz DDR4 RAM - ASUS Strix ROG 370-G Motherboard - Gigabyte RTX 3090 OC Edition GPU - Corsair RM-1000W PSU - Windows 10 - 20H2 TROUBLESHOOTING SO FAR: - Updates Updates Updates! Windows 10, BIOS, latest Nvidia drivers (clean install after using DDU in Safe Mode) - Re-Rack of GPU - Thorough check of all PSU wiring & plugs (GPU is using two seperate PSU Cables / Sockets) - 100% Stress / Thermal testing (using both AIDA64 and Superposition) GPU & CPU temps are quite good with no issues. - Plugging the Reverb USB into different USB 3 ports - Plugging the DP Cable into different GPU DP ports - Device Manager - USB Power Management Tab, preventing any / all of them from 'saving power / powering down' *** Am I missing something basic? May I please put it out there to anyone that is more 'Hardware Tech Savvy' or has seen this before? Any ideas or help would be greatly appreciated *** Cheers...

Hello DCS community... May I please request some assistance from anyone who has an idea about VR - 'Blue Screen of Death issues'...? Any ideas or help would be greatly appreciated. In short, I'm trying to troubleshoot the reason why using my Reverb G2 causes the dreaded 'Blue Screen of Death' 99% of the time I use it with DCS (and I think any other title). It can be 3 minutes after commencing a flight / mission, or 20 minutes - the timing is random. *** Further to that, I can be playing using the monitor (2D), and if the Reverb is simply plugged in (Display Port, USB 3 & Power Adapter) even without WMR & Steam VR running, then DCS will still BSOD at any random time after starting to play *** SYMPTOM: - Blue Screen of Death with varying error messages, causing a reboot of the PC - Timing can be at any stage of gameplay (2 minutes or 30 minutes) - I can play DCS all day long using the Monitor, but if the Reverb is plugged in & idle in the background (even without WMR or Steam VR running) I'll still get the BSOD after a random amount of time BASIC SYSTEM SPECS: - i7 8700k - water cooled - 32MB 3600Mhz DDR4 RAM - ASUS Strix ROG 370-G Motherboard - Gigabyte RTX 3090 OC Edition GPU - Corsair RM-1000W PSU - Windows 10 - 20H2 TROUBLESHOOTING SO FAR: - Updates Updates Updates! Windows 10, BIOS, latest Nvidia drivers (clean install after using DDU in Safe Mode) - Re-Rack of GPU - Thorough check of all PSU wiring & plugs (GPU is using two seperate PSU Cables / Sockets) - 100% Stress / Thermal testing (using both AIDA64 and Superposition) GPU & CPU temps are quite good with no issues. - Plugging the Reverb USB into different USB 3 ports - Plugging the DP Cable into different GPU DP ports - Device Manager - USB Power Management Tab, preventing any / all of them from 'saving power / powering down' *** Am I missing something basic? May I please put it out there to anyone that is more 'Hardware Tech Savvy' or has seen this before? Any ideas or help would be greatly appreciated *** Cheers...