Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.