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
Can't say for sure since I have not encountered this, but here is what I would try:
-Make sure your game files are in order by right-clicking homeworld in your library, then select 'Properties', followed by "local files", and lastly "verify integrity of files".
-Make sure that you are using the correct monitor resolution in the game's video settings. Reset every other graphic setting to its default on chance you have adjusted a few things.
Verifying the files is usually the first thing I do as well, but I am reluctant to do so as the first time Homeworld Remastered did anything out of the ordinary I verified the game files and ended up having to fully uninstall and reinstall due to it improperly fixing the issue in several instances.
I just find this to be downright weird as whenever I run the base game I have no issues, and I can run the Gundam mod without issue, as well as a few other mods I had installed at one point.
The issue here is related to range, not the line of sight but more being aware of the enemy without seeing him (like when you launch an assault on an ennemy ship, then, he's aware that another entity is here to fight). With small maps, the "awareness range" defined is too big (due to huge size of certain ships, as the Nupetiet or the Zentrans' mothership) and, because the ennemy is already inside that range, the combat behavior couldn't trigger because he's considered as an object from the map itself. It is kinda more complicated than that but basically this is the problem here with small map...
Anyway, did you use another mod with this one ? And if yes, which one ? Did it happen with a custom map or vanilla ?
I sadly can't think about anything helpful about that AI issue for now... I'm going to alert Cooper about that matter and run another round of tests to try to find out what's going on.
Did you have any other mod running when this happened ? Like "instant building", "no limit cap" or something like that ?
Nailed that list, I feel very much the same.
I am very much into the "original saga" for Macross/Robotech, and am very much at home with those craft.
As cool as Megaroad is (I mean, the model is wonderfully reproduced in this mod) it isn't my "era". Didn't it only appear in a manga or a game too, right?
Separating the factions like this is my personal number one desired change, and would make this the perfect mod for me. I bought Homeworld just for this mod, I only play the game with this mod, I adore it. Alongside the PS2 Japan only title this is one of the best Macross games out there.
I agree with this post, also I guess the New United spacy will be split that way as well.
The Nousjadeul, Glaug, and Queadluun are all way over powered.
Or they spawn off the ARMD carriers which is OK, but doesn't have the same feeling as it did when the SDF-1 served as a mothership and actually launched fighters off the deck of the carrier strapped to its' side.
Instead the SDF-1 is the last ship you can buy in the game. In fact it often gets to the point where the ship cannot be purchased, even if you have the required research. And forget about buying the DYRL version, that's greyed out!
Oh, and the big Reflex Cannon? Fire that thing and there's barely a scratch on any of the Zentraedi capitol vessels, even the weakest one.
So the only function the SDF-1 has in the game now, is to:
Look pretty.
Yeah, you heard me. "Looking pretty" is literally the only function that the SDF-1 Macross has, in a mod from an anime series that is solely about the SDF-1 Macross and her fighter crews. Nuts, isn't it?
The transformation sequence looks great, but it's only a very small part of what makes the battle fortress an integral part of SDF-1 Macross. Because of this, I wouldn't mind if the mod reverted to its' 2017 format, back when it wasn't able to transform and was still the Mothership, with the rest of the ship being fully functional.
Like many of us in this thread, I bought this game exclusively for this mod. With the current state of this mod, I can't, WON'T, play this game, because the SDF-1 is ruined.
Homeworld Remastered will remain sitting in my library, gathering virtual dust, until which point as the desperately needed changes are made to the mod and the SDF-1's functions are restored.
"But look, it transforms!" So what? It's still a nonfunctional piece of space junk that might as well be removed from the game in its' current state.
And what exactly did they replace it with? The "Megaroad", a vessel that can't defend itself and if it is so much as tapped by an enemy, it explodes causing a game over.
People say Macross was butchered to make Robotech. Well, the makers of this mod butchered it to make the SDF-1 transform. They removed all that was good from the SDF-1, and turned it into a piece of junk, then replaced it with something that was even less good, and more junk.
EDIT: I have news:
Apparently in order to have all the things that made the SDF-1 Macross, the SDF-1 Macross; the developers have to disable the transformation.