reepblue

Yep, always happens. You have to click off the viewpoint/another viewport to stop the camera.

You can pharse the output stream with C++.

While I think we should have less tutorials, example content is a must. I myself learn things by looking at examples, and then modifying those samples to make it do what I want it to do. Samples should both be freely available and on the market place. We should also have a tutorial on the editor, and where everything is/what it does. But otherwise I agree; no "How to make an FPS shooter" this time. Give them a template and let them be creative. 🙂

Canonical back tracked on that decision due to the concerns, everything is going to be fine for now. The new engine will be 64 bit and you can always sell your game on other distributions.

Make this another property in the json file so it can be toggled. 🙂

I recall doing a similar test myself and I don't remember lights without shadows decreasing performance.

Do these models have bones? If so, might be a reason why. We had a lot of people had issues with models with a full body rig.

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.