Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Trung giản thể)
繁體中文 (Trung phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
Do you select Legacy Runtime 1.0 in Steam?
For me it solved both NCR and IMT, so *may be* if NC (no "R") works and only IMT is throwing the exception it could help?
It's in the runtimes where the mono and .net dependencies are, so if doesn't matter what you have install on your own system, it only matters what runtime from steam you are usuing, cause thats where the game is looking.
Setting to "Legacy runtime 1.0" seems to have effectively solved the issue
Thanks for the help!
It's a pity this advice is not included in the warning displayed when selecting the mods in game... It would save so much headache!
What you are looking for, in that case, is "Legacy runtime 1.0" using Steam Play compatibility tool. By default it will set to "Steam Linux Runtime 1.0 (Scout)". That's the new mono that lacks certain dependencies that the game and mods need.
Not sure if thats your problem though, because the result of that was crashing during a save, not during startup....becuase it would be during a save that the game/mod would then look for those dependencies that aren't there, and either hang or crash.
I *think* I read somewhere it was linked to mono which the mod requires to install if it's not on the system already.
*May be* finding an old version of mono could help?
And yes, I'll try steam-runtime instead of native.
So many possibilities here...