[Convert Texture to DDS]

Just tried this out.  It works but doubles up on the texture uri's in the gltf file?  Is this intended?

	"images": [
		{
			"uri": "PineLeaves_DIFF.png"
		},
		{
			"uri": "PineLeaves_DIFF.dds"
		},
		{
			"uri": "PineLeaves_NORM.png"
		},
		{
			"uri": "PineLeaves_NORM.dds"
		},
		{
			"uri": "PineTrunk_DIFF.png"
		},
		{
			"uri": "PineTrunk_DIFF.dds"
		},
		{
			"uri": "PineTrunk_NORM.png"
		},
		{
			"uri": "PineTrunk_NORM.dds"
		}
	]

I also can't load the converted images into GIMP.  I know it's a plugin issue, but I've not heard of this format.  Just checking it's all good?

[Editor not loading other projects]

I had to change this manually to get it to work.

"openFolderPath": "C:/UltraEngine/Projects/New Project"

 

[Editor not loading other projects]

No matter which project I click in the client it always loads the editor with NewProject.  If I remove NewProject from the client and delete the projects contents the editor will load with a blank project.

[Ultra - Release Mode Not Compiling]

Have you managed to solve this yet? 

[Turn off culling]

Yeah that's a good approach.  Personally I like the idea of selecting which entities should have fixed visibily, especially for UI.  But enlarging the frustrum may have uses too.

[Turn off culling]

Soooo back to my original question.  Is possible to turn off frustum culling?

[DevLog Leadwerks Engine.]

Nice!  😁

[Turn off culling]

I just figured that if the UI follows the camera then turning culling off would nip the issue it in the bud.

[Turn off culling]

Haven't tested that in a while due to the version mismatch thing but I remember it being a lot better in Release, but still noticeable.

[Turn off culling]

Oh I just have some simple meshes rendering to the UI camera, and I move them about, in and out of view for reasons too complex to explain.  I've mentioned before that especially in debug mode the culling is quite slow at the moment.  I thought If I could turn off culling for the UI camera it would probably solve the small issue, that's all.

[Shader Master (Node Editor for Custom Shaders)]

It's for Ultra.  Not sure if I'll make it work for Leadwerks yet.

[Turn off culling]

Ah, Ultra Engine.

[Shader Master (Node Editor for Custom Shaders)]

Still churning away at this.  Working on the geometry shader at the moment and custom outputs.

[DevLog Leadwerks Engine.]

Looking good!

[Turn off culling]

Can I turn off culling for a particular camera?

[fullbright surface?]

There's bloom.lua in the posteffects folder under the shaders folder in your project.  I think you add that to your camera as a post effect.

For an emission shader I think you just need to change the shader from diffuse.shader to emission.shader in the material editor.  I haven't used Leadwerks in a while though.

[fullbright surface?]

A bloom post effect maybe?  Or if your talking about the lens of the light you'll need an emission material.

[No collsion with mesh collider]

I thought I'd better post this here as I think it's a bug.  Though I'm not sure...  I can't seem to get the mesh to collide with the falling cube - I think I got the collider in the right spot to catch the cube.

#include "UltraEngine.h"
#include "Components/Mover.hpp"

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, 1280, 720, displays[0], WINDOW_CENTER | WINDOW_TITLEBAR);

    //Create a world
    auto world = CreateWorld();

    //Create a framebuffer
    auto framebuffer = CreateFramebuffer(window);

    //Create a camera
    auto camera = CreateCamera(world);
    camera->SetClearColor(0.125);
    camera->SetFov(70);
    camera->SetPosition(0, 1, -5);

    camera->SetDebugPhysicsMode(true);

    //Create a light
    auto light = CreateBoxLight(world);
    light->SetRotation(35, 45, 0);
    light->SetRange(-10, 10);

    bool flip = true;
    float extents = 3.0f;
    vector<Vec3> verts;
    if (flip == false) {
        verts.push_back(Vec3(-extents, 0.0f, -extents));
        verts.push_back(Vec3(extents, 0.0f, -extents));
        verts.push_back(Vec3(0.0f, 0.0f, extents));
    }
    else {
        verts.push_back(Vec3(-extents, 0.0f, -extents));
        verts.push_back(Vec3(0.0f, 0.0f, extents));
        verts.push_back(Vec3(extents, 0.0f, -extents));
    }

    auto c = CreateMeshCollider();
    c->AddFace(verts);
    c->Finalize();

    auto pivot = CreateModel(world);//Works
    // auto pivot = CreatePivot(world);//Dosn't Work
    pivot->SetCollider(c);
    pivot->SetCollisionType(COLLISION_SCENE);

    world->SetCollisionResponse(COLLISION_SCENE, COLLISION_PROP, COLLISION_COLLIDE);

    //Main loop
    vector<shared_ptr<Entity>> cubes;
    while (window->Closed() == false and window->KeyDown(KEY_ESCAPE) == false) {
        if (window->KeyHit(KEY_SPACE) == true) {
            auto cube = CreateBox(world);
            cube->SetPosition(0.0f, 10.0f, 0.0f, true);
            cube->SetMass(1.0f);
            cube->SetCollisionType(COLLISION_PROP);

            cubes.push_back(cube);
        }

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

 

[Save Texture to Stream]

Can a texture be saved to a stream and then loaded back again with LoadTexture(stream)?

auto stream = WriteFile(filename);

//Write some stuff

texture->Save(stream);

stream.Close();

[Visualize Colliders on a Pivot]

 I made a bug report for the Collison thing.

[CreateMeshCollider() with no arguments?]

Thanks, I'll see what I can do.

[CreateMeshCollider() with no arguments?]

It needs refining, but currently I create a collider per voxel.  This can be up to 5 or so triangles in total per collider.  It worked the old way because I was able to set the indices as well.

[CreateMeshCollider() with no arguments?]

I think the answer is yes... would it be practical to add the ability to set the indices?  Just that going through this and adding vertices in order is going to be a headache to figure out.

[Visualize Colliders on a Pivot]

The collider is not visible on a pivot.  I use pivots as the hubs for Collison patches on voxel terrain, mainly due to the fact it doesn't need a visible model.  The code below shows the problem but I have just found out it will work on a model even if it doesn't have a mesh.

Should a pivot be used like this?  Or is is there any harm in using a model without a mesh assigned to it this way?

#include "UltraEngine.h"
#include "Components/Mover.hpp"

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, 1280, 720, displays[0], WINDOW_CENTER | WINDOW_TITLEBAR);

    //Create a world
    auto world = CreateWorld();

    //Create a framebuffer
    auto framebuffer = CreateFramebuffer(window);

    //Create a camera
    auto camera = CreateCamera(world);
    camera->SetClearColor(0.125);
    camera->SetFov(70);
    camera->SetPosition(0, 1, -5);

    camera->SetDebugPhysicsMode(true);

    //Create a light
    auto light = CreateBoxLight(world);
    light->SetRotation(35, 45, 0);
    light->SetRange(-10, 10);

    vector<Vec3> verts;
    verts.push_back(Vec3(-3.0f, 0.0f, -3.0f));
    verts.push_back(Vec3(3.0f, 0.0f, -3.0f));
    verts.push_back(Vec3(3.0f, 0.0f, 3.0f));

    auto c = CreateMeshCollider();
    c->AddFace(verts);
    c->Finalize();

    auto pivot = CreateModel(world);//Works
   // auto pivot = CreatePivot(world);//Dosn't Work
    pivot->SetCollider(c);
    pivot->SetCollisionType(COLLISION_SCENE);

    world->SetCollisionResponse(COLLISION_SCENE, COLLISION_PROP, COLLISION_COLLIDE);

    //Main loop
    vector<shared_ptr<Entity>> cubes;
    while (window->Closed() == false and window->KeyDown(KEY_ESCAPE) == false) {
        if (window->KeyHit(KEY_SPACE) == true) {
            auto cube = CreateBox(world);
            cube->SetPosition(0.0f, 10.0f, 0.0f, true);
            cube->SetMass(1.0f);
            cube->SetCollisionType(COLLISION_PROP);

            cubes.push_back(cube);
        }

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

 

[CreateMeshCollider() with no arguments?]

So I should take care to add them in a certain order?  Like a triangle_strip in GLSL, otherwise I might get overlapping faces...?