Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
But given that the game is pretty much capped at 40 fps due to the engine, I dunno if it does anything.
Any chance there are any devs reading this, that could enlighten us?
V-sync.
And about native cursor setting - it enables rendering of cursor through OS natively, if you turn off it, then cursor will be rendered through game and its movement update will be capped to 40 FPS. So... with this setting you will have smoother cursor movement.
Excellent! Thank you.
However it does present another question. What is screen tearing?
And just to be clear, I already have fullscreen (exclusive) display mode enabled.
My understanding of Native Cursor was that whatever your pointer (cursor) looks like outside of Stoneshard is duplicated in game. And since that didn't happen, I just presumed that it wasn't working.
V-sync then prevents the GPU from pushing a new frame to the display buffer before the display has had time to fully draw an old frame.
Thank you.