prancibald

If I'm playing multiplayer, I definitely use my voice to announce I'm landing, but to get the carrier to place units in a queue for landing, I think they have to go through the communications menu, no? I also don't have voice attack or vaicom or anything like that.

Yes! Especially when trying to land a carrier AND do proper communications with the carrier, it can be tough.

Are you running dynamic foveated rendering? It made a big performance difference for me. https://github.com/mbucchia/Varjo-Foveated/releases

The NVG mod no longer passes IC Hopefully someone else can find a workaround. Or ED can make a way to disable the ring effect for VR users

it's this thing!

This new DFR thing released by @mbucchia is amazing. I don't know exactly what you did, but it really changes the game. I feel like motion smoothing has actually improved with it somehow. Thank you thank you thank you!

I've had quite a few crashes after this patch as well, but my playtime seems to last a lot longer. Game freezes and quits. Are you running the multithreaded version as well?

I was pretty unimpressed with this update at first, as it messed up the openVR method I've been using, but I bit the bullet and tried openXR. Wasn't very impressed either. But then I did a DCS slow repair, installed the wrapper that disables quad views, and now I can finally tell a difference. Feels much smoother than it did before.

Does anybody else get really bad stuttering when switching to the F10 map while using the aero?

Yes, that helps. I wonder now if I was getting some reflection. I covered up a metallic trashcan and removed some other metallic debris (maybe it's acting like chaff!) And it seems much better now.

About what height and distance? Mine are about 6 feet up about 6 feet away, angled down toward my chair. Other thing is that I'm wearing some over-the ear headphones, and maybe they're obstructing something on the headset?

Does anybody else get loss of tracking when looking down at side consoles? I have 2 base stations, positioned at my 10 and 3 o'clock right now. thinking of adding a third for this reason alone.

I tried forcing openxr and using the openxr wrapper that stops the varjo from rendering quad screens. However, I still keep coming back to forcing steamVR and using that instead. Feels a lot smoother overall, despite the weird flickering in the load screens (which doesn't matter much to me). No objective measurements just feels better at ground level, especially in multiplayer missions. Edit:should say I'm leaving steam using openVR

weird... This is how it's copied and pasted from my shortcut target box "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_steam_VR it looks identical to what you have there. I'm stumped.

I think you're using the wrong *.exe file. Should be DCS.exe, not the DCS_updater.exe.

Seems to pass IC!

Yep! I moved my textures and description.lua files into the "default" folder within the game install directory. I'm seeing my modifications now! thanks! C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Liveries\Cockpit_F-16C\default --placing them here works! C:\Users\prancibald\Saved Games\DCS.openbeta\Liveries\Cockpit_F-16C\Custom f16 cockpit --placing them here doesn't which is weird, because in the F-18, you can place custom cockpit liveries in the saved games\DCS.openbeta\liveries folders and the game will let you select them AND load them. The F-16 let's you select a custom cockpit folder when it's loaded into saved games\DCS.openbeta\liveries, yet it doesn't actually do anything. *sigh* Now I wonder if it will even pass integrity check

livery = { {"f16c_cpt04_gauges_light_bl_787_cntr", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_light_bl_787", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_light_w_787", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_gauges_light_bl_787", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_gauges_light_w_788", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_light_g1_788", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_light_g2_788", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_light_g_788", 0 , "f16c_cpt04.tga", false}; {"INSTR-03-C", 0 , "F16C-CPT-INSTR-03.dds", false}; {"f16c_cpt04_light_g", 0 , "f16c_cpt04.tga", false}; {"f16c_cpt04_gauges_light_g", 0 , "f16c_cpt04.tga", false}; } here's what I have now, matched the case of the files as well, but still not loading the textures.

oops, yes that link is incorrect, I did paste it wrong. So the file extensions need to be listed as well? I'll try that, but I'm looking at a similar mod for the F-18, and none of the file extensions are listed, just the first part of the filename

Thus far I have used the modelviewer to generate a description.lua file for the F-16C. I modded two texture files that I found within C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Textures\F-16C-CPT-TEXTURES.zip using GIMP. The files I modded are: f16c_cpt04.tga f16c-cpt-instr03.dds then I placed these two modded files in (fixed) C:\Users\Me\Saved Games\DCS.openbeta\Liveries\Cockpit_F-16C\Custom f16 cockpit Below is the description.lua file I made. Reading previous posts, I should either comment out or delete the lines in description.lua that I'm not using. Or set them to true (?), which will cause DCS to look in the default texture location. So for simplicity sake, I just deleted every line that didn't reference my modded files. description.lua: livery = { {"f16c_cpt04_gauges_light_bl_787_cntr", 0 , "f16c_cpt04", false}; {"f16c_cpt04_light_bl_787", 0 , "f16c_cpt04", false}; {"f16c_cpt04_light_w_787", 0 , "f16c_cpt04", false}; {"f16c_cpt04_gauges_light_bl_787", 0 , "f16c_cpt04", false}; {"f16c_cpt04_gauges_light_w_788", 0 , "f16c_cpt04", false}; {"f16c_cpt04_light_g1_788", 0 , "f16c_cpt04", false}; {"f16c_cpt04_light_g2_788", 0 , "f16c_cpt04", false}; {"f16c_cpt04_light_g_788", 0 , "f16c_cpt04", false}; {"INSTR-03-C", 0 , "f16c-cpt-instr-03", false}; {"f16c_cpt04_light_g", 0 , "f16c_cpt04", false}; {"f16c_cpt04_gauges_light_g", 0 , "f16c_cpt04", false}; } I load the game, find my "custom f16 cockpit" and select it within the special menu for the f16. However, NONE of the texture changes I made are appearing. I basically just changed the color of a few dials and switches as an initial test to make sure I'm doing this correctly before I go in and waste time tinkering with many image files. Any tips or ideas of what I'm doing wrong?

My friend and I are experiencing this bug as well. Also in 2.8.

I experienced this as well. Easier to align the IHADSS sight from the pilot seat (though still inaccurate by the intended procedure), but horribly inaccurate from the CPG seat. After much trial and error, I've found a workaround that works for me. I reset my seated position, then initiate the alignment procedure. I stare at a point around the top left of the TADS/PNVS camera on the nose of the helicopter and hit B/S now. It gets me a reasonably accurate alignment. I'm guessing it has something to do with the center of the seat position being slightly left of center, plus the fact that in VR there is no center "eye." I'm using Valve Index.

I've noticed this as well. Always sitting slightly to the left in the CPG seat whenever I hit the recenter VR position button. It centers me correctly in the pilot seat, but not CPG seat. I wonder if this has something to do with the difficulty aligning the IHADSS? I'm using Valve Index.