Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Let me be clear, "air" and "empty space" are two different things. Voxel objects which are made as one thing with space inbetween will have air voxels fill in that space, those are still accounted for in calculations and still need to continuously skipped through when doing those calculations. Empty space is space in the game which is no where in a shape bounding box.
Any time the rendering system comes comes in contact with this "air" it is fast to skip through unless there is a lot in the direction its going. Weight calculations for physics have to include the air as it checks each voxel and its structure and creates a collision box and maintains proper collision.
So it is fast to skip through the air but when you have thousands to hundreds of thousands of EXTRA voxels to pass through or check it slows down the shape calculations massively in different areas.
Though after viewing it again and understanding the length of the bridge it is very possible the long bridge is seriously too much
. Also theres a warning about going over 400 meters with the shadow volume as it seems to seriously mess with AMD gpus. What your video showed and my own test showed was that the bridge was the most taxing on the physics aspect.