Daemoc

It was worth a shot anyway. I use Track IR, but I have never tried 1080. I could see how the lack of pixel information would compound the issue.

How hard would it be to add the F-5E rocket pod options to the C-101CC? I have modding experience, but not with DCS. I have no interest in learning C++, visual or the Russian language, but I can do a bit of scripting. I don't mind doing the work, but would this be something that is easily doable, or are we talking rewriting half of the Library of Congress?

I noticed MSAA broken on my AMD card quite a few updates ago. I don't remember exactly when, but it has been a while. ReShade is another option though. You can use a version of DLAA through ReShade that has no ghosting, but it does soften the image quite a bit. You will definitely need some form of sharpening as well. I use personally use DCS TAA with no sharpening and the ReShade "AMD FidelityFX Contrast Adaptive Sharpening" with the "Contrast Adaptation" and "Sharpening intensity" both set to "1". That is the best sharpening option I have found that does not over sharpen and cause random pixels to pepper the image. As long as you have a decent framerate, the TAA ghosting is not as noticeable. It is still there obviously, but not a game breaker. I dunno, I guess I would rather deal with a little ghosting than the flashing pixels everywhere, but YMMV. As far as enemy spotting using TAA, I found it is best to use the 2x pixel dot option in DCS. Especially at 4k. The dots are impossible to see otherwise. This is no fix the MSAA bug, but I thought I would post what works for me on the off chance others might find it useful.

I just noticed this the other day. I don't know when it happened, but there is something wrong with the 30mm/50cal gun pods and the upper landing gear struts/arms. I only noticed this on the USAF skin, but it may affect more?

I pretty much stick to SP for that reason. I play to have fun and have an immersive experience. I have not played DCS multiplayer, but I used to play multiplayer games in the past and it's just not worth it. All of the bickering, accusations, little kids blowing out my speakers screaming in their headsets... ...yeah, no thanks. Anyway, back on topic. I would say the spotting dots are not ideal at the moment, but I am not sure what the fix is. I have just been sticking to 4k because I can't see the dots anyway.

To be fair, to say I can see the dots easier at lower resolutions does not necessarily mean an exploit. This is just what I have experienced during different missions. I have no idea at what distance those targets have the larger dots appear compared to the 4K native. I have not tried to replay the same missions and analyze every pixel at x miles. The sad truth is though, most of the "eye candy" options make it harder to spot everything period. TAA at high frame rates looks great overall, but the temporal aspect of it makes fine details hard to see.

I would not say "it works", but I do not see what the VR users see. 2D at 4K, I can not see anything. The dot's are so small, they might as well not even exist. There are very rare occasions that you may spot a dot in a clear sky, but it's rare. Using MSAA vs TAA helps a bit, but not much. I am using a 48" Samsung 4K TV for a monitor. If I drop the resolution to 2560x1440 and turn off TAA, I can see the larger dot squares much like the VR users describe. With a single aircraft it is not so bad though. It is REALLY noticeable in large formations at specific distance bands.

Yes, I am only having issues with the replay tracks. I watch the replays of about 90% of my flights and never had issues like this. I mean the replays do break a lot of times, (as in not represent the real flight), but they always open and play. This only seems to happen with the CH47 and it only seems to error out like this on the longer missions. That last part is just circumstantial though, I have no real way of proving it. The replay tracks do work using the CH47 sometimes. But I never had a replay track fail to load using the Huey or other modules. (I fly the Huey the most, and pretty much daily.) I am at work at the moment, but I will play around with it some more this weekend. I only check the logs when I have issues, so I will clear them and take a look after saving and replay a Huey track or two using the same mission to see if I get the same type of error in the log. BTW, are those CH47 debug controls entries normal, or is there something wrong with my control setup?

Ok, I have done all of the above. I did a complete steam re-install. No Mods. No Anti-Virus. Set DCS to low and everything I could set to off. Did a new play test of the mission and saved the replay. I "screen recorded" the loading of the track so I could pause the playback and see if the error had any information. It just says" Mission Load Fail" for a millisecond at the very end of the load bar then the bar restarts and hangs on "terrain init 1". The only thing I can do at that point is alt-tab and close window. New logs and screenshot of the error attached. The track file is about 8mb in size. Is there a way I can send it privately? dcs.log

This happened again today. I just did the exact same mission before using the Huey and watched the replay track. I switched to the CH47 played the mission then saved the track and it hangs when it tries to open. There is an error that pops up about "failed to load track" or something, but it flashes so fast I can't read exactly what it says. Technically DCS does not hang, it is just stuck on the loading screen. If I alt-tab out and "Close Window" I can return to the DCS window and it asks me if I want to quit. If I choose yes, it closes as normal. Log file attached. dcs.log

Here is a video of what is happening on my end... https://youtu.be/ZKlRGk5hrQ8 This is using my primary DCS computer at home, but this is exactly how it was behaving on my laptop at work that supplied the log posted above. Sorry for the delayed takeoff, but I have not used this module in a while, I was a bit rusty. The real problems started once I was airborne and you could watch in real time what happens when I switch nav mode on and off. If I would have continued flying it would have crashed DCS, but the amount of time it takes is random.

Yeah, the NS430 is broken again. I have attached a log file. I purged the shaders and created a new mission with 8 waypoints. I could tell right away it was broken though. My frametimes where all over the place. Sometimes up to 3 second lag spikes. Empty solo mission. I am at work so I can't do much more testing here, but if you need something else let me know. dcs.log

I just deleted all files in the two following locations. C:\Users\Name\Saved Games\DCS\fxo C:\Users\Name\Saved Games\DCS\metashaders2 This was a few updates ago though. I have not used the NS430 in a while. I will try to get some time in with it tonight. I will give those tracks a try and see if I can reproduce the crash as well.

Well, I can say it runs worse now for me as well. Probably the new Pilot/crew models just compounding the issue. I tried the optimized textures and it did seem to help a bit, but performance is still pretty piss-poor. I think there is more involved here. My DCS logs have thousands of entries about controls... 2024-10-02 19:39:39.060 DEBUG LuaGUI (Main): Input: Profile[CH-47F] key command[PDP2, LIGHTING, PDP/MAP Circuit Breaker (E12) - PULL] for device[Mouse] has different name from command[PDP2, LIGHTING, PLT SLT FIL Circuit Breaker (E11) - PULL] for device[Mouse] 2024-10-02 19:39:39.060 DEBUG LuaGUI (Main): Input: Profile[CH-47F] key command[PDP2, LIGHTING, PDP/MAP Circuit Breaker (E12) - PUSH] for device[Mouse] has different name from command[PDP2, LIGHTING, PLT SLT FIL Circuit Breaker (E11) - PUSH] for device[Mouse] 2024-10-02 19:39:39.060 DEBUG LuaGUI (Main): Input: Profile[CH-47F] key command[Clickable Mouse Cockpit Mode - ON/OFF] for device[Saitek Side Panel Control Deck {B0D78B10-5BB8-11ee-8002-444553540000}] has different name from command[Force cursor to show, toggle] for device[Mouse] Pages upon pages of the above. I think I am just going to shelve this and hope this just needs more time to cook.

I am not entirely sure what to make of the performance issues with this module. For me it seems to come and go which is even weirder. Sometimes it runs ok, other times it halves my frame rate. All in the same mission. I have made some very large missions with multiple units, even newer units like the F4 and it still runs fine. I have 16g of VRAM and it is ALWAYS maxed out running DCS and it does not tank the frame rate until I use the CH47. Even using an empty map. Even though I think it is ludicrous to use the texture fidelity they do for the newer modules, I am not sure that is the entire cause of the performance issues. It is hard to say for sure. I have not had a chance to test the new update, but I hope to have some time today. I was hoping to see an improvement, but after the above comments, I am not very hopeful.

So after an entire weekend of trying to reproduce this, I had no luck. To add to the confusion, one of the original "corrupted" track files opened without issue. Well, without issue may be a stretch, but it did open and play. About every other time I use this module in realtime or playback track, it get massive FPS lag spikes and other times it runs smooth watching the exact same track or flying the same mission. I am going to say whatever caused the track hang on load was a fluke that day. I don't mind sharing a log file, but the track was of a custom mission I have been working on. And while there is nothing top secret about it and plan to share it freely at some point, I just don't want it "public" in it's current state. While I have you here though, I do have some really weird things in my logs files. it's not just about the CH-47 though, but rather an absolute ton of errors. A lot of them contain stuff about the AH64, a module I don't even own, and also a bunch of other random module errors. Then there is a list a mile long pertaining to the CH-47 and control debug/inputs? Were would I post this type of issue? Do you think the general bug section would be best?

I will see if I can reproduce this on a smaller mission/test when I get home today. The mission I played last night was a large one and the track file was huge.

Everytime I try to replay a track using the CH-47, DCS hangs on loading as the title says. I can watch tracks using every other module without issue. I even tried the exact mission using the Huey instead and it works fine. Any ideas?

I had this issue as well. I don't know if this has even been acknowledged, but I found what was causing it on my end. This only seems to happen on certain maps/airfields and it is intermittent. For me it was the VHF Comms. I think this is always blasting static, it is just louder sometimes depending on the mission. I have a track here if someone wants to investigate. If this is not a bug or has already been acknowledged, disregard post. Radio.trk

Sorry @BIGNEWY I know that may have sounded a bit harsh, but I just dropped 60 bones on a module I will probably never use. I am sure you guys can squeeze a bit more performance out of it, but with textures being locked to a power of two, I don't see much you can do outside of cutting the fidelity in half. Which I am all for btw, I just know you would have another mob with pitchforks burning down the forums if you did. I know you can drop the textures to medium, but most of the modules I fly regularly are already old and showing their age. The Huey and F5 look pretty rough on medium. I just don't see myself changing settings every time I decide to fly something different. As a result I can see the Ch-47 going largely unused. If I could make one suggestion? Going forward, with these new modules and the insane amount of detail you want to push, make a new "ultra" texture setting. That way we could turn down the setting to high which would not effect all of the older modules/units that look bad enough as it is. High: current high settings for older modules and lower fidelity for the new modules with insane levels of detail. Ultra: Full r****d Everybody wins.

Wow, I just had a look at the texture files. Yeah, good luck with that. Oh well, I just wish I could say this was the first time I had regret for an impulse buy.

I don't know what is going on, but I have a few flights that actually work as you described. (-10-20fps loss) Other times though, I average about 10-15 FPS. It's a complete slideshow. If I restart the mission a few times I will get better frame rates for a while, then just have them tank again. My longest run of somewhat normal FPS using the CH-47 was about 9 minutes before I was taken out by a mid-air, but that was the exception, not the rule. Anyway, I hope this is due to some sort of bug rather than a side effect of some lunacy hardware requirements.

I can't believe I am the only one experiencing this, but there is something wrong with this module. I have done a few free flights and it seems ok, but the second I try to add it to one of my existing missions it completely tanks the frame rate. I can use F4's on the same mission so I don't think it is hardware related, but who knows. All I know is that this is the only module that completely tanks performance like this. No mods, no script hooks. Deleted shaders for both DCS and my GPU.

Sorry for the late reply, I have been busy with work and have not been online in a while. The only way I found to accomplish my particular goal was to keep all unit tasks to a single stage. If I had multiple tasks, I would have to fake it with different units. Example: Spawn a unit, (Troop 1), that needed transport and have them embark then disembark and perform a task. After Troop 1 preformed their task, I would remove Troop 1 from the map and spawn a new unit (Troop 2) and have them pick up the next embark, disembark, task. Then remove Troop 2 and spawn a Troop 3 etc, until I completed the missions tasks. It's not ideal, but it worked.

Sorry for the late reply gents, been busy at work. I will definitely try DCS on Linux again once they make the switch to Vulkan and I will try to remember to post the results in this thread. VR may still be a problem though even if DCS does work. As far as I know, the Valve Index is the only HMD that has official Linux support. There have been a few attempts at making open source drivers for other HMD's via "Open HMD" or "Monado", but I have not tried either yet. I was a early adopter of the Oculus Rift and a huge VR fan myself, but I am not going to buy new HMD until there is a proper open source product available. I am not a fan of expensive hardware being locked behind online accounts and activation.