Jump to content

Raven (Elysian Angel)

Members
  • Posts

    3686
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Raven (Elysian Angel)

  1. Actually I experience both. Yes the stutters on the main menu last for about a minute and then go away. Then during the mission it's a stutter-fest again, and once I exit the mission there are the same stutters on the main menu once again. It's why I'm posting in both threads...
  2. This is what I normally see when I open the in-game frametime counter (first image): Second and third is what I am seeing now... I didn't change any drivers, driver settings nor anything in BIOS. Windows settings are still the same too. I did test adding bkg_load_all_plugins = false to autoexec.cfg and bkg_load_signed_plugins = false (in another sesstion, not both of those commands at the same time) but that didn't change anything (not about the stuttering anyway). Of note is that I see that same stuttering and the CPU BOUND MAIN THREAD on the main menu. Added info: - I am not using any mods; - I ran a slow repair twice; - I have always set any game folder as exclusions in my AV (Windows Defender). dcs.log
  3. I’d prefer if they get their latest one in a flyable state first (aka pedal trim options and more manageable cockpit textures). Also, the Mi-24 still doesn’t have a manual and didn’t get a Mini-Update post in years…
  4. Sure but for example door gunners' ROE can be set to "return fire" only, so that tells me the underlying logic is already present and functioning.
  5. Glad this worked for you, but this is general advice (same counts for nVidia btw) that doesn't really have anything to do with this particular issue. Anti-lag and Reflex have their uses but mindlessly turning them on for everything and then forgetting about it is a bad idea. There are videos on YT explaining how that tech works (Gamers Nexus has one I believe) for those who want to know *why* it can lead to worse performance. In Nvidia's case there's even a tooltip warning users that turning it on potentially leads to worse framerates and can introduce stuttering.
  6. Is that the one made by Baltic Dragon? If so, yes I agree I would like that as well.
  7. Pretty much this. These last few patches introduced the first framerate/frametime problems I experienced in a long time, so at first I blamed windows update, but no other games has any issues so it definitely is caused by ED. I tried a whole list of different settings but nothing changes the headache-inducing stuttering. The only thing we can do is hope for a hotfix soon...
  8. That’s because the underlying cause is quite complex, and takes time to properly implement. The reason why people have so many problems with yaw control is because of the rotor model that’s currently being used. There have been plenty of problems in the past with torque and torque onset rates, with varying degrees of fixes being made, but until we get the new rotor model, these problems will persist. We need the cause to be fixed instead of patches for symptoms.
  9. There is no such thing as "Su-25A". The basic version is just 'Su-25'.
  10. I have the same issue. At first I tried to fix it myself, but nothing I could think of made any difference so after pulling out my hair (stuttering issues when DCS has been running flawlessly before is quite frustrating) I decided to look on the forum, and here it is: more people talking about the exact same thing. And yes the stuttering on the main menu stops after about a minute, but even in a mission I am seeing "cpu limited main thread" more often than I care about.
  11. Yes that’s not the first time she teased it. Last time - iirc - she said we’d get MiG-23 sooner than we think.
  12. For now I choose to remain optimistic. Rumours had it that MiG-23 was about to be released when the drama became public, so in case things get sorted between both parties chances are we won’t have to wait too long. Obviously I agree that we need a MiG-23 in DCS, preferably sooner rather than later.
  13. Thanks for the patch for the CPU issue, and have a nice weekend!
  14. Yes you're correct: the problem was on my end. Rebooting my router fixed it
  15. The server hamsters already left work for the weekend I take it?
  16. Which waypoint issue? I have flown that campaign numerous times myself with other FF modules based on fixes I made, and there are other people who uploaded their versions to the User Files. I have never encountered a problem with waypoints Besides, while that campaign was fine for a game-y product like flaming cliffs, I’d say the standards for campaigns have risen quite a bit since those days…
  17. Keep in mind you might want to edit it a bit to suit your particular setup, which is most likely different from mine. I use a Z-extension which offsets the grip, so that needs to be compensated in order to allow for proper re-centring.
  18. I remember it was yellow back in the DCS 1.5 days. Flaming Cliffs modules are old though and were not built for the changes to lighting and material properties that came after 2.5 . Not even the recent "remaster" fixes that.
  19. Here you go. If you want even more force, you can increase master gain from my 80% to 100. Third_generation.vpconf
  20. That depends on which preset you use. In my experience, preset K is "meh" when it comes to image quality, but has zero ghosting. Preset J is "OMG I didn't know this is possible in VR" when it comes to image quality, but has ghosting (to a degree which will bother you if you do a lot of dogfighting). So pick whichever you prefer... In the end, I stick with Preset J: it makes the Kola winter textures actually look good, which is quite the feat IMO
  21. I tested this mod, and it indeed decreases the font size to the proper level for VR.... << BUT>> It comes with a major disadvantage: it disables the "yellow text" aka you can no longer control the communication menu with HOTAS - only with mouse. This is why I disabled the mod again, and I'll live with the oversized text size... (I am not interested in voice activation)
×
×
  • Create New...