[kfm187]

I'm trying to get fs2_open 3_6_9RC7 to use missions that I have edited myself. But, for some reason, it continues to load the old versions!    I have removed root_fs2.vp and mv_core.vp after extracting their contents using vpview to ~freespace2/data/ and then deleted all files named *.fs2 in ~freespace2/data and subfolders. But it still finds missions to load! I've also cleared out the contents of all cache directories I could find (data/missions/backup* and mediavps/data/cache/).

I've tried putting my new missions in my mods directory (mediavps/), into data/missions/, and into data/, all with no success. I still get this old version of the missions being loaded.

Using debug mode, it says the following:
Building file index...
Searching root 'C:\program files\freespace2\mediavps\'
Searching root pack 'C:\program files\freespace2\mediavps\mp-710_adveffects.vp'
Searching root pack 'C:\program files\freespace2\mediavps\mp-710_effects.vp'
Searching root pack 'C:\program files\freespace2\mediavps\mp-710_models.vp'
Searching root pack 'C:\program files\freespace2\mediavps\mv_adveffects.vp'
Searching root pack 'C:\program files\freespace2\mediavps\mv_effects.vp'
Searching root pack 'C:\program files\freespace2\mediavps\mv_models.vp'
Searching root pack 'C:\program files\freespace2\mediavps\mv_music.vp'
Searching root pack 'C:\program files\freespace2\mediavps\mv_textures.vp'
Searching root 'C:\program files\freespace2\'
Searching root pack 'C:\program files\freespace2\smarty_fs2.vp'
Searching root pack 'C:\program files\freespace2\sparky_fs2.vp'
Searching root pack 'C:\program files\freespace2\sparky_hi_fs2.vp'
Searching root pack 'C:\program files\freespace2\stu_fs2.vp'
Searching root pack 'C:\program files\freespace2\tango1_fs2.vp'
Searching root pack 'C:\program files\freespace2\tango2_fs2.vp'
Searching root pack 'C:\program files\freespace2\tango3_fs2.vp'
Searching root pack 'C:\program files\freespace2\warble_fs2.vp'
Searching root 'h:\'
Found 19 roots and 11938 files.

(H is my cd drive, but it has no cd in it. There are no *.fs2 files in any of those roots, as far as I can tell using VPVIEW and windows file search.)

On the briefing screen, it says 'NAME:SM2-05.fs2, mod: 04/16/05 at 20:39.58' and the original mission loads and plays properly.  I know that something is happening because, when I delete 'freespace2.fc2' from ~freespace2/data/missions, I get an ingame message saying it can't find the current campaign.

So can somebody tell me where these missions live? Or how I can get the debugger to print out the whole path to the mission file? Thanks!



By the way, FS2_open is an awesome project.

[Mobius]

BERSAGLIO INDIVIDUATO! PREPARATE I CANNONI!!!

PRONTI A FAR FUOCO!!!


FUOCO!!!



Ehm,clearing the VPs is not a good thing....
Are you using a MOD?

[kfm187]

Thanks for the welcome. Italian??

Ehm,clearing the VPs is not a good thing....
Are you using a MOD?

This is a fresh install of fs2_open on a fresh install of fs2 original. The only mod I'm using is the suggested technique of putting the fs2_open .vp files in a separate directory (mediavps) and then setting up the launcher (5.4, by the way) to load mediavps as a mod directory. No oher mods.

I'd prefer to not unpack the vps, either, but I don't have much choice since I'm trying to find these phantom mission files. Just simply putting a new, updated mission file (with the same name as the original) in my mediavps mods folder isn't doing the trick. Unpacking the relevent vps is the only way I can see to remove all the mission files that fs2_open can find *without* making it choke on not being able to find other needed files.

[Dark Hunter]

#1. Deleting the original VP files was NOT SMART.
#2. Deleting Freespace.fc2 was also not smart. That file controls the entire original campaign!. It's no wonder you can't find the currently active campaign... you deleted it.

#3. Why did you put your missions into mediavps/data/missions? I can't think of a reason that it wouldn't work, but I also don't see why you did that. There is already a data/missions in the FS2 folder, that's where I put my missions, and they work just fine.


Solution: Re-install both FS2 and FS_Open, cause you've caused a bunch of damage in there, my friend. Put your missions into FS2/data/missions, look in the simulator in the tech room, and select "Single Missions". They should show up.

[karajorma]

Do me a favour. Instead of trying to use the names of existing FS2 missions try saving a copy with a new filename and see if you can find that in the flight simulator instead.

#3. Why did you put your missions into mediavps/data/missions? I can't think of a reason that it wouldn't work, but I also don't see why you did that. There is already a data/missions in the FS2 folder, that's where I put my missions, and they work just fine.

Frankly I'd say that Mediavps\Data\Missions is a more correct place to put them. Those missions will either crash or fail to load when used with the retail builds so why place them where it will find them when you have a second equally valid place to put them?

In addition if you are also working on a mod which uses its own tables rather than the default FS2 ones these missions will still show up in the flight simulator and will still crash FS2_Open as soon as the game encounters something it doesn't like. That's a problem with using the mediavps folder too but it's less likely to appear cause not all mods use the mediavps.

Personally I've always said that the best place for mission files is in the Data\missions subfolder of a folder with the same name as your campaign.

[kfm187]

Do me a favour. Instead of trying to use the names of existing FS2 missions try saving a copy with a new filename and see if you can find that in the flight simulator instead.

Good Idea... Here's my results, and they just get weirder:

1. In ~freespace/data/missions, there is nothing but the campaign file.
2. root_fs2.vp and mv_core.vp extracted (except for *.fs2) in ~freespace/data and removed.
3. In mediavps/data/mission, I created 3 missions:
 * SM2-04.fs2 - Just like the original, but with a ship name changed
 * SM2-05.fs2 - Just like the original, but with a ship name changed
 * SM2-04-Newname.fs2 - Just like the original, but with a new name and ship name changed
4. In the campaign, my pilot is currently attempting SM2-05.fs2

Going to the tech room, when I click on single mission, I get SM2-04-Newname.fs2, which is good. 

When I click on campaign missions in the tech room, I get everything from the first mission all the way up to and including SM2-04.fs2 (which makes sense because that is how far my pilot has got in the campaign).

When I run SM2-04.fs2 from the tech room, I get new SM2-04 with the changed ship name. The debugger claims the modification date for SM2-4 is today, which is good.

When I go to campagin mode, I also get the new mission (with timestamp=today). So far, so good.


BUT when I delete SM2-05.fs2 from mediavps/data/missions (and there are no missions in ~freespace/data/missions and no root.vp or core.vp) and restart FS2_open, it somehow picks up an old SM2-05.fs2 (with a timestamp in 2005) from somewhere rather than complaining with something like 'Can't find mission....' I've searched my entire drive for all *.fs2 files and there are none in any subfolder of ~freespace2, and no copies of the root or core vps anywher eon the dirve, either. There is also no cd in the cdrom drive, and no virutal drives moutned, either.

So, karajorma, you fixed my problem, but I'm not sure how. Is there a duplicate set of missions hidden in one of the other vps? Is there a cache somewhere that I don't know about?

#3. Why did you put your missions into mediavps/data/missions? I can't think of a reason that it wouldn't work, but I also don't see why you did that. There is already a data/missions in the FS2 folder, that's where I put my missions, and they work just fine.

Frankly I'd say that Mediavps\Data\Missions is a more correct place to put them. Those missions will either crash or fail to load when used with the retail builds so why place them where it will find them when you have a second equally valid place to put them?

I'd concur. As far as I can tell with the priority system, if you put new missions in the original data/missions and you mistakenly have missions with the same name anywhere in one of your mod folders, the old missions in the mod folder will take precedence which is probably not what you want. For missions it's prolly not a big deal, but I'll bet it would wreak havoc if you were doing that with tables or textures.

[Dark Hunter]

@Kara: I never use retail since getting FS_Open so that isn't an issue.

@kfm187: When it comes time to VP-ify my campaign, those missions will be deleted from data/missions. I never place a file in more than one place.

[karajorma]

@Kara: I never use retail since getting FS_Open so that isn't an issue.

This is where you're going to kick yourself. The problem IS caused by where he was choosing to install the missions. There IS a second set of mission in the media VPs. I forgot about them last time but they're in mv_models and they're there to make the ship nameplates work. These are the missions that should be used as the basis for any changes that are made to the canon mission rather than the version in root_fs2.vp.

Installing the edited missions to mediavps\data\missions should override these. Installing to data\missions would not.

[Mobius]

@Kara:

Ha-hem!!!!

Thanks for the welcome. Italian??

It wasn't a welcome,I said:

TARGET SPOTTED! PREPARE THE CANNONS!!

READY TO FIRE!!

FIRE!!!

As for the welcome,then:

BENVENUTO AI FORUM DI HLP!!!!

[kfm187]

This is where you're going to kick yourself. The problem IS caused by where he was choosing to install the missions. There IS a second set of mission in the media VPs. I forgot about them last time but they're in mv_models and they're there to make the ship nameplates work. These are the missions that should be used as the basis for any changes that are made to the canon mission rather than the version in root_fs2.vp.

Installing the edited missions to mediavps\data\missions should override these. Installing to data\missions would not.

Well, that explains it, but it is still weird. Do you really need the missions in mv_models to have the same name? Can't the fs2_open global file finder/indexer find them just as well in root_fs2?

[Turey]

Do you really need the missions in mv_models to have the same name?

short answer: Yes.


longer answer: yes, because otherwise you would have two main freespace campains. When you name them the same as the old ones, they hide the old ones.