EPTSimple Questions Simple Answers - Page 620
| Forum Index > Tech Support |
|
Craton
United States17303 Posts
| ||
|
Gullis
Sweden740 Posts
I will leave it on 144hz for now then  | ||
|
Craton
United States17303 Posts
As I understand it, VSync will basically prevent the frame buffer from updating until the monitor refreshes. This solves the issue with tearing (the appearance of a slightly disjointed image where one part of the screen is slightly off from the other), but adds additional delay to you seeing the image. I believe tearing is primarily an issue when your rendered framerate exceeds your monitor's refresh rate. https://en.wikipedia.org/wiki/Screen_tearing For some people that delay is more of an issue than tearing. Technologies like G-Sync try to get the best of both worlds, mitigating tearing without increasing delay. In my opinion you should just try both ways and see what you prefer. | ||
|
ZapRoffo
United States5544 Posts
I didn't know if that's also just a symptom of the battery going, that it's not reporting its capacity correctly (was going to just order a new battery), or if there's likely something wrong with the computer's interaction with the battery and it would shut down at 85% of a new battery too and thus be not worth it (the replacements for my model are like $50 min from random sellers). Anyone know on this? | ||
|
Cyro
United Kingdom20343 Posts
144hz is much better than 60hz for displaying both low and high framerates. -------- I believe tearing is primarily an issue when your rendered framerate exceeds your monitor's refresh rate. A static refresh monitor at say 144hz will refresh every 6.94ms Frame taking 5ms or 8ms it doesn't matter, it's not 6.94ms so the amount of frames shown per refresh will not be exactly 1. 5ms frametimes would show 1.39 frames per refresh and 8ms frametimes would show 0.87 frames per refresh. Tearing can be visually annoying with a low refresh rate and very high framerate (e.g. 60hz, 200fps) but the perceived effects (even if not directly noticed and attributed to tearing) are at their worst when the framerate is at around 70% of the refresh rate. A 60hz display can show 30fps or 60fps very well but it cannot display the middle of the range between them properly, instead of a frame every 1 refresh or every 2 refreshes you have to deal with a new frame every 1.3, 1.5 or 1.7 refreshes and that causes a lot of inconsistency in motion and input. That's the main thing that gsync fixes to get the "wtf smooth" motion at a range of framerates, if the frame isn't ready then it will idle until the frame is ready instead of partially re-refreshing the old frame. Higher refresh rates also fix that problem - 42fps on 240hz is way smoother and more consistent than 42fps on 60hz - but more indirectly through brute force and they can't remove it completely without gsync. If you want to use Vsync or Gsync for any reason, this is a good guide: http://www.blurbusters.com/howto-low-lag-vsync-on/ The problem for vsync off is essentially just aliasing between two different and mismatching update rates since one is variable and the other static, a lot of similar problems exist in other areas. Adaptive sync techs turn the static update rate into a variable one and pin the two together on a frame by frame basis so that there is no aliasing any more. This is the best video that i've seen on the subject: Examples of vsync off, vsync on and gsync across the most problematic framerate ranges. At the edges of the pan the FPS is around the refresh rate, panning across the middle of the scene makes FPS fall into the red zone where vsync off/on both suck but gsync is perfect. Side note; sc2 microstutter doesn't apply since they're doing it on a paused replay. It's a good watch when slowed down to various speeds as well, may be even easier to see that way; make sure to view in full screen as well. | ||
|
Jonoman92
United States9110 Posts
| ||
|
felisconcolori
United States6168 Posts
| ||
|
Dangermousecatdog
United Kingdom7084 Posts
| ||
|
Jonoman92
United States9110 Posts
| ||
|
OsaX Nymloth
Poland3244 Posts
| ||
|
arb
Noobville17922 Posts
Sometimes when playing games(actually only when playing games) sometimes the monitor will lose signal and wont reconnect until i restart, that or the entire screen turns a milky white until i restart CPU not getting too hot, what else could it be? | ||
|
Simberto
Germany11969 Posts
| ||
|
arb
Noobville17922 Posts
my graphics card isnt even 2 years old yet, (960 Nvidia) | ||
|
Craton
United States17303 Posts
| ||
|
arb
Noobville17922 Posts
On October 16 2017 16:07 Craton wrote: Have you tried replugging the monitor when it happens? Yes, nothing happens. Friend suggested since im not using an actual HDMI cable(using the old fashioned big block thing) I should go buy one of those to see if its just the port being bad | ||
|
Artesimo
Germany627 Posts
When booting today as soon as Windows startet my screen got black with some weird artifacts. I had this before when the Ram on my old graphicscard died... Bootable option would be preferable, right now my PC boots fine but I expect the problem will return. Does is there an option to bring back the old dialoge to boot in safe mode under win10? I have an SSD and already read that the F8 method doesnt work anymore because of the short bootng times, but all the instructions I find for it either require you to be able to boot windows in the first place (how the hell is that supposed to help me when a driver gone rogue?!), and using a windows CD doesnt work either, the option for booting in safe I see in the tutorials online are flat out missing and the command promp doesnt work. | ||
|
OsaX Nymloth
Poland3244 Posts
It's pain in the a... As for the main question: confirm on different drivers, just to be sure. There might be some programs that are able to correctly test VRAM. Or just any gaming should be problematic if that's the issue. | ||
|
Artesimo
Germany627 Posts
On October 20 2017 20:20 OsaX Nymloth wrote: You can access the boot options in either Windows (yeah, wtf) or.... boot your PC, wait a sec or two (see the loading circle? good) and force-restart. Repeat up to 3 times till automatic repair comes up instead of normal loading of OS. Then you will be able to click through few levels of menus before being able to chose option which leads to safe mode. It's pain in the a... Yeah, the 3 times thing doesn't work either reliably for some weird reason. No matter how I did it it wouldn't work, but after many attempts suddenly I could boot in windows just fine - only to get the ability to safe boot AFTER I was able to boot just fine and shut the PC down normally... had this issue before on a different machine, while on a 3rd machine the interrupting boot 3 times worked like a charm. Maaaagic. As for the main question: confirm on different drivers, just to be sure. There might be some programs that are able to correctly test VRAM. Or just any gaming should be problematic if that's the issue. My problem is, that now it’s working just fine, so if the VRAM is indeed faulty, it doesn't seem to be a big issue. With my old graphics card it was rather easy since it would always show weird artefacts / blackscreen when booting in windows. I could then proceed to enter safe mode, remove the driver, reinstall it, chose the lowest resolution and move it up gradually until it failed again, which was rather quick. With this one it is not that easy, currently everything seems to work just fine, including gaming. So either the issue wasn’t the graphics card, or as I said it is only a small one. I would need a program of the sorts of memtest86 which allows me to test the whole 4GB of VRAM in a same manner, otherwise it’s very difficult due to memory management and other technologies that graphic cards use these days. So far all solutions I found where either unsuited or outdated or scrappy workarounds like having multiple instances of video memory stress tester which unfortunately produces inconclusive results. | ||
|
Ropid
Germany3557 Posts
| ||
|
Artesimo
Germany627 Posts
On October 20 2017 22:17 Ropid wrote: Do you also have problems while in Windows, or just at boot? I only encountered the problem this morning when booting. Turned on the PC, went afk and came back to the monitor not getting a signal. I checked the cable, rebooted and either while Windows was booting or after it fully booted (so either after the loading bar was done or during it) I got a black screen with a thick grey horizontal line with some artefacts around it (some pixelated pattern that looked a bit like tilted As, also grey but without clear edges and some discolouring at the edges. I am not sure if I would been able to log in since there is no longer a login sound (now I added one for further debugging, so if it happens again I can at least test if it’s just a graphical error). I did what should have resulted in a login but I can't tell since the screen didn't change. I got the same artefacts when my old graphic card died, even though they filled the whole screen back then, so I suspected that being the problem. Also up until windows loading/ windows being loaded the screen was normal, like post bios message etc. being displayed properly. I then tried to boot in safe mode and in the process, the error stopped appearing. Since then windows boots and everything gets displayed properly. I also tried playing some games and could do so without any problems, which isn't a guarantee though. Because of this I am looking for a program like memtestx86 for VRAM since another theory of mine was that it was a issue with the cable, even though the problem only disappeared long after I readjusted the cable. Last time I checked everything worked fine. I would rather not wait until the problem occurs again since my graphic card loses its warranty in ~20 days and I also don't want to send it in just because of a suspicion since I would have to ship it to the manufacturer at my own cost + a possible fee for checking the card. | ||
| ||
