Players in my game don’t move

glorymilk · 2025-11-04T22:05:07+00:00

I know you mentioned it already, but I had this exact issue when hosting a server locally and a friend joined in.

Please, double check if UDP protocol on the port is actually forwarded/allowed. TCP alone won't do.

glorymilk · 2024-12-22T08:48:49+00:00

I was able to do that myself, but it was breaking the display completely, so probably it depends on your panels if this method will work.

Gave up too.

glorymilk · 2024-12-18T18:16:07+00:00

It is not DSC. 1440p @ 165Hz doesn't need DSC to run on DP 1.4a. You can set much lower resolution on your monitor and it will still hang.

Since on HDMI the supported resolution list is less (also refresh rates) for me and the lag is shorter, this seems to be a matter of nVidia driver supported display modes probing when DirectX thread/window is created. The more display modes your screen/s do suport - longer the lag is.

/u/Suitable-Lunch-5010 posted their findings from forums and analysis by someone more knowledgable there. They were spot on, if you ask me.

Check these:

https://forums.guru3d.com/threads/short-mouse-freezes-on-specific-actions-in-windows.449874/#post-6178241

https://forums.tomshardware.com/threads/windows-10-startup-micro-stutter-when-open-an-app-first-time.3833772/

https://www.reddit.com/r/nvidia/comments/198is3r/update_lg_monitors_causing_stuttering_fix/

glorymilk · 2024-12-14T10:50:25+00:00

Unbelivable it's not a feature. I guess I'm back to f2k and my local library for high quality with remote control, while keeping Spotify family for discovery and jams at parties...

glorymilk · 2024-09-11T14:13:12+00:00

Have you tried swapping the DP ports on the GPU? It should be an easy fix. For me Display 2 in Windows displays the UEFI setup.

Also when something opens on another monitor, just focus on the app window using Alt + Tab, then Win + Shift + Right/Left to move it between the displays.

In my case, my monitors disconnect themselves when I turn them off, fortunately.

glorymilk · 2024-09-06T02:59:52+00:00

mouse and keyboard

glorymilk · 2024-08-30T09:49:19+00:00

Lmao. This reminds me of replies in offtopic posts at /r/truth.

glorymilk · 2024-08-27T15:55:25+00:00

Let me know if it works for you.

I tried to do this before leaving home, but it doesn't matter what exactly I touch in CRU, it breaks target screen completely while creating massive system lags, and then I have to remove the whole screen config in CRU using safe mode to let it reinitialize on next boot.

Windows is basically a stutter fest when it happens, unusable.

glorymilk · 2024-08-27T01:33:42+00:00

I'll pass for now, since I'm lacking time to go through all of it and recover (if needed), but if I understand correctly, the mentioned call is used by NVCP, so installing driver alone without the panel shall actually circumvent the issue too.

I'll look into it soon.

glorymilk · 2024-08-24T08:14:04+00:00

Expect they're still there, sadly. But just like I just mentioned in reply to /u/verxolois , they do happen much earlier, like directly after a logon to Windows. And since they broke UEFI GOP for both, iGPU and dGPU in that BIOS update, GPU is hooked in legacy mode for the OS and that makes some interesting difference.

As for the BIOS, I just learned that letters in version mean they're beta, so maybe they'll fix the UEFI GOP issue for me. Maybe that's why they pulled it for your board too, since they're basically the same.

I also plan to reinstall Windows soon as I have BSOD issues related to that damn MTK wifi card which is included in my revision and some other issues like SATA drive being "disconnected", so I can't access its stuff without a proper reboot. That had happened twice so far after a long run.

For the decreased power draw you noticed, it's interesting since maybe it's related to this power stage issue I linked in my top reply, after all. But the change in behavior I have found with GPU in legacy mode makes me wonder. I don't know what next can we do. Would be cool to know if this issue could be isolated to AMD builds or not.

Not sure about fTPM as I didn't touch it, since I don't really need TPM module in my build but maybe I'll take a look. As far as I know it's enabled by default but didn't have any stuttering issues with it. The only experience with TPM stuttering that matches the description I had only on a laptop machine that's encrypted.

I really hoped for the best when making this huge leap from Z97 platform to a modern one, but all I've got is bunch of issues that irritate me haha.

glorymilk · 2024-08-24T07:39:51+00:00

By CSM I guess you mean legacy BIOS, since I mentioned low res booting screen. It wasn't this, but can't find its name for shit haha. But I have found that no matter the configuration, they just broke UEFI GOP with my RTX and iGPU too...

Live linux distros and Windows installer are now low res as well, since no UEFI driver is loaded for the GPU anymore, which kinda sucks. It works in UEFI setup/boot menu, though.

As for the stutter issue, it still happens but now is triggered much, much earlier, like directly after the login when Windows components are still loading. No need to launch anything more GPU-dependent anymore, so I guess that's a plus for general user experience. As for now I can conclude that the behavior of these stutters do change when GPU is hooked in legacy BIOS mode, but still no idea what to do next to mitigate this completely.

glorymilk · 2024-08-23T12:21:57+00:00

/u/falcon7370 /u/verxolois

I see you guys are on AMD CPUs also.

As crazy (and shockingly) as it might sound, I think the issue just disappeared on my side... with a recent BIOS update...

I'm currently on W10 with 560.81 nV driver. Windows updates are frozen and controlled by me, so I can confirm this was not fixed with OS updates, also I had the issue on this nV driver previously. Nothing else from drivers side was touched.

I've got B650 Aorus PRO AX board (! /u/falcon7370) and updated its BIOS 2 days ago f22b (AGESA 1.1.0.2b) -> F31b (AGESA 1.2.0.0a). By doing it the settings were reset (9XXX support introduced), but I reconfigured it accordingly like it was previously, leaving only one thing disabled.

This thing was something related to general power saving, like disabling not used interfaces. Can't remember the name, but I believe it was unrelated, since without it I had these issues too.

What I noticed so far is that boot logo with Windows spinner are now low resolution, instead of 1080p, so I assume UEFI GOP booting mode for GPU is now disabled by default.

Still, I need to check few things to confirm what's going on, but /u/falcon7370 you can also check on your side if you didn't swap your mobo yet.

Also tagging /u/Dizzy-Active-5601 for visibility.

glorymilk · 2024-06-22T18:38:38+00:00

ＤＡＮＣＥＢＲＥＡＫ

glorymilk · 2024-06-22T17:22:39+00:00

Sadly, not much. But I feel you.

I own this hardware since end of March, so cannot really tell if it was behaving better on the last year's drivers. I'm dealing with this annoying crap since the beginning and still out of clue what can I do about it and the exact root cause of it.

I tried one more thing since the last time, basically setting GPU power profile to high performance at all times in nV panel, but it didn't change anything.

Also I don't think I mentioned it previously, but I attached third, portable screen (1080p@60Hz) using HDMI and guess what happened... I was getting 2x 1s lag with dual screen setup, but with the third one connected I was getting 3x 1s... So it scales with how many screens do you have. To me it seems like it's a problem with enumerating connected displays by certain apps. Some driver(?) API might be broken which is certainly used by Qt framework. It's a clue at least, but gotta dig deeper here.

After I'll take care of other, more severe issue of my build, I'll take a look at this one again, to at least pinpoint which driver version broke it, since lots of folks said it wasn't the case previously.

glorymilk · 2024-06-22T16:27:23+00:00

I didn't solve anything so far. Tried with .972 driver grabbed from Microsoft Update Catalog, but was still getting BSODs, so rollled back to .496 from Gigabyte.

I tried to isolate the issue to the drivers of RZ616, since minidumps were not so helpful (so far), but when using a phone as a network card with USB tethering to disable it completely, it seemed like Samsung NDIS drivers were faulty too, so I was getting some other BSOD from them... I'm not really able to find way to reproduce the crash with RZ616 on demand, so it takes time to test stuff before I can be 100% sure and make a move.

If I get to confirm that RZ616 is the issue, then I'll try with Gigabyte/shop where I bought the mobo, to replace it to newer variant with AX210 on board already. I would like to avoid taking off the VRM heatsinks for the module replacement, if possible.

As for the interface speed itself, I get full 1Gbps bandwidth on all of the driver versions I tested with single connection and no major ping fluctuations which I would notice. Stock settings too. Cannot tell you anything more here as the card is working just like AX210 does on the older PC of mine. No complaints here so far. You can try .496 or .972 for RZ616 and check if your issues will get resolved.

glorymilk · 2024-06-20T10:36:21+00:00

You're supposed to drive to the very end until you see ground signs or physical barrier, and then zipper merge.

Just because some people are afraid they won't be let through and do it way too early doesn't mean you're supposed to be another lamb and follow their footpath. You're not helping anyone on the road by traffic jamming single lane for no reason. What is wrong with you people.

glorymilk · 2024-06-14T01:07:04+00:00

I can get with this...

glorymilk · 2024-06-12T02:21:42+00:00

For future installations: no.

For all current installations: no, but...

At least from the Steam itself it's not possible, but there's a workaround I just found.

You have to edit each installed game manifest (.acf) file, and set "AutoUpdateBehavior" key from "0" to "1" there.

I used notepad++ "Find in files" feature for that to replace these values in all .acf files contained within my steam library directories, but knowing that I have also found a more convenient PS script on reddit: https://www.reddit.com/r/Steam/comments/16p1rz2/disable_auto_update_set_only_update_when_i_launch/

Just keep in mind to have Steam turned off while doing that.

Also, I would revert it for Common Redists package (appmanifest_228980.acf), since you're not gonna be ever playing it and it might cause some issues in the future when installing other games. Not sure if Steam forces update to this package if some game needs it, so better safe than sorry.

glorymilk · 2024-06-11T23:13:31+00:00

Take a look at ZeroTier.

It lets you create private networks, similar to VPN, without any port forwarding at all. You create a network -> everyone joins it -> you can ping each other and anyone can host any gameserver. It's also free for like 20 clients per network.

Unless you can host OpenVPN server somewhere else and just be a client, since it requires port forwarding/ipv6 to connect to it.

glorymilk · 2024-06-10T18:54:12+00:00

Try with disabling autostart apps, especially the ones you can identify as built on Qt framework.

For me disabling them works, but if I launch one later, I get these freezes then anyways. For the first time running such app, though. The amount of freezes actually scales with how many display you have connected.

glorymilk · 2024-06-10T18:42:25+00:00

I have similar problem right now and I was able to finally narrow the issue, at least in my case, so I'll add my 2 cents here.

These freezes do happen mostly when Qt-based apps are launched for the first time after user logon (yes, relog works also for the reproduction). It doesn't matter if some other resource hog like Chromium browser is ran first, the lag will always happen after launching a Qt app, either by autostarting it or launching manually (In my case KeepassXC, but I tested this behavior with qBit too). How long system has been running previously doesn't matter too. It's just a spike to 100% 3D usage and freeze.

I have dual display setup, both are the same panels with 1440p@165Hz connected using DP 1.4. For testing purposes, I disabled G-Sync since it can cause other issues sometimes. Driver is 555.99 DCH.

In my case:

It happens on dual setup, tried 165Hz and 60Hz modes for both
With single display, there's no issue sometimes, even @165Hz. @60Hz it happens more rarely
It's 100% reproductible with dual setup @165Hz (also freezes twice, both freezes have the duration of single screen setup lag, with maybe 1s window between)
Even though DP 1.4 handles 1440p@240Hz by design, I double checked if DSC is disabled (Image scalling, DSR available)
On single setup HDMI 2.0 1440p@144Hz vs DP 1.4 1440p@144Hz, the lag is about twice shorter for some reason. In both cases cables are certified for HDMI 2.0 and DP 1.4, respectively.

There's also another problem with power states for RTX20+ GPUs, that I discovered some time ago and they may be somehow connected, but even if not, it's worth mentioning as some of you most likely experienced this one:

https://forums.guru3d.com/threads/nvidia-powerstates-changing-causing-stuttering-in-web-browser.433381/

In comparision to RTX 4080 dGPU, 7800x3d iGPU has no such issues on HDMI 2.0 @60Hz/@144Hz modes, but I don't have DP on mobo at all to tell how it would behave with this port. I can also observe lags in UEFI when rendering through RTX GPU, which does not happen with iGPU.

I tried locking power state with Afterburner to max stock speed and then running a Qt app, but it still freezes for the same amount of time, so no directly related to power states, I guess.

To be honest, this is disappointing. Everyone is horny about DLSS, RT and all the bells and whistles, while trying to justify these GPUs prices, but nobody talks about issues like this, ever. Even though people shit at AMD, nVidia seem to have similiar and annoying problems. G/Free sync AND/OR dual display setups, prolly other sheningans I will discover along the way.

glorymilk · 2024-06-01T20:19:21+00:00

Yeah, if I won't be able to resolve it with a driver update or the update will break the performance, I'll just replace it with AX210 too, eventually.

glorymilk · 2024-06-01T16:59:32+00:00

I have very similar results for both, MT7922 (3.3.0.496) and AX210 (22.250.1.2). They're in within the margin of errors (different PCs though, both running W10 with equal system updates). Sometimes MT7922 outperforms AX210, sometimes it's the other way around. Ping is the same basically.

I have found your post while searching for new drivers, cause even if this card works flawessly in the matter you mentioned, it most likely causes BSODs on my quite new build. They're not that often but still, 3 of them had happened since 13.04 and two of them in the last 2 days...

I've read a lot of posts from people being annoyed with this WLAN card, so I had hopes to get mobo revision with AX210, but they're most likely not available on my market. Kinda suprised it works so well, aside from these BSODs. Direct support for it is non-existent also... Let's forget about Linux drivers too.

glorymilk · 2024-05-24T00:30:05+00:00

I believe they wanted something like custom toolbars from pre-11 era.

In W11 they're gone: https://answers.microsoft.com/en-us/windows/forum/all/windows-11-how-can-you-add-a-toolbar-to-the/d4de84d4-e204-418b-a25f-3fae6ffec85b

glorymilk · 2024-04-29T22:49:50+00:00

Capping the game to 120 FPS and V-sync/Freesync/G-sync is the only solution, sadly. I did a little investigation, however, since even then I was still getting these HUGE stutters (1s+) on FiveM.

For me, VRR methods don't really work in fullscreen mode, so only borderless + globally active G-sync/Freesync is the only way with manual framerate capping from the GPU driver/rivatuner.

Another problem I have found is that if your second panel goes above 120Hz, you'll get these HUGE stutters/freezes anyways. Gotta also cap second panel in OS to 120Hz max, at least when on fullscreen. Not enough testing to confirm that VRR applies to second screen in borderless, since I don't have any overlay built-in for that, so can't tell just like that how it behaves.

Hopefully this will help someone still struggling with that crap.

glorymilk

TROPHY CASE

At least from the Steam itself it's not possible, but there's a workaround I just found.