Qiou87

Although I personally agree with the fact that cold & dark is the best for my enjoyment, I see problems in the way the game is working right now. Many things are timed on the time in the game, for example other planes launching etc. There are huge time differences between start times, due to game updates (INS being the major time difference, depending on the availability of fast alignment or not, or the choice of the pilot to not wait for full alignment if doing only A/A...) and simply player proficiency. Imagine someone doing the startup with a guide on his knees, slowly, and compare that to someone who has 50 flight hours in the jet already and just goes through the procedure very fast. Even the "auto-start" cheat is very slow in comparison to a proficient player. So whilst I support wholeheartedly to have this option in all missions, mission & campaign creators need an easy way to avoid that this option breaks their missions due to the large time differences in jet start procedures from one player to the next and from one game patch to the next. Some seem to manage this with triggers, but it needs to be quite easy to use - the quantity of missions available is already a problem in this game, making it more difficult to create them is clearly not a desirable outcome.

I would if I could, it is a DCS Liberation mission (it is always overwriting the same "liberation_nextturn.miz") which has quite a lot of scripts in it. I tried sharing one with someone before, and basically it won't open in the ME due to those scripts (I think it is reporting the mission results to DCS Liberation using those scripts). Since it was the last one I played I can open it again, check the wind in the ME. Maybe ATC makes a rounding up and it is, like you say, a borderline case. Thanks for taking the time to check, so probably not a map issue and only a game engine issue. It is very stupid to have this limitation, as fog usually happens when wind is low, and fog is when you need ILS. In that case the runway was barely visible until I was at 100ft AGL, landing would have been totally impossible without the steerpoint on the runway. IRL I would have diverted for sure.

Are you sure? I read 7kts somewhere, which is 3,6m/s. As I said the wind was announced by ATC at 4m/s, so over the threshold. It would be pretty weird to have a high 14kts (7m/s) threshold for ILS.

EDIT: probably not a map bug, only a game engine bug (wind at or close to 7kts). Hi, I read other threads about ILS not working in Incirlik and it was actually due to wind, so I checked this. I noticed twice, in separate missions (auto-gen from DCS Liberation), that the ILS for Hatay RWY 04 is not working (108.90MHz if my memory is correct). Both times, I entered it twice (to make sure after seeing that it wasn't working the first time) in my Viper after checking in F10 view the exact ILS frequency for the runway, ILS ON, course 40°. Each time, the aircraft is not picking up the ILS. It works fine on RWY23. Wind was 020 at 4m/s according to ATC. I used RWY04 based on instruction from ATC (250.15Mhz), because I know that wind direction affects runway selection. I basically fly the approach as vectored by the ATC, but the ILS is never picked up. Due to some low-level fog, it made for some very difficult approaches (luckily my mission had a steerpoint on the runway).

Also, as a stop-gap, you can use the Frenchpack v3.5 MOD which has a technical pickup truck with machinegun and even a "kamikaze" version. ED said somewhere they were bringing some AI assets like this but in the meantime, this mod can provide this valuable vehicle for the insurgent faction and any ISIS-scenario! Watch out if you are flying helos though, they can really hurt you at short range.

I just feel more at home in VR in the Viper. That big bubble is a big draw for me. The way it flies also works better for me. Overall readibility of the instruments also works better in my Rift S than the Hornet. Carrier ops is the only reason I will still fly the Hornet for years, it is just so much fun. Once both are feature complete I suspect I will fly the Viper a lot more though.

Might be easier to get a licence from the Marsians for their saucers than from Russia for their MiGs and Sukhois. Although I think I'd go for an Independence Day kind of alien ship if given a choice. They seem to give some trouble to the Hornets in the movie, would make multiplayer PvP more interesting for the BLUFOR guys complaining about the lack of Fox3 REDFOR jets. Of course the question is how to get the flight model just right so our game remains a true sim.:megalol:

Your crash is probably due to VRS, you’ll learn about it in due time. But yeah, the Huey is wonderful to fly, more so in VR. My only gripe is the ridiculously underpowered armament now which makes it a purely recon/sightseeing tool (it can still be fun against ground troops with door gunners, but the AI grunts are so dumb it’s not fun).But man, just flying around in it is so awesome. Enjoy! It is also a great time to step into helos, they are getting some love in DCS. The Syria map is exceptional for helo ops, and we have a Hind and Kiowa Warrior coming very soon.

I can at least confirm that the problem does not appear in SP anymore, thanks probably to the higher page file size. I played 1:30 hours on Through the inferno in Syria, switched aircraft twice, l tried to load as many ground units as possible by cycling through them with F7, and still no stutter. I did not have time to check if it is also gone in MP but at least it looks like a great step forward. I am wondering if the small size of page file didn’t appear on my pc with update 2004. Since it was done recently, it could explain why this issue appeared in August for me.

Still need to make another few tests but the pagefile issue could have been the culprit. Mine was set automatically at 5GB by the system. I manually set it to 16-32GB and have seen improvements in MP. However I will make another couple of flights to check and make sure, and come back here to close the issue if it is.

I think I read somewhere that it would be in two weeks. :music_whistling: At any rate, I did appreciate the last one, even if it made me spend money on a Viper and maps. If another one comes, it will be the same all over again.:pilotfly:

I think I found a way to replicate it in Single Player, but sending a track file is not necessarily the best solution since a track file would only correspond to the first loading. I loaded the same mission (SP) multiple times. Just take off, crash, click "Fly again" (the idea is to spend 1-2min each time so the game is really loading everything around you). After the third time, the framerate is again very bad for me and I had to restart the game entirely. This is replicable for anyone, just take a heavy SP mission with lots of assets and load it multiple times. I was getting 40fps stable on the ground the first time, by the third time the FPS was dropping below 20fps and had horrible stutter. I flew it despite the stutter and it was still bad after 10min of flying, it did not solve itself over time. I had to quit that mission as it was barely playable. @Alec: I would gladly join you to make this investigation, any chance you could offer me a RTX3090 as well? My b'day is coming up, so... :music_whistling::lol:

I did that, at this point I only have Microsoft services running. Same problem happened after a long play. I first switched planes after 15min, and it was fine. But I played another 40min in a different server, then switched and the stutter was back. How do I create a track file in multiplayer? My understanding is that it only works in SP, where I am not able to replicate this so easily (happened only once in many hours). Today I will revert to the previous video driver, as it is the last solution on the list.

No, that’s not how it works. A GPU will throttle back once it reaches one of it’s limits: temperature, power consumption, etc. Just being used at 100% is not going to make it throttle. My GPU temp is fine, around 70C under max load. My case is well ventilated and the card is a MSI Gaming X, one of the best models of 2070S. My GPU is at 100% all the time simply because it is the performance bottleneck, which is understandable in VR. @Flappie: will do. @BigNewy: I will try and do that, thanks.

The thing is, I apparently run out of video memory, not system. System ram sits at a stable 22/24gb when I play, even when it stutters like crazy. But vram is maxed out, or at least that’s what the performance manager is telling me. Why it doesn’t get cleared, for example when I exit the server then join again (I still have stutter once I rejoin) is indeed the question.

I might just try your advise. I have been wary over rolling back to a previous driver due to FS, even if I am growing tired of it (still playing DCS every chance I get). Thanks!

It is not. I still have the issue, NordVPN is not running as a service in the background. I tried Hornet (30min) to Viper = still stutter. Quit server then rejoin = still stutter. Quit game then restart & rejoin = smooth. Then I tried Viper (20min) to Hornet = stutter as well. Next is to revert back to previous WHQL driver I guess.

No, I never had these issues before, but during our usual missions I stick to the same aircraft for the whole evening. It happened once in a Liberation mission (I played probably 30 or 40 sorties in the last month and a half using this software), in which I just flew one module. I understanding it is in development and didn't worry about it. It is only when the same stuttering happened in a repeatable way, when playing the 4YA servers (PvE dynamic mission) that I opened this thread. One thing I should also check is if it is Viper specific. In all those MP missions I flew something else, then changed to the Viper because it's the one I prefer to fly even if loadout is limited. Each of these stutters happen when I am in the Viper, I should see if doing the same (fly Hornet first, switch to another plane after 30min) in a Mirage will trigger the same stutter. Yesterday once the stutter was gone (after killing nordvpn service and taking a screenshot to post here), I spawned in 3 different modules in the same server (Viper, then UH-1H, then F5-E) without any stutter returning.

Thanks for your input, I will check this tonight hopefully. It definitely also happens in solo, but after a while and in a very very dense mission (if you have played it, you know DCS Liberation can generate those). If it is a memory leak, I guess the next step for me is to try the previous nVidia driver. I never noticed it before the last update.

Playing without VR? Are you mad? :) So tonight I experimented some more. First in solo, loaded 4 different modules at 4 different airports in succession in the same mission - no issue at all, butter smooth framerate. Then I went back to multiplayer, same server I had problems in the last 2 days. Sure, after 30min in the Hornet, the Viper gave me very bad FPS and especially stutter like last times. I took the screenshot attached. I killed nordvpn service, after that it was not so bad. I mean I still got 20fps around the airport, then 40fps when airborne, but it was stable FPS. With reproduction it didn't feel bad actually. I had a look at FPS when it is stuttering ; I get between 16 and 2 fps, depending how much I move my head apparently. If I don't move, around 15-20. As soon as I move my head, it gets very bad. I will try to block nordvpn service to start next time and see if that's the source of my problems, or if just alt-tabing out of the game, taking a screenshot and stuff had some magical effect on the game.

I actually kill RocketDock when I launch DCS (because it interferes when I click in the cockpit). And I just uninstalled Novabench, I had no idea I had it installed and that it was running 24/7 in the background. What I probably need is actually to generate this stutter somehow (happened tonight again, after flying the Hornet 30min then respawn in a Viper). Once it is stuttering, the only way to normally make it stop is exit DCS. I will try to kill those processes... Let's see. Thanks for your help.

Hi Flappie, Funny seeing you here. :) Files are attached as requested. I do not use a lot of external software. dcs.log process_list.txt

Indeed, the free Serpent's head (in DCS Files) is really quite good - I liked the fact that we are starting before deployment in Nevada, and generally it is well made and interesting to follow. Little surprises here and there as well keep it fresh. I'm sure the DLC is even better, waiting for the next stable update to pick it up. Nothing beats a Baltic Dragon campaign though, but sometimes others come close.

The carrier (Valley Forge) also is fictional, the only CV named like this was decommissioned in 1970. I think for a real pilot it was safer to create a fictional squadron and boat, so he could tap into his own memories and real-life events without too many people feeling offended. I don't see how this breaks immersion.

It depends how much assymetric load you have. I had a similar, albeit different, experience: right rudder and right aileron got destroyed by AAA. Aircraft was flying fine once trimmed until 250kts ; below that and it started to become seriously uncontrollable. Low speeds and high AoA can be tricky if you have a high assymetric load. In my case I had to land at 250kts, which is not really a possibility for you on the carrier because you'd never catch a wire. Trim is dependent on airspeed and attitude (something you learn flying GA without FBW, you constantly have to adjust trim), so for sure trim for your landing speed. It might be a good idea to follow a long final instead of making a short case I approach in your case, at least once you get used to the plane's behavior, to be able to stabilize the plane with trim once in the correct configuration (on speed, flaps & gear down).