Josh

Fixed.

thanks

Easy fix, thanks for reporting.

Yes, this is the correct behavior. Otherwise if you loaded a model, all the limbs would get deleted automatically unless you created a variable for each object in the hierarchy.

No, never.
This week I am focusing on bug fixes and enhancements to the editor, but I will be focusing again on hardware compatibility soon.

You are experiencing something called Gimbal lock:

https://en.wikipedia.org/wiki/Gimbal_lock
The solution is to rotate the mesh in your modeling program so it's not pointing near +/- 90 degrees.

Fixed.

Press Enter or right-click and select the Create popup menu item.
Object types that require extra parameters like cylinders and terrain will crash the program right now. I am finishing it today.
This is only on the beta / dev branch, the stable branch still works the same as before.

This is a known issue in the dev channel right now, due to changes in the object creation process. It will be fixed shortly.

We are on a new version now and it will be going through some experimental changes. If you need something more stable, 0.9.2 is now on the default branch.

This change will be in the next build.

You are correct. This will be fixed in the next build that is uploaded.

Fixed in incoming update...

In the process of explaining the problem I think I solved it. Update is incoming later today.

This has been fixed in 0.9.2

I think this is a repeat of this, which is solved
 

Fixed

I believe this is fixed. Uploading now...

You can set the background / root panel's background color to 0,0,0,0 to make is see-through. Then create a smaller panel on it for your visible GUI area.

When the project was created, the editor should have asked to create an environment variable. It will create a system environment variable like this, which tells the compiler where to find required files:

The short answer to your question is yes. 
The engine is design as an object-oriented C++ framework. If you wish to use it, you have full control over the program at the very base level. This is also nice for documentation because it allows us to demonstrate how a command works in a very simple program:
#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, 800, 600, displays[0], WINDOW_CENTER | WINDOW_TITLEBAR); //Create world auto world = CreateWorld(); //Create framebuffer auto framebuffer = CreateFramebuffer(window); //Create a camera auto camera = CreateCamera(world); //Main loop while (not window->Closed() and not window->KeyDown(KEY_ESCAPE)) { world->Update(); world->Render(framebuffer); } return 0; } An entity component system is also available, which is particularly useful for setting up object properties in the editor and then accessing them in component code in your game:
https://www.ultraengine.com/learn/Component
Someone who is making something like a space game with all procedurally placed content would not need the editor, and might not need the ECS at all. Someone else who is using the editor a lot for level design will probably want to rely on the ECS in order to set up properties in the editor and access them in the game.
The ECS is also good for user-created modular code that can be reused in many projects.
You don't have to choose between one or the other. You can use the ECS and you still have access to the main function in case you want to do something special there. I like to use the OOP approach for documentation examples because the user can just copy and paste one block of code into any project, without a lot of complicated setup, but the functionality demonstrated can be implemented in any entity component.

Thank you, I found the cause. I think I will wait until Tuesday to upload any more changes.

It looks like the error is only in the editor, and not in the engine library itself. I updated the editor and this example works:
start.zip
#include "UltraEngine.h" using namespace UltraEngine; int main(int argc, const char* argv[]) { auto cl = ParseCommandLine(argc, argv); //Load FreeImage plugin (optional) auto fiplugin = LoadPlugin("Plugins/FITextureLoader"); //Get the displays auto displays = GetDisplays(); //Create a window auto window = CreateWindow("Ultra Engine", 0, 0, 1280 * displays[0]->scale, 720 * displays[0]->scale, displays[0], WINDOW_CENTER | WINDOW_TITLEBAR); //Create a world auto world = CreateWorld(); //Create a framebuffer auto framebuffer = CreateFramebuffer(window); //Load the map WString mapname = "Maps/start.ultra"; auto scene = LoadMap(world, mapname); auto navmesh = scene->navmeshes[0]; navmesh->SetDebugging(true); auto agent = CreateNavAgent(navmesh); auto player = CreateBox(world); player->SetColor(0, 1, 0); player->Attach(agent); auto camera = CreateCamera(world); camera->SetPosition(0, 1, -4); //Main loop while (window->Closed() == false and window->KeyDown(KEY_ESCAPE) == false) { if (window->KeyHit(KEY_SPACE)) agent->Navigate(1, 0, 0); world->Update(); world->Render(framebuffer); } return 0; }  

In MouseMovementController.cpp, GetComponent is returning null:
else if (!pick.entity->tags.empty()) { for (auto tag : pick.entity->tags) { if (tag == "gather_water_task") { auto task = entity->GetComponent<GatherWaterTask>(); task->OnTaskStart(entity, pick.entity);// set a breakpoint here and look at the task variable break; } } }  

Error code -4 is VK_ERROR_DEVICE_LOST. Please see this solution: