Karuva Campaign crashes that do not appear movie related Thread - Ultimate Apocalypse Mod (DOW SS) for Dawn of War
Ultimate Apocalypse is a mod for Dawn of War Soulstorm, which aims to create the most diverse possible unit and faction selection within the confines of the original DOW engine. We strive to create the most engaging and balanced Warhammer 40,000 game that we can, without sacrificing the fun factor. From hordes of Orks to the towering Titans, you can always find a new way to play UA. We invite all of you to join us on our Discord server to keep up with the development of the mod!
| Posts | ||
|---|---|---|
| Karuva Campaign crashes that do not appear movie related | Locked | |
| Thread Options | ||
| Oct 12 2013 Anchor | ||
|
I have been having a strange issue that appears to be some yet unknown bug. at first it looked like the movie bug because the game crashed imediatly after a stronghold mission. however the behavior continued after copying the movie files. saving before nuking the base also had no effect. the reason i do not believe this issue is related to the movies issue is the fact that both intro and ending movies play normally and that the crash doesn't occur until you click continue after the prologue screen. this leads me to believe the issue has something to do with the game trying to update or load the system map possible a bug with the commanders war-gear awards either way the tips on the FAQ have not worked at all |
||
| Oct 12 2013 Anchor | ||
|
I keep forgetting about this: The solution (that works for me and a few others I've indicated to do so) for these crashes is to set Soulstorm.exe to compatibility mode for Windows XP SP3. Assuming you're running Windows Vista/7/8, or at least not Windows XP, of course. I don't have enough confirmed cases of this fixing the Kaurava campaign crashes to make a decisive conclusion though, so if you (yes you, the UA player) can help me and everyone by setting Soulstorm to compatibility mode for XP, try this out and posting the results here, that would be grand -- How to improve performance on DoW: Soulstorm |
||
| Oct 13 2013 Anchor | ||
|
tested this issue again with compatibility mode no changes. i am am going to try assaulting the Ork stronghold using another race to see if this is issue is race specific than i will try again on another races strong hold to see if the issue is Ork specific if you want the game did produce a crash dump i can upload additionally there also appears to be some AI bugs in the karuva campaign that prevents the opponents from using the mod added units as freely. the campaign is too easy because you basically win when you build a titan because the opponents cant use their own super heavies Edited by: mikeloeven |
||
| Oct 13 2013 Anchor | ||
|
Gah, ErrorLog chunk-o-text, why. Though, while these are normally useless as they can get, the one you've posted gets me an exceptional amount of information. Though said info isn't even related to the mod itself. Unfortunately, as the crash that specific ErrorLog points to was the 32bit app handler hitting its memory limitation and you've got Soulstorm on Steam (meaning we can't alter its executable), all I can recommend you to do to address this specific problem is to close unnecessary programs before running DoW -- How to improve performance on DoW: Soulstorm |
||
| Oct 13 2013 Anchor | ||
|
why cant you edit the executable for the steam version??? last i checked there aren't any changes aside from a few dll dependencies to make sure you have steam running not sure why it is triggering a memory limitation error a game that old should not use any where near 3 gigs also the system has 16 gigs total and i have run large numbers of 32 bit applications running totaling over 10 gigs so obviously the system can open multiple instances of 32 bit app handler and spread the memory load. to be honest i am thinking memory leak at this point cause thats the only way i can see the game getting so high that it hits a hard limit. maby i should create a second partition with windows 7 x32 it is defiantly a memory leak in the mod code. running vanilla on max graphics doesn't trigger this crash on stronghold missions running UA on max graphics does running UA in Safe Mode 800x600 does not crash after completing a stronghold. so it would appear that something is not properly unloading after the mission completes leading to a massive spike in memory usage for a brief moment that is just enough to trigger the error. since running on low settings slashes memory usage significantly it would appear the only way to get past this issue is to save at the exact moment the stronghold is defeated play out the ending sequence in low quality and than turn the settings back up after you saved. is there something that can be done in the mod code to help release extra ram before the ending sequence ??? Edited by: mikeloeven |
||
| Oct 13 2013 Anchor | ||
You aren't the only one. I and few others have discovered that this is a game engine issue that can not be fixed. I could be wrong, but I looked through the coding, 5, 6, 7, hell 8 times in three - four different strongholds throughout the two years of modding, and even commenting out things one by one by one after 5, 10 test runs, random results happen and it bugs the hell out of me. Other mods, countless mods. Playing campaign on corncobman's mod, FOK, others, even Titanium Wars on Soulstorm (so I've heard) can cause these random crashes to some people. But to this very day, people do not give me what it takes to fix this error, and I tried everything I could do, back in August, actually. But... the Apocalypse mod team is developing our own campaign, that will indeed in the future replace Kaurava as the Kaurava campaign will only at random disappoint people because of crash to desktops. Wargear? No that can't be it, too, because if that is so, skirmish missions in the campaign would not work either... I don't know what to tell you, but there is no way in curing this without getting what I need to fix it. Edited by: Lord_Cylarne |
||
| Oct 14 2013 Anchor | ||
|
the wargear observation i kinda scrapped that idea too and i am convinced it has to do with memory not being released after the campaign ends. but at least i found a workaround if you save before completing the stronghold and play the ending cinematic in 800-600 the crashes do not occur so it seems to be something that is directly related to either memory or video resolution] Edited by: mikeloeven |
||
|
|
Nov 24 2013 Anchor | |
The reason is because Steam tends to prevent the editing of an executable as an anti-piracy and anti-cheating measure, apparently. Normally it's good, but in this case it has a drawback.
If I recall correctly, I read somewhere that Soulstorm has a two gigabyte max memory limit built into it. You could edit the executable to change this, but...well, drawback of Steam version. The only hope now is to either contact Relic and see if they would release a patch to fix this (not likely) or contact Valve to see if they could do something about this (also not likely, but probably more possible). I wonder who honestly thought it was a good idea to have a two gigabyte max memory limit built into the game? It's incredibly stupid. -- Dawn of War Mod Manager (Version 1.2 - 2016/03/21)
A mod manager for Dawn of War, Winter Assault, Dark Crusade and Soulstorm. Eliminates common problems with launching mods, such as not having required mods or the correct version of required mods installed. Check it out and let me know what you think. |
||
| Feb 4 2014 Anchor | ||
|
This may be a bit late, but after encountering the exact same issue, i ran in Xp-SP3 compatibility and (even though im already administrator with no UAC) told it to run as admin in properties and it worked just fine. -Edit: I also gave soulstorm.exe full control in its properties; read/write, all of them besides special access (I am running Windows 8.1) ***-Second Edit: Nevermind, now the game will only run windowed, has begun crashing again, and is acting like when i tell it to change display settings it isn't saving them, so I guess it's back to the drawing board on that one. AHA! Moddb.com That .exe, when copied over the one in the directory, ran the game just fine and addressed all the ram, bypassing steam's file check, and resolving the error-51, also the in-game overlay appears to be disabled by default in this .exe file. (Credit to grOrc for the exe, I reccomend that UA Mod team lets people know about this in their help forum, so people quit complaining and we get around steams dumb walls. Edited by: Pheonix_Baharroth -- Ask not the Eldar a question, for they will give you three answers, all of which are true and terrifying to know. |
||
Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.