Jump to content


  • Posts

  • Joined

  • Last visited


Personal Information

  • Flight Simulators
    Falcon BMS
    MSFS 2020
    Strike Commander
  • Location
    Mainz / Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. To bump this thread and to raise awareness to that it might be related to the LOD switching which might have been changed from 2.8 to 2.9 Have a look at the thread I created right after 2.9 was released. My latest test was to revert to 2.8 where performance was good. Correct me if I am wrong but if a simple revert to 2.8 gets rid of the stutters, then it's not a faulty driver or Hardware or anything else that suddenly caused the stutters. It's DCS 2.9 only which causes the stutters. I am really sick of comments making me look for the cause on my end. Also comments like it's running fine on a 2d monitor. I am pretty sure it's there too. But people don't notice as 2D stutters are not as obvious.
  2. +1 Until then give https://openkneeboard.com/ a try. You can use it in VR bind it to your HOTAS. Have different folders, a radio log etc. I spend too much time in my life not using it
  3. Which ones are you referring to? I thought ED models only things that data can be publicly accessed.
  4. If you lock a bandit with STT through the JHMCS helmet, in a ratio of about every 3rd lock will be lost showing this behavior. The bandit is not jamming. I was trying to find similarities in the situations where it happens. Thats why I played it back with the radar MFD showing. Also I thought maybe it only happens when the bandit or another aircraft was locked before through STT. But that was not the case either. It can happen with the first lock attempt too. It happens with the clear sky behind so its no ground clutter involved. Also even if it should not be possible to notch a radar against the clear sky, that can not be the case here. There is always a good closure rate when watching the numbers on radar MFD. Note that the radar is not on its gimbal limits either. If you want, try it by yourself. Take one of the track files and take control. It should not take more than 3 or 4 attempts. To summarize: No notch, not jamming, no radar gimbal limits involved. What else can it be? Maybe someone with a fresh eye can watch the video and look for hints what may cause it, by taking a closer look at the radar screen. Hope that its helpful with the radar MFD showing although the cockpit view and the JHMCS is not very sharp that way. I included all the track files shown in the video lock air behind the bandit4.trk lock air behind the bandit0.trk lock air behind the bandit1.trk lock air behind the bandit2.trk
  5. Yes. I am not doubting how the DCS F16 is modelled with the currently available data. I was saying unless, if not out of a sudden contrary evidence pops up, which is unlikely, we need to work with what we have. Thats the whole point of what I try to contribute here is how to get the 21 deg/sec out of the current F16 FM. Trying to point people struggling in the DCS F16 to look into other factors they need to consider other than flying 450 kts circles and wondering why they cant win a dogfight that way.
  6. Yes and here comes all the misconception from. Staying at the "low" 18 degrees per second is only if you are one of the dudes who think if you fly the perfect speed on a horizontal plane of motion, then you'll win with your "not" rate king F16. If youre already on the deck, sure, youre out of options. Or at least you have less. If you want, you can replay my track file against the mig 29 and watch in Tacview for how long and when I hit 21 degrees per second. Spoiler: Its when I dump the nose below the horizon and pull 9G. And luckily my pilot does not black out because g effects is off. So I have the 21 degrees for as long and when I needed them. I would wish someone came up with a unclassified document that the FM of the DCS F16 is wrong and a sustainable 18 deg/sec is too little ( drag?). But until then we have to work with what we have. So forget about winning a fight by sticking to 450 kts and wait until you win a medal.
  7. Sorry for bumping it up again @BIGNEWY and @Lord Vader. But I did some more testing. I was suspecting the LOD switch factor to have effect on it as many signs point to the sutters coming from geometry and textures loading in and out of the CPU threads. Different LOD switch factor settings produce different CPU frame time spikes and thus different stutters. Interestingly a factor of 1 which is default, produces the worst results. This was all done with the same the track replay. In my previous test using the ST branch of DCS DCS did not produce stutters as expected. We know that already. But for this test I reverted to DCS OB where I remembered not to experience these stutters. And whatever was added to DCS from 2.8 MT to 2.9 MT contributed to this bad CPU frame time behavior a lot. I used the same mission as it was simple enough that I could run it in 2.8 too. So the results are pretty well comparable. I am knowing that DCS is progessing. But from 2.8 MT to 2.9 MT something was introduced that made the LOD handling in MT worse. And the root cause seems not having been adressed since then. Edit: My test reverting back to 2.8 at the present day is not irrelevant, as it clearly shows it's not a change in hardware or driver software that caused my well running system to perform worse with 2.9. because I get my performance back the very moment I revert to 2.8
  8. Good to hear the g modelling is being adressed and already in testing phase. What I wanted to illustrate above was not for questioning the sustained or the instantaneous turn rate of the DCS F16. This track file should bring to the attention to people starting to fly the F16, wondering about why outrating an opponent by using sustained turn rate only, does not work, that there are other options too. Because mostly they dont do anything wrong, besides not noticing that they simply wont be able to out rate their opponent considering their jet configuration / weight.
  9. You can measure it in Tacview or try the "SustainedTurnRateMissionF16.miz". I uploaded it. Unfortunately the refresh rate is not too good, but it gives you a clue in the cockpit. As @MTM was very thankful in a PM about my track file dogfighting the Mig29 with 3000 lbs of fuel by not stubbornly trying to outrate it, using bursts of the full 9G and 21 degrees per second capability instead, I feel that it is necessary to answer these questions about out rating an opponent also with the advice that out rating is not the solution for all of the engagements you'll end up in the F16. In fact it mostly is not. That encouraged me to try the initial setup with 7000 lbs of fuel @MTM requested. Although it is not possible to outrate the Mig 29 you can defeat it with by bringing a lot of speed into the merge. Again, whats needed is the capability of the DCS pilot to sustain 9G for around 15 seconds. I was using 8+ G for 13 seconds and for 17 seconds in that engagement. And ended up in his control zone. Even with 7000 lbs of fuel. (track attached) So please ED @BIGNEWY. As even your demo for the sustained turn rate was with g effects off : Do us and yourself a favor and consider to adjust the G tolerance of the DCS pilot for the F16 soon. It makes it much easier in these arguments about the DCS F16 "performance in dogfights" if not only the F16 performance is correct as is, but also the performance of the DCS pilot meets real world requirements. SustainedTurnRateMissionF16.miz Mig 29 vs F16 7000 lbs fuel no sustained turning with no g modelling.trk
  10. Thanks a lot. Me running an Intel 13900KS with an RTX 4090. Vr Headset is a Varjo Aero. And second VR headset is the Pimax Crystal. The user I talked to had a comparable system. Crystal, RTX 4090, 13900K ( not KS). He even had stutters in the menu which were gone using ST. Another user on the dogfight server has the 7800x3d + 4090 + Reverb G2 without issues. Unfortunately he has a different headset and processor. I really am thinking about the intel processor at least contributing to it...
  11. @BIGNEWY Can we please get a tag if it is being worked on or not? As soon as the ST exe will be taken away from us, we wont have any reference to test it with. It is definitely a MT issue here. Testing again with ST and no lags or spikes occurr on the CPU frame time graph. If there was MT optimisation done in the latest update it does not show up in improved texture and geometry streaming performance of displayed aircraft in MT. I had a talk with another VR user who got hefty stutters in the DCS menu already. Switching to ST got rid of the stutters. But this is no permanent solution as ED is planning to take away the ST exe and the lower performance ST has compared to MT.
  12. The topic is "F16 performance in dogfight" and initially it was asked about outrating an F18. To which the answer is simple. You just cant outrate a player flown F18 in an F16 in DCS. About the question @MTMbrought up later in the discussion, outrating a Mig29 but not being able to sustain 21 degrees per seconds is related to when to utilize the max turn performance that is only available pulling 9G which is of course not sustainable in the F16. To make it clear to @MTM. Thats what my video should illustrate. You need to use the 21 degrees per second under 9G at certain points in the engagement for a certain amount of time. Which was a maximum of 13 seconds in the test I did. Just to compare it to the requested minimum of 15 seconds 9G tolerance for the DCS pilot which make total sense in watching my engagement flown with G effects off. This is even more important against an F18 that you cant outrate. When people talk about dogfight performance its just not only sustained turnrate that counts. I am pretty sure the OP is also happy if someone tells him not to just lock the stick at max sustained turn rate and wait.
  13. @MTM Although you can outrate the Mig as @BIGNEWYshowed, it took him 5,5 circles and 2 minutes to get into the control zone. You want to kill as quick as possible and not to be proud to maintain the perfect rate speed all the time until the wingman of the Mig killed you with a heater while you were doing your airshow. If you start with excess speed, climb, bleed the speed down to gain angles, then speed up again, and repeat: You can do it in 44 seconds for the first shot opportunity and you can be in his control zone after 3,5 circles or 1:20 minutes. Thats 40 seconds less for his wingman to potentially shoot you. But only if you DISABLE G effects. You can watch the tacview the track file creates and count the completed circles in each engagement. And watch the control indicator in the video how often I just go for full stick aft bleeding down my speed to gain angles. The thing why I am saying this is because people have the impression that the F16 is a bad dogfighter. This is not necessarly the case. The DCS pilot is bad and blacks out after a few seconds. So the only thing that remains as gameplan is to fly at rate speed not exceeding 8G to keep the DCS pilot awake. This thread is about the DCS F16 performance in dogfight. And if the pilot is the limiting factor for a jet that was designed to pull 9G with a reclined seat, I find it totally legit to bring the g modelling into this discussion... again. It is being worked on, I know. And in the respective threads there are documents that state that an F16 pilot needs to be certified for at least 15 seconds of 9G tolerance. If not even 30 seconds. How should you fly and win in a jet as it was designed to be flown with that limitation created by the DCS pilot. kill no sustained turning3.trk
  14. @BIGNEWY No! The stutters with aircraft coming close to the player are still there as before. DCS - 22.02.2024 The gazelle seems to have a good impact for testing. Another F16 does the same, but gives not that much of a CPU impact. As soon as I come close to the gazelle the CPU frame time goes up. Creating bad spikes in fpsVR which are visible as hefty stutters. Thats the yellow dashes in the GPU graph. Thats what looks like stutters in VR. Especially in dogfighting it is really annoying when youre close to your opponent when smooth playback is needed you end up in a stutter mess. See how the CPU frame time goes up every time DxDiag2_9.txt stutters gazelle.trk
  • Create New...