Jarhead0331 Posted May 29, 2019 Posted May 29, 2019 I have a weird issue with the Hornet in VR...the left and right DDIs are completely unreadable. The text on them is blurred and blocked out...zooming in does not help. It is an odd problem since I do not have the issue in the AV8b...it just effects the Hornet, and only the left and right DDI, not the MPCD. I do have the DDIs exported to a small 11" monitor with cougar MFDs for non-VR play when I fly with TrackIR. I presume the lua file for the export might be the source of the problem, but why only the hornet and none of the other aircraft that also use the exported DDI/MFD? Any feedback is appreciated. Thanks.
Strikeeagle345 Posted May 29, 2019 Posted May 29, 2019 I have a weird issue with the Hornet in VR...the left and right DDIs are completely unreadable. The text on them is blurred and blocked out...zooming in does not help. It is an odd problem since I do not have the issue in the AV8b...it just effects the Hornet, and only the left and right DDI, not the MPCD. I do have the DDIs exported to a small 11" monitor with cougar MFDs for non-VR play when I fly with TrackIR. I presume the lua file for the export might be the source of the problem, but why only the hornet and none of the other aircraft that also use the exported DDI/MFD? Any feedback is appreciated. Thanks. In the options, make sure you have your Cockpit displays setting on at least 512, or 1024. What HMD are you using and what is your PD set to? Strike USLANTCOM.com i7-9700K OC 5GHz| MSI MPG Z390 GAMING PRO CARBON | 32GB DDR4 3200 | GTX 3090 | Samsung SSD | HP Reverb G2 | VIRPIL Alpha | VIRPIL Blackhawk | HOTAS Warthog
Jarhead0331 Posted May 29, 2019 Author Posted May 29, 2019 ^I'm using a Rift S. I have a Vive and will check if the problem persists with that HMD. What is PD? Sorry...:cry:
pimp Posted May 29, 2019 Posted May 29, 2019 ^I'm using a Rift S. I have a Vive and will check if the problem persists with that HMD. What is PD? Sorry...:cry: It's the pixel density. In DCS VR options, set it between 1.2 - 1.5 depending on your computer specs. i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT | HOTAS Warthog | Saitek Flight Pedals
Nagilem Posted May 29, 2019 Posted May 29, 2019 I have also found that MSAAx2 and AAx4+ also helps with the DDIs if you have a GPU that can handle the calculations. Put the shadows to FLAT also which could give you the overhead on the GPU for the two things above. :pilotfly: Specs: I9-9900k; ROG Strix RTX 2080ti; Valve Index HMD; 32GB DDR4 3200 Ram; Samsung 970 EVO 1TB SSD; TM Warthog with pedals, 3 TM MFDs
Harlikwin Posted May 29, 2019 Posted May 29, 2019 There is also a DDI mod that makes them less fuzzy, you can play with things like line/text thickness. Just go back a few pages and you should see it. New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).
Jarhead0331 Posted May 29, 2019 Author Posted May 29, 2019 I changed the pixel desnity to 1.5 and changed MSAA to 4x and SSAA to 2x. This has improved the overall graphics quality and even sharpened the MFDs in the Harrier, but it has not improved the problem with the Hornet DDIs...any other thoughts?
Soma888 Posted May 30, 2019 Posted May 30, 2019 I haven’t flown the hornet for awhile but is it something to do with the contrast/ brightness settings on the ddi?
Jarhead0331 Posted May 30, 2019 Author Posted May 30, 2019 Changed stroke thickness and fuzziness settings in the MDG_strokesDefs.lua file and this definitely helped. Its still not super clear and some digits are very hard to read, but, it is definitely flyable, whereas before it was not. Before: stroke_thickness = 0.8 stroke_fuzziness = 0.5 After: stroke_thickness = 0.3 stroke_fuzziness = 0.1
hansangb Posted May 30, 2019 Posted May 30, 2019 Maybe it's time to delete the contents of shader/fxo files or do a repair? Mine certainly don't look that awful. The shader and FXO files are in (default) C:\users\Your_UserName\Saved Games\DCS\metaShaders and ...DCS\fxo folders. I don't know if it'll help, but it's simple to try. hsb HW Spec in Spoiler --- i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1
Supmua Posted May 30, 2019 Posted May 30, 2019 F/A-18C Unflyable in VR...Help! When you fly in VR don’t export the DDI. Do you change to single monitor profile in DCS setting when you switch to VR mode? PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
Jarhead0331 Posted May 30, 2019 Author Posted May 30, 2019 When you fly in VR don’t export the DDI. Do you change to single monitor profile in DCS setting when you switch to VR mode? When I fly in VR the DDIs do not export. The export monitor goes black. I do not change any other settings.
Jarhead0331 Posted May 30, 2019 Author Posted May 30, 2019 Maybe it's time to delete the contents of shader/fxo files or do a repair? Mine certainly don't look that awful. The shader and FXO files are in (default) C:\users\Your_UserName\Saved Games\DCS\metaShaders and ...DCS\fxo folders. I don't know if it'll help, but it's simple to try. This is likely not the issue since the problem is only with a single aircraft and not others.
Strikeeagle345 Posted May 30, 2019 Posted May 30, 2019 Yeah that is messed up, never had this problem. You have something enabled / edited in a config that is screwing with the DDI displays. If you have an export setup, I suggest turning that off completely prior to booting DCS into the VR environment. Strike USLANTCOM.com i7-9700K OC 5GHz| MSI MPG Z390 GAMING PRO CARBON | 32GB DDR4 3200 | GTX 3090 | Samsung SSD | HP Reverb G2 | VIRPIL Alpha | VIRPIL Blackhawk | HOTAS Warthog
Harlikwin Posted May 30, 2019 Posted May 30, 2019 That pic you posted looks like the error with exported mfds. I would disable it entirely. New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).
Strikeeagle345 Posted May 30, 2019 Posted May 30, 2019 That pic you posted looks like the error with exported mfds. I would disable it entirely. This. Strike USLANTCOM.com i7-9700K OC 5GHz| MSI MPG Z390 GAMING PRO CARBON | 32GB DDR4 3200 | GTX 3090 | Samsung SSD | HP Reverb G2 | VIRPIL Alpha | VIRPIL Blackhawk | HOTAS Warthog
Gruman Posted May 31, 2019 Posted May 31, 2019 I got the Rift S and my MFD look clear and crisp. Nothing blurry or washed out. Easely readable from neutral seating position. It's a fresh vanilla install. No Mods or anything. Try the things mentioned above. Delete shaders, disable export of MFD's, select VR preset and top of any texture texture Including the MFD Settings. Should make everything crisp again. Intel I9 10900k @5.1GHz | MSI MEG Z490 Unify | Corsair Vengeance 64GB - 3600MHz | EVGA RTX 3090 FTW3 VPC T-50 Base /w Viper & Hornet Grip | VPC Rotor TCS Pro w/ Hawk-60 Grip | TM TPR LG C2 42" | Reverb G2 | TIR 5 | PointCtrl | OpenKneeboard
VirusAM Posted May 31, 2019 Posted May 31, 2019 I have a weird issue with the Hornet in VR...the left and right DDIs are completely unreadable. The text on them is blurred and blocked out...zooming in does not help. It is an odd problem since I do not have the issue in the AV8b...it just effects the Hornet, and only the left and right DDI, not the MPCD. I do have the DDIs exported to a small 11" monitor with cougar MFDs for non-VR play when I fly with TrackIR. I presume the lua file for the export might be the source of the problem, but why only the hornet and none of the other aircraft that also use the exported DDI/MFD? Any feedback is appreciated. Thanks.Did you change some lua file or installed some mod about screen exports? If so revert from thar or do a dcs cleanup and repair R7-5800X3D 64GB RTX-4090 LG-38GN950 N/A Realsimulator FFSB MKII Ultra+F-16 grip+F/A-18 grip, VKB Stecs Max, VKB T-Rudder MKV, Razer Tartarus V2 Secrets Lab Tytan, Monstertech ChairMounts
Jarhead0331 Posted May 31, 2019 Author Posted May 31, 2019 Reverting to a single monitor from the a10c virtual cockpit and moving down to a 4K resolution seems to have solved the problem. Still find it interesting that the export setup only negatively impacted the Hornet DDIs. Anyway thanks to everyone for all of your helpful suggestions.
Supmua Posted May 31, 2019 Posted May 31, 2019 It’s been like this as far as I can remember with the Hornet, at least for me. Switching to single monitor profile resolves the fuzzy DDI issue. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
Jarhead0331 Posted May 31, 2019 Author Posted May 31, 2019 It’s been like this as far as I can remember with the Hornet, at least for me. Switching to single monitor profile resolves the fuzzy DDI issue. LoL...where were you a week ago. :megalol:
BigDuke6ixx Posted June 3, 2019 Posted June 3, 2019 Try uninstalling your graphics drivers and doing a proper clean install of the latest stable ones.
Recommended Posts