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
The reason it's not enabled by default is that the mod's core functionality, such as texture, material, and/or mesh sharing, can break assets being made in the editor. That is fundamental to the nature of what sharing does and cannot be 'fixed'. Feel free to use it in the editor at your own risk, accepting that if your asset gets corrupted and can't be restored then it's on you.
One of the DXVK devs told me the over-allocation, which DXVK does as well, is a common Unity issue. Anyway, the excessive usage of system RAM instead of VRAM would explain the phenomenon I was seeing in the loading screen, sorry for bothering you about it.
Are your graphics drivers the latest possible for your hardware?
Any issue is going to be at your end. Make sure that you have the latest version of this mod, by unsubscribing/resubscribing if necessary to force the update.