azl

I use Voicemeeter to route audio to multiple outputs: Oculus Rift and an onboard Realtek analog connected to a subwoofer. The latest 2.5.1 beta ignores my default output selection. In fact, it appears it binds to the Realtek audio device (all DCS audio is played exclusively through my subwoofer and nothing else). Based on the feedback in another thread, I suspect DCS is attempting to bind to the Rift audio output and fails because it is in use by Voicemeeter, failing over to another non-default audio output (Realtek). Is there a way to force DCS 2.5.1 to use the default audio device? All other applications output audio as expected, and all prior versions of DCS did as well.

Looks like it does work in CV1, however the placement and text size make the pages difficult to read (useless). Perhaps moving the board and enlarging it would help? Video link here

I haven't tested it in my CV1 yet, but I was able to enable the in-cockpit kneeboard in 1.5. Would this still be useful? Basically I integrated aspects of Peter P's code with the somewhat different common scripts files (rather than replacing them outright).

I rarely participate in this board, but wanted to take a minute to thank and congratulate you for saying so many completely accurate things with so few words.

This already exists and is integrated into the Rift developer kit. Initial setup takes you through a series of tests that allow you to establish a profile for your pupil separation, head height, eye/neck distance, etc. This profile is available to any application that has proper Rift support. Unfortunately some apps ignore the profile and cause a lot of unnecessary sickness.

Just to get back on topic: with the new Vizualizer.dll, I think DCS is the #1 Rift/VR flight simulator. Amazing framerates, tracking, and 3D. It is really almost perfect. Hopefully the yaw drift can be minimized further, but it is OK as long as I have a recalibrate buttion on the joystick. I don't have any IPD or border issues (they did exist before the latest Visualizer.dll). For a moment I was so immersed that I felt I could reach out and flip the switches myself. I used to fly DCS with a TrackIR 3-screen setup, and I kept thinking to myself (while in VR) how primitive that was compared to a modern 360° 3D interface. Once the resolution improves to allow reading of the HUD and MCFD's, VR pilots will reach a new level of air superiority. The hardest part now will be for us to learn to fly these complex aircraft without being able to see the keyboard.

Nice competition everybody. I helped Squirrel on some of the shots and it really makes you appreciate the game when you get into the details. I know if I hadn't bought the game yet, seeing some of these videos would have definitely sold me.

Our trouble was TARS did not always update the radio freq being exported by DCS. So if one of us tuned away from a station, the TARS plugin in TS indicated we were still on the old station, thus unmuting anybody on the old station. TARS was still working because we were hearing the modulated audio.. It just thought we were still on an old freq. Love the app by the way :thumbup:

Dire, my crew has had problems w/ TARS too. It's awesome when it works, but sometimes it just doesn't. We had the same issue as you - TARS control panel showing that it was installed, not on standby, but TS3 would show "TARS not running" when in-game. I haven't upgraded to TARS 1.0.1 yet. You can troubleshoot where the problem is coming from by looking at these two files: C:\Program Files\Eagle Dynamics\DCS A-10C\Temp\TARS.log C:\Users\[username]\AppData\Local\TARS\tars-plugin.log If you want to paste those in here, maybe we can figure out where your problem is coming from. In our case, the logs were showing that the game wasn't exporting to TARS, so removing and reinstalling TARS worked. However, even now that it works, we still see some odd behavior with TARS. Sometimes I can be on VHF and my team can hear me on UHF. It also doesn't matter what freq I'm tuned to; we all hear each other.

Just wanted to say thanks for the guide and put in my experiences to help others who are starting out. I have three screens, a 19", 22" wide, and 19". I had to set my left monitor as primary or I would get weird location issues with the center screen. Here are the pertinent parts of my monitors LUA, in case anybody is struggling with a similar configuration: Viewports = { Center = { x = 1280; y = 0; width = 1680; height = 1050; viewDx = 0; viewDy = 0; aspect = 1680 / 1050; } } LEFT_MFCD = { x = 0; y = 0; width = 1280; height = 1024; aspect = 1280 / 1024 } RIGHT_MFCD = { x = 1280 + 1680; y = 0; width = 1280; height = 1024; aspect = 1280 / 1024 }

any chance of you sharing your bitmaps and config, Ghost? I downloaded the free version of keypad pro and it seems like it works well enough, so Im thinking of getting the $4 version but don't really feel like going through all the trouble setting up the layouts :)

Win7 x64 here. I also reinstalled DX9 from June 2010 and the MS Visual C++ 2005 runtimes. I can't seem to get any output. I get the overlay but the image is black. This occurs whether I use "internal" or "stream". Here's what it looks like: Also, if I switch to my DSMS and manually select STA9 (AGM-65), there is no change (still blank). But if I select STA3 (AGM-65), the game crashes immediately. Problem signature: Problem Event Name: APPCRASH Application Name: dcs.exe Application Version: 1.0.0.0 Application Timestamp: 4ccaa0f1 Fault Module Name: d3d9.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4c76cedf Exception Code: c0000005 Exception Offset: 000019ff The relevant DebugView lines: [4408] AIESTV: Config path: <C:\Program Files\Eagle Dynamics\DCS A-10C Beta\AIESTV\AIESTV.cfg> [4408] AIESTV: Got RTT (512x512) Plenty of TERRAIN errors, but nothing else from AIESTV.