安装 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(越南语)
Українська(乌克兰语)
报告翻译问题






在 Twitter 上
在 Youtube 上 



And I tried doing the thing of having the chromatic volume muted whenever the player misses, but due to how Source handles sounds, that didn't work--the player's sounds would still end up not playing when prompted, so you just don't hear anything. (I also tried tying the player's sound to an entity that is moved away from the camera when you miss, but, same thing)
In Hammer, create notes that are delayed to those timestamps. I know that it is timed to instead create the note, and not timed to where the note is actually hit, so for any timestamp you'd have to subtract -5 seconds, or however long it takes for the note to reach the top.
I saw how you create each series of notes separately, and not all in one entity. It is helpful, but this means you cannot add the timestamp normally, it's inaccurate to when the series of notes are activated. So, take the time that the entity is activated and subtract that timestamp by it.