reepblue

Lights are cheap, it's the shadows you have to worry about for the most part.

Compare these results to how it looks in Leadwerks:

Thanks for that link, it pointed me to an application that I was looking for. http://orsvarn.com/entry/channel-shuffle/

Sorta how Leadwerks knows what masks are your color. normal, and spec; how you name them. mytex, mytex_n, mytex_r, mytex_m, mytex_ao. I'm thinking that the editor would read your raw images copy the pixels and merge them into one image then output it as one dds texture.

Set a standard, make a tool that merges peoples masks into one image, call it a day. You can have the editor detect these sheets and auto merge them

Try making the platforms models and repeat the test. Sounds like the "If I add too many objects to my scene, it slows down" issue.

Yeah, Ok. So The issue is that it's common to open Photoshop and merge all those outputted sheets into one images using the RBGA channels. However, there is no standard; people put whatever mask in whatever channel and then when they import it into an engine, they use the silly nodes to define what's their roughness/metal/AO/etc. Issue is that right now, Turbo doesn't have a node editor, and from the looks of it, Josh wants a standard which is non-existent within the art space. Really big mess right now.

@wadaltmon Does it merge all the masks into one image or outputs one by one separately?

Let's just do separate images for each map and call it a day. ?

the gltf model actually loads each image as a separate mask like how we were doing things in Leadwerks. To be completely honest, this is the most easiest method.

Blender 2.8 has a material node system. It's pretty similar what you'll find in Unreal. There is no real standard for any of this.

The issue is that other engines/tools allow the end user to pick what mask goes in what channel; creating the fragmentation. I used to put my roughness in Red, metal in Green, and AO in Blue personally. There can be an issue when it comes time for artist to port their assets in the new engine. To be fair, I think most people just want to copy and paste their textures and to create a material file. A fixer/mask importer app would be nice.

Might not be much help, but here is an example of using cmake for a Super Mario Clone. You can see the definitions for gcc and MSVC. https://github.com/jakowskidev/uMario_Jakowski?files=1

From what I understand, you can use the same CMake script for both platforms. There is a bit of if statements and switches you can implement. Not getting what's the concern minus the mess of dependences and preprocessors. (Or that's it and you don't want to be bothered, lol)

Really cool. I have some assets that I'm working on in which I can't wait to use in Turbo. ?

The editor is gimped on Linux, and you can't collapse models (not even with the command parameter, the model will crash the editor).

Lua scripts still work, you just removed the entry point being the Main.lua script. You can execute any script using a function call. Check out App.cpp for more details.

I'll look at this when I get home tonight. Really cool.

Here's how to make UVMagic work in 2.8 https://github.com/nutti/Magic-UV/issues/105 I didn't test 2.8 nor the plug-in, but I want to this weekend.

Neat. Is there a specific entry function for the start scripts, or just it just "import" the script into memory?

Not a C# user, so bare with me. From the looks of it, it seems you need to export every fiction call via a wrapper function. Wouldn't that just be silly in real use cases? I'm sure there is a better way. Still neat tho.

Seems like a lot of work, but very cool.

You can't. Only Josh can. It needs to be updated for the new index controllers anyway. I'm sure he'll do it once he's done with the new renderer for Turbo. (Hopefully sooner)

Maybe the openvr API needs to be updated with the engine?

I can give you one when I get home. What's the issue you are having?