Slastraf
-
Posts
705 -
Joined
-
Last visited
Content Type
Blogs
Forums
Store
Gallery
Videos
Posts posted by Slastraf
-
-
Yes I can share it, but with the seed you don't need to store it in a db because it will generate the same output every time.
I will put it on in a bit. I want to add texture generation and make it more readable / stable. Its missing physics and textures basically. The player is moved by raycasts. -
-
Description
See utube desc for more.
-
2
-
Description
-
It looks like you are drawing it twice. Maybe some other value in a different script (at the position y 100 120 140)
-
The space behind the screenshot is black. Maybe there is no camera or anything to render above the "last" postrender ?
-
You wont be able to access the surface in a normal model
-
Hmmm. I cant tell for sure but copy seems to make it lag even less than Instantiate.
-
6 minutes ago, Rick said:
@Slastraf I would imagine you're recycling 9 chunks? If you make 8 copies of the 1 terrain model then as the player moves around I would think you could just reuse the ones the player is furthest away from so then you only need to call Copy() during initialization of your game right?
That would be doable if copy takes a long time. For now the Idea is to copy it and iterate over vertices for every new chunk and hide out of bound ones.
-
9 minutes ago, Josh said:
Use Copy() if you want to create a new model with unique geometry.
I was very happy with performance of Instance. Does Copy have similar performance ?
-
Here another screenshot without the block.
The hole in the middle should only generate 3 times, as the other times the offset for this position is 0. But it is there on every chunk.
-
I Instantiate a loaded model like this
worldGenerator->terrainChunk = Model::Load("Models/terrain_Plane.mdl"); ... c->chunkModel = (Model*)terrainChunk->Instance();
then I applied some previously tested code on the surface of the model like this:
Surface* surface = c->chunkModel->GetSurface(0); for(int i = 0; i<surface->CountVertices(); i++) { Vec3 xy = surface->GetVertexPosition(i); float height = (rand()%(3)); if(i==surface->CountVertices()*0.5) { height = -100*(rand()%(3)); cout<<"Offset height:"<<height; } if(i==0)cout<<"height at: "<<height<<endl; surface->SetVertexPosition(i, xy+Vec3(0,height*.1,0)); } surface->Update(); c->chunkModel->UpdateAABB(Entity::LocalAABB | Entity::GlobalAABB);
For every vertex, I set a randomly generated position. This is simplified to show the issue.
All the generated model chunks are the same. A good guess would be that LE copies an already Instantiated model over, and overwrites all changes of the current one to all previous ones, or somehow ignores changes otherwise.
I put a screnshot of the console and two images showing duplicate chunks. There are 9 chunks and each of them looks the same. How to fix this behaviour ? -
Most .mdl files have a hierarchy similar to this
STATIC_MESH (< no surface)
- OBJECT THING (< with surface)
The surface count in the latter case will be zero, even if there is a surface in the OBJECT THING
The workaround is to collapse the whole thing in the model editor.
It would be nice if getsurface will check the first child for surface too if the top level doesn't have one because it is exported like this in most modeling software. -
-
1 minute ago, Rick said:
It's been awhile since I've done that but search for maybe "terrain manipulation" or raising lowering terrain on the forums here and you'll probably find something.
GetSurface is promising
-
1
-
-
Just now, Rick said:
What is actually causing the little pause? Is it the creation of the flat mesh itself? Is it manipulating the terrain mesh it 1 iteration? Off the top of my head I would copy the flat terrain mesh, which should be instant and I don't think cause a pause, and then as you're manipulating the vertices of the terrain that would have to be done over multiple frames so there is no noticeable pause. I think I did something like this back in the day and it was easiest to do in lua because of coroutines running over multiple frames. I was able to manipulate a handful of terrain vertices every loop before I'd yield out of the coroutine to give cycles back to the game so it didn't cause a noticeable pause.
I generate new vertices, traingles for every new mesh completely new. Agreeably this takes long. To copy it over and iterate all verts to put them on the generated position could be much faster. The chunks don't have that many verts so it takes less than a few frames. How to access mesh information ?
-
I have coded a basic terrain generator which takes a perlin noise and builds a mesh from that.
The problem is this is an expensive task for real time. So I put the whole function which calculates the chunks in a second thread which is handled in the game loop.
This has not helped much with the performance, as I am using Leadwerks functions inside the thread which still accesses the game world and makes it freeze for a split second. Is there any way to calculate the mesh in a different thread and then "load" it into the world ?
An explanatory video below.
Thanks -
2 minutes ago, Josh said:
Your code above is creating 1000 new model entities. I would expect that to be a fairly slow process.
That pointed me in the right direction. I made everything into one model, it still lagged, then I also made only one surface and then I got acceptable performance. Still it should not lag in the first place. The code looks like this and now I can proceed.
void generateTest(){ // std::random_device rd; // std::uint32_t seed = rd(); //const siv::PerlinNoise perlin(seed); Surface* surface = NULL; Model* model = NULL; model = Model::Create(); model->SetColor(1.0, 0.0, 1.0); surface = model->AddSurface(); for(int i = 0; i<1000; i++) { surface->AddVertex(0.5, 0, 0.5, 0, 0, 1); surface->AddVertex(0.5, 0, -0.5, 0, 0, 1); surface->AddVertex(-0.5, 0, 0.5, 0, 0, 1); surface->AddVertex(-0.5, 0, -0.5, 0, 0, 1); surface->AddTriangle(0, 1, 2); surface->AddTriangle(1, 2, 3); surface->Update(); model->UpdateAABB(Entity::LocalAABB | Entity::GlobalAABB); } }
-
void generateTest(){ //const siv::PerlinNoise perlin(seed); Surface* surface = NULL; Model* model = NULL; for(int i = 0; i<1000; i++) { model = Model::Create(); model->SetColor(1.0, 0.0, 1.0); surface = model->AddSurface(); surface->AddVertex(0.5, 0, 0.5, 0, 0, 1); surface->AddVertex(0.5, 0, -0.5, 0, 0, 1); surface->AddVertex(-0.5, 0, 0.5, 0, 0, 1); surface->AddVertex(-0.5, 0, -0.5, 0, 0, 1); surface->AddTriangle(0, 1, 2); surface->AddTriangle(1, 2, 3); surface->Update(); model->UpdateAABB(Entity::LocalAABB | Entity::GlobalAABB); } }
Hello
after I wanted to make a mesh generation algorithm I found out that I get a lot of lag when trying to have a small amount of vertex (<10k) in the scene
If you run the test example above, it will make the game run at 2 fps or less.
It does not max out my ram / gpu at all. I guess it has to do with memory leaks because I did not delete surface and model pointer.
Then I tried to do the latter but it made different errors. -
I dont want to add my libs in
:/SteamLibrary/steamapps/common/Leadwerks\Include
but in the project files somewhere.-
1
-
-
-
Hello,
what is happening ?
Please see the video.
-
I am trying to implement this and the more I look into it the harder the math gets. Hats off I cant do it but is so crucial in a game engine and has been done in LE before.
https://www.ultraengine.com/community/blogs/entry/94-ik-animation/ -
And this whole thing makes me stuck at my project right now because there really is no alternative
-
3 minutes ago, Optimus Josh said:
I created an example that shows the error you described, and I am working on fixing it, and now you are describing another situation you want me to guess and try to create before I have fixed the thing you were reporting? You are dancing around too much. I need a piece of code I can copy and paste.
Sorry to bother so much, yes the original post was about selection Nodes, but my post from 19 hours ago was to reset the whole tree (and it worked prior but not anymore). Regardless, both things need to work. There shou.ld be ->SetParent(NULL) to remove 1 item and also tree->root->SetParent(NULL) or an equivalent tree->root->ClearNodes() (exists but throws error currently) which resets the whole tree.
-
11 minutes ago, Optimus Josh said:
Step one is to produce the bug. Now I have done that and we have something we can both run:
#include "pch.h" using namespace UltraEngine; int main(int argc, const char* argv[]) { //Get the displays auto displays = ListDisplays(); //Create a window auto window = CreateWindow("Ultra Engine", 0, 0, 1280, 720, displays[0]); //Create User Interface auto ui = CreateInterface(window); //Create widget auto sz = ui->root->ClientSize(); auto treeview = CreateTreeView(10, 10, sz.x - 20, sz.y - 20, ui->root); auto node = treeview->root->AddNode("Node 1"); node->AddNode("Subnode 1"); node->AddNode("Subnode 2"); node->AddNode("Subnode 3"); node = treeview->root->AddNode("Node 2"); node->AddNode("Subnode 1"); node->AddNode("Subnode 2"); node->AddNode("Subnode 3"); node = treeview->root->AddNode("Node 3"); node->AddNode("Subnode 1"); node->AddNode("Subnode 2"); node->AddNode("Subnode 3"); while (true) { const auto& event = WaitEvent(); switch (event.id) { case EVENT_WINDOWCLOSE: return 0; break; case EVENT_WIDGETACTION: { node = event.extra->As<TreeViewNode>(); node->SetParent(NULL); } break; } } return 0; }
That is good and I have implemented a similar thing, but what if you want to remove all nodes from the tree ?
You could select an item and delete it, but in an other case I want to reset the whole tree. For example you have 10 different users and for each user there is a list of items and you want the tree to display all items of the selected user. This requires for the entire tree to refresh and rebuild. This functionality does not work anymore because a few days ago you could take the node which you iterated the tree with (like my example above) and set its parent to null and the tree would hide. This does not work anymore. Can you provide an example for reseting the tree ?
We have finally made it
in Showcase
Posted
All random number generators only produce pseudo random numbers and you can use it to your advantage because if you initialize it with a seed like "123" it will always generate the same infinite numbers for that seed. For the terrain height generation I use perlin noise which is like a controlled 2d fractal / noise. I used a cpp library for perlin noise as a height map to set the vertices height of the tiles.
It can never be the same if the seed is always different for each new playtrough. But if you you use the same seed you can have the exact same world as someone else.