Jump to content

Argo Navis

Members
  • Posts

    52
  • Joined

  • Last visited

Everything posted by Argo Navis

  1. Have you tried switching off MSAA in DCS and setting the Link to the highest resolution at 90Hz? I have a very similar system to yours, and I am getting very fluid, stutter free gameplay. No super sampling needed at this resolution and I am not dipping below 45fps at all.
  2. If I set bitrate to 500 in the Oculus Tray Tool head movement becomes very jittery for me. Setting it to 150 makes everything smooth. I experimented with the encode resolution settings, but I did not see any change. My resolution is set to the max in Oculus Link (see post above).
  3. I am looking for maximum smoothness, and I am willing to sacrifice some quality for that. I have been in the mid ranges in the Oculus resolution settings, and I didn't even consider higher settings than these: I used 3920x1984 resolution, and super sampling set to 1.3 in OTT. DCS settings are mostly low or off, however, in order to get rid of the jagged edges I had to set MSAA to at least 2x. These settings would give me a solid 45fps and 22ms frame time over the Syria map when you fly low over trees or towns, and it would jump to 90fps and 11ms when flying over more open areas with less trees and buildings. The difference between 22ms and 11ms is very noticeable. If I switch off MSAA in DCS, I would get 90fps and 11ms more often. I noticed that if you fiddle with ASW settings in OTT, the performance numbers would not change at all but smoothness gets highly effected. I set ASW to Adaptive, and while I am getting the same fps and frame times as before, flying at treetop level is smoother than ever. If I look 90 degrees to the side the trees are not ghosting or stuttering at all and the sensation of speed is amazing. These resolution and super sampling settings, however, are not that great. Details do not show on objects that are further away like the carrier deck on final approach, or the enemy aircraft's wings in a dogfight are hard to see without zooming in. The only solution to improve these effects is increasing MSAA in DCS, increasing super sampling in OTT, or increase resolution in Oculus Link. All of these will reduce the smoothness and I just could not find a better balance than the settings above. If fps starts to dip below 45 and frame time goes up in the 30ms range smoothness is totally lost. I find that the most detrimental to performance is MSAA and super sampling used together. Anyway, I got fed up with the constant tweaking, and I turned off MSAA and super sampling. I went nuts and set resolution to the maximum which is 5407x2736 in Oculus Link. To my surprise it works! The high resolution takes care of the jagged edges and the details. Fps is mostly 45 with 22ms frame time and it does jump up to 90 over open areas or flying high. Basically, I am getting the same performance as with the settings described above with much higher image quality without MSAA and super sampling. It feels very smooth and the details are amazing. Important note: I updated my Nvidia driver yesterday and the high performance was gone, and DCS became unplayable with the high res Oculus settings. I rolled back the driver to 457.51 and it is okay again. System: i7-8700k stock 2080ti overclocked 32 GB RAM
  4. I also wanted the G2. Same situation here, no G2 yet, so I decided to get the Quest 2 for now. It's relatively cheap, and hopefully it will be easy to sell when the G2 becomes available. I am not sure that applies to an older headset like the Reverb Pro. I was very skeptical of the Link cable first, but it runs DCS very nicely on my system. I have not tried online gaming with it yet though. Apparently, picture quality is not much behind the G2. You will be amazed by the crisp, sharp, high resolution screen after the HTC Vive. For training it's probably perfect until you get your G2. On the other hand, I am not familiar with the original Reverb, so I can not really compare the two.
  5. I use Oculus Tray Tool. I just updated it today. It now has an option to vary the bitrate for the Oculus Link. Before this you could only change the bitrate in the Oculus Debug Tool. I have always left it at zero because that seemed to be the smoothest. Now with this new OTT update I tried the 500 bitrate setting. While fps and frame time did not change at all head movement got jittery again. I set the bitrate to the lowest setting which is 150, and it went back to very smooth with no effect on fps. I have not tried the settings in between. Maybe give it a shot.
  6. Hit right Ctrl+Pause. This will give you fps. If you hit it the second time it will show you a bunch of more stuff. Frame time is in the second row starting with Obj, Trg and then frame time.
  7. Hey Falcon 87, hope you're good. I am now getting Encode Bit Rate Option. So is it better to put that to 500 or leave that at 0 and use encode resolution width at 3648? What are your system specs? To me bitrate 0 works much better than 500. Try it and see what it does. As far as I know, if you set pixel density in the debug tool, that will overwrite what you have set in DCS (I am using Oculus Tray Tool instead of the debug tool). Besides fps, frame time is also very important. If you can find a setting that keeps it below 20ms you won. Low level flying is just unbelievable with low frame times.
  8. Thanks a lot! I am now running between 45-90fps at 11ms in most cockpits. The Tomcat is at a solid 45fps at 22ms. It is amazingly smooth.
  9. What a difference! Setting the Vsync to Fast did the trick. Thank you so much jmuthy! Would you mind sharing your other nvidia settings? I'm getting a solid 22ms frame time and I wonder if it could be lowered without reducing the resolution.
  10. Yep, the "big" update hasn't helped me either. I am still getting the choppy, jittery head movements in the cockpit irrespective of frame rate and resolution settings. I have been trying different methods but nothing seems to help. Other games are fine, so I am also leaning towards a DCS issue.
  11. Are you guys able to get smooth head movement in the cockpit with the Quest 2? I am playing around with the settings in Oculus Home using 90Hz refresh rate. I tried all resolution settings from the lowest to the highest but the in cockpit head movement is the same throughout, it is consistently bad. I am getting high fps, low frame time up until 3920x1984 resolution, but while the flying is very smooth head movement is jittery. I also tried using the debug tool and the oculus tray tool as well, changing ASW modes but no luck so far. Lowering super sampling below 1.0 has no effect either. My nvidia 3D settings for DCS are still set for the Rift S. This might be an issue. Any help is appreciated. Thanks System: i7-8700k stock 2080ti overclocked 32 GB RAM
  12. Apparently there is a big update being released for the Quest 2 that will enable the 90Hz feature, higher resolution, and more control over your settings. Link will be out of beta as well. This is the version 23 update that people have been waiting for and probably the biggest update the Quest 2 will receive during its lifetime. Theoretically it was released yesterday, however, mine is still on version 21. They say if you keep your device on and plugged in, it should update itself in the next couple of days.
  13. I am new to the Quest 2. I am trying to get a similar experience to the Rift S by playing around with the settings but the Quest is kind of a nightmare with all this nonsense like a mobile app, facebook login, sidequest, virtual desktop, and oculus deboug tool. Man, try to figure this out. Anyway, I get better fps and frame time with the Quest 2 compared to the Rift S in DCS, however, the overall experience is way behind the Rift. Moving around in the cockpit is extremely choppy, and the picture quality is much worse than it was with the Rift. Yet the higher fps and lower frame time is very confusing. With these performance numbers the Quest 2 should be better but it isn't. I got this headset today and so far the only thing I could figure out is that this issue with the choppy movements is probably down to the 72hz refresh rate. Can you guys set it to 90hz and get a smooth, enjoyable play out of it in DCS? If yes how?
  14. I have the same system with a 2080ti. I am using the Oculus Link cable. I am getting around 30 fps and the frame time is 30ms. It is unflyable like this. With the Rift S and the Oculus tray tool I can get 80 fps and 12ms frame time which is butter smooth with using shader mods. Without the shader mods I get solid 20ms frame time and fps is between 40-80 which is still pretty good. With the Quest 2 DCS is unplayable for me too. The oculus debug tool does not change things that much. If I lower the super sampling to 1.0 I can get 60 fps out of it but it still sucks because of high frame times. I set the headset to 90hz but while I am in the Oculus app I only see 72hz in the performance HUD. I am really curious how people on Youtube got better results than the Rift S.
  15. I really like the new FM. Great work Hiromachi! Congrats! Flying this aircraft around is becoming a sexual experience.
  16. I agree with Shmal. I didn't have much time to test, but it looks very promising. It has never been so close to the descriptions in different manuals.
  17. Wow!! Thanks! I have been looking for this manual for years! Would be nice to find the whole book.
  18. Rossmum, I agree with you on everything you said. Could you please elaborate on that post by Skyrider? Did he upload some sort of manual? I am really interested.
  19. I do not have a goal here. My opinion has no impact on DCS Mig-21 development. Of course, I do agree, there should be a stall speed there, and a departure as well. My comment about the thrust to weight ratio is actually ended up in the wrong topic here. It was meant to be a reply to a comment in a different topic about the F-5 being a better dogfighter by default. Apologies for that (the wink at the end was there for a reason). On the other hand, if you are familiar with the book mentioned above, it is stated several times by pilots who flew both types, the F-5 and the Mig-21 at the same time, that they are almost identical when it comes to performance. It must be pointed out that the constant peg program flew the Mig-21F-13 which is way behind the Bis at low altitudes. There are implications that they also flew the MF, but that info is still classified. I got the info from Mig-21 pilots that the Bis was a beast with the 2nd AB when it is compared to the MF or the F-13. It is a totally different ballgame when your thrust to weight ratio changes so much in the Bis. If the F-13's performance is identical to the F-5, the Bis should be a much better performer even if the 2nd AB is only allwed for 3 minutes (no restriction in the sim, and not much performance gain in the sim either). Now, about how you exploit that thrust to weight ratio I have no idea. It is definitely not by pulling as much as you can. The emphasis is on the AOA. The aircraft WILL NOT STALL at 33 degrees on the UUA-1 instrument. There are a bunch of videos on youtube where the aircraft is at 33 degrees and the speed is only around 115 knots. There is no stall, no wing rocking, no wing drop. I have seen 90KTS on HUD footage! (Romanian Lancer which is basically an MF with the R-13 engine). The Bis manual is stating minimum speeds at around right there by the way (190km/h). The most surprising info is an F-13 flying against an F-14 where the 21 pilot slows down the aircraft to 70KTS with flaps! No stall. The F-14 still beats him though. In a different chapter there is a departure described way above the stall speed. You gotta forgive the devs for trying to figure out the whole envelope. Anyway, read the book. I can't wait to see the next update.
  20. The previous FMs were just as unrealistic. As soon as you hit 33 degrees the aircraft became uncontrollable and went into the ground. From Constant Peg pilots we know that the aircraft has excellent low speed characteristics. In the Red Eagles book one guy even says that only the F-18 had better low speed handling. I spoke to a guy who flew the early F-13 and the Bis versions as well. He says the wing rocking at low speeds were typical of the F-13 but he has never experienced it in the Bis even though it is in the manual. No wing drop either. On the other hand, he says dogfighting should be flown around 800km/h and above where the extra afterburner is at its max. At those speeds or above with the second AB on every maneuver can be flown without loosing airspeed even at max G (below 4000m AGL with thurst to weight ratio higher than 1). That's why you should be able to beat the F-5 every time in the Bis:smilewink:.
  21. I got this module on release in 2014. I seem to remember, that we even had the wing rocking at low speeds, or am I just imagining things?
  22. My only problem with the graph riojax is using here is that we don't know where it is from. It is just a page that does not mention aircraft type. Yes, there are lots of clues that it's for the Mig-21 like the 33/28 degree AoA which is typical of the 21. The UUA-1 instrument is also mentioned, but still, there is no proof this graph is for the Mig-21bis. The UUA-1 was used in every variant that followed the Mig-21PFM like the M, SM, SMT, MF, Bis, UM etc. On the other hand, there are no huge differences between variants when it comes to flying characteristics. You can find this graph in a simpler version in the real manual. It is a bit different though. It is clear that at certain M numbers there is no buffet at all before the stall. I still agree, the flight model is on a good track, though. Now, it might be a confusing or even a disturbing fact, but not even a real Mig-21 pilot can really tell you how the aircraft stalls, or how it behaves prestall and during a stall. I know a bunch of ex 21 drivers from Eastern Europe. Most of them flew the type for 20+ years. I asked them about slow speed characteristics and the answer is always the same: they simply don't know. They were not allowed to fly the aircraft below 400km/h. They did not practice stalls and spins in this aircraft at all. If you get hold of the real flight manual it does tell you that the minimum speed is 190-220km/h depending on thrust and flaps settings. However, the flight manual also states that flying below 400 km/h IAS is prohibited unless you are landing. In a dogfight the minimum speed with two missiles is 450km/h, and with four missiles it is 500km/h. There are only three nations that I can think of that flew the aircraft differently than what the Russian AFM allows. The first one is the Americans. Under the Constant Peg program the Mig-21 was exploited to its max and there are a bunch of interviews online about flying the aircraft at around 100kts and beating even the F-15 in a dogfight. Under Constant Peg they flew the F-13 and the MF versions. It must be kept in mind that the US pilots who flew in this program were way more experienced than the average guy in any air force even in the US. Here is a quote from an ex constant peg pilot: "Because its delta wing, it has good low speed handling characteristics. I have flown it around at full aft stick. It gets down to around 110-115 KIAS, and goes into a wing rock, but there is no stall break, no tendency to depart. Longitudinally, the airplane handles pretty well. In terms of gross maneuvering you can sure move the nose around. It's got good pitch authority. I think it's an excellent airplane over all. It has excellent slow speed characteristics, high roll rate, almost carefree maneuvering in terms of no tendencies for departures." The second nation is the Syrians. There are stories that they did exploit the aircraft to its maximum and happily flew it down to minimum speeds. Because of this they had more trouble with the engines than other nations and they complained about it. The manufacturer sent their engineers and test pilots to investigate why they had more wear and tear than other operators. When they realized that they flew the aircraft around way below the 400 km/h limitation they were able to dismiss their claims about manufacturing problems. This is from a Russian article: "The Syrians quickly realized that on the MiG-21 you can literally do everything without fear of stalling, because it is difficult to drive the MiG-21 into a stable spin, and it easily comes out of stalling. While flying at low speeds, losing speed to “zero”, falling on the tail in a hammerhead the engine worked stably on all “exotic” flight modes. At low altitude, the R-11 engine worked in afterburner operation stably at any low speed, up to zero, but there was the so-called “pulsating combustion” in the afterburner, which led to vibration of the turbine and, therefore, the compressor, especially the first stage. Cracks appeared in the compressor disk, in some cases leading to engine destruction." The third nation is the Romanian. Look at the Lancer's HUD footage during airshows. The AOA is maxed out at 33 and you can see speeds below 200 km/h. There is no stall or even wing rocking. Of course, the aircraft has much more advanced avionics than the original Mig-21MF and there might be an AOA limiter to avoid stalls. The wings and the engine, however, are the same as in the original airframe. I know there are the F-13 and MF versions, and R-11 engines mentioned above while we have the Bis with the R-25 engine in DCS. I know a guy who flew all versions. He says above 4000 meters they all behave about the same aerodynamically. Below 4000 meters the Bis beats all earlier versions in a dogfight. I asked him recently which version he would take to a guns only fight. His answer: the Bis. I might share our conversation next time. To summarize all of the above, yes it is incorrect that the aircraft can fly around at zero speeds without stalling in DCS, but in previous flight models the aircraft became uncontrollable way too easily which is clearly not the case. Hopefully the devs will get it right soon.
  23. Very interesting discussion gents. This graph was posted here a couple of years ago in a similar topic, and I have been looking for the book it came from for a while now. No luck so far. I have a bunch of original manuals in different languages, including Russian ones, but none of these manuals have this exact graph. A simplified version of this graph is there in every book I have, but not this one. This graph has much higher data resolution and more detail. My suspicion is that this page is from a book that goes into much more detail about the aerodynamics of the Mig-21 than the common flight manual. Since it is a pretty good quality scan, I suppose the whole book is out there somewhere with even more graphs about the aircraft that might help to improve the FM further. Does anybody here have the whole book by any chance?
  24. Привет gentlemen! Извините не говорю по русски. I am looking for this document for the Mig-21M or CM or Бис: Особенности пилотирования самолета на малых скоростях пожалуйста помоги Спасибо
×
×
  • Create New...