Both pcsx2 Vsync and NVCP vsync can fix that tearing without causing any new stutter, I see no difference between either method. ini change, these changes introduce good old screen tearing. ini and set EnableVsyncWindowFlag=enabled and also must set Aspect Ratio in GS window to "fit to window/screen" OR to "16:9", meaning the actual issue is when it's set to 4:3 standard (but also, those two other options still need the. To summarize: to fix stutter for me, I first must edit. After actually disabling it, the method no longer worked. ![]() ini didn't save changes and it was actually still enabled. Just enabling pcsx2 vsync (plus the aforementioned) even without ws_popup?Īctually no, I meant to test without ws_popup too to see if it was needed, and thought it wasn't, but apparently the. No no, in window mode no tearing no matter what. are you saying that "fit to window/screen" gets you tearing EVEN in windowed mode? Until then I'll have to be using version pcsx2-v-windows-x86 to avoid this issue unfortunately.And. I should be buying a discrete GPU when prices return to normal in my country. Perhaps disabling the use of the d-GPU in the BIOS could allow you to reproduce the issue hopefully? Otherwise, we would need a developer with an Intel 6th gen+ desktop CPU with integrated graphics to try this eventually. If you use a laptop with an Intel CPU I'm not sure whether selecting "Intel GPU" in the program isolates the influence of the dedicated GPU chip or drivers. There is no way to use a discrete GPU if I don't have one connected to the motherboard. I suppose this change has waken some kind of incompatibility with the Intel video drivers.Īnyway, I use an i5-10400 which is a desktop CPU with integrated graphics. Just to remind you that issue seems to have started with version pcsx2-v-windows-x86, which introduced improved overlay statistics. I also had the opportunity to test PCSX2 with a discrete NVIDIA desktop GPU and couldn't reproduce the problem there in any of the PCSX2 versions I had tested before, so I really suspect it's related to the Intel video drivers. I downloaded version pcsx2-v-windows-64bit-AVX2 and curiously the first time I tried it it didn't freeze the emulator, but then by the second turn I was able to trigger the problem again unfortunately. Hello again! So I went and did some more testings related to this issue: Anyway, I reinstalled the December 2021 drivers (version 30.0.101.1191) and could still reproduce the bug in PCSX2, sadly. I suspect a Windows update may have reverted the drivers to an older version. But I'm pretty sure I had already updated the drivers for the ones released in December 2021 (which are the latest as of today). The following information was included with the event:Ĭuriously by the time I opened this issue I was using display drivers version 27.20.100.9316, which is from March 2021. If the event originated on another computer, the display information had to be saved with the event. You can install or repair the component on the local computer. Either the component that raises this event is not installed on your local computer or the installation is corrupted. "The description for Event ID 0 from source igfxCUIService2.0.0.0 cannot be found. But I do have some messages about Intel graphics around the moment the the bug showed, they read something like this: I guess I would need some assistance here. I don't know exactly what to look for in the event viewer. I've tried to trigger the bug with version pcsx2-v-windows-64bit-AVX2 and unfortunately got the same results. ![]() Windows 10 (64bit) If Linux - Specify Distro I can't seem to be able to reproduce the problem with previous versions such as pcsx2-v-windows-x86 Operating System I've tried it with pcsx2-v-windows-x86, pcsx2-v-windows-x86 and pcsx2-v-windows-x86 versions. ![]() It was supposed to work normally as it used to happen some versions before. ![]() Reproduction StepsĪll options are default except for the vertical sync mode set to "Standard" and "Always ask when booting" for the ISO selector. Issue seems to have started with version pcsx2-v-windows-x86, which introduced the enhanced statistics display. However, I don't know how the v-sync option could affect this menu. I'm also experiencing random crashes when opening the graphics settings. I can no longer interact with the system except by resetting or powering off the computer. When the bug is triggered the only thing that still works is the mouse cursor. I've tried it with games such as Silent Hill 2 (USA) and KoF 2003 (Japan). Hello! I'm experiencing a weird issue in which the emulator will freeze the whole system if I go full-screen with v-sync turned on (either standard or adaptive modes).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |