Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
No stuttering
Problem is that the game cant handle high polling rate fpr mouse, a console bad port.
I found the game just before the last x-play stresstest and it ran fine, no lag, no mouse issue, nothing.
Hardware back then:
5800X3D
32GB Ram
RX480 (with a RX580 Bios mod) [don't ask...bad story]
Crosshair K70Lux Keyboard
Razer Deathadder V2 Pro @ 1kHz polling
PreSonos iO24 Audio Interface
Now it's released and I got issues with "move your mouse to get 0 FPS unless you hold your aim button, aka rightclick, down". When this occurs, the game actually stops utilizing the GPU, you can see in taskmanager that it goes down vom normal uzilisation down to 0-7%.
My Hardware now:
same 5800X3D
same 32B RAM
new RX 7800XT
new AKKO 5075B+ Keyboard
new Glorious Model D Pro Wireless Vice Edition @ 1kHz
new Roland Bridge Cast Audio Interface
And yes, I testes wired and wireless on the mouse, it's the same.
Also different is the software:
I don't use Wallpaper Engine anymore, DisplayFusion got 2 updates since back then, I got a pen display and it's driver but unplugged during gaming (even closed the driver and service, doesn't matter), installed Clip Studio Paint Pro 3.0 and G-Drive to back up my bad drawings. And of course I also stopped G-Drive and DisplayFusion to test if they are the issue...they aren't.
What I noticed though:
First starting the game and going right into it without opening any menu, everything works fine in Albion, but as soon as I open ANY menu, close it and THEN rightclick to aim (which is just a rightclick in Albion) the issue starts to happen. This further tells me, something is wrong with the game and it's menus.
It would be incredible if they allowed us to switch from DX12 to DX11 willingly.
I think there's a few reasons for the stuttering, that ALL contribute to it.
- Mouse Polling Rate (Some players reported that turning it down to 1k fixed their stutters, however im stuttering WITH 1k)
- Client Information Being Sent to Nexon (This is a setting that in almost every game is OPTIONAL, unfortunately is a requirement for TFD)
- Bad Optimisation (Game even on low settings, runs horribly. Getting above 100FPS is DIFFICULT, even on the lowest settings, and I have a 3070ti, it's not like I have a bad PC)
- DX 12 (Known to cause stuttering in a MOUNTAIN of games, some of them: Fortnite, COD, Ready Or Not, Last of Us Part 1)
- Shader Pre-Compiling (Every game I've ever played with this exact thing, has stuttered continuously. TFD is no exception it seems.)
I think all of these are factors towards stuttering, and there isn't a way to make them ALL minimal / nullified without the help from devs directly contributing in form of optimisation updates and etc
Windows + TAB and select TFD.
After that, 0 stuttering !
I can finally enjoy playing it !
What is TFD?
Oh okay, thanks. I have to wait, because the server isn't responding
Anyway, I did a bit more testing on my end and found something...weird, so it might be a one time thing.
When I started the game today, EVERYTHING was fine, even opening a menu didn't cause issues. Then a friend wanted to play and messaged me through steam. Still fine until here.
I "tabbed out" to start teamspeak, joined and the issue was back there. Holding rightclick (aim) and all smooth, only moving the mouse bringes the GPU utilization back down.
My current thinking is:
The game has in some circumstances issues with properly refocussing.
It is as if the game is in some kind of inbetween state, where it is in focus unless you move your mouse. That it goes back to normal when you aim might indicate that the button press/hold temporarily force focusses the game, temporarily fixing the issue for the duration of the button press.
Why lowering the polling rate can some times be a workaround is beyond me though.