Dangerzone

But if you fly in a squadron - I'm guessing someone other than ED is creating missions and hosting the server, so you are relying on community contributions such as the server hosting, mission designing and maybe scripting too, etc? Sure thing. And I need to make an apology to you. I think my previous response to you was bad. My idea was more about how much people rely on other community contributors for their DCS experience. This includes any community contribution. Reflecting on this - it could include Mods (Such as QVFR) for sure. But it could also include non-commercial content creators (C130 mod, etc) - or 3rd party community missions, or using a community server, or using scripts, etc. It's a pretty broad spectrum. My understanding is that the majority of players are Single Player only - so this poll was a way of referencing just how many people here are happy with "ED only" material, vs how many actually rely on other community members also contributing something to the mix. I wasn't really focusing on QVFR, etc that are essential to people running DCS - but in all honesty reflecting back on this - if they are non commercial community contributions, then I was probably wrong with my previous response, and they probably should be considered, but it's not limited only to those. Or another way to put it. how much would DCS suffer if there was no volunteer / community contribution at all.

Can you please expand on this for the rest of us. Are you saying you had VSync on in DCS, and turned it off? (And have it nowhere now)? Are you also saying that turning off Full Screen fixed all your stutters. And lastly - can you clarify if you're running 2D or VR? Thanks.

Yeah... we've come so far. I remember with DOS games... I'm finished. Half a second later POWER BUTTON and walk away.

You're more optimistic than me. When ED can't even keep their own modules from having repeated issues (scoreboard, ground unit pathing, track replay desync, etc where they have all the source code and can work on it from all angles - it seems more plausible that sooner or later there's going to be a change they make that's going to change something that breaks the F15E in a similar way too - but without the F15's source code to be able to diagnose from all angles - well, as I said - if they struggle when they do have it, this can only make it far more difficult. (This isn't a go at ED with their bugs - but just to point out that if it's so involved when you have the source code, it's going to be far harder without) Agreed. I see only 2 ways that the F15E survives this. Either Razbam and ED come back to a mutually beneficial arrangement, or somewhere in the contract it's stipulated that ED must get a copy of the source code and the legal proceedings end up forcing Razbam to hand it over. Otherwise, without developers actively maintaining the source code - it would be a very hard ask to expect this to remain operational long term.

That's definitely not true in my case. If you are right - then there's a connection between you and I that is missing. To clarify though - and maybe this is where the miscommunication is: The problem isn't that I'm getting over 72FPS without limiting it - the VR does indeed limit the frames still to 72 as you say - so I agree there. (So if you think we're saying RTSS is needed to limit the FPS to 72 in the headset - that's not what I'm saying). What I'm saying is if I use RTSS and set 72FPS - I get a far more stable 72 fps with far less drops than compared to if I wasn't using RTSS. Now as for the part that RTSS only affects the monitor - if I change RTSS to 60fps - according to what I understand from what you've written - this should only change the mirror window to 60fps? That's not the case - what I observe is immediately after changing this setting, my VR drops to 60fps. As such - I can only conclude that RTSS does indeed force a limit on DCS's FPS in VR. This isn't placebo - I'm viewing the DCS's actual FPS counter in VR - and I also see the effects visually well. I can lower this significantly more to 30fps or less - and the effects are even more obvious. Obviously I have no intentions to lower FPS that far - but for the sake of this exercise to test if your theory is correct that VR isn't affected - and I can conclude it definitely is affected by RTSS. The headset can't go above it's refresh rate - but RTSS is definitely affecting the frames that the HMD is delivering. Not only visually - but I can see this also reported in DCS's FPS dialog as well. The main reason to limit FPS to 72 using RTSS in VR isn't to lower the FPS to 72 because it's rendering more than 72fps- but rather because doing so gives a clear change to the amount of stuttering and CPU binding that is going on. I don't know the reason for this. Maybe the 72FPS isn't being fully limited correctly with Pimax software, or DCS has some HID interrupts coming in the wrong place that causes issues that manually setting RTSS to 72FPS helps as a workaround. I suspect DCS since this was working smooth on the previous version of DCS but the latest updates cause issues. (And rolling back to previous version works fine again). The reasons I can only guess - but the effects are plainly obvious. For me - without RTSS I'm removing my headset after 10 minutes with a headache due to the very obvious and significant stuttering. With RTSS at 72 - the major stutters have gone (the odd micro stutter remains),but I can play for hours. I also just tested again too - running with no limit gives me 72fps in VR with significant stutters. (72FPS dropping to around 60FPS as reported by DCS as well as is plain to see - no placebo). I see CPU Binding flash between yellow and green in the DCS FPS window as well. Then, setting RTSS to limit to 72FPS, the DCS FPS window shows a green 'GPU Bound' the majority of the time, with the occasional stutter - and I see a more consistent 72FPS in the DCS FPS window - I definitely see far fewer stutters. Cheers DZ

I'm curious about this. In my case it's definitely not a placebo. I can literally be in my headset - see what DCS is doing - while DCS is still running set the FPS limit in RivaTuner, come back and see a significant difference in what I experience in DCS plus what the DCS FPS Window is telling me. If this is not supposed to have any impact - I'm very keen to find out why it does - as anything I can do to remedy the issues DCS is having another way - I'm all up for learning more. However if I change RTSS to 60FPS - it definitely locks my DCS Frames to 60FPS in VR. My best guess is that there's some sort of over-rendering happening with DCS behind the scenes, and limiting it to 72FPS helps DCS to not 'race ahead' - but all I know is what I've done from experimentation - I'm no expert at this. Are you saying we should be enabling VSYNC for the VR mirror / monitors sake instead? I don't believe I have any VSYNC enabled. The only limitor there at present is Rivatuner? I'd be happy not to have a mirror at all on my desktop - if it meant better experience in VR, but I don't think that's possible?

Yes. Does your ISP give you the option to 'opt out' of CG-nat and get a public IP address? Many of decent ones give this option to their customers. It's worth checking.

Wow - this thread almost made a week with no responses. NL and BN must have enjoyed a break. Is 6 days the new 'high score'? One thing I found interesting though. I bought the AV-8B. Really enjoyed it. I heard a lot of bad stuff about it, but I'm guessing I came on 'late' when it had matured. When the F15-E was announced, many predicted disaster with it being in the hands of RB. I was one of those that thought they were naysayers and were holding a grudge about something no longer relevant. I enjoyed the AV8B, and FWIW - I thought the F15E was coming along nicely as well. Such a pity that things didn't work out - as it looked like RB were actually kicking goals and developing a product that was loved and enjoyed by many during it's early access.

I've found RivaTuner to be my best option. I've also found it helps change the yellow and red 'cpu bound' to the green 'gpu bound' status in the DCS FPS inspection. (With the exception of the stutters that I still haven't been able to overcome). However different people for some reason report different results with limiting the frames. For some like me, it greatly improves the experience. For others, it creates more complications, so give that a shot and see whether it makes it better or not for you. I've been trying to figure out what the difference is between those who limiting works for, and those it doesn't, but haven't found something yet. For me - I'm 13900 on 4090 with 64GB RAM. Other options for you are to use DCS to limit to 75FPS (and let your headset do the rest), or lock it in with NVIDIA Cpanel. But as mentioned, I've found RivaTuner works the best for me, but may not hurt to try all options as YMMV.

That's what I was insinuating. ie: the last two versions having the stuttering issues. Seems that we're the beta testers, but also the ones that need to diagnose and resolve the issue. Closed Beta always existed, but we also had open beta. Now, that extra step of testing has been removed (the open beta) leaving one less level between them and us (by 'us', those who used stable release). Since one of those steps has been removed, so we're all in the open beta testing together. For those of us that used to favor stable release - there's definitely a difference - but I also appreciate that there re those that never really understood the concept though between OB and SR or just always ran OB as their version - so I understand how some would see things from a different perspective. Tomato/Tomarto...

There can be - but people seem to have differing opinions. I've tried both DCS limiter, and NVIDIA limiter. I've found the best one to use (if limiting) is actually RivaTuner instead. It allows for more precise limiting than DCS (plus you can change it without having to pause the game) to see the effects. I think a big no-no is using more than one at the same time. For myself - I have noticed that I get smoother FPS by limiting using RivaTuner to the same Hz as my headset. I'm still getting stuttering on the latest DCS version though - but if I limit below 72hz to around 68 - the stuttering goes away. Unfortunately 68 though on a 72hz headset is not real nice. But in the end - you're going to get different answers from different people as some find limiting works better, others find it gives more problems. The only real way is to try it yourself.

Very wise. Works great if you're single player, but if you're into multi-player, it's a little less helpful. Being so new, you probably didn't know that we used to have 2 versions - an Open Beta and a Stable release. Those who wanted a more stable option could opt for Stable release, and those who wanted the latest changes yesterday could go with O.B. This worked OK IMO originally for those who wanted to use it (even if a number didn't really understand it properly), but then Stable Release got neglected, going months without updates, and no real 'bedding down' of a version occurred before moving onto the next version, and eventually it because unmanageable for stable release server operators with more forced to move to Open Beta to keep up. Eventually ED dropped Stable release altogether, and only carried on Open Beta as the main version. I have wondered about actually starting some sort of website/voting thing where people give feedback as to which are the better / more stable releases of DCS so there's a list we can work with for a multiplayer aspect who want stable again, but after thinking about it for a while I don't think it'd be that popular so probably wouldn't work.

Not really. This is more stuff directly related to DCS itself. Edit: I'm sorry - I shouldn't have said that. I didn't really have 3rd party software for VR in mind when I was asking the question - however in reflection, if 3rd party community based VR software is essential for people, then that would be considered a community contribution. Sorry for my poor response yesterday.

I’ve heard that most DCS players focus on single-player. My own experience is mostly MP, where community contributions are essential — hosted servers, mission design, scripting tools like MOOSE/MIST, SRS, Overlordbot, and the list goes on... It’s made me wonder: is my reliance on community-created content typical, or am I in a niche? This poll is a way to gauge how much of the DCS experience really depends on volunteer and community input — whether it’s essential, just a bonus, or barely needed. Even in single-player, many missions and tools come from the community, so the impact may be larger than it appears. I’m curious where others stand. Feel free to share thoughts in the comments as well. Obviously if you play multiplayer, unless you're hosting your own server and creating your own missions without any third-party tools, you are relying on community contributions such as the hoster - but I don't know how much of an impact this has if the majority of players are SP as I've been told...

Normally the different levels I've observed are 1) ED acknowledging / being aware that some people are having issues 2) ED able to replicate the issue 3) ED working on resolving the issue. At the moment we don't even know if we've reached level 1 yet - as I've seen no acknowledgement from ED that they're even considering there's an issue. Sometimes it's done in silence, and I was hoping that it's just lack of communication and they're actually aware of an issue and are looking into it, but after hearing your experience that they don't even know what this is about is concerning indeed. It's understandable that with so many different hardware configuration and user settings that this isn't an easy one to deal with. But if the common denominator here is the latest DCS update among a variety of different users, it would seem that we're at the mercy of ED actually investigating this internally.