[Kazan]

Kazan, does PCS2's VP library have the capability to extract any given file from a VP into any given directory? that would be nice, I could extract to a temp directory and open from there, and I could add an extract to folder button in there too for any textures that are in a vp.

should be able to do whatever you want

it's util/VPReader.h

this function should do you

Code: [Select]

bool ReadFromVP(kaz_string vp, kaz_string filename, kaz_string destination)
{
    VolitionPackfileReader VPR(vp);
    int filenum = VPR.FindFile(filename);
    if (filenum != -1)
    {
        char membuffer;
        VPR.LoadFile(filenum, membuffer); // loadfile allocates the required size of memory
       
        ofstream outfile(destination.c_str(), ios::out | ios::binary);
        outfile.write(membuffer, VPR.FileSize(filenum));
        outfile.close();
 
        delete[] membuffer;
        return true;
    }
    return false;
}

example call would be

ReadFromVP("c:\games\freespace2\sparky_fs2.vp", "bomber09.pof", "c:\games\freespace2\data\models\bomber09.pof")

[edit]
VolitionPackfileReader can also give you a handle to an open ifstream that is set to the right spot in the file to read the file - i can probably modify POF::LoadPOF() to be able to deal with this

[Bobboau]

excellent

[Kazan]

just be aware that if you go to save a 400meg file that function will allocate 400megs.. so if you're going to be working with large files i'll need to make a function that reads in blocks

[Bobboau]

well... are there 400 meg files in any VPs? or do you mean 400 meg VPs?

[Kazan]

individual files in a vp, and yes... movies can be that big

[Kazan]

If any of these are useful...

did you make those?

[Bobboau]

I'm assuming he did.

are movies (MVE) in the VPs? or do you mean the ANIs.

which brings up a point, we need ANI/EFF support.

[Kazan]

.mve's were unvp'ed on the disk
there is a vp floating around with all the movies in .ogg

[Bobboau]

oh, well I don't plan on using it for anything but extracting the <250k PCX and maybe a handful of larger ANI files.

[Kazan]

hey bob.. i just notied the turret editor is lacking the ability to select gun or missile turret

[Bobboau]

well that's ok, cause there the same, they get filled into the same array in FSO, with no way of telling which they were originally, though I suppose I should make sure they get merged to support the V models that have them differentiated.

literaly

Code: [Select]

case ID_TMIS:
case ID_TGUN:
{
//add turrets here
}


[Kazan]

did i forget to have it mark which type they were in the POF? oops

[edit]
oh.. no i didn't... just FS2 doesn't care anymore - a turret is a turret is a turret

[Bobboau]

it never did.

well maybe FS1, but that's not important now.

[Kazan]

i could have sworn i once had problems with FS2 refusing to treat a turret as a missile turret for me because it was a gun turret

[Bobboau]

I was shocked when I first saw it, even though I knew it treated them the same, I figured it would have SOME difference, but nope they both go through the exact same code.

[Bobboau]

ok, I've been fighting with wxExecute and more specificaly wxFileType::GetOpenCommand for the last few hours, and I just give up, win32 solution done, we'll figure something else out later. in the texture editor, there is now another button for opening the file externally.

it only works for files not in VPs currently.
 it's in my sig.
also make sure I didn't screw up anything when I migrated the new BSP compiler.

[Kazan]

please commit top_level_selected.xpm to the respository

[Bobboau]

oops

should be fixed now.
 I took a look at getting glow and shine mapping implemented, and we will need version 1.3 if we are to have a decent implementation.

[Kazan]

i can import a library that will grab all openGL functions, not just the ones in the microsoft headers but it'll make SDL a dependancy

[Bobboau]

I think that will be acceptable.
though it would be nice if that wasn't necessary, but I guess it is...

it doesn't NEED to be 2.0, it would be nice though, I'm not planing on using any 2.0 features, though I might need something >1.3 at some point, and I might find a use for something from 2.0 later.