 |
Removing the contents of "currentfm.txt" seems to help, too, but then you lose all your config settings and have to re-install any FM to be able to save them again. |
 |
Using the latest SVN, I followed the steps that lead to the crash, but TDM didn't crash. The main menu came up fine. Can you reproduce this problem today? If so, I want a list of all missions in fms and the name of the mission whose folder you delete to cause the crash. |
 |
It didn't crash for me either I don't know why this is listed as Crash. I just got the weird black screen with the darkmod menu music playing in the background. |
 |
So is this still a problem or not? |
|
|
When Grayman asked me to try it again on the 5th I did try it and it screwed up. But I just compiled newest source and now it no longer seems to be an issue. The main menu comes up just fine. Going to new mission however shows that nothing is installed, and when I press start mission the dark mod video shows and a blank parchement page is there with objectives at the bottom right. If I press Objectives I get a console window with errors. This should be changed so that if there is anything missing from the installed FMs folder that are needed to make the map run, Darkmod should default to no installed mission state. |
 |
Initial fix for this in Revision 5480. At the moment I just check if the directory is there, but in the future, we can look for other required files like either a pk4 or .map. On that note, exactly which files are required to count a mission as available? |
|
|
Well if there's a pk4 check for a map file inside. If no pk4 exists look for a map file in the /maps folder of installed fm? |
|
|
Additional fan mission checks add in darmod_src SVN rev. 5573. The startup code now checks for the existence of a .pk4 file in <fm folder>/ or .map file in <fm folder>/maps/ I did not go as far as confirming the name of the pk4 (the name of the pk4 file doesn't seem to affect the ability to load the mission) or map file and I did not verify the existence of a map file within the pk4, but this should be sufficient to avoid issues (hopefully). Can I mark issue 0003057 (after testing of the changes) or should I check the file names and existence of map file in the pk4? |
|
|
I don't think it's our job to check that there's a map file in the pk4. |
|
|
Sufficient checks added to guard against missing mission folders and/or map files. |
- Anonymous
