Jump to content

Glide

Members
  • Posts

    767
  • Joined

  • Last visited

Everything posted by Glide

  1. I just noticed the speed brakes have gradual opening. Thank you very much! I was wondering why my Viper wouldn't slow down.
  2. Excellent post! I am using SSAA x2 (with Antialiasing -Transparancey = x2 supersample) with SSLR on my 1080Ti. At 4k I don't really notice the jaggies but, this setting is very nice. Also, SSAA 1.5 is much lighter impact than SSAA X2, and is great if you absolutely need some AA.
  3. @Fakum In your screenshots of the NCP, you are showing the Global settings tab. Sorry if this is obvious, but under the Programs Settings tab you will see a dropdown. Under this dropdown you will find DCS Black Shark. This is a profile for the game that you should use WHEN you are a pro at this. Here's the drill: get your NCP settings the way you want them. Then Restore the global defaults by clicking the Restore button. Then go into the Program Settings tab, and select DCS Black Shark from the dropdown menu. Then set up your NCP settings just as you had them in the Global Tab. This way, you can restore the global defaults anytime you wish, but you won't lose your DCS settings on the Program Settings tab.
  4. Sorry for that confusion. That was very "theoretical". It would make more sense for VR to set Max Frame Rate to 90 and 2D to set it to 60 with vsync off. Forget about Max Frame Rate, anyway. With your hardware, this should be OFF. And turn off all Gsync and Vsync in DCS, NCP and in the monitor control panel if you have a Gysnc monitor. You will see DisplayPort Compression 1.2 and/or 1.4 in the monitor control panel. This is required to be ON for the higher refresh rates in the monitor to work, AND you need a DisplayPort cable. Otherwise, it will probably default to 60hz all the time. The newer HDMI 2.1 monitors I have no experience with. At this point, DCS is pumping frames as fast as it can go, and your hardware can keep up. If you see that screen tearing mentioned, you can turn ON vsync in DCS without changing anything else, and it should sync at the native 60 or 100 hz of the monitor. If it drops frames with vsync ON, you will see the odd tear go by. This is the simplest way to test vsync. Alternatively, leave vsync OFF in DCS, and turn vsync ON in NCP. This should behave exactly the same way as using vsync in DCS. Nvidia recommends Adaptive vsync if you have vsync ON and are still getting tearing. Haven't tried it. FAST is supposed to try for higher increments of sync but drop frames if it can't. My experience with FAST is that the highs are higher, but lows are still below 60 fps. Gsync is supposed to flip this around and let the monitor tell the card to sync at 60 or 100 or 122, etc instead of the card detecting the monitor rate and syncing. I hope this helps.
  5. Yeah, there's no guarantees. My monitor actually goes from 30 to 144 but it's "native" at 60hz, and DCS will ignore any vsync setting if it can't keep up. And yes, that's where the 58 comes from -- some number just below the max refresh rate of your monitor. BTW, 60 comes from the old cathode ray tubes and the fact that 60hz is the resonance of power in the US. Tesla chose 60 for the resonance. I digress.
  6. Screen tearing is what happens when a the card drops a frame when it shouldn't. For example, if you use Low Latency Mode = Ultra, your card will not queue any frames. However, if a frame drops for some reason you get a tear running across the screen. Google is your friend.
  7. I have trackir too, but I never do anything with refresh rates there. Sorry for the confusion. I also don't mess with autoexec.cfg for settings. Remember, film is 30 fps, so 60 fps is twice as fast as a movie theatre. They say the human eye can't detect differences after 30fps, so that's why 60 is a safe number. VR guys need 45 per eye or 90 fps to keep from being seasick. More than 60 fps doesn't add any value for 2d, so no reason not to enable Vsync and have 60 fps all the time.
  8. About Gsync, I had a gsync monitor for 1 day before I gave it to my son. It doesn't make sense to have Gsync on and Vsync off or vice versa. You are either limiting frames or not limiting frames. If you are getting consistently over 60fps with your card, you don't need to use sync in 2d. However, it doesn't hurt to use vsync and lock frames down at 60 fps in 2d. Vsync ON, OFF or FAST are the 3 main choices I see. I also can't tell if DCS vsync is better than NCP vsync. So, I would experiment with DCS vsync ON - all NCP Vsync/Gysnc off, DCS vsync OFF - NCP vsync/gsync ON, and DCS vsync OFF and NCP vsync FAST.
  9. These are likely shaders being recompiled or swapped from shared to dedicated GPU, but I can't confirm. You can see this behaviour reflected in Task Manager. Watch for copy activity on the GPU. They usually coincide with the stutters. Not so. SSAA works for any resolution.
  10. As mentioned OC, not supported. FXAA is post processing AA (ie AFTER DCS has finished rendering) and is easy on FPS, but don't use this with MSAA or SSAA. Anti-Aliasing - Transparency: 8x (supersample) This doesn't make sense because it should match the AA choice in DCS. Since DCS has 1.5x and 2x, only 2x supersample matches. This should be either multisample or 2x. Max Frame Rate: not sure why you want this at 90fps. If your system was having trouble maintaining 60 fps for example, you would set this to 58 fps. That's like saying, I can't quite make 95 fps, so limit me to 90 fps. Should be OFF. Texture Filtering just does some presets. LOD is old and doesn't do anything on your card. Trilinear optimization only works if you use Anisotropic Filtering in DCS.
  11. @Fakum The only thing I would suggest is turning OFF vsync entirely, and setting Antialiasing -transparancy to Multisample in the NCP. This has to match your choice of AA in DCS. Your settings are almost identical to mine. I have terrain object shadows OFF now. That saves some FPS. At your resolution you can get by with MSAA x2 and that will save FPS. Your 2080Ti has 11GB of VRAM, correct? I am guessing you don't have stuttering on Caucasus or PG, but you get it on Syria? Syria will push our 11GB cards into Shared GPU memory, and this causes all kinds of stuttering for people.
  12. I believe MSAA is best for fences since they are mostly just edges. SSAA does the entire texture surface for jaggies.
  13. You many need to do some mapping. Chuck's Guides have more information on tuning the axis during setup.
  14. I just got caught up on that LOD stuff the other day myself. Profile Inspector on Github. There's a digital profile for it under the dropdown. Look for Black Shark. This is my first time trying it. Be careful to reset any "non-standard" settings in Profile Inspector if you decide to go back to using NCP. I am nervous that the NCP will screech at trying to read the settings after Profile Inspector changes them. Use at own risk.
  15. Thanks for that tip! I'm using 2x SGSS to match my SSAA x2. Looking good!
  16. Technically, @Taz1004 is correct. However, artists like to start with 32bit so they can go smaller if they need to. They also run 24 core E5's with max everything, so they may not see the same urgency about performance.
  17. I believe with your hardware LOD-clamp does nothing anymore, but that is the correct setting when using AF with older (Fermi?) cards.
  18. First successful AAR in the Viper today! Some tips. Forget the tanker and fly your normal climb out, just like it's another beautiful day on the job. When you reach 15000 @270 kts note your coordinates and place a waypoint there. Add a waypoint for the tanker at the same spot. This way you can adjust the location of the tanker so that you are first to the pumps as soon as you arrive at altitude. After making a couple of successful contacts, I had a good idea of where I needed to be relative to the tanker. I used my peripheral vision to keep the taker in place while I concentrated on my flight instruments. Another week and it should be routine.
  19. I've been trying for about a week now. I have managed to get some fuel to flow, but I can't stay connected long enough yet. I got sucked into the intakes last night too.
  20. Has anyone else noticed the tanker veering to the left just as you get into contact position?
  21. Lots of interest in skins: https://www.digitalcombatsimulator.com/en/files/?PAGEN_1=2&set_filter=Y&arrFilter_pf[filetype]=&arrFilter_pf[gameversion]=&arrFilter_pf[filelang]=&arrFilter_pf[aircraft]=564&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter
×
×
  • Create New...