Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
u can try simple test that shows this, get your favorite video game engine start adding something like simple cube at some point your framerate will crash. the exact point depends on the game engine, your gpu,cpu,memory,storage, your drivers, ect...
there is just so much that can be drawn at a time and so much that can be batched together and rendered in a single point beyond that its like very low framerate
the same with textures. if u have lots of objects with different textures not in a batched texture atlas at some point your framerate will crash too cause it just cant get the textures in fast enough. so video games take a bunch of textures and batch them together in an atlas. at some point you cant stick any more and at some point you have too many atlases / textures that have to be stream into video card to render a frame. the exact amount and size ect depends again on your game engine, your gpu,cpu,memory,storage, your drivers, ect...
so this could just be a sweet spot for some. others with let say laptop that cant move / crunch things fast enough, ect still cant deal with it and will be getting horrible framerate cause of the size of the map, the complexity of the level, the number of objects in it, the draw distance, the number of players, the numbers of npc, ect...