Simplex started as a branch from Complex. It has combined features from Path To Victory as well as many other mods through a long history of R&D. This mod aims to excavate the full potential of the Homeworld 2 engine and it will simply blow your mind with incredible fun!
Description
Slightly improved multiplayer stability 👌
Preview
Post a comment
Profile
Icon
Game
Homeworld 2Creator
siliconwormContact
Send MessageHomepage
Moddb.comRelease date
Mod watch
Follow
Related Mods
Related Games
Homeworld 2
Real Time Strategy
Tags
Cool mod, just the fish is wierd to be honest
the fish are really OP in single player they can ruin your day in moments
Здравствуйте , Hello Im from Ukraine Zaporozhye , может кто то в Homeworld_2_Complex_Simple_1.5 Изменить название роли исследовательского корабля , а так в этом моде мне всё нравится, все поперепробывал !!! С уважением - arkturserg@mail.ru
Bug Report: M03 is completely broken. The step where the 3 Vaygr carriers hyperspace in and continue to send Infiltration frigates does not properly execute. Haxor console cannot be used to select and detonate the AI ships as they are not 'inbounds' on the map anywhere for selection to be possible. Attempted to edit playercfg.lua to bypass it but I must be misunderstanding something about that as all I did was create a crash trigger.
The initial fighter/corvette assault for mission start does trigger. The secondary objective to deploy a mobile refinery does trigger and react. The Vaygr probes do spawn the extra carrier near the asteroid field for the secondary objective. One initial wave of the infiltrator frigates plus escorts does spawn in, but their associated carriers do not. It appears map scripts for progression depend on the deaths of those three carriers.
Thank you for the info! I checked the code. The condition for the Vaygr Carriers to exit Hyperspace is a single simple trigger: when the health of the first Infiltrator Frigate is <= 0.8
Did you try to damage the Infiltrator Frigate to trigger the carrier event? If you instantantly kill the Infiltrator Frigate, then I guess it could trigger the bug and the Vaygr Carriers won't exit hyperspace. This is the most likely cause I'm suspecting.
Another less likely cause is that the three Vaygr Carriers have been already destroyed.
I just tried M03 and saw the three Vaygr Carriers spawning without any problem. If you can record how you play M03 and send me the Hw2.log, it would be helpful for debugging.
I've messed around with some other mods, so I'll need to find time to sit back down and attempt it again to refreshed the HW2.log. I don't have any good video software, but I can attest that I'm using the strategic bombers awarded from successful crewship rescue in the prior mission as part of my strikecraft swarm and they may be obliterating the infiltration frigates almost instantly. That would line up with your suspicions. I'll include holding them back when I get the chance to play again.
Ok, following up.
1) In M03, the bug is explicitly killing the first infiltrator too fast. Once I held the strategic bombers back, it lived long enough to trigger the script properly.
2) Much lesser bug - in M05 there's a voice file triggered claiming that Ion Frigates have been made available, but the Ion Frigate tech does not become available for research until M06.
If I see anything else as I play through I will add more here. Thanks.
What causes this crash? Out of memory? "Homeworld2.exe caused an Access Violation in module Util.dll at 0023:0101356a" Game works fine till some point and then always crashes there.
What's in the Hw2.log? Can you send a screenshot of all the game settings? And even better, also record the gameplay video and show when it crashes?
Settings and log files => Drive.google.com
Another strange thing i have steam version of the game but everytime i launch it with modded shortcut it opens Epic Games Website :D
Gearbox recently patched the HWRM suite to 2.3 to include Epic Games multiplayer for when they released it on there. That's why its started forcing the EGS login to open in a browser. Rather annoying, but nothing to do with this mod. For some people the forced alt-tab is breaking their resolution and making classic unplayable.
Can you send the skirmish settings? And also what's in the Hw2.log (not ErrorLog.txt)?
Files updated. I'm trying to record gameplay but the game crashes faster than I can record it..
Thank you! I checked it. There is no problem with your installation or game settings, but your Hw2.log message is very strange. Your Hw2.log keeps saying authorization failure with www.epicgames.com.. I don't know why HW2 has anything to do with epic games... So I recommend trying the mod with the original version of HW2 (the one from 2001).
Also, were you trying to load a saved game, or starting a new game? The Hw2.log suggests that you were trying to load a previously saved game with 3 CPU players. If the saved game was from an earlier version of this mod or another mod, it would not work.
I sent logs from a saved game, but the situation occurs regardless of whether I start a new game or load a saved game. It just takes more time before it crashes in a new game. I will do as you advise and try to run the mod from the original version if I still manage to buy it somewhere. This is a bit strange for me because I haven't had any problems so far and I've been playing since version 2.* or 3.*? Anyway thanks for all your help :)
For what its worth, Gearbox just did a hotfix patch and after said patch I stopped seeing it force the EGS login to open in a browser. Hopefully that prevents the issue you've been seeing.
After many tries, I managed to solve the problem. As with AMD graphics cards, I had to use "-nopbuffer" on the RTX2060S (because it looked like the shadows were taking up practically all memory). In addition, it was also necessary to use openGL from the mod folder and a partially edited "QeffectsGL.ini" file. I also had to force the use of a single CPU core (despite the fact that the game uses a single core anyway). If any of the steps are skipped, the problem returns. The above trick was only necessary for the RTX2060S card, when I mounted the old GTX1050Ti, nothing needed to be done. It looks a bit like a hardware compatibility issue causing the error in this particular case. It took me over half a month but it was worth it for this mod :D
That's quite a feat! Thanks for sharing the details!
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
Is it correct that the main menu still says version 4.6? or have i broken something with my install?
I did a fresh install and done it from scratch, its working correctly now no idea what was wrong.