WYSIWYG HUD Editor - Coming Together
Current version - permalink to the latest version
Currently working on: Image loading (the pictures you see on your HUD). If anyone has information regarding what happens after the first 64 bytes in a VTF file, or VMT files, please share :)
Since my last post here, I've been focused on the UI and in turn user experience. As such, I have added a bunch of non-functioning menu items to try and get a feel for how I want it to look. I have also further optimized the methods which draw components on the screen, but they still aren't completely accurate, nor do I claim them to be. Still to-do: text, images. Ideas for UI design welcome.
To get them to be accurate, I have to load vtf files from the game itself. To load the vtf files, I have to load them from the gcf files... Would it be unreasonable to include those files in the editor, at least until I can implement loading of the local gcf and vtf files? The file size would jump at least 20mb higher from the current <64kb, and I really don't like the thought of that for multiple reasons: updates changing or adding things, more to download/upload when something is updated.
Also included is an auto-update feature. Note that this feature can be buggy sometimes and overwrite the editor with a bogus copy - you will have to re-download it manually. I will try to push a minor update out at least every 48 hours with at least one visible feature.
I have started writing the code to deal with saving your modifications, but I think I will have to re-design a few things internally to make it function correctly.
Planned interface additions:
- Making the properties table content-sensitive. i.e, if the value is a colour, show a colour chooser.
- Drag and drop palette (labels, images, coloured rectangles)
- Making everything work :P
So.. opinions/thoughts on interface design? Please don't just vote and move on..
Posted Oct 23, 2012, 10:19 AM UTC · edited
For the vtf resources you could make them a separate download that you didn't update as much so that every update to your program didn't require users to redownload resources. They could just unzip to a specific directory.
Wow, why didn't I think of that? >_< Now I won't feel so bad for packaging them as raw images.
This is a good fallback solution for as long as you need to avoid reading them from the game itself. From one programmer to another, what is the downside of reading the files from the local game installation?
Just a stopgap to tide the program over till it can read from the game files. Seems like the project goals would suggest pursuing a working interface before implementing reading the game files. In addition, putting the files in a directory in the installation allows the user to drop in their own files in a similar way and have them implemented consistently by the program, if anyone wanted to do that.
Not that many would be overriding those - they don't work on sv_pure.
Then where do custom frames and stuff for the hud end up? Sorry if I have no idea what i'm doing...
If I read from the game itself, I don't have to manually update whatever is new. Meaning I won't get yelled at to update it after a major TF2 update ;)
I may have misspoke. I presume that is the upside of reading the files from the local game installation as opposed to some other source. I just wasn't sure if there was some sort of computation or complexity downside to that to make it not considered as an initial solution.
The complexity is that I have never worked with those file formats before, and they would take a while to implement which would mean less progress elsewhere. It is just me working on this too...