This is the sample level that will be included with all future versions of ToeTag. It’s a small level that lets you chose your skill level and then throws you into E1M1 afterwards. Straightforward and simple but it shows that ToeTag works!
Screen shots:
I released a new version today because I believe I’ve got all of the endian madness sorted out with PowerPC machines. Definitely lucky that I have an old iBook G4 laying around here that I could test on! If you’ve had trouble running ToeTag on your machine, try the latest version:
http://www.wantonhubris.com/toetag/Download.html
It still requires Leopard but it should be processor agnostic now. Let me know if it isn’t!
As a side note, the development of this version was interesting. I, of course, had to learn about byte swapping and such to make it work on PowerPC but I had to figure out how to work on the code on the little iBook.
The screen blows on that laptop, limited to 1024×768, so working on it directly was not realistic. So what I ended up doing was I set up the new Screen Sharing feature in Leopard and was able to work on the iBook through a window on my Macbook Pro. Sure, the window was still 1024×768 in size but at least I could use my good screen and my good keyboard to work on the code.
It’s not super fast to work through a network connection but it DID work, and far better than what I was expecting.
So I copied the code over to that machine, worked out the byte swapping and other issues, then copied the code back to my main development machine. Pretty painless and I never had to try and develop code on that little 13″ screen.
Rock on, Apple!
I think … think, mind you … the reason some people can’t run the editor on Leopard is that I didn’t account for PowerPC processor and endian byte order issues. I thought that building a Universal Binary automagically took care of all of that junk but evidently that isn’t the case.
I have a PowerPC iBook here and I will get ToeTag running on it this weekend. So if you can’t run ToeTag at this point, hang in there! If this is the problem, it’ll be sorted out over the weekend.
Wrote up some new documentation:
Texture Alignment. How to make your level look pretty.
My First Room. A run through of how to easily create a room with a player and a light.
More to come!
The latest version of the editor just went up. Damn, I love Sparkle. Automatic updates are SO nice.
This version adds brush clipping, which was one of the last remaining large-ish features missing from ToeTag. Check out the documentation on it here:
The last few days have been a real experience for me in terms of optimizations and code improvements. It’s great when a code base gets to this state because now it’s less about adding features and more about making what is there better. And easier to use. And faster.
I’ve been using E2M6 as my benchmark level. It was atrocious 2 days ago but now I can work on it and it’s smooth as silk! Well, not quite that smooth, but pretty darn smooth!
Enjoy the new version!
ToeTag
I created a new ToeTag build this morning and the Sparkle framework worked great! I tested it out locally and it told me there was a new version, showed me the change list, and downloaded/installed it without a problem. Free libraries like Sparkle are a true benefit to software developers everywhere!
Documentation
I am writing more and more documentation for ToeTag so if you’re using it and are getting stuck, please check this URL regularly:
I am going to strive to get several written each week so the body of work there should grow rather quickly.
Software
Before I go, let me plug 2 pieces of software.
The first is Sparkle. It’s free, it’s easy to implement, and it works. If you’re writing an application for the Mac, you need to incorporate Sparkle. Period.
The other would be Feeder. It makes the publishing of a Sparkle compatible appCast super simple and it works amazingly well. Feeder is not free but it’s well worth the small fee they want.
I’ve started up a small documentation project for ToeTag. It’s barely started but you can take a look at it now if you like. I’m hoping to get a few tutorials up there each week until a decent body of documentation is done.
Enjoy!
I’ve got a few bugs to fix in ToeTag that came out of the beta. Nothing major but annoying nonetheless.
I’m also starting to write some documentation and tutorials that should get people over the initial learning hump.
I don’t know why I’m so compelled to do all of this work for the 5 people who will ever actually USE ToeTag for anything but it’s fun.
OK, so I have a beta version ready that comes with no documentation whatsoever but I wanted to start testing this Sparkle framework and see how the automatic updates really work.
If you want to download a version, click here:
ToeTag Beta V:0.1
(edit: forgot to mention this before - ToeTag requires Leopard)
It should start up on any modern Mac and once you tell it where to find your Quake directory, you should be golden. I KNOW there are some bugs in this and the icons and such are all defaults. This is just a stability and “does it actually work on someone else’s machine?” type release.
Since I’m using Sparkle, the theory is that you should be able to easily grab any future versions automatically.
Leave feedback in the comment section if you have any. Which I hope you will. Because without it, well, it’s not much of a beta now is it?
Thanks!
Hooray! That was an ass load of work but I’ve got the editor refactored now to nicely handle mods and standard Quake side by side. On the user side of things, to use a mod you just set a key/value in the worldspawn called “_game“. For example:
You can also see a key called “_cmdline” there. That’s for passing extra commands to Quake when running it.
The menus inside the editor dynamically adapt to whatever mod you’ve chosen. You can have standard Quake maps loaded alongside Quoth maps alongside Team Fortress maps. It all works seamlessly! You can even change the mod name in the middle of an editing session and the editor will adapt correctly. Entities that aren’t supported in the current mod will turn into black boxes but will retain their class names. If you switch back to the old mod, they will jump back to looking correct again.
Here’s a look at the standard entity create menu:
And here’s that same menu when you’ve told the editor you’re using Quoth:
I’m pretty happy with this set up!
Just 2 tasks left until I can feel good about letting beta testers at ToeTag. One is small and one may consume a good chunk of a day. Getting close! In closing, here are some Quoth editing shots:
