Haydenmango

Finally got to testing this today and I am really enjoying it. It works very well and is easy to use. Now I just need access through code to really get to work!

Wow, this is super useful! Thank you for taking the time to write this.

It is looking very good! I am getting 50+ fps on my GeForce GTX 960M. I noticed that trees collision shapes seem to be to wide but maybe that has to do with the camera collision?

Nice. It even makes burnt pancakes? Impressive.

Looking good, I am getting very excited!!

I found this buried deep in the forums a while back and it works well. math.randomseed( tonumber(tostring(Time:Millisecs()):reverse():sub(1,6)) ) edit- oops didn't see the other topic

Well I have a Nvidia card so that might have something to do with it. I also figured out that this only happens when the terrain quality is either medium or high. This is from my program log after starting Leadwerks and turning water mode to true - programlog.txt Edit- Ok, I didn't actually see the error the last time (or the water for that matter) so I tested it again. When I tested it the second time I moved the camera to look at the water and two shaders loaded (which I'm guessing are the shaders that are causing the issue). Here is the second program log from when I actually saw the error. - programlog2.txt

I have been having similar issues when using decals on scenery. I was thinking that if you give a decal a parent that it should only project itself onto its parent. That might be a nice work-around if it is possible.

I am getting this error everytime I turn water mode on.

Hmm.. that's unfortunate. The terrain on low settings didn't look good but it was playable (and increased my fps) before but now I can't see it being used for anything. Oh well, I guess this isn't a bug then.

Terrain on Low Settings looks extremely blurry after the beta update. The terrain on low settings wasn't this blurry before the beta update. Photo Example -

Will we be able to place vegetation through code?

Alright I guess I will upload a new version of my game then, thank you for the response!

I have to upload two updates every time I update my workshop game because the first update uploads the previous build of my game. Should I just make a new workshop game and delete the current one or is anyone else experiencing the same issue?

The night sequence is based on the directional lights color being turned to black. To recreate this make a terrain, set water mode to true, and place a directional light in the scene with a diffuse color of 0.

I noticed at night time in my game that water reflections don't take current lighting into account. This doesn't seem right. Here is a picture for an example -

Awesome! This change cleared up the last of my major bugs and now I can get ready to put my game on the Game Player.

Great job, it looks very professional and functional. I have been working on a better GUI for my game lately and reading through your blogs/watching your videos has helped me a lot. Thanks for sharing!

Other than updating shaders I haven't changed or added anything. It seems like the terrain rendering is much slower because my games without a terrain have the same performance as before.

Decals look good and work quite well. I am getting very bad performance after this update though (10-15 fps less than before the update) and can't seem to do anything to make it better.

After the beta update terrain textures are removed when loading a map in game or in the editor.

Most of my animated characters are red after the recent beta update earlier. It seems that they are always flagged as selected. Edit - Alright I found the issue, they were using a custom shader. This can be locked.

Will these new features (Vegetation and Terrain Offsets) be accessible through code?

This makes me happy. Seriously this is awesome, keep up the great work!

I don't know what changed but I am not encountering this error anymore, I was able to publish my game to the Workshop without any issues.