Kreutzberg

I didn't realize this was pretty much the same thing I posted as well: I think the description in this thread is better than mine, but I'm definitely seeing it too (I'm including my track as well). F15E Laser Program Turns Off.trk

I ran into a weird issue the other day. The F-15E was loaded with 4 GBU-12s on one of the CFTs. I dropped the first three, but on the last drop, the laser did not engage. I had it set to automatic lasing with lasing for the last 12 seconds (ALAS :12). Doing some further testing, I've noticed that the entire laser program disappears from the targeting pod when the last LGB on a station is dropped. For ALAS CONT or manual lasing, that won't cause a miss because the laser either fires immediately or fires with the manual input. But for ALAS with a delay, it means that the laser never fires. To summarize, the issue is only 1) the last LGB on a station and 2) ALAS with a delay. It's possible that this is intended behavior, but seems more like a bug. A track file is attached where I reproduced the issue on a simple bombing range. F15E Laser Program Turns Off.trk

Sorry to resurrect an older thread, but I do think there is an error later in the comms. The pop up messages later in the mission say to switch to departure on AUX, which is not something we have in the kneeboard. I switched to departure on PRI and it seemed to work, so that might be what's intended.

The 2024 and beyond newsletter mentions further tuning and enhancements, especially in VR. I'm really hoping this doesn't go unnoticed, as it's a pretty big thing with newer VR systems that will only grow in importance as resolutions continue to rise. A light visibility slider (or settings) would be a pretty easy fix, I think.

Somehow, MSFS handles this better. Either the draw distances are much further out or it better smooths the transition, but there's nothing like this blatantly obvious line we see in DCS. That would be a really important improvement for low level CAS and helicopters.

That was my first thought, as well. However, changing the visibility range (and the new LOD switch factor slider) doesn't seem to solve the issue. I suppose it's possible that it pushes it out a little further, but that's difficult to measure with how the issue presents. For how close it is to the aircraft/camera (see my pictures), I suspect it might be something not behaving property. I'm just an American with German heritage. I've been to Kreuzberg in Berlin but not the Rhone one.

Interesting. Could you point to your topic? I'd like to compare notes!

Agreed. The pictures I posted took a fair bit of trial and error, and while not perfect, show it pretty well. I'm surprised we're not seeing more people noting this! I wonder if there might be some setting.

Here's another picture of the issue with a shadow. This one is from a VR headset. Interestingly, moving my head around (or the camera) moves the line, which may be a clue. I'm surprised others aren't seeing this. Perhaps there is some sort of issue with my system?

If anyone from ED is watching this, it would be a very important improvement to the Supercarrier module, at least (and there are improvements coming there). It's really disruptive to immersion to not be able to see the IFLOLS at all! There are other, much more visible, lights, so there should be a pretty easy fix. ETA: The legacy carrier lights are the same for now at least.

It looks like this got fixed, probably with the 2.9 radio overhaul. I mostly post so that someone stumbling on this post in five years with a similar (but different) problem doesn't think it's the same (unless it really does come back).

I've been noticing this issue for quite a while, but am having a hard time describing exactly what it is. When I fly at relatively low level, there is a line that travels slightly ahead of the aircraft where the details of terrain and shadows changes. The attached image "Syria split highlighted" shows what I'm talking about. I had quite a bit of difficulty capturing an image even that good, as it's tough to see in a still picture. But there is a clear discontinuity where I highlighted it. The way it projects across as a line (and the difficulty in getting a screenshot) made me think of screen tearing. However, running Vsync or setting a frame rate cap to well within my monitor's gsync range does not resolve the issue (I have a 4090 so have plenty of horsepower to avoid low FPS tearing in 2D). Most of my flying is in VR, but it also happens in 2D (and I got the screenshots in 2D). I've also tried every setting in DCS, none of which resolve the issue. Turning up details does mask the problem to some degree, but does not solve it totally. I tend to run fairly low settings to get 90 FPS in VR (normally in the multi thread client, but this does occur in single thread as well). The issue is similar to how some details appear to just change up close. The two pictures labeled "Syria Fence 1 highlighted" and "Syria Fence 1 highlighted" were taken shortly apart. I've highlighted how the detail on the fence moves along with the aircraft in a similar way to the line, above. It might be the same issue, or not, but it presents similarly. Is this something others are experiencing? I've tried to search for this issue, but may not be phrasing it well. Thanks, all. Syria split highlighted.bmp

One other note--the lights on the KC-135 are much more visible, as are PAPI lights on the Caucuses map. There must be some different ways lights are being displayed that control whether this issue appears.

It's interesting--I can't see the lights at all now. I wonder if there might be a setting causing that different behavior?

I recently transitioned to a Pimax Crystal from a Reverb G2. Using quad view foveated rendering, I can run a solid supersampled center and get really good visuals with good performance. However, I note that the various lights (including ground based PAPI lights on most maps and IFLOLS and LRLLS on the Supercarrier) are extremely dim (basically unusable). I briefly used a Varjo Aero, and recall the same issue, so my suspicion is that it is related to high resolution VR headsets and how the lights are rendered. They are much more visible with the G2. Are others encountering this issue?