DroptheHammer Posted September 16, 2020 Share Posted September 16, 2020 (edited) Hello all, Since the last patch, the interior lights ( or rather the light they show on surfaces) of the tomcat do not render in the left eye of the HMD. To be clear, both eyes can see the light origin (the bulb itself) but only the right eye sees the light cast unto other objects as intended, to the left eye, even with all white and red lights on at night the cockpit is pitch black. Prior to the patch, this bug existed in the same way only when Culling was manually enabled by command line/LUA. The bug is similar to how the deck crew prior to the patch wasn't rendering in the left eye either (an ED bug they fixed last patch). It is most likely that the change ED made to ensure the Deck Crew was rendered to both eyes with Culling = ON needs to be followed by either ED or Heatblur to ensure the F-14 interior lights effects on the dashboard replicated to both eyes. Since Culling is now on by default since the last patch, all SteamVR , Windows MR and possibly oculus users should have this issue. I've tried toggling culling of via the lua, but the option can no longer be manually disabled (at least by the same line we used to manually enable it last patch). Hopefully this puts you on the right path and you can enable what ED did for the deck crew on your lighting. If they are unrelated, good luck finding it! Can't wait to gaze on your beautiful tomcat cockpit with both eyes at night yet again. A happy T-cat pilot, Slash Edited September 16, 2020 by IronMike New Setup : 13900K, Asus ROG Strix 4090, 64GB of DDR3600C14, 4x 2TB ADATA NVME, HP Reverb G2, Virpil Alpha on WarBRD, Virpil TM3 throttle, Monolith External Amp, DT 1990 Pro Headphones & TrackIR v5 Old Setup: 12900KS @ 5.5 , EVGA FTW3 Hybrid 3090, 64GB of DDR3600C14, 4x 2TB ADATA NVME, HP Reverb G2, Virpil Alpha on WarBRD, Virpil TM3 throttle, Monolith External Amp, Philips X2HR Headphones & TrackIR v5 Old Old Setup: 9900KS @ 5.2, EVGA FTW3 3090. 32GB of DDR3866, 3x 1TB ADATA NVME Link to comment Share on other sites More sharing options...
IronMike Posted September 16, 2020 Share Posted September 16, 2020 (edited) Thank you for the report. We will take a look. EDIT: Just confirmed, this is a DCS engine issue, not on our side. (It is best to report it to ED directly.) Edited September 16, 2020 by IronMike Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
Recommended Posts