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
All they had to do was download an engine update and fix a few broken lines of code here and there. Whatever, not like they gonna do it now.
Hey I don't know how they wrote their framework. If everything is inherited then sure it's a lotta work. I don't know how tiny the leak is but it's entirely possible to override garbage collection. So blaming it all on Unity for not working "out of the box" is short sighted. Either way, it's not getting fixed so I'm not sure what your argument here is.
This is the best Commercial Battle Tech turn based tactical game in the last 30 years, No its not perfect but Commercial products are run to strict rules, if they get to the cut off date for development planned and have fulfilled said plans they move on.
I play Rogue Tech because it due to being a mod doesn't have the same restrictions.
The people doing the big in depth code reworks to add features did a lot of work to reduce the leak, they needed too due to the big part being the assets get added to lists in memory, and with nearly 50 times the assets from the vanilla game Rogue tech wouldn't work if they didn't work on the problem.
But you being rude wasn't necessary.
Leaving an obvious problem that was known for while is indeed lazy. And yes it is also a lame thing to do. Because you see, just like you said, OTHER people had to do a lot more work since of course there's no source available to actually fix instead of working around it.
If I sold you a car I made, would you be happy when you realize you have a leaking gasket? And exactly what would you think of me if you found out that I knew about the problem, but I just couldn't be arsed to dismantle the engine block again in order to fix the issue? You'd be cool adding oil to it every 10 days would you? And here's the lame part in this analogy, any mechanic you ask to fix your car would give you a high price because of the huge PIA it is to repair. In this case, I was too lazy to fix what I knew was broken, and I was lame because I created a headache for other people. This is not a derogatory statement, it is what it is.
I wasn't rude to anybody, what I said will always be true for such cases. The fact that the devs don't like this reality doesn't change anything, nor does the relative quality of the game. Maybe the devs are cool guys. Maybe this is indeed the best BattleTech game to date, but all of that is irrelevant when the results are in.
And the bottom line is that there's a 4 year old memory leak that through 3 DLC's nobody fixed. And that in my mind is lazy and lame. If you can't see that then I don't know what else to tell you.
And a memory leak is a serious problem, no matter how small. I'm sure I don't have to explain the reasons as to why that is. Also, this was a Kickstarted project, so whatever deadlines were set, were the result of the devs choosing a pushy publisher. I don't know what they did with 2.8 mil but this to me seems like a good enough number to make sure whatever you make has the appropriate level of polish.
Regardless, I started this topic for technical info, not debate the integrity of the dev team. I appreciate the additional background details you shared, but that doesn't help me at all. And clearly neither will the devs since they moved on, so my best bet is to Mod this game and hope the modders plugged enough holes. In any case, this topic is done.
If it is happening (and it likely is, to some extent) it must be inconsequential for reasonable session length / unmodded game. And that's probably why it wass left as is - nothing is ever perfect in this world and spending a bunch of time fixing issues which are never going to affect things significantly is a good way to waste money and never release anything.
It is very easy to just say "it must be a memory leak" and stop there, while the actual issue might something else entirely. This is, in fact, how all those myths about "overheating GPU" "memory leak" and whatnot end up filling all the discussions of different games - a bunch of people just keep repeting them without even understanding what it means.
That is you being Rude Kensei.
Devs get paid to do a job they are doing this for the people that pay them and tell them when to move to the next project, so its lame to be rude about people doing their jobs, and very stupid to think they can carry on projects after their boss says its done.
But I guess our expert will be like the other experts and talk lots, but wont turn up at the Discords for the mods and offer to work on anything, because he in fact doesn't know that much.
Just because I know what I'm doing doesn't mean that I have any interest in working on a BattleTech mod, especially not one with a leaking source. Not to mention that I dumped Unity years ago and have no intention of ever again bothering with it.
I don't know what your experience is, or maybe you have short play sessions, but in my experience the game starts dropping FPS after about 4 contracts. After about 10 performance tanks badly, especially in Urban areas.
I'm installing the BTA mod now with the hope that it might stabilize, but judging by the Wiki the only real solution is to restart the game often. A real pity.
You didn't pay the devs anything, you paid steam for the game as it is, HBS tells the devs when its finished not you since they do pay the devs and get to tell them what to do. If you post stuff about not liking HBS for putting out a game with faults that would be your choice, but talking about the devs in the manner you did is wrong they don't get choices they get told what to do.
It seems to be a modern cowards way out to insult and be rude about devs knowing they cant answer you.
This seems to be a growing situation