安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
Also what is the exact message. I can't remember putting a warning in this one .. But in all honesty, It's hard remembering all details when having too many things going on at once.
Some more details:
- Console window opens in the bottom-right, black background with white text. Scrollbar on the right is slightly overlapped by the x-button in the top-right.
- Two types of messages, it's either:
a. Object.updateWavesRtl (index.html:552:15): stutter! 93.9 16.666666666666668
b. wallpaper.js:121:12: Not receiving audio from Wallpaper Engine
In the a message the number after "stutter!" varies (goes as high as 401302.1 in one instance.
- Console has several messages that appear only once and only at the beginning:
Object.get (three.js:19318:14): THREE.WebGLRenderer: WEBGL_depth_texture extension not supported.
new WebGLRenderer (three.js:19502:11): 82
new WebGLRenderer (three:js:19502:11): THREE.WebGLRenderer
log.js:131:14: log started
The "not receiving audio from wallpaper engine" is something that can happen when paused and should automatically disappear when playing again. That high 401k value sounds like it was paused too, but I would have to check my code.
The stutter message is something from me trying to test and tweak the code. I think I might of left that in and forgot about it.
Thnx for the feedback. That was perfect. Sometimes some bug might be in there and nobody reports it. I will look into it in the coming days and see if there is anything to worry about or if I just left some testing code in there and forgot about it when doing the last update.
I will figure out the exact details of the stutter message soon and let you know what I have done about it.
The stutter message was mostly related to me testing some code that should protect from stuttering due to lack of audio for a frame or two. ( which at high fps could happen ). In general its fine, but in a rare case ( in the ones it reported ) it was often 6frames out of sync for whatever reason. And the 16.66 should be your frame interval, meaning you were trying to run at 60fps if im not mistaken :)