T-Pickle

So far we could only reproduce it in multiplayer.

@Flappie the problem keeps happening after a while, sadly that means the tracks get quite big (usually above 100 MB). How would I send a track of that size here? This is what happens: The range indication "freezes" and won't update anymore while you get closer to the TACAN, and the course deviation doesn't seem to change either anymore. If you turn your TACAN receiver off at the black knob and back to T/R it suddenly works again and jumps to the correct range. This means it can be worked around, but only if you notice it is not updating anymore in time.

I think it may be a LOD issue with the FARP models. I've not noticed it this close yet, but when I get to a certain distance from it the LOD change is very visible since it changes to a way darker green. Not much you can do to avoid this, just need to wait for an updated model or updated LODs.

While I think many of the settings should work with less powerful hardware once the underlaying problems are solved, I agree that the option to separately change cockpit texture quality from overall texture quality is much needed. Especially with tomeye's idea to implement it as special options we would have much more room to tune the game to our own hardware on a per aircraft basis, while other aircraft around us could be rendered with low textures and thus hopefully save a lot of memory. I hope ED is aware of this wish.

Good point. I will look into that next time.

You can try this tool, I managed to play a Tomcat campaign with a friend in multiplayer that way. Since it has been a while I can't tell if it still works though.

This happened to me just a week ago in a multiplayer session (trying to ripple from the centre pylon with the 5x snakeye rack).

I wasn't able to reproduce the FPS gain by disabling terrain object shadows. In fact I lowered all my graphics option to a low/medium preset and didn't notice a big change, even after clearing shader caches. I assume this trick is more noticeable if you aren't affected as much by other limiting factors, like loading of objects tanking your performance.

Since it happens to me while close to objects (either many simple objects, like buildings in cities, or very detailed objects like aircraft), I am suspecting it may have to do with the way resources are loaded and unloaded. Perhaps too many requests clutter up the VRAM? In a multiplayer mission with another Hind close to me I kept seeing an approximately 10 fps decrease every time it was within view. Unfortunately my fps is already limited to 45 which I barely reach, but in these situations the framerate is in the 30s or even 20s sometimes and produces noticeable stutter in VR. None of the tweaks mentioned so far helped me, not increasing page file size, removing paging or the MT.lua.

Hey, thanks for looking into it again. The issue is not that it does not show range, but that sometimes the needles would just freeze in place. Since it is seemingly random I wasn't able to create a short track of it yet, last time I noticed after 30 minutes or so in a multiplayer session. I will upload a track as soon as I can narrow it down in a shorter timeframe.

The problem described in the linked topic is still happening in the latest open beta of DCS. The F-5s Tacan just seems to freeze randomly after a while and needs to be reset by turning the Tacan off and back on, otherwise the needles just won't move anymore.

Tacan still keeps freezing in the latest version of the game.

I've noticed some spikes when "merging" with other aircraft, as if something is loading in and takes some time to do so. When staying in range and following them I couldn't reproduce the spikes reliably anymore, so aiming was usually fine. Sometimes it still felt like the spikes came back randomly, usually during heavy manoeuvring, possibly due to the rapid change of camera perspective and objects coming in and out of view. However, a similar thing happens when I'm close to scenery objects like buildings (the more the worse) and this time it won't simply go away, as if any building nearby has to load a lot of data again and again while flying past a city. The spikes can be anything between 5 and 20 fps loss, which is quite noticeable for me in VR with my FPS capped at 45. Graphics settings didn't seem to make a difference with the general impact (even anti-aliasing off), I use a moderate custom preset. Game is on M.2 SSD, 32 GB of RAM, Intel i7-6700K, GTX 1080. Yes I know it is a bit older, but these issues seem to happen for people with much better systems as well so I just want to contribute my experience. Running MT and currently testing the new MT.lua @BIGNEWY has linked in another thread. So far no luck with the issues described above. Hope we can find a solution together at some point.

Hello, just wanted to point out this clipping issue with the left pilot leg. Once you notice it is really hard to unsee, especially in VR

Hello, I would like to ask if a sensitivity slider for the button controlled rudders could be added. Currently pressing the button to push the rudder left or right will move the pedals in the chosen direction almost instantly. The sensitivity would mainly affect how fast the pedals and the virtual pilots legs would move in one direction while the button is held. I think this would make the module more enjoyable to control for those who don't have rudder pedals or can't use them for any reason, and also don't have an alternative axis that is suitable. Preferably such an option would also come with a keybind to toggle between "rudders staying in place after button release" and "rudders re-centering at the same rate which was selected with the sensitivity slider". Thank you in advance for looking into this!

I know this is not cockpit art, but seems to fit this topic better than creating a new one. Looks like the mesh has a hole or some flipped faces at the upper part of the left vertical stabilizer. It is visible with every livery.null

I'll think about another configuration for my controls, I guess you are right and it's probably better to not have anything happen unintendedly.

Makes sense, thanks. I managed to bind it nearly exactly like I had it before now by switching my T1 and TV buttons. So I can still relatively quickly aim and fire RB75s but without interfering with the BK90 target waypoint anymore (or any other waypoint, I assume the problem would have been for any other weapon I just didn't notice it). Regarding the fixes: As far as I understand from testing now, in attack T1 does not start the "wait for waypoint fix" routine, so it's usually fine to press. TV though will update the target waypoint to your current location, so it shouldn't be pressed in attack mode except when using RB75s and you want to lock on with them.

Thank you! I tested it now and it was indeed the problem, did not think about this at all. But again, I do not press T1 so I am not sure why the waypoint changes, but I see what you described now, when I only press TV M1 already resets. I thought for a waypoint/target fix I always need to press T1 first... Now I need to think of a better binding, I only have so many buttons

Here is how my setup looks (the point M1 marked on the radar map looks correct to me): In fact my binding is a bit specific, I have TV on my first trigger stage and Release Weapon on the second stage. So when I release the BK90 I would indeed press TV first, but not T1 (that's a completly different button in my bindings). As far as I know, the waypoint update should not happen as long as I don't press T1 before, correct?

I followed the explanations of the training, the waypoint was already M1 if I remember correctly. Game version was latest open beta. I'm also pretty sure I did all those steps, I tried it multiple times. Even the single drop switch does not change it, just that only one BK90 does that weird turn away from target then. Since it's such a weird pattern where they fly basically 90° to each side, I couldn't believe it would happen with a wrong QFE or altitude, surely it would rather look like they "miss" the waypoint due to wrong data (like in your situation), but not fly away from it. I had a couple of aircraft mods installed (to play on Grayflag for example) and was thinking maybe they mess with some data, so tried uninstalling them but still got the same effect.

Very strange, I can't figure out what I'm doing wrong...

During the BK90 Training mission, did you manage to get the bombs on target @Machalot & @The_Tau? I'm pretty sure I followed the instructions but perhaps I missed something? I also wonder if it has to do with wind now...

Allright, here is the track again which hopefully should work this time. I had the exact same problem with the BK90s again. P.S.: If this helps anyone, the track file problem was caused by me forgetting about "disable_write_track = true" in my "autoexec.cfg". This causes DCS to create a placeholder F-5 track file if you force it to save one. 10 - AJS37 Training BK90.miz_04022023_00-07.trk

I wonder what's going on Sorry but I didn't edit the file or the mission, I will try this again tomorrow but so far I have no idea why it would become a F-5 in the track?