[Multiple Windows with 3D UI?]

Wouldn't I still need a framebuffer for the second window?  The problem seems to be with two framebuffers... 

[Multiple Windows with 3D UI?]

That's what I was thinking too.  Though it seems a panel can only have texture assigned to it if the interface has been created with a world and I can't get two interfaces working with one world.  I can create another world for this purpose but I need two framebuffers, one for each window, and that dosn't work very well.

[Multiple Windows with 3D UI?]

Is it possible to create 2 or more windows each one with UI with 3D?  I can't think of a way to do it that doesn't involve multiple framebuffers.

[Panel texture not showing with 3D cam]

I fixed it 

auto ui = CreateInterface(world, font, framebuffer->size);
ui->background->SetColor(0, 0, 0, 0);
ui->SetRenderLayers(RENDERLAYER_1);//<----- Needs this!!

 

[Rendering 2 worlds is slow and choppy]

Thanks, I'll try a different approach then.

[Rendering 2 worlds is slow and choppy]

I'm rendering two worlds to two separate windows with a UI overlay.  The moment I render the 2nd world it cause FPS to drop and rendering is very choppy in both windows.  I've also noticed that the window position in CreateWindow() seems to have no effect.

#include "UltraEngine.h"

using namespace UltraEngine;

#define RENDERLAYER_1 2
#define RENDERLAYER_2 4

int main(int argc, const char* argv[])
{
    auto displays = GetDisplays();

    //WINDOW A
    auto window = CreateWindow("WindowA", 0, 0, 512, 512, displays[0]);
    auto framebuffer = CreateFramebuffer(window);
    auto world = CreateWorld();
    world->RecordStats(true);
    auto font = LoadFont("Fonts/arial.ttf");

    auto camera = CreateCamera(world);
    camera->SetPosition(0, 0, -2);

    auto ui_camera = CreateCamera(world, UltraEngine::PROJECTION_ORTHOGRAPHIC);
    ui_camera->SetRenderLayers(RENDERLAYER_1);
    ui_camera->SetPosition(framebuffer->size.x / 2.0f, framebuffer->size.y / 2.0f);
    ui_camera->SetClearMode(UltraEngine::CLEAR_DEPTH);

    auto ui = CreateInterface(world, font, framebuffer->size);
    ui->background->SetColor(0, 0, 0, 0);
    ui->SetRenderLayers(RENDERLAYER_1);

    //WINDOW B
    auto worldB = CreateWorld();
    worldB->RecordStats(true);
    auto windowB = CreateWindow("WindowB", 800, 0, 512, 512, displays[0]);
    auto framebufferB = CreateFramebuffer(windowB);
    auto cameraB = CreateCamera(worldB);
    cameraB->SetPosition(0, 0, -2);

    auto ui_cameraB = CreateCamera(worldB, UltraEngine::PROJECTION_ORTHOGRAPHIC);
    ui_cameraB->SetRenderLayers(RENDERLAYER_2);
    ui_cameraB->SetPosition(framebufferB->size.x / 2.0f, framebufferB->size.y / 2.0f);
    ui_cameraB->SetClearMode(UltraEngine::CLEAR_DEPTH);

    auto uiB = CreateInterface(worldB, font, framebufferB->size);
    uiB->background->SetColor(0, 0, 0, 0);
    uiB->SetRenderLayers(RENDERLAYER_2);

    auto fpsA = CreateLabel("FPS : 0", 10, 10, 100, 20, ui->root);
    auto fpsB = CreateLabel("FPS : 0", 10, 10, 100, 20, uiB->root);

    auto boxA = CreateBox(world);
    boxA->SetColor(1, 0, 0);

    auto boxB = CreateBox(worldB);
    boxB->SetColor(0, 1, 0);

    while (true)
    {
        while (UltraEngine::PeekEvent()) {
            auto event = UltraEngine::WaitEvent();
            switch (event.id) {
            case UltraEngine::EVENT_WINDOWCLOSE:
                if (event.source == window) {
                    return 0;
                }
                break;
            }

            ui->ProcessEvent(event);
            uiB->ProcessEvent(event);
        }

        fpsA->SetText("FPS : " + WString(world->renderstats.framerate));
        fpsB->SetText("FPS : " + WString(worldB->renderstats.framerate));

        boxA->Turn(0.1f, 0.1f, 0.2f);
        boxB->Turn(0.2f, 0.1f, 0.1f);

        worldB->Update();
        worldB->Render(framebufferB, false);

        world->Update();
        world->Render(framebuffer, false);
    }
    return 0;
}

 

[Panel texture not showing with 3D cam]

While the example here works, it seems if you are overlaying an interface over a 3D environment the panel won't show the assigned texture.  I first noticed this in my project where I wanted to show the real-time render of a 2nd camera on the panel.

#include "UltraEngine.h"

using namespace UltraEngine;

int main(int argc, const char* argv[])
{
    auto displays = GetDisplays();
    auto window = CreateWindow("Ultra Engine", 0, 0, 1280, 720, displays[0]);
    auto framebuffer = CreateFramebuffer(window);
    auto world = CreateWorld();
    auto font = LoadFont("Fonts/arial.ttf");

    auto ui = CreateInterface(world, font, framebuffer->size);
    ui->background->SetColor(0, 0, 0, 0);

    //Create and position camera
    auto camera = CreateCamera(world);
    camera->SetPosition(0, 1, -2);

    int RENDERLAYER_1 = 2;
    auto ui_camera = CreateCamera(world, UltraEngine::PROJECTION_ORTHOGRAPHIC);
    ui_camera->SetRenderLayers(RENDERLAYER_1);
    ui_camera->SetPosition(framebuffer->size.x / 2.0f, framebuffer->size.y / 2.0f);
    ui_camera->SetClearMode(UltraEngine::CLEAR_DEPTH);

    auto panel = CreatePanel(0, 0, 512, 512, ui->root);
    auto tex = LoadTexture("https://raw.githubusercontent.com/UltraEngine/Documentation/master/Assets/Materials/Ground/river_small_rocks_diff_4k.dds");
    panel->SetTexture(tex);

    auto box = CreateBox(world);
    box->SetColor(1, 0, 0);

    while (true)
    {
        while (UltraEngine::PeekEvent()) {
            auto event = UltraEngine::WaitEvent();
            switch (event.id) {
            case UltraEngine::EVENT_WINDOWCLOSE:
                if (event.source == window) {
                    return 0;
                }
                break;
            }

            ui->ProcessEvent(event);
        }

        world->Update();
        world->Render(framebuffer);
    }
    return 0;
}

 

[RGBA16 pixel data]

Thanks that worked a treat.  Should we be able to change the format of a texturebuffer, like to RGBA or is RGBA16 the only one that will work for camera targets?

[RGBA16 pixel data]

Thanks.  It's actually 3 times slower to do that per pixel than to convert the whole pixmap and access the pixel data directly.

I am I correct in saying that for an RGBA16 format, the data here 2 bytes per channel?

char* data = pixmap->pixels->Data();

I need a value between 0 and 255 but I'm not positive if bit shifting like this is the right way.  And then I'm not positive how to get back the 0 - 255 range.

auto r = (data[index] << 8) | data[index + 1];
auto g = (data[index + 2] << 8) | data[index + 3];
auto b = (data[index + 4] << 8) | data[index + 5];
auto a = (data[index + 6] << 8) | data[index + 7];

index += 8;

 

[RGBA16 pixel data]

How can I access the pixel data from a pixmap generated with TextureBuffer::Capture()?  I want to access the pixel data directly like this:

auto captures = texture_buffer->GetCaptures();
if (captures.size() != 0) {
    auto pixmap = captures[0];
    auto data = pixmap->pixels->Data();

    int x = 0, y = 0, stride = 4;
    auto i = ((y * pixmap->size.x) + x) * stride;

    auto r = data[0];
    auto g = data[1];
    auto b = data[2];
    auto a = data[3];
}

I've also tried this but it shows an error saying it "Bytes per block must be four or less"

auto pix = pixmap->ReadPixel(x, y);
auto r = Red(pix);
auto g = Green(pix);
auto b = Blue(pix);
auto a = Alpha(pix);

I can convert the pixmap from TEXTURE_RGB16 to TEXTURE_RGBA and both code will work but it's far too slow for my situation (I'm doing it once per frame).

 

[Sprite::GetMaterial()]

Can we please get a GetMaterial() method for the Sprite class.

[Documentation Error]

Just a minor error in the C++ section for Framebuffer::Capture()

auto path = GetPath(PATH_DESKTOP) .. "/screenshot.jpg";
pixmap:Save(path);

Should be:

auto path = GetPath(PATH_DESKTOP) + "/screenshot.jpg";
pixmap->Save(path);

 

[Texture::GetPixels()]

Perfect!  I'll give it a go.  Thankyou.

[Texture::GetPixels()]

On 5/15/2022 at 8:40 PM, Josh said:

If you retrieve a texture from the GPU into system memory, that will be extremely slow.

I'm thinking about giving this a go as it's not really a real time application I want this for.  How slow do you think this could be though for a 512x512 image rendered with a camera?  1FPS?

[Blender glTF export and DDS]

I tried this some time ago.  I only ever got png to export in the gltf file.  Even if I imported the textures as dds.  What I ended up doing was as you say, using the asset editor.

[Transfer Entity to different World]

I thought it might.  Worth the check though.   I'll do the former!

[Transfer Entity to different World]

Would something like this be possible?  Or is there too much going on behind the scene?

Entity::SetWorld(my_2nd_world)

 

[Collider Not Removed From Object]

Thanks.  All is working well. 

[Collider Not Removed From Object]

Just wondering if you've had a chance to look at this yet?  None of my projects work at the moment.

[Collider Not Removed From Object]

Thankyou the example now works.  However there is a new issue - it appears if you set a collider to nullptr when the mass is zero the program will crash.  Comment out this line and it will crash.

   // box->SetMass(1.0f);

 

[Collider Not Removed From Object]

Not sure if this is a bug or not a good way to use the physics engine

The box will still collide with the floor if you store it's collider elsewhere and set the boxes collider to nullptr.  Are colliders unique to the object they are applied too?

#include "UltraEngine.h"

using namespace UltraEngine;

int main(int argc, const char* argv[])
{
    auto displays = GetDisplays();
    auto window = CreateWindow("Ultra Engine", 0, 0, 1280, 720, displays[0], WINDOW_CENTER | WINDOW_TITLEBAR);
    auto framebuffer = CreateFramebuffer(window);
    auto world = CreateWorld();
    world->SetGravity(0.0f, -2.0f, 0.0f);

    auto camera = CreateCamera(world);
    camera->SetClearColor(0.125);
    camera->SetPosition(0, 0, -8);
    camera->SetDebugPhysicsMode(true);

    auto light = CreateDirectionalLight(world);
    light->SetRotation(35, 35, 0);

    auto box = CreateBox(world);
    box->SetMass(1.0f);
    box->SetColor(0, 1, 0);

    auto store = box->GetCollider();
    box->SetCollider(nullptr);//Will still collide...

    auto floor = CreateBox(world, 10, .1, 10);
    floor->SetPosition(0, -2, 0);

    while (window->Closed() == false and window->KeyDown(KEY_ESCAPE) == false)
    {
        world->Update();
        world->Render(framebuffer);
    }
    return 0;
}

 

[Multiple Physics Worlds]

Never mind.  Physics objects in two separate worlds don't collide at all.  It turns out that the code I was using to transfer a collider from an entity to a pivot was flawed.

auto box = CreateBox(worldA);

//Transfer Collider to 2nd world
auto pivot = CreatePivot(worldB);
pivot->SetCollider(box->GetCollider());

box->SetCollider(nullptr);

It seems that if I set an entities collider to another object and then remove that collider from the original entity, although the collider is no longer visible when debugging physics, that box still collides.  

[Multiple Physics Worlds]

Now that this works - should it be that physics bodies in two separate worlds can still collide?  Or is it up to the user to disable those collisions themselves?

[Parenting Physics Objects to Platforms]

Gravity is cool 

I wonder if the jitter of the boxes is because the sphere is too small for there to be a flat enough face to rest on.

[Parenting Physics Objects to Platforms]

Yes that should work well.  I disable world gravity and use AddForce() in a loop elsewhere for now, it works but overwriting the default world gravity would be much cleaner.