GPatricks

I have 3 32" Samsung G5's curved (7680x1440 @144hz GSync) and if I was to do it again I would buy 1 Samsung G9 49". With triples comes some distortion in the outer monitors and of course the bezels are there. To say the bezels bother me would be incorrect, they actually "disappear" while playing but when looking beyond the center monitor there is definitely some distortion... use the 28" for a Helios cockpit extraction or to put a manual up on.. and don't forget a TrackIR! Pic is BMS 4.35 but you get the idea..

Noticed something when I created my "AH-64D - GR" profile. Made it from scratch and copied/pasted the MFDs from a profile already made, I have it working fine and both MFDs are showing with no errors in Helios. Went back to see, with all the DCS updates since I made it, if my F-16 profile still worked. Nope, all kinds of errors. Tried re-creating it from scratch with the "F-16 Simulator Viewports" in Helios. 1. New Profile 2. Added DCS monitor Setup Interface, saved. Profile. Status - "Monitor setup files need to be configured" Hit "Configure" button. 3. Here's where I got confused. In the "DCS Monitor Setup File Output" window it shows the setup is "Combined" with the Monitor Setup for the "H_AH64D-GR" Monitor Setup. This time I hit the "-" in the "Monitor Setup 'H_AH64D-GR' " line and now it (the AH64 Monitor line) appears under a new "Separate" category. Not sure if this was the correct procedure. 4. Once again, "Monitor setup files need to be configured" Hit "Configure" button. No errors. 5. Added "DCS F-16C_50" Interface, Saved again to remove the caution under "Profile Interface" window under Interface Status. All green checkmarks. 5. Tried running it, get 4 "UDP Interface created duplicate function ID. (Interface="DCS F-16C_50". " errors. Go back to profile editor and now DCS Monitor Setup says "viewport 'F_16C_LEFT_MFCD' requires patches to be installed". Repeats same error for Right MFCD. I see no way to "Install Patches", hitting the Gear icon takes me to Monitor Layout and there are no errors there... Am I missing something (obviously I am, but what)? Thank you for taking the time to read this!

@hreich, in the Helios Profile Editor click Profile in the title bar menu, the select "+ Add Interface". A window should show as in the pic...

Ok, new profile, Installed DCS Monitor Interface (did not do that before), Installed AH-64D Interface, copied the two MFD screens from Apache Duel V1.hpf on a second instance of Helios Profile Editor over, saved and it now works great. I have the Gunner's MFDs on my small screens, the Pilots on the main screen for now.. just need to set up the TM MFD bezels.

@hreich, be happy to if/when it ever works but all I did was start a new profile, add the "DCS AH-64D" Interface, open a second window with the "Apache Duel V1" profile and copy/paste the Right/Left MCFD's over and save... and so far and I get nothing on my screen. I'm trying to wrap my head around how this works in DCS as my F-16 profile has "F-16 Simulator Viewports" listed in the Helios Toolbox Column, as are all the Images I need for the "other F-16 sim under the appropriate folders. Keep in mind all I want is two 580x580 MFD screens onto my 8" lilliputs w/TM MFD bezels, possibly at some point have them swap to gunner position MFDs when I go there.. Edit: Ok, I have it working correctly now. The gunners left/right MFD's are being drawn correctly on my screens. What I failed to do initially was start out by installing the DCS Monitor Interface first, then install the AH-64 Interface.. Now to figure out a way to swap to Pilots MFDs on the fly... Attaching my profile just so you can see how simple it can be. Now to start setting up keybindings to the TM Bezels.. AH64D - GR.hpf

Thank you @Scaley, I created a new profile, added @Bunny Clark's Interface, and then copied the Right and Left MDU's from the original profile I made (a cut down version of "Apache Dual V1") to my MFD monitors to start. Saved it and it "looks" like it will work, no errors in Helios Control Center, going to pop into DCS and see what happens. Thank you!

@Bunny Clark, any idea why I am getting the error above with your interface?

Thanks man, stumbled on that thread and working on it now!

I have the same issue, Bunnys Interface (DCS.AH-64D.hif.json) is installed in x:\Program Files\Helios Virtual Cockpit\Helios\Interfaces (with all the other DCS Interfaces). x:\Documents\Helios (as shown in the error messages ) does not contain an "Interfaces" folder. Creating one, dropping in "DCS.AH-64D.hif.json" does nothing. Looking at the error it seems to be looking for DCS.NAH-64D.hif.json, and renaming the Interface gives the same error. Also, I get 3 errors in Process Control as it is looking for Short/Alarm1/Alarm2.wav files in C:\SoundTest\SoundTest.exe, which does not exist. These I can ignore but I doubt I can ignore the Interface error. Any ideas? This is where I am -

Fantastic finding this thread, just got the AH64 and was hoping someone had created a profile I could "steal" the MFDs and some critical gauges from for my 8" Lilliputs with TM Bezels! Have not used Helios in quite a while in DCS (did set up my F-16 MFDs a while back) but am very familiar with using it in the "other" F16 sim, will re-read through here and hopefully figure it out!

Is their a Helios profile out there (not on Zeen's site that I see) for the Apache? Would really be nice to have....

Don - You've got my finger hovering over the "Order Now" button again, but I still need some sort of mod to allow me to see behind me.. <sigh>... someday!

Don - Been off the Varjo discord since my order got pushed back and I cancelled, how is it coming along, have they fixed some of the complaints?

Have you tried different (direct to mobo) USB outlets?

They do a nice job on ground targets (in IL-2) also!

I'm hoping the "cool new fix" not only negates the need for the WMR tool but also adds a scaling function to headset movement, basically integrating VRNeckSafer into the app itself..

I would suggest to any Varjo owner that you hop on the "Varjo Gamers Club" Discord, there is a DCS section among many others... https://discord.gg/

It is the radar slew hat for the F-16 also, quite important..

Mine is less than a year old, this video was spot on for the Delta install.. now replace the Warthog stick's base with the VirPil WarBrd base and be a happy guy!

If you have had other headsets installed it seems that SteamVR may get a bit "confused" and cause issues. Here is the definitive way to get SteamVR back to a fresh install for the Aero.. https://steamcommunity.com/app/250820/discussions/2/1640917625015598552/ In a nutshell - 1. Close Steam and Steam VR 2. Delete "default.vrsettings" from x:\Program Files (x86)\Steam\Steamapps\common\SteamVR\resources\settings folder 3. Delete "steamvr.vrsettings" from x:\Program Files (x86)\Steam\Config folder 4. Delete "lighthousedb.json" from x:\Program Files (x86)\Steam\Config\lighthouse folder (in my case coming from a G2 the Lighthouse folder was empty) 5. Start the Steam app, be sure Games and Tools are checked so SteamVR shows up in the list. Right click SteamVR then \Manage\UNINSTALL 6.Go back and look in x:\Program Files (x86)\Steam\Steamapps\common\SteamVR\ folder, delete all contents under it. 7. Go back into Steam, select SteamVR, click the big Blue INSTALL button.. Done.

I would suggest you take a look at the most active Varjo discussion at he Varjo Gamers Club Discord. There are sections for DCS/IL-2, and general discussions.. New headsets are arriving daily and being written about/reviewed. I found the Quest 2 horrible, the G2 much better but not good enough, and have high hopes for the Varjo to pull me away from 2D..

Defects are never good but happen to the best manufacturers. How they DEAL with it is what sets the stage for the future. From what I am reading Varjo has listened to the reports, identified and rectified the problem at the assembly line stage in China, and stepped up with this policy of re-ship a new unit immediately (BEFORE you ship yours back!). Unheard of in general, and once again has made me comfortable with my purchase (and wait..).

I would ask them on their official support page...

Isn't this the fix?

I couldn't use the G2 on DCS or IL2 without labels on as no matter what I did the planes were little black fuzzballs out beyond 1k and I could not ID them so I had to get real close before firing, which of course if it's an enemy it is not beneficial to wait as they know exactly who you are.. sent it back.