Daemoc

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.

Thanks for this. It turns out the Oh-6A was the cause of my stuttering issue. Specifically the scripts/hooks files. I removed all mods as a first step in troubleshooting when this issue came about with the last update, but I must have missed those script files. I spent days trying everything to stop the stuttering and nothing worked. The odd part is it only effected the Caucasus map and I did not use the OH-6 mod on that map. I could use the OH-6 on other maps and I had no stutter. And it only stuttered after the last update. It is just weird. Anyway, just wanted to say thanks again. I can finally play DCS again. The A4 and the OH6 where the only two mods I used, but I think I am done with mods going forward.

Been at this for two days. I still can't make sense of this. I can run this exact mission as a spectator and it runs fine. The second I hop in a vehicle it stutters. If I am inside an aircraft sitting on the tarmac, every time the game stutters, the aircraft bounces. I have started recreating this mission from scratch and I am about 25% the way through it and I still can not reproduce this stutter.

No dice on the power service. I have been testing this all day and here is what I found... 1: Out of all of my large custom missions which are all built very similarly, this only happens on the Caucasus map. 2: If I start a new mission on the Caucasus map, it works fine. 3: If I delete everything from the mission other than my Huey, it runs fine. If you look at the large over all map. I systematically deleted everything outside of the circle and tested it at each stage. It was still bugged. Once I had it narrowed down to this little area, I systematically deleted everything one step at a time and tested. I first deleted all AI air units, then AI tasks then deleted ground units and statics in small areas. The bug was still there until the last pass when I deleted everything. I then loaded the original mission and deleted everything in this little area and left everything else. It was still buggy. There has to be a single unit type somewhere causing this. It has to be a static or ground unit as that was the only thing left on my last pass. One that I did not use on my other missions. I will find it, it is just going to take a lot of trial and error to do so.

I did see that, but I figured it did not apply because of the circumstances involved. I will give it a shot though, it can't hurt. Thanks for the info.

I have no idea what a real F-5 with a single wingtip aim9 should feel like, but this has been my observation as well. At first I thought the rolling moment was a result of asymmetric weight and tried to counter with aileron, which never seemed to behave. Again, no real world experience here, but it just felt off. It got to the point that I would just launch both missiles at the same target because having the single winder was more of a liability in a turn fight. After while I noticed that if I counter the "roll" with rudder instead of aileron, it was easier to control at slower speeds which points to asymmetric drag rather than weight. I don't know how you could test something like this let alone prove anything right or wrong, but my gut tells me the wingtip stores create too much drag.

I made the full time switch to Linux during the Windows 7-10 transition. After a little learning curve, I found Linux to be a much better user experience than Windows will ever be. I know people are afraid of change, but with distros like Mint, anyone can make that change. You can do everything in Mint without a single command line. 90% of my steam library works out of the box using proton. On top of that, a lot of older games that have issues with the newer versions of windows actually run more stable via Linux/Proton. I told myself I would never go back to Windows. Every time I use it I want to pull my hair out. My DCS rig is the only reason I still have a windows machine. DCS is all it does. It is my hope that DCS will at least work under Proton once they make the switch to Vulkan as my DCS rig is going Linux when windows 10 is end of life. DCS working or not.

I had an unusual performance bug show up with the last update. There is a massive frame time spike every second or two. The weird part is, it only effects the Caucasus map, and only my custom missions made before the update. I have three custom missions on this map and they all do it. I am not sure what to make of it. I have attached a video of the issue. https://youtu.be/i_UAQLfO7SU I have similar custom missions on other maps that do not do this, which is even more confusing. My GPU usage drops from >90% to <60% with each lag spike. Nothing stands out in the logs either. Any ideas?

Sorry for the late reply, I have been been super busy. I have been doing a lot of testing, and I think I fixed it with a shader wipe. I have not had the issue since.

I don't think there have been any recent changes. I have been using the new flight model since it was implemented and I have not noticed anything new. One thing to note, you have a lot more power available with the new engine. If you are heavy, the main rotor torque will overpower the available tail rotor. Especially if you do not baby the collective. I should also note, I am not saying there is nothing wrong with the flight model, just my experience with it.

I have noticed this shimmering is only an issue if you have sharpening enabled. I am not saying there is nothing wrong with the texture map. I have no proof of that either way, but I think sharpening is the culprit. I have found the DCS native sharpen fx causes a lot of visual anomalies. Especially if used without some form of up-scaling. That said, the F1 cockpit aliasing is visible even using ReShade sharpening shaders. I think it just the result of fine noise/sand type texture being over sharpened.

I do have that power. Everyone does. I pay for zero subscription services, but I get your point. My little boycott may not change the industry and I am ok with that. I am not a junkie either and I take comfort in the fact that I have a little willpower. For the most part, good games always work. If a game is worth playing, there is always a fan base that keeps them going. I own the disc versions of the only two fallout games that were worthy of the title and I still play them to this day. Oddly enough, they only games that truly disappear are the ones that require online activation and payment to play. Which is just about all AAA games now. And for the record, I do understand that DCS falls into that category, but despite the multitude of little issues it has, I think it is worth it. So I choose to support it. I agree these tech companies are are quickly becoming monopolies and that is a problem, but that is not the reason for the state of the industry. In fact, it proves my point. These entertainment companies make more money than they ever have and they somehow make a worse product. Is that because they have a monopoly, or because people still choose to pay for the **** product they make anyway and complain about it later. It's funny. Just the other day a video popped up in my youtube feed about some game review. I don't even remember what is was about exactly, but this guy was up in arms about this new game he bought and how the devs destroyed the IP. So I get that people can get a little obsessive about IP's, but what I found to be the most ironical of the entire situation was the fact that they knew what the game was before they bought it. Then threw a fit about how bad it was after the fact. Why? Why would you buy it in the first place. You knew exactly what is was and you bought it anyway. I guess the word junkie fits quite well. Anyway, I digress. In the end, it is of my opinion that even if DCS went to a sub model, it would not magically fix the old bugs and engine. At the end of the day, even a sub model is driven by new content and that is where their priority will stay.

While this may be the bottom line, in the end it is much worse than that. Subscriptions are the worst thing to happen to the entertainment industry as a whole. You have zero agency with a subscription. Good, bad, absolutely worthless, you still pay for it. At least when I buy a module or a tv series as a physical copy I only support what I like. Even if I don't "own" it. Paying for netflix, prime, whatever? No thanks. 90% of the industry is garbage and the only thing that keeps these clowns afloat is everyone paying for convenience. The game industry is going the same way, but I guess that's what people want. You pay for ****, you get ****. Is 10-20 bucks a month going to break the bank? No, but I would rather burn my money than give it to someone with zero say in how it is spent. Well, besides taxes for obvious reasons.

I tried to have the convoy ambush something that happens in real time and something dynamic, but it never worked quite right. I think I worked once out of 10 tries. It looked cool when it worked, but it was just too unreliable. I ended up just scripting the entire event. It was still pretty fun though.

A quick screen grab from my latest flight.

I have been using this exact setup for quite a while. It works great. I am about 80% done with a 3D printed scale Huey collective. I still need to model the control plate and the additional box on the top of the head, but it is getting there. It is strictly cosmetic at the moment, but it does have a wire channel in the center if I ever get around to building a custom input device for the head.

Aye, I saw this as well. That said, in game you can run MPR until you run out of fuel. At least it used to be this way. I have been keeping myself honest and only using it during takeoff/climb, but I know you could run it forever before. I guess I have not tried it the last few updates.