Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Marcov on January 01, 2010, 06:37:43 am
-
Ancient-Shivan War
"The currently active mod has generated 64 error messages during startup. This may be the cause of incorrect formatted table files to corrupt models etc. etc."
WTF?
:mad:
Then it says something like
"cannot load main screen. You are probably missing the main hall file"
:mad:
Why the hell does this happen? The same thing happened to me in Blue Planet (though the Main Screen was OK, it's just the no laser models that I was amused at), but Procyon Insurgency was freaking fine! Somebody help me!
-
Oh, for the love of kittens.
Why the hell did you post this HERE?????
Plz to split and move to support.
-
- Select the debug build (fs2_open_3_6_10_debug.exe) and run it. If you've been experiencing crashes, do exactly what you've done previously, up until it crashes.
If you have had other issues, it is sufficient to run it until you get to the Main Hall. If the debug build crashes fatally even before getting to the Main Hall, no worries. - Quit the game.
- Find fs2_open.log from \freespace2\data\, copy it to a safe location and include it to your post, either as an attachment (click Additional Options when posting) or using the "code" tags.
-
Okay, here's the log;
[attachment deleted by admin]
-
1. There are no ASW files to be seen anywhere.
2. Searching root pack 'C:\Games\Copy of FreeSpace2\fsport-missions.vp' ... 139 filesBelongs to your \fsport\ folder.
3. Searching root pack 'C:\Games\Copy of FreeSpace2\Merkar_Demo.vp' ... 8 filesDunno what that is, but put it into its very own subfolder.
4. Searching root pack 'C:\Games\Copy of FreeSpace2\data\tables\INF_Enemies.vp' ... 107 filesProbably belongs to your \inf\ folder, but most certainly not to \freespace2\data\tables\ .
-
1. There are no ASW files to be seen anywhere.
So what do I do know? If I open the debugger (after selecting ASW from the Launcher) it crashes. If I run ASW with the launcher, the error message still is there and there's no main screen. I'll just show you what my file exactly looks like;
Okay, here's my main FreeSpace directory, and the "Ancient Shivan War" folder is highlighted.
(http://img689.imageshack.us/img689/6258/howmyfileexactlylooksli.jpg)
Then I opened the "Ancient-Shivan War" folder...
(http://img189.imageshack.us/img189/6258/howmyfileexactlylooksli.jpg)I then opend the "ASW" folder and this is how it looks like (strangely enough it's almost 700 MB in size);
(http://img189.imageshack.us/img189/9715/howmyfileexactlylookslic.jpg)
-
Passed cmdline options:
<none>
Building file index...
You need to select the debug build in the Launcher, and start it with the same options that you start the regular exe with.
Before you do that, however, do the things Jeff told you to do above.
In addition, the "ASW" folder should be in the FS2 directory, not nested in an "Ancient-Shivan War" folder like you have now.
-
Incidentally, please don't resize the screenshots (the same thing as with A Celebration of FreeSpace). It's really hard to try and read the file names.
And as The E already explained: do what you've tried to do before, but this time, use the Launcher to select fs2_open_3_6_10d.exe instead of fs2_open_3_6_10.exe. Running a debug build outside the Launcher doesn't really benefit anyone. Then, Run the game. If you get warnings, click No (the option that allows you to proceed). Then, the log will probably be sufficient by the time you reach the main hall, so quit the game. Now, post the fs2_open.log file; it will probably be useful this time.
I then opend the "ASW" folder and this is how it looks like (strangely enough it's almost 700 MB in size)
Not particularly strange. My ASW folder is the same size. If you mean that the size of the folder is larger than the reported file sizes in the ASW release thread at Sectorgame, it's perfectly normal: the files there (apart from the insignificantly tiny patch) are .zip archives. If you zip a bunch of files, the resulting .zip is often noticeably smaller than the original files. And that's the idea. Packed archives like .zip, .rar, .7z etc take up conciderably less space on the servers, and they'll conserve bandwidth, when the end users download only the smaller archives and then unpack them at their own computers.
-
Here's the log (after exiting the main hall);
Problem is, when I ran it with the debug build, it crashed instead of going to the main hall. Does this affect anything?
[attachment deleted by admin]
-
And now, you have apparently managed to mess up your mediavps. Make sure all the mediavps vp files (those starting with mv_) are in the mediavps directory. ASW needs those to function correctly.
You do have the mediavps, don't you?
-
Squinting my eyes to the max here, but can't see a "mediavps" folder in those screenshots. But with that graphics card, I'm not that surprised.
-
What's in the "freespace special features" folder? If the mediavps are in there, that may very well be the problem.
-
And now, you have apparently managed to mess up your mediavps. Make sure all the mediavps vp files (those starting with mv_) are in the mediavps directory. ASW needs those to function correctly.
You do have the mediavps, don't you?
The mediavps are in the "Mods folder" (when I open Mods there's another folder called "mediavps" where I put the mv files). The "FS2 Special features" folder is the old mediavps which the FS2 Open thread told me to delete.
-
I'm pretty sure that means your MediaVPs will not work. Nor will any mod using a mod.ini, basically. You should place all your mods in correctly named individual folders in your main FS2 directory. For example, MediaVPs should go in a folder called 'MediaVPs' located in your main FS2 folder.
-
Yeah. The mediavps folder (and all other mod folders) should be in the root fs2 directory. That's where other modders expect them to be, which means that their mod.inis will be written with that in mind. If you choose to do it differently, you are of course free to do so. However, you will need to edit the mod.inis to reflect your setup.
And if we tell you to delete something, we usually mean "delete". Unless you want to keep old data around for archival reasons, there is literally no point at all in not following our advice.
-
EDIT: Just realized I posted this on the wrong thread. Dang 4 hours of sleep......