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
As for the last 10% as I mentioned you can go into the Rimpy json file and update the specific mod so that it sorts correctly or removes the dependency error.
Till then Rimpy is still the better manager.
There is no issue with starting the game via RimPy, and then later starting it with Steam.
I've searched the Internet, but unfortunately, the posts about this are very old, and the suggested fixes don't work.
This really bothers me because my playthroughs are very story-driven, so I often come across wholesome moments that I'd like to capture in a screenshot.
I want the screenshots to be taken directly through Steam so I can easily browse them later — I don’t want to use any external tools.
Do you know any solutions?
If rinpys database has a rule that a modder has removed
Rimpys app will still think it's there months after the modder removes it till paladin updates this database