Battlezone Forums

Nice. This confirms that large textures actually work. :) 256x256 was typical of the era due to memory limitations and also turned out to be maximum texture size supported by the popular 3Dfx Voodoo graphics card series. The engine didn't otherwise restrict texture size, though. (Well, the file form...

AHadley wrote:Ken Miller has a character named after him. Her name is Tom. I find that amusing; Ken, on the other hand, does not.

"The reports of my lack of amusement are greatly exaggerated."

OK, I finally found it (in grtypes.h) and it was set to 223. The sky color really should have been a setting in the [Color] section of the TRN instead of a hardcoded value... Also, gpuff.map seems to be missing from 1.5; it was an effect asset from RO that would need to be put in SW, HW, or HW16 pac...

The 1.5.1 asset pack includes a bunch of stuff from Red Odyssey so some files might be different from what you're expecting. Also, 1.5 (and RO) is based off the 1.3 code base so it's possible that 1.4 made some changes that I don't have. I can take a look. The sky thing sounds like it might be a cod...

Larger textures should work though I can't absolutely guarantee it. Higher-detail textures would also stand out relative to other textures in the game, and would also take up a lot more space. (I'm using uncompressed texture formats so a 1024x1024 16-bit texture would be 2 megabytes.)

Closing in on a final release for the 1.5.2 series... This build fixes a few problems introduced in earlier versions, adds a bunch of handy new Lua functions for mission scripting, and fixes up some networking related issues. It also turns off data execution prevention so it should be compatible wit...

The ordnance evasion was super-obnoxious for a while, making it nearly impossible to hit AI units at range with slow-moving projectiles. I retuned it for this build based on Sporkinator's feedback so it's a lot more fair now. (They still have good chance to evade but they don't respond instantaneous...

It's possible I busted some of the CD reading with various things I've done for 1.5. You can copy the movie files from the CD though I'd have to check where you'd need to put them.

I already voted.

The main distinction is between opaque (model) and translucent (interface and effect) textures. Until recently, Battlezone hardware rendering supported only 8-bit opaque textures and A4R4G4B4 translucent textures. I added tool and engine support for the other formats so I could make "high quali...

Customization and moddability would be a good theme for 1.5.3, just as mission scripting was the theme for 1.5.2. While I do want to put together full-featured model cooking and uncooking tools, retexturing is such a common operation that it's worth making a lot simpler for end-users. I think a text...

I've been using the pre-made full installers for so long that I haven't checked the process of updating from 1.0-1.4. The 1.5.0 page has an all-in-one package for 1.5.0 and instructions for getting things started from a retail install. It's a bit involved but you only have to do it once. The 1.5.1 p...

Agh, I meant to work on a explaining how to do a retail to 1.5.x upgrade last night. I also need to streamline it since the process is pretty rough and unfriendly.

Updating a retail install to the latest 1.5.x is currently much harder than it should be. I need to write better instructions for it or better yet make an installer to automate the process.

I can certainly appreciate the "cut out the middle man" approach that Battlezone 2 used. What might work would be a cooked binary format for speed and a raw binary or ascii format for ease of content creation. Raw and especially raw ascii formats are somewhat slower to load, especially if ...