Lame Video Stuff

M8.V1


The Modern Vtest

This has the functionally vtest.exe but in C++ rather than C.

Yes, this means that I'm at the same level I was over a year ago, but this is in C++, which I only started learning this year (2000), not C, which I knew to various degrees for what seems like forever.

For M8, the render library in particular will be developed and maintained until I have surpassed the featureset of M7.

Anyhow, there is for now just the prebuilt version, which is only slightly interactive and is really nothing all that impressive, but is here anyhow.

So, get the zip file, containing M8.V1:Vtest Mark 1, C++ Edition, Latest Prebuilt Release .

This is compiled for DOS32 with DJGPP and uses Allegro... in english, that means you can run it under Windows 9x or under DOS with a DPMI manager.

The Ancient Vtest Demo

Actually, for comparison, you can get The Old Vtest, C Edition, Zeroth Anniversary edition, which is also build for DOS32, and is based directly on code I did back in April 1999.

The Ancient Vtest Code

If you life really lacks excitement and occupation, then you can download a weird package with source, DOS32 executables, no documentation (and I mean none!), and all the required data files for the reconstructed C version of Vtest... but I warn you to think twice before looking at rendlib1.c, and also note that the comments in the text may appear to be written by a madman.

So... leave you unsanity at the door if you chose to pursue Vtest: Final C Version, Uncut, Undocumented, Unsuppoted, Unkool... , the ultimate test of sanity! Muwhahahahaha!

A bit of history: This version of Vtest was made from old rotting source, to act as a basis for creating the C++ version. Not basis as in code, but basis as in functionality.

Some things that have changed for the C++ version are file support: the C++ version used sacas (plaintext files with a format developed over the M series) for everything, but the old Vtest used binary files (.sp2, .rom) for data sourcing.

It is theoretically possible for me to implement binary file support in the C++ version, but it is not currently a priority.

Good luck with "conv.cc" (which converts "char.rom" to "chr.txt"), writing the doc for that, is not something I bothered to do, yet. If you want me to, drop me a line and I will, most likely.

That is all...


IVP:Developer Edition


In order to try doing something in C++, and test out a few theories, I did IVP, which originally stood for Intelligent Video Processor, but now is Intentionally Vague Project.

Download the source, made to build under DJGPP (but also successfully compiled under Linux by brave souls), over here, in a nifty little .zip file.
There is documentation, in that archive, which describes how to build and use IVP.

Mythical User Edition


There is currently no user edition of IVP, if you just want something to play with, or (gasp) use, then please look elsewhere, this page will not help you.

Credits


Thanks and hails to the #kode crew, in particular, Chip, Sig9, Nelish, for testing out (a slightly earlier version of) this code and giving me feedback.

Rantlet


The version of IVP on this page is virtually identical to that which was tested by the #kode@doot.fdf.net crew, which is good in some ways but bad in others.

One change of questionable merit is my addition of a "UserInterface" class which is incomplete, almost useless, and does not rhyme with jelly.

Someday I may finish the UserInterface class, and demonstrate why it is a good idea. For now, IVP on a whole is sorta shoddy an incomplete. Nonetheless, it is functional to an extent.

Well, anyhow, I am not going to pledge to support IVP or continue its development.

The concept of IVP will likely be embodied in some form in something else I do in the future. There is a lot of stuff i would like to try but just feel too frustrated and unelightened to, right now.

However, anything can happen.




Go home now, or email me, granitor@yahoo.com, or something.