Tuesday, February 8, 2011
first is done
Okay, all assets are updated to work correctly. Now on to the disassemble of the Q3 into bite sized pieces. (and hoping to get over whatever is making me ill right now, grrr)
Monday, February 7, 2011
finishing up first part.
going through and adding the code to mark each asset correctly when written out. The read code checks the asset type, but doesn't save it anywhere. So adding in alittle code to put back in the asset type in the file when writting to disk. It is simply putting in a little code at the beginning of each base asset but alittle digging for it.
After that then I will start on the code to rip the Q3's apart. Then on one that will put it back together so I can see if the Q3 still works after the take apart and rebuild. If all goes well, then I have to learn some more graphics coding to get the editor running.
Will see where this heads off into.
After that then I will start on the code to rip the Q3's apart. Then on one that will put it back together so I can see if the Q3 still works after the take apart and rebuild. If all goes well, then I have to learn some more graphics coding to get the editor running.
Will see where this heads off into.
Slow weekend
Well, not as far as I wanted, but weeked was brothers daughters b-day party (three day pool party), was sick (somewhat), and spent way to much time working on some syntactic sugar that just wouldn't sweeten up for me (so will continue with some ugly code).
So far got almost all the functions neater now and almost done with the mSave functions so it will write out to a file properly. Next is to start putting together some of the code to tear apart the Q3 into bitesized chunks for working on it. First is to pull all the images and assets that point to them into one file as a master that all the others will reference. This will be messy going, but once done it will make the editing easier for how I picture doing it.
So far got almost all the functions neater now and almost done with the mSave functions so it will write out to a file properly. Next is to start putting together some of the code to tear apart the Q3 into bitesized chunks for working on it. First is to pull all the images and assets that point to them into one file as a master that all the others will reference. This will be messy going, but once done it will make the editing easier for how I picture doing it.
Friday, February 4, 2011
Rework of editor idea and such
Okay. Have been thinking on how would be best to edit a file that has in the ten's of thousand assets in it. I have decided to make a slight modification to the Q3 general format to allow me to pull apart the whole file and make subfiles of each tree of assets. They will all reference a central image file.
This way I can have a file that would be each ship UI in the game and hold all the information needed for that specific UI. The references to the central image file will be by image number and not by specific offsets as in the Q3 right now. This will allow images to change without having to worry about all the offsets of all images after it. Since when you write out a full intergrated Q3 file for use it will simply figure the offsets on the fly and insert them into the file as it is written out.
I am still kicking around an idea of a fully stand alone update format that can be integrated into the Q3 from stand alone editors that can be handed out to developers (like FoaS to make the UI's) These files would hold the new images in themselves, but reference the main image file for the images that are used in multiple UI's (like the image of a weapon point, or the shields).
This would allow the community to make updates to the Q3 with the stand alone editors and submit them. Then we can review them, make sure they look good and integrate them into the Q3 with minimum problems.
A full editor that can change anything in the whole Q3 will be worked on also, but will not be released to the general people (the first one might not also, have to kick the idea around to those in charge but who knows.) I am going to jump on modifying my reading and writing code to handle this edition to the data. This will mainly add the extra information to the parts needed and write a second set of read and write functions that use the different data so it will work.
The editor will be nasty to work with to start as I am learning the programming stuff needed to work with SDL/graphics and such as I go along. So start crude, and refine as I go along and learn more.
I am hoping to get the main functions modified before the weekend is over. This also might allow me to pull the Q3's of SFC, SFC:EAW, and SFC:OP apart and put together a new Q3 file using parts of each (with a probable need of updating images from the older stuff).
On to coding. . . .
This way I can have a file that would be each ship UI in the game and hold all the information needed for that specific UI. The references to the central image file will be by image number and not by specific offsets as in the Q3 right now. This will allow images to change without having to worry about all the offsets of all images after it. Since when you write out a full intergrated Q3 file for use it will simply figure the offsets on the fly and insert them into the file as it is written out.
I am still kicking around an idea of a fully stand alone update format that can be integrated into the Q3 from stand alone editors that can be handed out to developers (like FoaS to make the UI's) These files would hold the new images in themselves, but reference the main image file for the images that are used in multiple UI's (like the image of a weapon point, or the shields).
This would allow the community to make updates to the Q3 with the stand alone editors and submit them. Then we can review them, make sure they look good and integrate them into the Q3 with minimum problems.
A full editor that can change anything in the whole Q3 will be worked on also, but will not be released to the general people (the first one might not also, have to kick the idea around to those in charge but who knows.) I am going to jump on modifying my reading and writing code to handle this edition to the data. This will mainly add the extra information to the parts needed and write a second set of read and write functions that use the different data so it will work.
The editor will be nasty to work with to start as I am learning the programming stuff needed to work with SDL/graphics and such as I go along. So start crude, and refine as I go along and learn more.
I am hoping to get the main functions modified before the weekend is over. This also might allow me to pull the Q3's of SFC, SFC:EAW, and SFC:OP apart and put together a new Q3 file using parts of each (with a probable need of updating images from the older stuff).
On to coding. . . .
Thursday, February 3, 2011
wow.
Going back into using SDL and doing some graphics. I have forgot a bit of this. But it shall come back to me as I move forward. Hopefully.
Wednesday, February 2, 2011
found flash
I found my flash drive that has all the Q3 work I had done so far, so no need to try and necro my old computer yet. Going to copy it over and work on the graphics again. Then back to the fun of trying to get an editor started. This will be slow as I have never made a graphical editor before, only CLI ones.
Tuesday, February 1, 2011
step one
Well, got the base done now. Can load in all the assets. Have to revive the dead machine long anough to pull some files off it. That way I can get the graphic stuff. But then again a rewrite might be in order.
Subscribe to:
Posts (Atom)