Topper81

@BIGNEWY I havn't found this issue as a bug report so far, so if it has not been reported could you please report this issue?

Was there ever any bug report?

Hello, I noticed that by passing the carriers stern, there seems to be some "turbolences" which lead into a "Grade C 3PTS" touch down. I never noticed this with the old flight model. Opton for "wake turbolences" is on, but I don't know if it has to do with this issue and if it was set to on earlier. I haven't moved the stick so far just before touch down, however in external view, you can see how the FCS is working. Maybe this is not a bug and I'm doing something wrong, do I have to pull the stick just before touchdown? Or do I give to late full throttle? I attached a track file and a video where you can see my explained behaviour. nose_down_3pts.trk case1.mp4

Seems to be no issue anymore

Hi is this fixed by todays patch?

As mentioned, I have the feeling that it has to do fith the FLIR rendering. If I don't have any FLIR rendering device selected, I never noticed this issue. Does this happent to someone without FLIR image rendering? Even the TV mode for the TGP seems to make no trouble, but as soon as I swicht to FLIR, I always got "black frames"... I know I'm speculating with this, but as we saw, it's not really a black frame. What we saw it that it's a different "time of the day" for one frame or so... The question is why? And my next question is, how do you avoid shadows in the FLIR image? Or in other words: Is it possible that the time is change for rendering the FLIR image, and it's not changed back for the "Main Frame" in time? I know it's a very specualtive Idea

Just one more possible hint: I only have noticed this issue when TGP or MAV picture was displayed, or video image in the Apache. When I turn off those stuff, I don't see any dark frames so far. Maybe it has something to do with the rendering of those picture... But for sure it could also be performance related.

Hi sure I added a trackfile I noticed that it seems to be depend on where you looking at. I also recorded this as a video, and when I look frame by frame, it seems not to be complete black, to me it looks more like flying in the dusk for one frame: "Black" frame (dusk): Next frame (normal): you can see this also in the attached video: I also sometimes observed some "flickering" caused by lighning changes on the displays (Maybe related to this issue in general): But it's not related to the Hornet, I have the same issue with the Apache... blackframes.trk options.lua

Hello, I sometimes have "black frames", in the attached video @ ~ 20sec. I tested to change some settings without success. Settings are as Desktop 2023.10.28 - 14.46.55.01_2.mp4 follows:

Hello, after complete uninstall and reinstall of the graphic drivers I can now seect DLSS thank you!

@Insonia I think I havn't installed any VR mods. I cannot enable DLSS in non-VR mode using "D:\Programme\Eagle Dynamics\DCS World\bin-mt\DCS.exe" --force_disable_VR" to start DCS World

@Flappie I cannot find that key:

NVIDIA GeForce RTX 4090

Hello, I'm having the same issue but I'm not using the steam version with this launcher option: null dcs.log

Hello, is it possible somehow to change the position of the NVG for VR? The reason I ask is that because of the limited FOV in VR, almost the complete FOV is covered by the NVG, so it's hard to read the instuments etc....

I think the problem is: What should a chart of this show you? Because it's depending on so many factors: - Your alt and speed - Target alt, speed, maneuvering, radar cross section, - Weather: Air pressure, wind, ... So all you can get from my point of view, is a propability, but depending on so many factors, that I don't know how to bring it into a chart... The question what the best tactic is, is always depending on the situation. For that reason, in a one : one scenario, it might be a good idea to fire 2 120s: First one so that the target has to start maneuvering and it loses energy, and prossibly it has to break the lock of it's fired missiles, and another close to the "no escape zone". In this tactic, keep the target close to the border of the radars scan zone after firering the first missile, and keep it locked until the second missile goes pit bull. I don't know if it's a good real tactic, but it works good against some AI aircrafts if they only have semi active missiles. But 20 miles seems to be an effective range to me, if you and your target are fast and high and you are closing in. Even more is possible.

I guess there aren't any realistic charts you can find like that because this stuff is classified. However, as far as I know: - AIM 120C: Most modern, simulated Amram in DCS. Has a bit less range then the B but it has higher manoeuvrability - Sparrow: https://en.wikipedia.org/wiki/AIM-7_Sparrow, see AIM-7 variants However, I don't know if these differences are really simulated in DCS. It's mostly a good Idea to fly high (>= 30.000 ft) and fast (> M1.0) when firing these weapons, which will increase it's range significantly, but for Tomcat it might be better to fly a bit lower than the target because it's radar can't handle radar ground reflections so good. (Not sure about that) Note that for the Sparrow, you need a lock until it passes or it hits the target, because of it's semi active radar which cannot emit itself. For the AIM-120, you need a lock until it goes pit bull (You see a counter for this in the HUD), at that point it's active radar should be able to lock the target itself. Maybe this helps a bit... You can also check this YouTube videos:

Then the switch should be set to down position (GUNARM), because PAC should only be active if you defenetly plan to fly a pinpoint attack with the gun. (My point of view).

Thiy is maybe not a bug, but when a mission starts in the air, the GUN PAC switch should not be in ARM position, because if so the plane aerodynamic behaviour is not optimal for flying arround and the planse works unnecessarily against aerodynamic forces and maybe some people don't notice that.

Do you miss something for this report? Or is it not clear?

Whats the status of this issue? I added some screenshots in a higher resolution where you can clearly see that it's alligned for ~ 5° which is a way to high and a track file. I also checked the behaviour for Tibilis Lochini and it's the same issue, it seems that they are all aligned for 5° instead of 3° since a while: Batumi: Tibilis Lochini: batumi_landing_5deg.trk

Hello, I noticed that the ALS for Batumi is not adjusted for 3° as described in the aerodrome chart. In this example, there are allready 3 red lights at a ~5° approach angle. I haven't checked if it's an issue for Batumi only or if other airfields are affected as well.

How can I detach the TGP from the gun piper to use the TGP for searching targets in AG mode with gun selected?

After firering rockets in CCIP mode, it's not possible to switch to GBU-12 (e.g.) and use them in CCRP mode in the store page (choosing "Auto" mode). It looks that it's not neccesarry to fire the rockets (see secnod track file), so I guess it happens after CCIP has been calculated somehow... ccrp_bug2.trk ccrp_bug.trk