Archive: A very simple preset


9th March 2005 13:04 UTC

A very simple preset
not

http://www.deviantart.com/deviation/15917528/

enjoy


9th March 2005 13:52 UTC

too bad, J's ape is not working under *nix.

seems like a kickass preset... if it had normal and bump maps :p

[edit]
im not sure, maybe it already supports it =\


10th March 2005 09:57 UTC

Sucks that the APE doesnt work under nix

(It is bump mapped btw)


10th March 2005 17:03 UTC

Originally posted by PAK-9
(It is bump mapped btw) [/B]
deamn! sucks not to see it

10th March 2005 18:31 UTC

Yea well, thats what you get for not having a windows box


10th March 2005 21:53 UTC

OMFG

Nice job.
:D


14th March 2005 23:57 UTC

that was/is a awesome preset :D


15th March 2005 17:02 UTC

Awesome tech demo, mediocre preset....


16th March 2005 06:57 UTC

i improved that menu a bit and optimised it for full-screen
(which runs quite well for me btw :P)

btw that sideopt is kind of borked
it draws white triangles everywhere


16th March 2005 07:43 UTC

mad, totaly mad.


16th March 2005 10:38 UTC

oops, i forgot to add some bitmaps :)


16th March 2005 18:10 UTC

ooh, I'll have to check it when I get home

"btw that sideopt is kind of borked it draws white triangles everywhere" Do you mean you borked it up or it was borked to start off with, cos it works fine for me.

[edit]

(Still havent checked it)
There are actually a lot of optimisations that can be done for this preset, such as having lower res side faces that arent calculated but are just different lower res bitmaps.

the preset was really to show the principles involved, in the future I (and others I'm sure) will refine the technique to be more efficient and prettyer. The first attempt at a new idea is never perfect. I'm not making excuses for the preset, it is what it is, I'm just saying this isnt my difinitive vision of texture mapping in AVS

[/edit]


17th March 2005 03:38 UTC

I loaded it, it's a blank screen.

Should it all get loaded into the same directory where the rest of the visuals are?


17th March 2005 07:34 UTC

you have to get all components it needs (ape files and bitmaps). you can get them at the first link Pak posted on the top of the page.


17th March 2005 14:30 UTC

Hmm, that 'optimised' version does work nicer in fullscreen... but I think the word 'optimised' was a bit overstated, I couldnt see any actual optimisations in the code.


17th March 2005 16:10 UTC

oh, btw pak

it does work, it just takes ages to load... -.-
quite good, but still far from doom 3 quality :p


17th March 2005 16:37 UTC

haha, you thought it was broken cos it took so long to load. Its not my fault its evallib being slow.


17th March 2005 18:57 UTC

Yeah, that was the problem, I didn't expect it to take 20 seconds to load up.


17th March 2005 21:35 UTC

maybe these long load times are partly my fault...
compare the load times with and without eeltrans :)


18th March 2005 16:34 UTC

Yea evvalib parsing the code really slows it down, but all my code is written for evallib so I'd have to hack it around to prevent it. i.e. having avstrans in an effect list thats diabled on the first frame or something... I'm not going to bother though, that preset is old news, time to move on to bigger better things.


22nd March 2005 19:51 UTC

yes, but if eeltrans really had a big impact on the loading time, i could maybe change it.
i could make a new comment code, which would skip further pre-processing for the current code block in the fastest possible way.

even with no actual conversion done, the whole code is copied around 2-3 times and split up into chunks and parsed for commands inside all of the brackets


23rd March 2005 12:38 UTC

Yea I had a feeling a lot of chopping and parsing was going on in the background, I suppose it would be nice to have some way of stopping it from parsing. Maybe a disable and enable keyword to stop Trans intercepting code, an option to start the AVSTrans disabled too, since all the loading is always going to be done when the preset starts.