not
http://www.deviantart.com/deviation/15917528/
enjoy
A very simple preset
22 posts
too bad, J's ape is not working under *nix.
seems like a kickass preset... if it had normal and bump maps 😛
[edit]
im not sure, maybe it already supports it =\
seems like a kickass preset... if it had normal and bump maps 😛
[edit]
im not sure, maybe it already supports it =\
Sucks that the APE doesnt work under nix
(It is bump mapped btw)
(It is bump mapped btw)
Originally posted by PAK-9deamn! sucks not to see it
(It is bump mapped btw) [/B]
Yea well, thats what you get for not having a windows box
OMFG
Nice job.
😁
Nice job.
😁
that was/is a awesome preset 😁
Awesome tech demo, mediocre preset....
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
(which runs quite well for me btw :P)
btw that sideopt is kind of borked
it draws white triangles everywhere
mad, totaly mad.
oops, i forgot to add some bitmaps 🙂
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]
"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]
I loaded it, it's a blank screen.
Should it all get loaded into the same directory where the rest of the visuals are?
Should it all get loaded into the same directory where the rest of the visuals are?
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.
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.
oh, btw pak
it does work, it just takes ages to load... -.-
quite good, but still far from doom 3 quality 😛
it does work, it just takes ages to load... -.-
quite good, but still far from doom 3 quality 😛
haha, you thought it was broken cos it took so long to load. Its not my fault its evallib being slow.
Yeah, that was the problem, I didn't expect it to take 20 seconds to load up.
maybe these long load times are partly my fault...
compare the load times with and without eeltrans 🙂
compare the load times with and without eeltrans 🙂
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.
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
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
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.