安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
In the basic term: Yes.
It IS possible, but really hard. You need to know scripting inside and out. Even then it would not look the best, as scrapmechanic has its limits on modding.
Theoretically cant you make your projectile do the raycast and by the ray difference make it determine the angle ?
For example if it sees a flat plain and makes a raycast it can determine the relative angle of the surface and then it can make a determination if it ricochets or not. But if it sees some undeterminable data it just ignores it and goes boom.
I've thought about this, but I'm not sure that it can work with polygons. I tried to test it, but due to lack of full docs for SM API (some years ago) I gave up very quickly. Maybe some day I will try again...
I would sudgest with polygons that it would just break it and scan the block behind it .
It fixes few issues
for example: ricochets still leave a mark on armor in IRL.
so it would use this algorithm every time it can't figure out what is going on. To clarify the data.
And btw check out my other suggestion about a ballistic computer in other discussion.