Trees
Moderators: MR.D, Moderators
Generated from what?? There must be some base infomation or set of rules it follows. And theres no way it just generates each leaf... they are definatly from a texture...
I was kinda thinking it looked like each tree was just a set of progresivly smaller sticks placed in a tree like way (which could be done by teh engin so fare does if there is no model), and that teh leaves were just added seperatly as a bunch of overlaping sprites.
However surly that can be rewiten to pick from say 5 different trunks , and then a load of differnt brances, and leaves just do them teh same way, but with a bigger texture for more detail.
aGorm
I was kinda thinking it looked like each tree was just a set of progresivly smaller sticks placed in a tree like way (which could be done by teh engin so fare does if there is no model), and that teh leaves were just added seperatly as a bunch of overlaping sprites.
However surly that can be rewiten to pick from say 5 different trunks , and then a load of differnt brances, and leaves just do them teh same way, but with a bigger texture for more detail.
aGorm
I know that but it will still be the fundamentally same tree I have read the code that GENERATES them and edited the textures will you *censored*ing people ever believe me... or do you only hear... "hi I'm smoth I talk out of my ass"AF wrote:aGorm+Smoth you're dead wrong.
Look at the trees, they're models that're generated durign the starting sequence using the leaves and bark and other textures in the spring content.
Modify the leaves and so on and you'll see the difference ingame.
The tree code is funny, we have 16 generated randomly at startup. Does this this mean they look different for each player and different each time you load the map? I am hoping someone can decypher code and tell me for sure.
If they are random each time, could we tweak the code a little for more variation between types? And could the coordinates be used as the seed for each tree so they dont change when they really shouldn't.
Another random snippet sort of related, the current map format stores a value for a size multiplier for features, but it is not used.
If all this was implemented we could have 16 distinctly different types of proceedural trees that could have an adjusteble size.
Sounds complicated but probably simpler to do than rotatable buildings.
If they are random each time, could we tweak the code a little for more variation between types? And could the coordinates be used as the seed for each tree so they dont change when they really shouldn't.
Another random snippet sort of related, the current map format stores a value for a size multiplier for features, but it is not used.
If all this was implemented we could have 16 distinctly different types of proceedural trees that could have an adjusteble size.
Sounds complicated but probably simpler to do than rotatable buildings.
What is wrong with you Smoth, just because we happened to start on the wrong note by you misintupreting my coment about growing trees, does not mean that Your "talking out your ass" and I have never said you are.
I happen to have read it to. Ages ago when I was first trying to find how come they got 1bit alpha and features didn't. I didn't totaly understand the code so I didn't try and suggest I had a clue what it realy did, but my suspision on them being generated by teh game engin was correct. So what big deal, nither of us are arguing about that!!! In fac the only thing we disagreeed on was trees growing!!
AF's post was mistimed, he said we were both wrong when both me and you had arived at what he said alrady.
So we are in agreement infact that the trees are generated.
Now can we scrap teh whole arguming about nothing and get on with the solution. Please.
Weaver has shed some more light on what happens, and has offered a few more ideas. Now, I may be wrong here, but if there generated, surly if someone re-wrote that code it could just be sloted in and the rest of the game would be none the wiser (apart from maybe the trees falling down stuff might be affected...). So surly its just a matter of us agreeing on how we think it should work.
Now surly the main question is: How do you make the engin create good looking trees, randomly.
Currently it just seems to through together a bunch of cilinders and add a look of leaf sprites to generate the folige around them...
It would surly be better if you insted gave the engin peices to build a tree out of, IE 10 trunks, 10 branches, and ten leaf types. This would give you 1000 different tree atleast and assuming each branch was used once and grow from fixed positions. But seeing as they could be randomly generated, that basicly add's an infinite number of possabilitys.
Now the way I'm think might, from the coder point of view, be very very messy and resource consuming, I dont know. But its a suggestion.
Obviolsy the generating would hgave to folow certain rules like, max and min number of branches, that sort of thing. And whilst they should be more complicated than the current trees, the ycant be say Half-life two style trees, no matter what people hope.
The one thing that would be cool with this method is that as you zoom out the branch peices can be replace by lesser and lesser detailed peices, insted of jumping stright to sprites, as that jump looks worse than the trees do IMO.
Long post sorry for rambeling and smoth, I dont think you talk out your ass. And Im realy sorry if I came across like I think you do.
aGorm
I happen to have read it to. Ages ago when I was first trying to find how come they got 1bit alpha and features didn't. I didn't totaly understand the code so I didn't try and suggest I had a clue what it realy did, but my suspision on them being generated by teh game engin was correct. So what big deal, nither of us are arguing about that!!! In fac the only thing we disagreeed on was trees growing!!
AF's post was mistimed, he said we were both wrong when both me and you had arived at what he said alrady.
So we are in agreement infact that the trees are generated.
Now can we scrap teh whole arguming about nothing and get on with the solution. Please.
Weaver has shed some more light on what happens, and has offered a few more ideas. Now, I may be wrong here, but if there generated, surly if someone re-wrote that code it could just be sloted in and the rest of the game would be none the wiser (apart from maybe the trees falling down stuff might be affected...). So surly its just a matter of us agreeing on how we think it should work.
Now surly the main question is: How do you make the engin create good looking trees, randomly.
Currently it just seems to through together a bunch of cilinders and add a look of leaf sprites to generate the folige around them...
It would surly be better if you insted gave the engin peices to build a tree out of, IE 10 trunks, 10 branches, and ten leaf types. This would give you 1000 different tree atleast and assuming each branch was used once and grow from fixed positions. But seeing as they could be randomly generated, that basicly add's an infinite number of possabilitys.
Now the way I'm think might, from the coder point of view, be very very messy and resource consuming, I dont know. But its a suggestion.
Obviolsy the generating would hgave to folow certain rules like, max and min number of branches, that sort of thing. And whilst they should be more complicated than the current trees, the ycant be say Half-life two style trees, no matter what people hope.
The one thing that would be cool with this method is that as you zoom out the branch peices can be replace by lesser and lesser detailed peices, insted of jumping stright to sprites, as that jump looks worse than the trees do IMO.
Long post sorry for rambeling and smoth, I dont think you talk out your ass. And Im realy sorry if I came across like I think you do.
aGorm
It would be really cool if there was some kind of script within the smd file to control the generation of trees for each particular map. The map maker would be able to specify what kind of tree would be constructed and what texture would be applied to what area (trunk,leaf,etc). It could be very simple like assigning a number for size, amount of branches/leaves, size of trunk (you get the idea).
- SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
- SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
- bobthedinosaur
- Blood & Steel Developer
- Posts: 2702
- Joined: 25 Aug 2004, 13:31