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
Amazing mod, held back by MAJOR stability issues. I follow all the "official" about not saving during pauses or battles, etc. but it just doesn't seem to make that much difference.
Ex: I saw an old thread on reddit suggesting that moving ground troops directly from the planet defense slot on Planet A to the space slot of Planet B, without moving them first to the space layer of Planet A, contributes to/causes the "frozen map" bug, where framerate, music, etc. is fine, but nothing actually moves.
What I don't understand, is that a lot of these bugs are known/have been tracked by lots of people around different forums over the years, and following their advice and good practices should alleviate a lot (a majority?) of bugs. But there is no thread. There is no bug thread collecting all these that I've found. I don't get why the devs aren't a bit more proactive, because this is THE issue with the mod. Go to reviews all over the internet, etc. everyone knows Remake is a work of art... except it never runs right and most people give up after one or two frustrating campaigns.
There seem to be two major types of bugs: map freezing-type bug(s), and ctd/app freezing bug(s).
1) The map freezing bug could be related to moving ground troops between planets without moving them into the space layer first, but I'm not sure. The effect seems delayed, since nobody can seem to pinpoint an exact moment that it just "froze". But I definitely did this before this happened to me last, and since I've stopped doing it, I haven't encountered this bug again.
2) The ctd/app freezing bugs seem to be related to minor factions interacting, potentially with each other. I don't get this bug when minor factions attacking is disabled (I haven't talked to anyone else though, so can't confirm this part 100%), as in the beginner galactic conquest mode. It's possible there is a specific condition that must be met to trigger this, and there is simply a random chance of it occurring, and as the AI minors grow and attack more and more, it triggers more often. I've seen people claiming a general ctd anywhere from months 30-270, and usually it is something that cannot be effectively avoided by loading older saves. Usually people write something along the lines of the ctd happening always at a specific time on a specific week, or they can maybe avoid it for a few (or many) weeks, but it comes soon after the month where they originally encountered it. This makes me think it's caused by an AI action that can be prevented, but is usually not practical to avoid or cancel, by say invading a series of planets, etc.
Not sure how much this helps. The bug reporting I've encountered across steam, reddit, etc. is pretty fractured, with lots of guessing as to what the problems really are.
How did TR do that? Huge support, Corey posting day after day on youtube, slowly building up his sub base from nothing into the tens of thousands. Lots of outreach to potential coders, etc. The front-facing parts of the TR team are feeding the entire TR mod team, and it's really helping them grow into something much more than I would have guessed even a few years ago.
In Short: I wish Remake had this kind of support, but they're going to have to grind for it, and that's not for everyone. Stability will need to come from a massive rebuild of the mod, and it's going to be hard for subscribers to swallow an update that takes years to make and provides no new content. I hope the 5.0 update susprises me and blows us all out of the water, it's just hard to have much hope for that.
Fun facts with Niko.
1. We wouldnt care if people supported us doing it or not. We'd just do it and tell them to deal with it if they complained. The mod isnt a product so their opinions matter very little in the end if we really want to do something.
2. It's been nearly 2 years since the last major full update besides a few people on the team doing little things in the interim updates while everyone else worked on 5.0.
3. 5.0 involves gutting everything to rework it, so yes we did basically rebuild the mod from the ground up code wise.
4. More chefs in the kitchen isnt always good for everyone. We work best with each member of our team having dominion over their own parts of the mod with a few of us bouncing between them. What works for some doesnt for others
.
5. Stability is relative. For every 1 person saying they have lots of instability there's another 10 that say it's perfectly fine. Steam is just the place where that 1 is usually the loudest. Same goes for any other mod. Even our biggest issue (The GC freeze caused by 2 AI factions in an auto-resolve loop) is something we only know about because Corey himself told us about it and said TR has it too and there's no known fix.
Keep on fighting the good fight!