Power Supply go poof

Well, wouldn't you know it, as I start to get going on things. My power supply on my desktop glitched. One of it's fans are dead, and it overheated on me. Not sure how bad it damaged it. But with it heating up now, it is not usable for development. I have all my programming IDE's up on that machine, so it kind of bites.

Will probably migrate stuff over to the wives laptop (argh, a Vista machine).

So the anouncement of a teaser was a teaser in itself. (as it delays everything for awhile) Hope things will work out alittle faster so I can get going on this again. Should be able to.

Little bit

Okay got it so it will load up an image and hold it on screen. Also can pull up an asset by name. It doesn't all show up yet, but I can open the startup.q3, index it, then pull up the opening asset by name.

It still has to get the code added to make the ui buttons function at least to the amount that you highlight when going over them. Then will add in a scripting language (lua) to make the buttons do something. (mainly just make the quit button quit. But also have the buttons that pull up other sub menu's actually do that.

This is the first step to getting a personal UI system that will read the whole Q3. As I get to know how the buttons work I will get a better feel for the UI system in general. If I ever get to read the code this should have given me a good foundation to work with it.

My scripting language will be Lua not QUIL as I have no access yet to how QUIL actually works or looks like. But off to bed, have to work in a few hours. Night all.

Oh, after I get this up and running my son wants me to make a teaser, so maybe next week sometime I shall do that.

A funny thing about memory

It is strange to go back over old code. To see what you were thinking at a specific spot in time. It is like a snapshot of a mindset. You can see how muddy the waters were, how much you have learned or forgotten from that point.

I am going back over some code that was in a folder Q3. (this under dev-c++, I was using three different compilers as I was working on this before). I was using the Setup.q3 from the CD. The initial install menu that comes up. I have to rework some of the code, but it loads all of it into memory and gets it ready to use for running the menu (without the actual function of installing). It will take alittle getting neatened up, and a few major changes on function but I hope to get a running simulation of that Q3 interface by tonight. Then it would be abit more work to expand out to make it work with the normal Q3. (will have to write UI scripts then)

Well, back to diddling.

a little time away

Well, was working on the plans of a sailboat I am going to be building over the next year or so. So took some time working over plans that were designed back in 1880's Picked one out so ready on that part.

Also have been going back over old code I have written. I have forgotten abit of how to do SDL and OpenGL over the summer. So gettting back in the swing of it. I need to know this so I can write the editor. I am hoping to get back up to speed in not to long a time. Got to get a program started that will load a Q3 image and then move it around on screen with a mouse. Then will work on getting it to do more. Baby steps.

newlife?

With anouncement on Dynaverse that maybe the development of SFC might start again, I have alittle more hope now.

So far I have been walking through the UI of the Mirak, getting about one little piece done a day. Still working on the top of the combat UI, did helm, engineering, science so far.

I am wondering if the combat interface is set in size from the images it uses, or the images are set by the size allocated by the interface. Logic says the first. If this is true, it might be possible to set up the side interface to be larger for higher resolutions. Will be looking into this as I move along.

working through assets

mapping out the asset trees now so I know what will change what. I want to get down how the UI runs, before making much in changes to it. So far found something like 180 major layout assets (combination of ones that just hold the buttons for general use, and radio button ones).

Each of these hold usually 3 or more other assets (buttons, images). With each button holding around 3 images each. So to totally change the Mirak UI, will take hundreds of images (mostly the buttons because each, have a normal, selected, and highlighted image) As I figure out each section, I will see about posting the images that work with it, first will be the helm controls.

so far.

Had a great idea last night, but checking it out today nixed it. I was thinking it might have been possible to add new races into the game after I get the hang of the race UI stuff. But from my research since I got back home, they use an enumerated type in the source for races, it is held in race.h (source code stuff so can't see it). So I was alittle let down this morning.

Bright side tho. I have gone through the 322 pages of the Mirak UI Q3 stuff. Took notes on the major assets (the ones that layout the basis of the screens, and hold the more detailed stuff in it). Now to go back through all 322 pages maybe two more times. Then match the assets to the images (find out how many images total are needed to change the UI). Then try and get it into a format so someone might be able to redo the UI's. Good thing is that every race has the UI done the same. So done once, it will work for all the races in case some tweaking is needed to images.

Rant first.

A little rant, I got most out of my system at work last night. But I just have to say, I have little faith in leadership in XC. Been waiting forever for an update to see if ever SFC is going to be worked on. Or if it is to just be scrapped as Frey seems to like STO alot now.

Going into year two since the announcement of SFC4 being worked on and seems not a thing has been done. I understand that leader doesn't want to be in charge of the project, but if no one is stepping up, please just announce that it is on hold. Someone should be at least going through the source to get it ready for when something might be done.

I had offered to help out (twice). Work on organizing and documenting the code. So much could be done faster if only some of the "precious" code would find itself in willing hands. I could be a half year or more ahead of where I am now.

We need server code working, games running, or what is the use of doing anything for the game.

Ah, better.

more and more

still going through the pages of information and trying to sort it out into a nice layout for me to work with. yea.

Images

Going back through the images my first image puller did. Boy they are not that great. Will have to write the translator of images to go both ways to make better ones. I had one that translated from Q3 to BMP, but was done when I didn't fully understand the format. I have one that goes from 8bit BMP to Q3 (but has to have the BMP use a specific color table). Now to put them together, let the 8bit image use any 8bit table (grayscale tho), and then also a 16 bit color version (or 24 bit that only uses 16 number of colors). The 16 bit images use a 555 color format but I still don't understand how an image is figured out since they have no way of letting you know what format the colors are saved in on a BMP.

Then expand out to use other formats for the source images to Q3. Adding more shouldn't be that hard after the first code goes down.

Wow part two

Okay, I think I have all Mirak stuff pulled aside, including ships and such. 345 pages of stuff (not including the actual image data). Will be going through slowly and putting together the tree's for how it works, then checking what images are used so they can be replaced. 'Tis alittle biger then I thought it would be.

Wow

Page count is growing on how many is used for the Mirak UI. Went an bought some more ink to print out more of the pages. The more I look it just keeps going. Should have it mapped out in the next two days, then will look at what is needed to add the new images. Also might have found the part that controls the boarding parties stuff and see what is up with that.

The fun way to work

As I go through and get the UI stuff out for the Mirak, I thought I might discuss the process of doing it. As I don't have any specific tools for working on the Q3, it is a fun little path to wonder.

First, I had extracted all the images from the file, with a so-so program I wrote. I didn't have the full format down at that time so some images are alittle funky. So for the Mirak UI, I started looking through all the images looking to see if I can find an image from the combat UI for the Mirak. I didn't find one as I paged through the few thousand images, but came across a Lyran image for the movement control (the one at the top of the UI). So I took note of the offset of the image, then opened up my sector editor (I love my sector editor) and did a search for the offset numbers. This would give me the asset that points to the image.

I then take the asset number off the image pointer, and do a search for a reference to that asset number (this is usually a search backwards through the file). When found, this will be the asset I need. Since this one is the Lyran and not the Mirak, I look at what it was named. It was LL_A3_HELM. So now I have the name for that part of the UI. The game uses the first two letters for the race, so for the Mirak it is ZZ_A3_HELM (yes, Mirak use ZZ since they are the Kzinti). So then I do a search for the new name of ZZ_A3_HELM. As the Q3 usually groups like parts togeather, I start looking down from there and when I don't see any references to ZZ anymore I cut the file off and print it out (I need to see it in copy to work on it as I can look at multiple pages at once this way)

Then I will build a table of what names and asset numbers are used for the UI (referencing back to the folder of images to see what each image being referenced is). After I get this table put togeather, then I will be able to change the images to new ones. By converting the images to the Q3 format, then manually coping chunks of the file to insert the new images at the end of the images in the Q3 (change the reference to where the images end and the assets start). Then edit every image asset so it points to the new images I just put in. (again by hand in the sector editor). If all goes well, after this is done, the Mirak will have a new interface. Might have to tweek some of the kerning on the font to make sure it fits in the spaces (kerning is the spacing on the font, you can move each phrase pixil by pixil up,down,right,or left as needed). Probably will end up with about a hundred things to change, but not sure yet. Have sixteen pages printed out and it isn't the whole Mirak interface yet.

Well, that is the fun I go through to do this, just to let you know why it takes alittle time.

A new start

Now to lay out some direction.

First, what is known about the Q3.

I understand how the images are saved, they made a special format because Q3 seems to have been started in pre-directX times and they have written their own blitter function (how you put an image on the screen). This function doesn't support different screen sizes and just copies pixel for pixel. This means that as you increase screen resolution the images get smaller (as everyone has seen when playing with your screen size).

I have all the asset types broken out, but don't have an understanding of all the parts. Without the ability to view the source code, some parts will probably not ever be figured out (but I have alot of it down). Maybe someday.

The way that the UI runs is in QUIL (Quicksilver U.I. Language), so no new functionality can be added just moved and the images changed around. But ship UI's can be added as the way it is looked for is by searching the Q3 file for names that are gotten from the Shiplist.txt file. So yea, I can add a ship UI to the game (just haven't automated the process yet, and do it with a sector editor).

I can usually fix small errors in the Q3, have fixed an error with the Lyrans using fusion beams. Not sure where it is on the net now, Bonk made an updater that you just had to run and it would fix the Q3 file so Lyrans ran properly.

Two other errors have been brought up to me, an error with the Mirak that the speed bar doesn't work properly and hit and run raids (or something with the security guys have to read it again). Will work on these two as I can.


What I am doing.

I am to get the UI editor done sometime this year (programming skills is holding back quick development).

I am working on a text file based Q3 that will compile into the normal Q3. This will help in editing the file, for fixing errors and adding new ships. It will allow us to make a single text file for a new ship, then run the compiler and add it into the game. It is a work in progress, but an important one in the long run.

I am going to dig in the game and see if they have any parts of the old crew stuff still in the game. I am thinking they might have just cut out the button that let you access it, since fully removing it would take more work to remove the interlinking of how crew woked. So I am thinking they might have just put it in the background. It is a guess, and as time permits I will see if I can find any trace of it.

Someday, if I ever get access to the source, I hope to be able to add new functions to the game and it's UI. Not planning on much of this yet as I don't think the access part will happen and is a waste of thinking.

Kzinti UI

Still working on pulling the Kzinti UI elements out so they can be changed to a nicer looking UI. Sadly I am not an artist so once they are pulled, not sure how quick a new UI will be done.

A dead end

Was looking at finding where the Q3 data was to do the fleet formation stuff. Figured if I found it I could use the information to set other sideline information on wide format screens. Now even tho I found the images, I can't find the Q3 code that uses it so it must be hard coded in the game (which is why it works with the wide screen formats and the rest of the Q3 doesn't. It was a bummer moment.