Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: CT27 on September 06, 2014, 02:11:06 am
-
I've played the campaign "Storm Front" relatively well but I'm at the fourth mission of act 2 and it won't seem to load.
Unable to find WEAPON_LIST_TYPE string "MX-52" in stuff_int_list
Many possible sources for this error. Get a programmer!
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes
This is what I got when I couldn't even load a debug build. I've also attached a fs2open log.
[attachment kidnapped by pirates]
-
It happens whether I use 3612 or 2014 vps.
-
To start with, it looks like you're loading Stormfront twice in your command line:
Passed cmdline options:
-mod StormFront_1+2,StormFront_1+2,StormFrontStock,MediaVPs_2014
Beyond that, I'm not sure. It's triggering an Int3 loading a model, it seems.
-
I have no idea why it's saying I'm loading Storm Front twice.
[launcher]
image255x112 = StormFront12-Logo.bmp;
infotext = The Storm Front Saga - Episodes I & II;
website = http://www.junk-productions.de.vu/;
forum = http://www.hard-light.net/forums/index.php?topic=67097.0;
[multimod]
primarylist = ;
secondarylist = StormFront_1+2,StormFrontStock,MediaVPs_2014;
That's what my mod.ini looks like and I don't have that one thing loaded twice.
-
...So the mod contains itself in the secondarylist? That would be why it's loading twice.
It's triggering an Int3 loading a model, it seems.
No, it's parsing mv_root-shp.tbm and weapon_info_lookup("MX-52") is failing, which is... odd.
-
http://www.hard-light.net/forums/index.php?topic=84844.0
I also tried the secondary list line Yarn suggested in this thread^ and same problems...
-
The secondary should never have the name of the mod you have selected in it.
secondarylist = StormFront_1+2,StormFrontStock,MediaVPs_2014;
Since you are playing StormFront_1+2, the secondary should be:
secondarylist = StormFrontStock,MediaVPs_2014;
-
I made the secondarylist what Macfie said and I still get the same problem. I select my pilot but after I click on the ready room to try and continue the campaign, nothing...the loading screen just sits there for minutes. When I click the mouse the game stops and I get a small popup saying that FS Open has stopped working.
For the record I'm using nightly build 11061.
http://www.freespacemods.net/download.php?view.615 (this is where I got my download from).
-
Here is what I did ( I just tried redownloading things):
I downloaded the campaign from the link I just provided. Then I used 7-Zip to extract things.
I got two folders from that: A Storm Front 1+2 folder and a StormFrontStock folder. I put both folders into my FS2 folder like I usually do for mods. I then went into the "1+2" folder and changed the mod.ini to the line Macfie suggested.
Is it possible that since I originally played with the campaign name in the secondarylist (like Macfie said shouldn't be done) that somehow my pilot file got corrupted? Would starting over with a new pilot file maybe fix things?
-
Pilot file corruption is always a possibility. you could do like you did for Tango and delete the .csg file, which just stores progress for this campaign.
-
I tried deleting all three FS files concerning my pilot file for this campaign instead of just deleting the .csg file.
After I beat act 2 mission 3 of Storm Front I and tried to go onto mission 4, like before, the mission just won't seem to load.
So I still have this problem unfortunately.
-
Also, should the Amun be a simple red dot in this campaign on the radar instead of the symbol for a bomber? That's another issue I noticed.
-
It just seems strange that a campaign works fine but then all of a sudden it just won't load one mission.
Is there any other place to download this other than FSMods?
-
I haven't actually tried playing this yet, but I think I know what the problem is. The StormFront1+2 mod includes a version of weapons.tbl that does not include an MX-52 entry (well, it has MX-52#Shivan, but that's it), even though the retail table has it. Thus, when tables referencing this weapon (like mv_root-shp.tbm) are loaded, the game can't find the weapon, resulting in the error message that CT27 is getting.
-
I haven't actually tried playing this yet, but I think I know what the problem is. The StormFront1+2 mod includes a version of weapons.tbl that does not include an MX-52 entry (well, it has MX-52#Shivan, but that's it), even though the retail table has it. Thus, when tables referencing this weapon (like mv_root-shp.tbm) are loaded, the game can't find the weapon, resulting in the error message that CT27 is getting.
...Somehow, it just didn't occur to me that the mod would actually be referencing the 2014 MediaVPs without being able to load them. Note to self: check for the most obvious reason the game can't find the damned weapon next time.
-
I tried fixing the problem myself by adding an MX-52 entry to Storm Front's weapons.tbl, and all it fixed was the message about that weapon being missing (and it's actually a warning, not an error, so it can be ignored by clicking "no"). The mission still crashed with a generic "this program has stopped working" message. That means that the problem must lie elsewhere.
-
I got the error message (about the MX-52) when trying to start a debug build.
On 'normal' builds (including nightly ones) I'm able at least to get to the main hall and click on the ready room to try and play act 2 mission 4 but that's when things freeze up (and this was using 3612 and 2014s).
-
I did some more testing. The crash happens when loading the Amalthea model, and it appears to be caused by an access violation in find_tri_counts() when reading the values for the id and size variables.
The patch below contains the code that I used to determine this. Once it's applied, load the Storm Front mod, go to the Tech Room, and select the GTC Amalthea. After the game crashes, open your fs2_open.log (did I mention that you need to run a debug build?) and scroll to the very bottom. You'll probably notice that the offset at the end suddenly grew by a few orders of magnitude and that the id value was not read (because of the crash).
Index: code/model/modelinterp.cpp
===================================================================
--- code/model/modelinterp.cpp (revision 11072)
+++ code/model/modelinterp.cpp (working copy)
@@ -4110,8 +4110,11 @@
// tri_count
void find_tri_counts(int offset, ubyte *bsp_data)
{
+ mprintf(("Yarn: offset = %d, ", offset));
int id = w(bsp_data+offset);
+ mprintf(("id read successful, "));
int size = w(bsp_data+offset+4);
+ mprintf(("size read successful\n"));
while (id != 0) {
switch (id)
I have no idea what's really causing the crash, though.
-
Is it perhaps the mission file that's not working right?
-
I think it's more likely that the GTC Amalthea POF has something wrong with it.
-
It's almost certainly a bad model, considering that the game is crashing while loading the Amalthea. I can trigger the crash without loading the mission by going to the Tech Room, pressing Ctrl+Shift+S to display all ships, and selecting the GTC Amalthea (which loads the model). I'm sure that the crash can also be triggered in the F3 lab.
I also tried loading the model in PCS 2.1 Alpha and got a similar crash, so the Amalthea POF might be corrupted.
(And just so we're clear, the MX-52 issue is completely unrelated. And no, the MX-52 message is not a crash; as I said earlier, you can ignore it whenever it appears by clicking "no," and the game will continue without problems, at least until it loads the Amalthea model.)
-
I'm fairly certain we're all on the same page here, but just to clarify what I mean when I say the game freezes/crashes (some may have different definitions of those words):
When I try to load up act 2 mission 4 of SF1 (whether it's by clicking on the next mission button after successfully completing act 2 mission 3 or by clicking on the ready room in the main hall), the mission loading screen (greenish background with GTVA logo on top and progress bar at the bottom) comes up with one dot filled in. It just stayed that way for several minutes. I would click the left button on my mouse and a blue circle would come up. I clicked that button again and then the game closed with a box saying Freespace 2 Open stopped working.
Again, I've kind of said this before, and I think we all understand each other, but I just wanted to be 100% sure.
-
Some people have said they're able to play this campaign without problems. It's weird how some people who download it have these problems but some people's downloads don't seem to have this problem with the cruiser.
-
I just noticed that the release for Stormfront12 on my hard drive is a completely different one compared to the one you linked CT27. Mine has no StormfrontStock folder and is only 23 something MB in total. Will look into playability right away and if it does work, I will upload it on mediafire.
Edit: 102 ship table errors does tell a tale of something definitely being wrong there.
Edit: After looking a bit around, I noticed that the StormFrontStock folder from the freespacemods download is missing some VPs compared to the VPs on the author's homepage. Try getting everything from here (http://sebastian.ramrod-network.de/Freespace/JunkProductions/News.html)
Edit: With all files from the author's homepage and trying to use mediavps_2014, I am down to 17 warnings and/or errors. Did a few missions and it looks perfectly playable. If someone tells me how to edit my campaign pilot file so that I can try out the mission in question from the campaign simulator, I'll do that right away.
-
Editing the pilotfile to do that is a bit tricky. I'd instead recommend using a fresh pilot (since the cheat will probably damage the pilot) with the "skipmemymissionyo" cheat to play the mission in question. You just need to find the mission filename, and you can get that by using the techroom with CTRL+SHIFT+S.
edit:
Or, another way of doing this is to modify the campaign file to make the problematic mission the 1st one in the campaign. I usually just delete all prior missions from the campaign file.
-
CTRL + SHIFT + S did the trick. Thanks niffiwan, I should have remembered that. I just suddenly had a sudden stroke of memory where you told me the exact same thing so that I could count missions for the campaign list.
CT27, the missions in question load just fine for me. The GTC Amalthea also loads just fine in the mission simulator. Try using the version I linked and report back to me. You can also just throw the vps from the StormFrontStock into the StormFront1+2 folder and delete the entry from the mod.ini. Less clutter. You need to download BOTH StormFront1+2 and StormFrontStock fresh though, just adding the missing vps to your installed version breaks it even more. At least it did for me.
On a completely different note, What If is ridiculously broken. That will be my next request for the FSCRP as soon as Dawn of Sol gets a rehaul. Then again, Dawn of Sol is at least working.
-
Did you modify the mod.ini for what if? I noticed it was released in 2010 and refers to old versions of the fsport, fsport-mediavps and mediavps. It also is dependent on the stormfrontstock folder so if you put those files in the Stormfront1+2 folder it probably won't work. Also Dawn of Sol will probably not be high on the list of campaigns to overhaul because it works and the original author is available to overhaul it. I would recommend asking the original author for an overhaul.
-
Macfie, I tried modifying the mod.ini in several ways for What If. The usual suspects. Also played around with the order a bit, but to no avail. Actually I did the very same thing I did with StormFront1+2, and StormFront1+2 works perfectly (even with the StormFrontStock VPs just thrown into the Folder, as the Stock has nothing but the VPs themselves). The fsport-mediavps are even compatible with the mediavps_2014, cudos to none other than yourself. ;)
Only What If seems to be completely unphazed by StormFront1+2 working perfectly.
Regarding Dawn of Sol, both CT27 and Droid803 himself stated (http://www.hard-light.net/forums/index.php?topic=88077.0) that he wasn't working on DoS anymore, that he'd help out anyone trying to restore it, but also stopped work completely on Sol:Invictus. So the request stands. ;)
Otherwise I'd throw Allied Worlds/Forces or What If into the fray. If I had the slightest clue, I'd even attempt to help.
-
Played Whatif in March with the new MediaVPS-2014 and didn't have any problems with it. Since I didn't have any problems with DOS when I played, it will go to the bottom of the list. Since I'm the only one working on restorations right now I'd rather focus on things that don't work.
-
What build did you use back in March for What If?
Dawn of Sol still works fine, I never said anythign different. It uses mediavps though and those are definitely dated. What doesn't work at all is Allied Worlds and Allied Forces though.
-
I played through DOS with the 2014 mediavps without any problems. I did not use the cockpits though.
Played Whatif with 10481 through 10506. I always use the latest nightly build.
-
I don't have all the nightlies in between on my system right now, but What If stops working completely somewhere between 3.7.2 RC1 and 3.7.2 RC3. 3.7.2 RC1 seems playable with 74 warnings, but I haven't managed to get that number to any less.
I'll try DoS with mediavps_2014 again then, last time I tried I was under the impression the mediavps_2014 weren't loading as intended at all.
-
I tried your guys' suggestion about downloading SFS from the author's site itself and it worked! Upon loading I got 17 errors in the warning screen but it seemed to work fine despite that. Something I noticed while playing though. Sometimes Ulysses fighters would just be a dot on the radar instead of the standard fighter 'triangle'. Amun bombers would also be a dot instead of the bomber symbol. It's not a big deal but just something I noticed.
Concerning something else you guys are talking about: I played Allied Forces and it seems playable to me despite getting a lot of error warning screens before missions. However, I would not be opposed to that getting a cleanup by the FSCRP.
-
I haven't started Allied Forces, but in the very first mission of Allied Worlds, there is supposed to happen a capship battle. And it's basically just half a dozen Ulysses flying around with Hercs and stuff. Hilarious, but not really playable to full enjoyment.
Oh and I'm glat you got Storm Front working. =)
-
Something I noticed while playing though. Sometimes Ulysses fighters would just be a dot on the radar instead of the standard fighter 'triangle'. Amun bombers would also be a dot instead of the bomber symbol. It's not a big deal but just something I noticed.
That's because those ship classes (GVF Ulysses and GVB Amun) aren't assigned radar icons by either Storm Front or MV_RadarIcons.vp. (MV_RadarIcons.vp does assign icons to the GTF Ulysses, the PVF Ulysses, and the PVB Amun, though.)
-
I've seen this thread just now, so sorry for not having answered. The versions of Storm Front which are currently available in public are all very old and outdated. I've been working on a major Upgrade (and episode III) for a couple of years now which has made some great progress lately. I hope to get it released until next year. Until then the least disappointing and annoying thing to do might to consider Storm Front a (partially) defunct and extremely outdated campaign.
-
I've run into another mission breaking problem.
It's the mission "Captain Phe". I get the defecting shuttle/transport to its first point ("time to" goes down to zero) but then it just sits there instead of going toward the Vasudan corvette like it's supposed to. Even after I destroy all of the bombers attacking the friendly corvette, both ships just sit there doing nothing.
-
I died five times to get past that mission and was able to continue the campaign...the last mission I completed was Act 3 mission 1 "In Sheep's Clothing".
The loading screen (green background with GTVA logo) would come up and the loading bar would go all the way across the screen so it looks good but then the game crashed like before. I can't get into the game with a debug build.
Here is something I came across though:
Weapon explosion 'bomb_flare' does not have an LOD0 anim!
KERNELBASE.dll! IsNLSDefinedString + 1154 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
fs2_open_3_7_1_20140902_r11061-DEBUG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes
That wasn't the only one like that I ran across. There were a number of notices that that something "does not have an LOD0 anim"
-
Weapon explosion 'bomb_flare' does not have an LOD0 anim!
That's a Warning, not an Error. You can hit "no" to continue and try to reach the actual crash.
-
I tried hitting no to continue and it kept giving those notices and I couldn't get into the mod on the debug build.
-
Any solutions/ideas or should I just wait until SF-Junky makes his update?
Also, has anyone else been able get beyond the level I reported the problem at?
-
I have the same problem, the mission we are talking about is the one after you retrieve LT Bakhu from the corvette right?
-
I believe so.