Josh

I'm going to keep the second set of texcoords, for lightmapping in the future.

Did you try reversing the order of the vertices so the triangle will face in the opposite direction?

try again, I think I did not upload earlier.

Did you sync the project to get the new shader? You don't need to recompile shaders, although that won't hurt anything.

The vertex alpha was being set to 1.0 in base_vert.glsl. It should work fine now.

I think so too. The transparency example seems to work fine in the current build: https://github.com/UltraEngine/Documentation/blob/master/CPP/Material_SetTransparent.md Investigating....

It's the GUI background you are seeing. What was the behavior before? Did panels use alpha blending? #include "UltraEngine.h" using namespace UltraEngine; int main(int argc, const char* argv[]) { //Get the displays auto displays = GetDisplays(); //Create a window auto window = CreateWindow("Ultra Engine", 0, 0, 1024, 768, displays[0], WINDOW_CENTER | WINDOW_TITLEBAR); //Create a framebuffer auto framebuffer = CreateFramebuffer(window); //Create a world auto world = CreateWorld(); //Create a camera auto camera = CreateCamera(world); camera->SetClearColor(0,0,1); auto sz = framebuffer->GetSize(); // Load a font auto font = LoadFont("Fonts/arial.ttf"); // Create user interface auto ui = CreateInterface(world, font, framebuffer->GetSize()); ui->SetRenderLayers(2); ui->root->SetColor(1,0,0,0); // Create ui camera auto uiCamera = CreateCamera(world, PROJECTION_ORTHOGRAPHIC); uiCamera->SetClearMode(CLEAR_DEPTH); uiCamera->SetRenderLayers(2); //Main loop while (window->Closed() == false and window->KeyDown(KEY_ESCAPE) == false) { world->Update(); world->Render(framebuffer, false); } return 0; }

Yes, that is the way it's supposed to work. When you use a hook you aren't calling Vulkan commands that get executed immediately. You are usually adding Vulkan command calls into a command buffer which is executed at a later time. The transfer command buffer only gets executed once, and the rendering command buffer may be executed several times. This is the way Vulkan works, everything is stored in a command buffer, then the whole command buffer is executed at once.

The transfer command buffer is executed once. The rendering command buffer may be reused several times. If something is an action that gets performed once, use the TRANSFER hook ID. If it is normal rendering, it should be in a RENDER hook.

Very very cool stuff to try: test.zip

1.0.3 Save/load of the new .ultra map format now supported. It could break at any time but it seems stable. The format is JSON-based, so I can add new data or change it slightly and maps will still load. Environment probes added in editor, along with controls of edge fade distance properties.

@klepto2has used this successfully.

No, it's really weird stuff. You call World::AddHook with HOOKID_RENDER or HOOKID_TRANSFER as the argument, along with your function. It will pass a class to your function that contains a lot of Vulkan structures, and then it's up to you.

We ended up using a callback so that Vulkan function calls can be made from the user's code, inside the rendering routine.

1.0.3 Rotation mouse cursor now used when rotation tool is active. Increased the minimum mouse move distance before drawing a new object is initiated.