[castor]

This is related to multiplayer on Linux.
I was in-game DL'ing this mission ShivanSps made, and at the end of the DL crashed with: "ERROR: "Couldn't open mission 'TSM_001_artofwar_fs2.fs2'" at mission/missionparse.cpp:6021" (edit: I guess that could be normal, dunno whether it was logged before or after the DL).

Still, the mission file ended up in ~/fs2_open/data/missions and worked ok when I tried to host it later.
Could it be that it doesn't know to look at user home when in-game DL'ing or...?

Edit: FSO 3.6.9 from CVS 07/01/20

[Turey]

Make sure that, on the multi options menu, you turn of the multidata options (there's one right above the pxo box, and one on the right hand side.)

I've gotten this error when it downloaded the mission to freespace2\data\multidata instead of freespace2\data\missions.

[castor]

Good point, seems it was set correctly though.

[taylor]

Remember that most Linux filesystems are case sensitive, and that isn't something that's fully dealt with properly in the code.

When you run the game it looks for all files that it understands and adds them to a memory cache so that they can be accessed very quickly later on.  The filenames in this cache are NOT case sensitive.  Anything that is added while the game is running however, does not get added to the file cache.  Instead it will have to manually search the disk to find the file(s), and those searches ARE case sensitive.

So, if it was trying to load "TSM_001_artofwar_fs2.fs2", and the filename on the hard drive wasn't exactly the same, then it wouldn't be able to find it.  But, if you exited the game after the file was downloaded, and then run it again, the file would work just fine since it would be in the file cache and not be subject to a case sensitive filename search.

Make sense? 


Oh, and the missions vs. multidata thing shouldn't matter one bit.  It will look on the hard drive for both paths, and a mission should work from either folder.  It's just that the case sensitivity becomes an issue anytime it looks on the hard drive.

[castor]

Make sense? 

It did... eventually
Well, it got me by surprise, not the next time..

[karajorma]

Oh, and the missions vs. multidata thing shouldn't matter one bit.  It will look on the hard drive for both paths, and a mission should work from either folder.  It's just that the case sensitivity becomes an issue anytime it looks on the hard drive.

Not on Window is won't. No idea about on Linux but on Windows the standard behaviour when multidata is turned on is to delete the mission from the missions folder, xfer to multidata and then try to load from the missions folder.

[taylor]

Not on Window is won't. No idea about on Linux but on Windows the standard behaviour when multidata is turned on is to delete the mission from the missions folder, xfer to multidata and then try to load from the missions folder.

Then it's a bug and should be in Mantis.

EDIT: I know that the delete thing has already been Mantis'd before, and there isn't really anything that we can do about it, but it should still be able to load just fine from multidata.  If it doesn't, then that's the buggy part.

[karajorma]

I remember sending you a PM or email about it and basically hearing that it couldn't be fixed easily and that the only thing to do was to simply stick the missions in a VP file or turn off multidata so I didn't bother submitting it.

And no it doesn't load from multidata (Or at least it didn't). If it did I probably would have only spotted the error after it had deleted half of my BtRL missions instead of one easily recoverable one.

[[DW]-Hunter]

that reminds me, that the mission packages on game-warden are out dated by a long shot, turey and I have updated the installer to download my mission package, which is a updated version of the old mission package made by the BDHR guys. I will be looking for more missions made by people for the next one, and if theyre any voices for the mission i need them too.

[taylor]

I remember sending you a PM or email about it and basically hearing that it couldn't be fixed easily and that the only thing to do was to simply stick the missions in a VP file or turn off multidata so I didn't bother submitting it.

Ehh, I guess I forgot about it then.

I'm tweaking lots of things for the first of my X-builds though, and I went ahead and modified the load order here.  The X-builds are just a test platform for new features anyway so this is a good opportunity to see how well the idea will work in practice.  I moved data/missions/ down in priority, and I'm also going to fix a couple of mission open issues which are probably making the problem worse as well.


@[DW]-Hunter:  I've got way too much on my plate at the moment to worry about this, but please remind me around the end of next month about your missions.  I'll be starting the move for the new FS2NetD upgrades at that point and I want to make sure to get all tables and all missions that everyone likes to use properly validated.  It will become more of an issue to have things validated at that point anyway since the stats saving code has gotten a major upgrade over how it worked before and, as one of the primary design bugs in the original FS2NetD code that has been addressed, I'd like it work as smoothly as possible for everyone.