Pof Tools is a program for Windows and Linux which let's you edit properties of Freespace's model format .pof as well as convert them to and from .dae that is meant as a successor to PCS2. If you're familiar with PCS2, this program will feel largely similar.Download hereThe github is here
. I'm more than willing to accept any code contributions, and if you have any bugs or feature proposals you can post an issue on the github, post here in the thread, PM me, or @ me on the discord.
This is still a work in progress, and this version will represent version 1.0 after a brief period of public testing on v0.9 to ensure nothing's too buggy. Including some of the features I've posted to the github, this is a brief list of features I intend to eventually implement that are not yet done:
Wait, What's Wrong With PCS2?
- Importing subobjects from other .pofs
- Importing/Exporting only geometry from/to a pof
Displaying Textures (basic stuff only, use the lab for something visually representative) Done in version 1.2!
- Blender-like movement/rotation handles on 'lollipops'
- Display of turret fovs and adding the additional turret fov parameters in .pof
- Adding several other table-only data structures to .pof (contrails, maneuvering thrusters, etc)
Not all that much really, it's still fundamentally capable of 99% of what modders need as is. However there are 3 main advantages to starting again:
1. PCS2 will totally let you enter all sorts of invalid states, and put in bad data all over the place, which makes for a lot of nasty surprises when used in FSO. There are a lot of avenues for aiding the user, presenting data in more intuitive ways, and warning them about potential issues, which are primary goals of Pof Tools.
2. The .pof format has been basically frozen since our only .pof authoring tool has not been maintained, preventing new features from being added and any that are added basically require hex-editing in order to do. This has also resulted in a lot of features that should have been in the .pof get put in the table instead, and nobody likes tweaking positional or directional vectors in text form.
3. There is still that 1% you can't do, like the new features added that PCS2 doesn't support, and the various bugs it has accrued over the years.