markturner1960 Posted January 22 Posted January 22 (edited) I know it seems picky after it’s just been brightened, but if you are not using the overlay, the new meatball is so bright, you can’t see the datum’s, so it’s not easy to use as purpose, especially in VR……Would it be easy to make it editable for brightness level? A slider perhaps? Or accessible .lua edit? I will tack another one here as it’s kinda related….in VR, is it possible to move the overlay position and / or adjust its brightness for night flying? Edited January 22 by markturner1960 1 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
ED Team BIGNEWY Posted January 22 ED Team Posted January 22 People could not see the IFLOS, the brightness was increased and we made some fixes which helped a lot, now you are saying it is to bright, can you see we are just going to be going back and forth between different people with different preferences and different hardware specs. The answer can not be to add sliders to adjust for each issue. I have asked the team to review the lighting on the carrier for the deck, but at the moment it is lower priority while they work on improving the deck crew. thank you 5 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Micr0 Posted January 22 Posted January 22 Bignewy, was the latest tweak designed with VR, or Monitor view in mind? It seems like players are getting different visual results depending on whether they are in VR or monitor. 2
Kallio Posted January 22 Posted January 22 With VR the IFLOLS is just a big bright ball when it comes visible. The lights are so bright that you can actually separate the ball from datums lights around 0.2-0.3 NM before hitting the deck. 2 Ryzen 7 9800X3D /w Fractal Design Celsius S36 AIO - MSI X670E Carbon Wifi - MSI RTX 4090 Supreme X - G.Skill Trident Z5 64gb 6000mhz CL32 DDR5 - Valve Index VR - Acer Predator XB271HU - WW Orion 2 throttle /w F-15EX handles - WW Phoenix MIP - VPC Mongoost CM2 base /w TM WH stick - MFG Crosswind
Lt_Jaeger Posted January 22 Posted January 22 IFLOLS is not usable in VR any more!!! We are where we were 2021 - full circle. Take a look at this mod from back then It helped than it helps now. Is nobody actually checking stuff before release? The whole carrier is bright like hell at night. One can only shake ones head 6
markturner1960 Posted January 22 Author Posted January 22 (edited) Just trying to provide some useful feedback from an end user………and btw, that’s not just me saying it, everyone in our squad says the same its only useful as a meatball if you can also see the datum’s. I will rely on the overlay for now then, thanks Edited January 22 by markturner1960 2 1 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
Micr0 Posted January 22 Posted January 22 All, there is a quick fix for those of you in VR. This mod has two settings. "Reduced" works well for me during the day, and "Removed" works well for night ops. Its a simple copy and paste of the Nimitz texture zip. For the devs.... its that glow on the left thats causing the problems. 2
ax2212 Posted January 23 Posted January 23 20 hours ago, markturner1960 said: I know it seems picky after it’s just been brightened, but if you are not using the overlay, the new meatball is so bright, you can’t see the datum’s, so it’s not easy to use as purpose, especially in VR……Would it be easy to make it editable for brightness level? A slider perhaps? Or accessible .lua edit? I will tack another one here as it’s kinda related….in VR, is it possible to move the overlay position and / or adjust its brightness for night flying? Came here looking for this issue. In VR night ops on supercarrier is unusable for case III recovery not just IFLOS - but carrier deck lights and the tower lights too. Please see attached. Its much worse with VR bloom effect on - and these screenshots dont quite do it justice. in the VR headset its just a messy blur. also +1 for ability to adjust the VR IFLOS overlay position/brightness running 4080s, 7800x3d, 64gb ddr5-6000, 8tb nvme, quest 3, virtual desktop w/ dedicated 6ghz network 19 hours ago, BIGNEWY said: People could not see the IFLOS, the brightness was increased and we made some fixes which helped a lot, now you are saying it is to bright, can you see we are just going to be going back and forth between different people with different preferences and different hardware specs. The answer can not be to add sliders to adjust for each issue. I have asked the team to review the lighting on the carrier for the deck, but at the moment it is lower priority while they work on improving the deck crew. thank you cant speak for how it looks in 2D - but perhaps we can get some sort of slider. i recognize this might be lower priority - but in my opinion the deck crew are at least functional enough to get on and off the carrier. the recovery light situation makes case III much more challenging. mods might help but some servers will fail integrity check with the above mod. happy to provide any additional logs or screenshots as required. 9 hours ago, Lt_Jaeger said: IFLOLS is not usable in VR any more!!! We are where we were 2021 - full circle. Take a look at this mod from back then It helped than it helps now. Is nobody actually checking stuff before release? The whole carrier is bright like hell at night. One can only shake ones head agree entire carrier is bright as hell.
ax2212 Posted January 23 Posted January 23 a few more representative shots up closer - its better in the single eye rectangle screen capture than it is in full resolution 2 eye in the headset. in the headset the approach is like flying towards the sun. null
Hippo Posted January 24 Posted January 24 (edited) That's strange, I'm not seeing that at all (just tested with VR). I think the iflols is now working pretty well, and I still think the deck lights are too dim as I don't see them until way too late. Maybe it's something in my settings? EDIT: Using the Stennis in that mission. EDIT2 (12 hrs later): Now swapped with Truman. Seems the same. At around 1.6 DME iflols pops into view but it is all just a blur (though this could be due to headset resolution limits) . At around the ball call (0.8) I am able to discern the ball , I can also just about see the deck lights at this point although they are very very dim. I don't know why I'm not getting the super bright carrier reported above?! Combining the ball with the ILS and trying really hard to see the deck lights in time I am able to make the trap; I was not able to do this before the latest patch. Edited January 25 by Hippo System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Fresh Posted January 26 Posted January 26 I would also like to add, that using Pimax Chrystal Light, the IFLOLS are too blurry to discern my position. I would also appreciate a slider to adjust the brightness. @markturner1960 You can move the IFLOLS overlay in VR, click and drag the title. I haven't found a way to dim it though... Fresh 1
Hippo Posted January 27 Posted January 27 (edited) And here it is in pancake. Usable and similar experience to VR. iflols becomes visible at 1.6, certainly usable at ball call. Pretty sure that the deck lights have got brighter since the patch, but still very dim - however a trap is perfectly achievable. I have no idea why I'm not seeing the super bright carrier reported above. CP07.01 Case III Approach DME 10_nofog_tru.miz Edited January 27 by Hippo System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Foka Posted January 28 Posted January 28 On 1/27/2025 at 12:44 PM, Hippo said: And here it is in pancake. Usable and similar experience to VR. iflols becomes visible at 1.6, certainly usable at ball call. Pretty sure that the deck lights have got brighter since the patch, but still very dim - however a trap is perfectly achievable. I have no idea why I'm not seeing the super bright carrier reported above. CP07.01 Case III Approach DME 10_nofog_tru.miz 273.83 kB · 6 downloads Dimm you AoA light, it will be easier to see outside. There is a knob for it under the UFC. 2
Micr0 Posted January 29 Posted January 29 The irony is that that glow around the AOA indexer is precisely the problem with the ball. Get rid of the glow around these lights. ED is simulating an astigmatism for the pilot.
Hippo Posted January 30 Posted January 30 On 1/28/2025 at 12:51 PM, Foka said: Dimm you AoA light, it will be easier to see outside. There is a knob for it under the UFC. Thank you for your suggestion, and I apologise as I must have failed to explain myself correctly. The iflols is usable for me in VR and in pancake, but I find the deck lights a bit too dim, however I can use them. This is entirely different to what others are reporting in this thread (an iflols and deck lights which are far too bright) and I'm puzzled as to why this is. I am able to trap without issue now in VR or pancake, which I wasn't before the patch, and the last thing I would want is for the brightness to be reduced any further. Reducing the brightness of the indexer doesn't make any noticeable difference to my ability to see the iflols or deck lights. On 1/29/2025 at 3:46 AM, Micr0 said: The irony is that that glow around the AOA indexer is precisely the problem with the ball. Get rid of the glow around these lights. ED is simulating an astigmatism for the pilot. I have no problem distinguishing and using the ball in VR from around the ball call. I get your point, but the glow is trying to replicate a real effect, whether it's overdone is a matter of debate; I suspect that if it were removed there would be just as many complaints. System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
draconus Posted January 30 Posted January 30 On 1/22/2025 at 9:34 AM, BIGNEWY said: can you see we are just going to be going back and forth between different people with different preferences and different hardware specs Obviously it has to work the same for monitor and VR users but I can't remember a time it worked correctly in VR. 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Micr0 Posted January 30 Posted January 30 If we want to get super specific, that glow effect happens in real life due to the humidity in the air. The more humidity, the bigger the glow around lights. Hence, a complete difussion glow in fog. So, a slider controlling humidity might be useful. But I'm curious if the altimeter setting would have an effect on this. 1
Hippo Posted February 2 Posted February 2 ... and just to add to the confusion, I added fog (4560 ft vis, 1000 ft "thickness", sorry for terrible vr screenshot) to the mission I posted above and the iflols became visible from over 3 miles away (vs 1.6 miles with no fog). null System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Rolln Posted February 21 Posted February 21 On 1/22/2025 at 10:06 AM, Micr0 said: Bignewy, was the latest tweak designed with VR, or Monitor view in mind? It seems like players are getting different visual results depending on whether they are in VR or monitor. Yeah, I'm thinking it wasn't done in VR as well. It's not usable without modding. 1
Rolln Posted February 21 Posted February 21 (edited) On 1/22/2025 at 1:34 AM, BIGNEWY said: People could not see the IFLOS, the brightness was increased and we made some fixes which helped a lot, now you are saying it is to bright, can you see we are just going to be going back and forth between different people with different preferences and different hardware specs. The answer can not be to add sliders to adjust for each issue. I have asked the team to review the lighting on the carrier for the deck, but at the moment it is lower priority while they work on improving the deck crew. thank you Again with what @Micr0 stated, it's not that we want to bring these things up and make your life miserable, but it's unusable in VR. So maybe the programmer or tech lead that signed off on it wasn't using it VR. Most of the pics here are at night but it's equally unusable in the daytime as well. If you use VR, take 5 mins to try it for yourself and you tell us we are wrong... Can't remember which update originally affected it but it was fine before xmas... Edited February 21 by Rolln 1
Hippo Posted February 21 Posted February 21 (edited) 7 hours ago, Rolln said: If you use VR, take 5 mins to try it for yourself and you tell us we are wrong... I am able to use in it VR (pretty much) without issue, see my posts above. Edited February 21 by Hippo System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Rolln Posted February 21 Posted February 21 6 hours ago, Hippo said: I am able to use in it VR (pretty much) without issue, see my posts above. I'll post some screenshots this evening.
Hippo Posted February 25 Posted February 25 On 2/21/2025 at 3:38 PM, Rolln said: I'll post some screenshots this evening. Thanks. I don't doubt it's happening to you and to others, but it's certainly not happening to me. Perhaps you could post your DCS settings and I can try them on my system (although I won't be able to for at least two weeks, as I'm away)? System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
draconus Posted February 25 Posted February 25 7 minutes ago, Hippo said: I don't doubt it's happening to you and to others, but it's certainly not happening to me. What's your mission then? What exactly you want to achieve apart from annoying all the others who do have a problem? 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Recommended Posts