Development Blog

Really cool. This will help with users building the game with their own systems instead of fighting with any conflicting ones.

Just keep the default plugs to a minimum and provide docs and examples. ?

I'm thinking about makign VSCode the official C++ IDE as well. We have one IDE that can handle C++ and Lua, on all platforms.

How can you compile projects with just VSCode? I can see if you were using the Windows GCC stuff and used makefiles, but you need the complete VS2017 to build anything using MSVC as far as I know.

@reepblue You can compile with Visual Studio compiler using Makefiles.

Have a look at CMake.

So I have a question about the LUA and DLL stuff. Does that mean I could search for things like (controller dll) and hook them in using the plugin system? Or load in dlls that would allow 64 bit commands?

6 minutes ago, Wafflesoft said:

So I have a question about the LUA and DLL stuff. Does that mean I could search for things like (controller dll) and hook them in using the plugin system? Or load in dlls that would allow 64 bit commands?

1. Yes.
2. It will all be 64-bit only.

OMG that is awesome news. So if its all 64 bit only, does that mean our existing projects will upgrade to 64 bit once this system is implemented? Or will we need to do that ourselves?

1 minute ago, Wafflesoft said:

OMG that is awesome news. So if its all 64 bit only, does that mean our existing projects will upgrade to 64 bit once this system is implemented? Or will we need to do that ourselves?

Your Leadwerks projects will not work with the new engine.

Here's C++ source code for a working plugin:

#ifdef _WIN32
	#define WIN32_LEAN_AND_MEAN
	#include <windows.h>
#endif

extern "C"
{
	#include <lua.h>
	#include <lauxlib.h>
	#include <lualib.h>
}

#include <sol.hpp>

BOOL APIENTRY DllMain( HMODULE hModule,
                       DWORD  ul_reason_for_call,
                       LPVOID lpReserved
                     )
{
    switch (ul_reason_for_call)
    {
    case DLL_PROCESS_ATTACH:
    case DLL_THREAD_ATTACH:
    case DLL_THREAD_DETACH:
    case DLL_PROCESS_DETACH:
        break;
    }
    return TRUE;
}

//Example function to add to Lua API
double Add(double a, double b)
{
	return a + b;
}

//Load plugin function
bool Load(sol::state* L)
{
	L->set("TEST", 462);
	L->set_function("Add",Add);
	return true;
}

That's all it takes.

4 hours ago, martyj said:

@reepblue You can compile with Visual Studio compiler using Makefiles.

Have a look at CMake.

What I was saying is that you still need MSVC to compile C++ code. Just having VSCode installed will not enable code compiling as it lacks a compiler to my knowledge.

Pretty much, can't make VSCode the official IDE because you still need MSVC on Windows and I couldn't figure out how to download only clang/g++ without XCode on macOS.

With Linux, it's not that big of a deal as the compiler is a small download away and your free to choose whatever compiler you want.

My question is why request the end user to download 2 additional pieces of software?

 

@Josh 

1. Do you think you will use the plugin system like a nuget store for several core Turbo functions? It would make the editor easier to update without constantly building the entire editor.
2. I do not entirely see the advantage of separating the menu logic from the importing logic. Lets say I make a C++ lib that works both in-game and in-editor, I would want to load it in via your second, but also make the menu options.
3. How many projects are you working on right now? Don't overwork yourself.

I find the process_event callback rather cluttering up the code. How about setting a callback for a click event? 

function Plugin:Load()
  local menu = Editor.modelEditor.menu:FindMenu("Plugins")
  if menu ~= nil then
    self.menuitem = menu:AddItem("Flip Normals")

    --syntax: self.menuitem.SetMenuClickEvent(callback, extraParams = {}))
    self.menuitem:SetMenuClickEvent(
      self:FlipNormals(Editor.modelEditor.model),
      {forceModelEditorRedraw = true, someOtherValue = 0.3}
    )
  end
end

function Plugin:FlipNormals(event, params, model)
  if Editor.modelEditor.model ~= nil then
    --code: Flip normals of model
    if params.forceModelEditorRedraw then
      Editor.modelEditor:Redraw()
    end
  end
end

Rather than relying on this long if chain in processEvent, you set the callback for the events you really need like.

• MenuClick
• ViewPanelLeftClick
• ViewPanelRightClick
• SceneTreeChanged
• TransformMoved (triggered when object in scene is moved)
• RotateEvent (triggered when object in scene is rotated)

9 hours ago, AggrorJorn said:

@Josh 

1. Do you think you will use the plugin system like a nuget store for several core Turbo functions? It would make the editor easier to update without constantly building the entire editor.
2. I do not entirely see the advantage of separating the menu logic from the importing logic. Lets say I make a C++ lib that works both in-game and in-editor, I would want to load it in via your second, but also make the menu options.
3. How many projects are you working on right now? Don't overwork yourself.

I find the process_event callback rather cluttering up the code. How about setting a callback for a click event? 

1. I have not thought about it. This isn't something I really worry about.
2. Game plugins are things that add new functionality. Editor plugins add new tools. I don't see a lot of crossover between those things.
3. Too many. There is a plan to fix this but I can't say anything more about it right now.