Jump to content

SAS_Storebror

Members
  • Content Count

    1131
  • Joined

  • Last visited

Everything posted by SAS_Storebror

  1. I won't call it an "issue" either, but my GTX 970 is definitely on it's edge in WQHD (2560x1440) in IL-2 Great Battles and if I can win another 10FPS just from lowering a setting I will never notice (mind you, the crispier shadows in cockpit are absolutely unnoticeable once your engine is running and the cockpit starts shaking), I will just use that option. With a GTX 1080Ti and/or a Full HD (1920x1080) monitor and/or a monitor with max. 60FPS I would probably never notice any "issue" either. Cheers! Mike
  2. Frankly that's nothing you will notice 99.9% of the time. I've been wondering the same thing about the mirrors by the way. Even at lowest setting, I get exactly the visual feedback which made me take the mirror with me. Sure, it might look a tad more "crisp" on maxed settings, but is that worth another 10FPS drop? Prolly not. Cheers! Mike
  3. Definitely not the plane shadows on the ground. Maybe smoke shadows, no clue. I gave it a try here: https://www.sas1946.com/main/index.php/topic,57904.msg639104.html#msg639104 If you can spot a difference, let me know. Cheers! Mike
  4. ...which gets you horrible tearing again if you don't have a G-Sync monitor. And if you do, you should enable V-Sync nevertheless, this has been stressed more than enough now me thinks. Cheers! Mike
  5. V-Sync stutter below 30FPS is true for non-G-Sync monitors. It must be stressed though that when you have a G-Sync monitor, you should enable V-Sync nevertheless. It will not cause stutter below 30FPS (because the sync will take place in scanouts and G-Sync will start to double frame rates), but it will avoid tearing. If you have no G-Sync Monitor, it's best to use Fast Sync if your GPU supports it. If you have no G-Sync Monitor and your GPU does not support Fast Sync, you should still use V-Sync (otherwise you get tearing all across the space) and rather reduce ingame settings in order to maintain 60FPS most of the time. Cheers! Mike
  6. Thanks for the config file hint, will give it a try. Concerning input lag with VSync, I somehow get that input lack matters much for first person shooters and tearing comes second, but in the CFS genre it feels odd when someone accepts tearing just to avoid a possible 7ms input lag. Cheers! Mike
  7. As you can see from the link I've posted earlier... https://forums.blurbusters.com/viewtopic.php?f=5&t=3441 ...limiting FPS ingame slightly below the G-Sync range's top end is the preferred and most recommended setting. It avoids touching the G-Sync boundaries and usually comes with no input lag (compared to Nvidia Control Panel FPS limiter, which gives 1-2 frames input lag). Unfortunately IL-2 Great Battles has rather coarse FPS limit settings and most of them don't fall within the optimum distance to common G-Sync boundaries. For instance, with common G-Sync max. rates of 60, 144 and 165 (OC'ed) FPS, ingame limits of 56, 58, 140, 142, 161 and 163 would fit perfectly, but we have none of these. Quite possible. You still risk facing tearing at the bottom of your screen when frametime variances become too heavy. The key message you need to understand is this: Enabling V-Sync doesn't hurt. Disabling might though. Cheers! Mike
  8. Where do I have to file my application? Great stuff, thanks for sharing! Cheers! Mike
  9. This would mean your last driver update was back in 2015, because that was when V-Sync became optional. Forgive me when I say Cheers! Mike
  10. What's funny is that you are the one making fun about other's understanding of G-Sync... ...while at the same time you are the one who shows a lack of understanding how it works. Let me shed a light on this: Enabling V-Sync does not lock the Frame Rate within it's range. It does not incur any input lag either. With G-Sync and V-Sync off you get tearing all over the place. I think we all agree on that - at least I hope so. With G-Sync on and V-Sync off, this is what you get: Within it's range, G-Sync will disable most of the visible tearing.However, with disabling V-Sync you also disable G-Sync's frametime variances compensation. As a result, you get tearing when frame times suddenly vary a lot, plus you get tearing at the bottom of the display in the upper FPS range plus in the lower FPS range (<36), frametime spikes can occur which will inflict tearing all over the screen. You simply won't want that, neither of it. Outside it's range, G-Sync will automatically be disabled.Since in this setting you have V-Sync disabled too, you will therefore get tearing all across the screen when frametimes exceed the G-Sync range. With G-Sync and V-Sync on, this is what you get: Within it's range, G-Sync will disable all tearing.This is because G-Sync's frametime variances compensation is active now (V-Sync is on). The frametime variances compensation avoids tearing when frame times suddenly vary a lot, plus it avoids tearing at the bottom of the display in the upper FPS range plus it avoids tearing in the lower FPS range (<36), where otherwise frametime spikes would occur which would inflict tearing all over the screen. This is what you will want. Outside it's range, G-Sync will automatically be disabled and the Frame Rates will be locked to the lower/upper limits, e.g. to 144FPS.You might say that this is bad, but it isn't. Remember: You only revert to V-Sync mode when G-Sync range is exceeded. Frametime compensation with V-SYNC “On” is performed during the vertical blanking interval (the span between the previous and next frame scan), and, as such, does not delay single frame delivery within the G-SYNC range and is recommended for a tear-free experience. You must understand that when you turn on G-Sync, the meaning of the V-Sync setting is not the old one you used to know. It much more turns into a "frametime variances compensation" setting, and this is something you will definitely not want to miss. Some relevant links for those who are interested: https://www.blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/ https://forums.blurbusters.com/viewtopic.php?f=5&t=3441 Cheers! Mike
  11. No. In that case you'll get tearing. You probably just haven't noticed it yet. Let me laugh back. The important point is to enable G-Sync and V-Sync in Nvidia Control panel. Cheers! Mike
  12. Sorry to say but this is definitely a VSync issue, nothing to do with stutter. Turn on VSync in Nvidia Control Panel. I know you said you tried, but try again please. Choose BoS on the programs tab and turn it on there, don't use the general tab. Cheers! Mike
  13. Ja gute Frage. Ich hab's aus eine Keyboard-Map, habe aber auch gerade kein IL-2 in der Tasche Da es sowieso nichts bringt: Vergiss es einfach
  14. These "one in a million" issues are not worth worrying about. I've once face the issue that I couldn't get back to my plane after spawning online. This was the sequence: I've bombed an enemy airfield, flak got me so I bailed out. Then I've watched a friendly player on externals attacking the same airfield. Finally I decided to refly. While I was in the aircraft selection menu, I could still hear my teammate's external sounds in the background. Upon spawn, I didn't see me in the cockpit, instead I still saw my teammate on externals. Hitting "F1" didn't get me into the pilot's seat, instead I saw my "old" pilot still hanging in his chute. Cycling through externals (Shift+F2) I could see my "new" plane parked on the ground, with the waiting pilot inside. I just couldn't get to control it for my life. Respawned once more, everything was fine. Could I reprocude it? No. Should I be worried? No. Cheers! Mike
  15. 2000m is absolutely sufficient for this. The last time I've dropped a 1.8ton egg from a Stuka, I've started to flip over at slightly above 1000m. Shorter time to aim, but still sufficient. You don't need to drop that massive egg as close as you have with 250kg bombs, so that's not that much of an issue. Cheers! Mike
  16. Thanks for the morning snigger Cheers! Mike
  17. Not at all but it's fun to fly nevertheless, in 1946 that is. Add me to the preorder list. I hate those italian spaghetti planes, so I have to have them all Cheers! Mike
  18. Hm okay, so it's solely up to the users to create, join, leave, edit squads and an admin can't do that. That's a bummer. Thanks for the answer nevertheless Cheers! Mike
  19. Ah sehr schön. Danke für den Link! Viele Grüße, Mike
  20. I have a potentially stupid question: How do I add a squad? Currently the Squad list is empty and there seems to be no way to start a new squad or add players to a squad, so I don't know where to start. This is what the main menu looks like: If I click the lower "Squads" link or the "Change" link in that line, it takes me straight to the next image, if I click "SQUADS", I get this menu inbetween: Whether I click "Squads" or "Change" here, takes me to this: - No chance to add a squad - I can search for one, but as none exist, the search result of course remains empty. In the player profiles I see this: Can't edit any value here, so no chance to join a squad again. Cheers! Mike
  21. Sieht leider so aus als ginge das nicht. Man kann in einigen Flugzeugen mit Alt+C den Funkkanal umschalten, aber in den Flugzeugen, die eigentlich gar kein Funkgerät haben (I-16 z.B. hatte in Echt selten bis gar kein Funk an Bord), funktioniert das logischerweise nicht, und trotz Abwesenheit eines Funkgerätes bekommt man permanent das Geplärre ins Ohr. Viele Grüße Mike
  22. ...and this is where you didn't get Galileo's inifite paradox yet Cheers! Mike
  23. I think we should meet in a pub and try that with beer. Pale and brown ale I'd suggest. And yes, that siggy just caught up with me lol Cheers! Mike
×
×
  • Create New...