安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
afaik fixes/issues:
(and again, below is only afaik)
vr has a bug with vram where it never removes un needed vram. so loading in vr, then loading in 3 differnt maps, if each map is 4gb vram, then you will already have 12gb vram being actively used
vram gets used up heavily by loading different maps, vehicles, having high settings, and by simply changing settings.
to get around this, go with lowest graphics you can handle, and if you want to change map etc try to restart beamng.
going overboard on vram causes freezes or massive performance hits
you should load up beamng, then load up vr, then load up a map
there is some issue where using wireless vr headsets have a massive performance hit - try cabled
vulkan is kinda buggy and iffy - like some dude is saying before .30 vulkan did 120fps on ultra, but post .30 vulkan does 30fps on ultra
(another reminder everything is only afaik)
thanks, this clears up and answers lot of issues i had.
and you dont need vulcan to run the game in, it actually runs better in normal mode. at least to me : )