Spring RTS Engine

I've revamped the HPI format and increased the version (to disallow old viewers from working). There will be a ton of updated features with the new version and access should be extremely fast, even with massive files, and compression will be updated as well.

Not to worry, the access DLL will be available as soon as I get it done. And integrating it into spring shouldn't be exceptionally hard.

I'll have to get with SY on when to implimen the new HPI format.

-Buggi

What is the HPI format? I thinked it was a simple compressed format like .zip

great news .. nice to hear that.

The HPI format is far from a zip file...

I call it the "happy" file, as the header is "HAPI".

My new file version will be much better, especially when it comes to large files.

I was able to compress a 20 meg map into a 8meg 7zip and a 10 meg zip. I'm looking into implimentation now.

*pokes owen*
:D
-Buggi

7/10 for innovation
9/10 for spiffyness (happy archives are good archives)
2/10 for details
5/10 for hype
8/10 for promise/hope

overrall good work

As for SY's I dont think there's any need to differentiate between different versions of HAPI in the engien as thats all handled by the dll, so the SY's need not bother. Unless I've just amde a total ass out of myself for saying that *quickly opens source folder for a look*

Ok, The HPI format is far from a zip file... so what is it?
It can be a container, compresse file ...

Great to see stuff in the workings, but how will the porting work?

I hope you just add a heap of new groundbreaking cool commands and leave the others alone as they were, in order to freely switch back and forth between S:TA and O:TA.

pfft whatever eh creates will be backwards compatible and I doubt anyone would bother creating OTA stuff in this new format.

A better definition would be that a HPI format is the HAPI archive format in its full name. It can do what ZIP archives or RAR archives do in its basic functions.

Hopefully this new innovation will decrease loading times and make HAPI a more viable format. Heck we could start using it for conventional use in replacement of zip and rar archives if it turns out good enough.

The first goal of the system is to create/manipulate/edit Spring related content. The SY's have put years of their life into this engine and creating something for IT is the first step to mass-use and acceptance.

As for backwards compatibility... I don't think that will be a major issue. You'll just have a bunch of features disabled

And I didn't forget about the porters, storm. Don't worry. The entire format is using open-source tools and the format itself will be open source. I need to get with the SY dev's to make sure transition to Spring is a smooth one. So eventually a version will be released to support the new HPI file version.

Have you got in touch with Dave, the coordinator of the porting project ? Because they we´re talking about changing the .hpi format / changing to a different format.

If your new format is not compatible with HPI, don't call your files HPI. Find yourself a new suffix.

If you think HPI isn't good enough, instead of inventing your own formats just use an existing one. There were some nice discussion with people saying that .7z are currently the best. It would really be much much better using an existing format, tried and tested, fully documentd, ported to every system, with a wide array of already existing .dlls and programs handling it, instead of your own custom format.

And I just don't believe in All-In-One editor. There's nothing in common between editing a map, a .3do, and a script. If you want to start making editors, what is really lacking now is something to remove and place features on a map.

I see a lot in an all in one editor.

Ever thought about making a modela nd then starting a script and testign out the script on the model without loading TA/Spring?

And his new format is absed on HAPI, but you will ahve to change the nae for other reasons, legal reasons?

Making a model? Heh, don't expect too much there. Rhino, the lightweight, cheap 3D program is a bargain compared to the others and it costs well above what any of us can afford right off the bat. You think Buggi would be able to develop one of his own just like that?

However, a combined texturing-scripting program would be good to have. So that you can test-run the script straight on the model.

FOR GAWDS Sake, I have said it before... try wings3d.

I am _NOT_ creating a 3d modeler... Holy crap that would be far beyond my sanity.

I never said I was creating a modeler, no more than Kinboat created a modeler, he created a 3do builder.

sh*t me bad, I meant the equivilant of 3d0 builder but I seem to have been misinterpreted. Besides a 3D modeller would be overkill with the 3d modelling progs already out there.

However I did not say 'making the model' as in referring to buggi' much anticipated all in one prog, that, is somethign your misread into what I said.