All Activity

#1 is some design that could be improved, but not a bug. #4 is resolved for the next build, I think. When you change textures all affected terrains will be updated. The other properties should just already be working right. #3 Tessellation on terrain is not currently supported. This will be implemented along with GPU culling.

My bad, shaders are updated now.

That's what's aggravating about this. When you battle test the undo system, it seems to work fine but when you're the middle of a mapping session, the undo system lets you down. I don't even know how you could debug this without doing a remote debugger on them while they map. I can try to find step by step examples, but watch it be fine on your end.

To be honest, I haven't ran into this issue since. Let's mark it as resolved it for now.

This is me changing the seed values.. I always look for Sync after i do updates so Im never worried about shaders or exe syncs not being right.

I think this is solved?

I assume the post-processing effect problem is solved in more recent builds? It does not seem to be a problem when I try it.

Can you link to a glTF or glb file that does not load correctly? I use glTF files from Sketchfab all the time. GLB should work as well. The FITextureLoader plugin must be loaded in order to load PNG and JPEG images as textures, but if it isn't the model should still load with no textures.

Marking this as solved, unless anyone tells me otherwise...

The program does not crash for me. Instead I see this: The solution is to specify a wide string in the string declaration: auto label2 = CreateLabel(L"Тест", 20, 50, 120, 30, ui->root, LABEL_BORDER | LABEL_CENTER | LABEL_MIDDLE); Then it looks like this: (Non-latin characters are currently not supported in a 3D GUI because I have to change the way characters are rasterized from the font. This is on my to-do list.)

I did not test the code above with the latest build, but this might be solved. I removed some "tight intersection testing" that was not working correctly. The results are more likely to include false positives but it might resolve this problem.

Added NavAgent:Stop Added NavMesh() casting function Added the missing CreateNavMesh overload These will be included in the next build that goes up. When an entity is attached to an object, it's local orientation is preserved relative to the parent. This might be a design decision that should be revisited, but it is currently working as intended. I don't think you need to move the agent, the entity's global orientation at the time of attachment will turn into its relative orientation to the attached object.

Problems that don't have a specific way to produce them unfortunately are harder to resolve.

Where did you send this model? I cannot find it in my messages.

This C++ example shows that deletion is working correctly. Are you sure there isn't a reference to the variable somewhere else in your code? #include "UltraEngine.h" using namespace UltraEngine; int main(int argc, const char* argv[]) { //Get the displays auto displays = GetDisplays(); //Create window auto window = CreateWindow("Ultra Engine", 0, 0, 1280, 720, displays[0]); //Create framebuffer auto framebuffer = CreateFramebuffer(window); //Create world auto world = CreateWorld(); //Create main camera auto camera = CreateCamera(world); camera->SetPosition(0, 0, -3); //Create a model auto box = CreateBox(world); //Create a light auto light = CreateBoxLight(world); light->SetRange(-5, 5); light->SetRotation(34, 45, 0); //Load a font auto font = LoadFont("Fonts/arial.ttf"); //Create user interface with a semi-transparent background auto ui = CreateInterface(world, font, framebuffer->size); ui->background->SetColor(0, 0, 0, 0.5); //Create widget iVec2 sz = ui->background->ClientSize(); auto button = CreateButton("Button", sz.x / 2 - 75, sz.y / 2 - 15, 150, 30, ui->background); //Create camera auto orthocamera = CreateCamera(world, PROJECTION_ORTHOGRAPHIC); orthocamera->SetClearMode(CLEAR_DEPTH); orthocamera->SetPosition(float(framebuffer->size.x) * 0.5f, float(framebuffer->size.y) * 0.5f, 0); //UI will only appear in orthographic camera orthocamera->SetRenderLayers(2); ui->SetRenderLayers(2); while (true) { box->Turn(0, 1, 0); while (PeekEvent()) { const Event ev = WaitEvent(); switch (ev.id) { case EVENT_WINDOWCLOSE: if (ev.source == window) { return 0; } break; default: if (ui) ui->ProcessEvent(ev); break; } } if (window->KeyHit(KEY_SPACE)) ui = nullptr; world->Update(); world->Render(framebuffer); } return 0; }

1. Make sure your shaders are up to date. 2. Change the seed value for the mesh layer, then change it back. This will force re-building of the noise data.

Still flickering, but now it's all laid out in this weird stretched format. That is the same model as this :

I made a small change that might resolve this. Since this error is difficult to produce I cannot test it.

I am changing it so the editor will ignore the material pick mode.

The pick mode is set to false. It shouldn't be hit-or-miss, it should just be miss, 100% of the time.

I'll probably pick it up tomorrow.

I found a 570 for sale locally at Best Buy. Will buy it very soon.

Does this resolve your issue?

Fixed!