![\"\"](\"http:\/\/www.vectorstorm.org\/wp-content\/uploads\/2012\/02\/MMORPG-Tycoon-2ScreenSnapz004.jpg\" "\\"MMORPG")
<\/a>So these are slowly coming along, again.<\/p>\nA few points to notice:<\/p>\n
- \n
- These are my first procedurally generated models which have a texture applied. \u00a0I added texture coordinates to generated models ages back<\/a>, for use with shader effects (ironically also being displayed on an early tree model). \u00a0But \u00a0this is the first time I’ve actually applied a texture to a generated model using those texture coordinates. \u00a0And that worked on the first try!<\/li>\n
- I did a lot of tweaking on the spacing of branches, to stop branches from (for example) being generated past the end of another branch.<\/li>\n
- The ‘canopy’ of trees, in this shot, is a simple dome-shape. \u00a0Eventually, I’ll want to have more than just this one shape, in order to make different types of trees.<\/li>\n
- There are rendering glitches right at the very top of each foliage dome, probably due to extremely compressed UV coordinates there. \u00a0I need to look at fixing these.<\/li>\n
- In this shot, all the visible trees are using exactly the same generated model, just with different rotations and scales applied. \u00a0For the final game, I’ll probably want to generate several different species of tree, and several variations of each.<\/li>\n
- I’m not completely happy with the single-shade green of the foliage canopy. \u00a0I’m trying to decide whether I can improve that using a greyscale texture, or whether I’m actually going to have to put colour data into the foliage texture. \u00a0I’d rather avoid doing that if I can, though, because I really want to be able to vary that colour according to different factors, and as soon as I actually put the colour into the texture, I can’t modify it in code any more. (Edit<\/strong>: \u00a0I’d forgotten to apply lighting to the foliage! \u00a0Updated the screenshot with lighting turned on. \u00a0Original screenshot for this post is here<\/a>)<\/em><\/li>\n
- Trees aren’t hovering above the ground any more; \u00a0now they properly project down through the ground. \u00a0This was surprisingly tricky to make work properly.<\/li>\n<\/ul>\n
There have also been a number of changes under the hood, which will eventually be propagated back to the VectorStorm trunk. \u00a0Most notably, vsTextureMaker<\/em> has been renamed to vsImage<\/em>, and can now load its image data from a file (previously, it could only be initialised by code setting each pixel manually). \u00a0You can still make a vsTexture<\/em> from a vsImage<\/em>, if desired.<\/p>\n
Also of note, I’ve been playing with different names for the vsBuffer<\/em> class, which wraps around the OpenGL VBO functionality. \u00a0Currently, I have it named vsRenderBuffer<\/em>, which at least gives a vague hint at what it’s used for, rather than implying that it’s some generic memory storage class.<\/p>\n","protected":false},"excerpt":{"rendered":"
So these are slowly coming along, again. A few points to notice: These are my first procedurally generated models which have a texture applied. \u00a0I added texture coordinates to generated models ages back, for use with shader effects (ironically also being displayed on an early tree model). \u00a0But \u00a0this is the first time I’ve…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":""},"categories":[24,25,3],"tags":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/po9WK-Cc","_links":{"self":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts\/2368"}],"collection":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/comments?post=2368"}],"version-history":[{"count":0,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts\/2368\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/media?parent=2368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/categories?post=2368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/tags?post=2368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![here<\/a>)<\/em><\/li>\nTrees aren’t hovering above the ground any more; \u00a0now they properly project down through the ground. \u00a0This was surprisingly tricky to make work properly.<\/li>\n<\/ul>\nThere have also been a number of changes under the hood, which will eventually be propagated back to the VectorStorm trunk. \u00a0Most notably, vsTextureMaker<\/em> has been renamed to vsImage<\/em>, and can now load its image data from a file (previously, it could only be initialised by code setting each pixel manually). \u00a0You can still make a vsTexture<\/em> from a vsImage<\/em>, if desired.<\/p>\nAlso of note, I’ve been playing with different names for the vsBuffer<\/em> class, which wraps around the OpenGL VBO functionality. \u00a0Currently, I have it named vsRenderBuffer<\/em>, which at least gives a vague hint at what it’s used for, rather than implying that it’s some generic memory storage class.<\/p>\n","protected":false},"excerpt":{"rendered":" So these are slowly coming along, again. A few points to notice: These are my first procedurally generated models which have a texture applied. \u00a0I added texture coordinates to generated models ages back, for use with shader effects (ironically also being displayed on an early tree model). \u00a0But \u00a0this is the first time I’ve…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":""},"categories":[24,25,3],"tags":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/po9WK-Cc","_links":{"self":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts\/2368"}],"collection":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/comments?post=2368"}],"version-history":[{"count":0,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts\/2368\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/media?parent=2368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/categories?post=2368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/tags?post=2368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"http:\/\/www.vectorstorm.org\/wp-content\/uploads\/2012\/02\/Tree.jpg\"){kind=link}