franx

Thanks guys. I’ll try this. Great advice.

Daisy chaining in Vaicom Pro/Voice Attack I've had Vaicom Pro for a year but am only now seriously trying to use it. I've read the manual and watched a couple of videos, but I'm still not "getting it." How exactly do I "daisy chain" my existing DCS profiles for Voice Attack with Vaicom Pro? Load them both at the same time and map the TX 6 radio button to communicate with VA? Maybe I'm misreading the manual or being too literal-minded, but the manual seems to say or imply that Vaicom Pro is the only profile I need since it automatically reads and adapts to all DCS modules. Is that even possible? Each module has different keyboard commands, etc. Sorry if this is a dumb question, but I'm baffled at the moment.

Yes, both running in admin. what is the file structure change? How do I address that?

Any other suggestions? Still no joy. Really weird.

I used VoiceAttack with TrackIR for a long time, and had no problems. But when I use it with my Oculus Rift, no joy. VoiceAttack is using my computer's microphone, and I've set VA to the same or higher task priority as DCS with Lasso. But I keep getting an "unable to perform command" response in my VA program record. Any counsel would be much appreciated.

I’ve flown free flight with the Oculus controllers. It’s doable but awkward and very limited in what can be controlled.

Thanks fellas. So a real world throttle and stick are still needed. Used with muscle memory?

Guys, I've been away from DCS for a year, and am now returning with an Oculus Rift. VR for the first time. I've tested it in free flight, and wow. But now some basic questions going forward. I'm assuming that my foot pedals are necessary for braking, yaw, etc, and that in-cabin throttle and stick eliminate the need for those pieces of hardware, but do most of you use Voice Attack or similar for guns, bombs, and the rest of the commands?

I don't seem to be getting an export.lua in my Saved Games\DCS World\Scripts folder when I reset monitors and save. Weird.

No just vanilla DCS. Standalone not Steam.

Thanks B. Yes, I've watched your video several times. I've worked on this for about an hour this morning and still no comms between the interface and DCS. The Capt Zeen export does nothing to help. Maybe I'm messing up your mods folder. In your profile, where are you putting the mods folder that you include in your profile? I'm also assuming that your inclusion of the iris installer is only for use with a second computer; I'm using only one computer with two monitors.

Thanks for monitor work, BlueFinBima, but it turns out that's not the problem. I've just spent another few hours on this. The profile simply isn't communicating with DCS, and I can't figure out why. I've watched the Capt Zeen video tutorial at least six times now; it's not really as clear as it seems. I just can't figure out where to place your mods file, how to integrate OVSGME, or what I'm doing wrong. At this point I'm just mentally exhausted.

Much obliged BlueFinBima. I will try this tonight when I’m back from work. Will let you know.

1680x1050. sorry.

Thanks for the reply. My left (main) monitor is 3840x2160; my right (secondary) monitor is 1650x1080. Both are set at 150 percent magnification, which is recommended for the main monitor. Both are Samsungs -- 27 inch and 22 inch respectively, I think.

I've spent the last two weeks watching Helios tutorials and reading as much as I can on Helios and interactive DCS panel setups. So I've tried to figure this out myself, but I need some experienced counsel. I've downloaded and installed Helios 1.4 to use with my DCS modules, specifically the AV-8B. I've downloaded BlueFinBima's Helios profile setup for the Harrier, installed it to Helios, and reset his single monitor layout to my two-monitor layout. I then successfully edited his monitor .lua file to serve my second monitor. The profile shows up fine, and I copied the profile's new export.lua file to my Saved Games/Scripts folder. But the Helios profile is still not communicating with DCS, So the panel images are all there on my second monitor, but none of the controls works. What am I missing? This is driving me nuts. Thanks for any help!

Ok, made some progress; still need some counsel Per my post above, I successfully edited BlueFinBima's monitor .lua, but I'm still not getting communication between the game and Helios. What am I not doing or doing wrong. See attached. AV-8B FX.lua

Grateful for any help with BlueFinBima profile I've been struggling to get BlueFinBima's excellent AV-8B Helios profile to work on my set up for the past week. Any counsel would be appreciated. Here's my arrangement: I'm using two Samsung monitors side by side; my main monitor on the left is a 27 inch at 3840x2160 resolution; on the right is a 22 inch at 1680x1050. So my combined resolution is 5520x2160. I'm running both monitors at 150 percent text magnification, which is recommended by Windows for the main monitor. The two monitors are properly aligned in my Windows monitors set up. So far, so good. In the Helios editor, I reset the monitors so that BlueFinBima's profile comes up and is saved on my second (righthand) monitor. I copy the export.lua to my Saved Games folder. I run Helios and BlueFinBima's profile comes up perfectly on my second monitor. So then I start DCS, and two problems are immediate: My cockpit extends across both monitors instead of just my main; and nothing comes up in the AV-8B panel windows on the second, righthand monitor except my extended cockpit in the background. I'm not competent in .lua editing and can't figure out what in the AV-8B config program to adjust: _ = function(p) return p; end; name = _('AV-8B Config'); Description = 'AV-8B MFCD, ODU, UFC etc. GUI Config' -- x = displays[1].width + displays[2].width + 0; if displays and #displays >2 then primary = { x = displays[1].x - screen.x; y = displays[1].y - screen.y; width = displays[1].width; height = displays[1].height; aspect = displays[1].width/displays[1].height; viewDx = 0; viewDy = 0; } GUI= { x = displays[2].x - screen.x; y = displays[2].y - screen.y; width = displays[2].width; height = displays[2].height; aspect = displays[2].width/displays[2].height; } UIMainView = primary xo = displays[2].width; -- xo = 0; LEFT_MFCD = { x = displays[1].width + xo + 0; y = 0; width = 334; height = 312; } RIGHT_MFCD = { x = displays[1].width + xo + 340; y = 0; width = 334; height = 312; } UFC_base = { x = displays[1].width + xo + 0; y = 320; width = 453; height = 385; } ODU_base = { x = displays[1].width + xo + 680; y = 0; width = 283; height = 140; } UVHF_base = { x = displays[1].width + xo + 460; y = 320; width = 210; height = 210; } Viewports = {primary} else primary = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } UIMainView = primary Viewports = {primary} end Any ideas?

OK, that did it. THANK YOU A MILLION hsb and Mapi. Now I just bneed to integrate my post screwup knowledge with my Helios profile. ;(

Second monitor was in the middle. Should I reset to up or down?

Yes my monitors are side by side and my resolution calculation has been done correctly. Main monitor on the left, smaller monitor to the right.

Thanks hsb. Yes I can see my set up option in the game. The main monitor looks good but the second monitor is just black.

OK, this still isn't working, and I can't figure out what's wrong. Any ideas?? See attached revised .lua file. 2Cameras.lua

Thanks guys. I’m using Notepad ++ and trying to copy and adapt from other monitor setups but having trouble with the precision programming. This should help.

Guys, please see the attached lua file. Can someone tell me what I'm doing wrong? I have a two monitor set up: center 3840x2160 and another on the right, 1680x1050 2Cameras.lua