L B

I agree that: "Leadwerks Engine" is long. The engine has to be differentiated from the company. However, the company must not promote 2 names, especially being focused on a single main product Reasons to not go with Leadwerks3D: "3D" seems to refer to rendering only, and not the game engine. Think Ogre3D Engine has no negative connotation in my humble opinion, but I'm curious to hear people's opinion The main product branded with Leadwerks is the engine, as as such would really rarely create a confusion with the company itself. The "Software" suffix is enough to differentiate the company in these cases. Single-word is simply bad. Typography geeks would probably disagree that a single-word is better to give balance to capitalization. Suggestions: Leadwerks 3 (companies don't have a version number) L3 as an abbreviation. (Pun on 1337 speek for the previous people who would look for the "Engine" in the name. Leadwerks 3D, if you really care for that name, please add a space.

Returns the preferred / default material name of a surface. I know it's available in BMX, but it'd be useful in other languages too.

Is the second line an edit?

This is a feature request? Dang, I just expected it to work. +1 for that.

Or, using Leadwerks .NET: using Leadwerks; class LoadAScene { static void Main(string[] args) { try { Engine.Initialize(800, 600); Window.Caption = "LoadAScene"; FileSystem.AbstractPath = @"D:\GameDevel"; Framework.Initialize(); Scene scene = Scene.Load("abstract::tunnels.sbx"); Framework.Camera.Position = Vector3.Parse(scene.Keys["cameraposition"]); Framework.Camera.Rotation = Vector3.Parse(scene.Keys["camerarotation"]); while (!Keyboard.IsKeyHit(Key.Escape) && !Window.HasRequestedClose) { if (Window.HasFocus) { Framework.Update(); Framework.Render(); Graphics.Flip(); } } } catch (LeadwerksException lex) { Debug.Alert(lex.Message); } finally { Framework.Dispose(); Engine.Dispose(); } } }

I like Lazario. He's a very good guy. Take my word for it.

Very very ferry nice.

Consider the FatCow icon suite for 32x32 icons on Mac OS X. They basically replicate the Silk icon set in bigger, with more variety also. Their 16x16 icons are not as pretty, though.

I'm pretty sure I will.

Sounds like voxel. <3

Thanks for taking care of the C# community RP.

Any update on this? I personnally humbly admit I cannot help at all.

The modification(s) to be done is(/are) in the engine DLL, hence why Metatron has to do it. And then, from that point, any language could use it.

How did changing the memory structure as we discussed the other day work out?

Don't forget the iPad. The only reason I do not already own a Mac and an iPad is because Leadwerks 3 is not out yet. Can you imagine?

Freaking perfect. Cannot wait for LE3.

We're talking about LE2 here, right?

Mm. Josh never said anything about it though. His answer seems to be that we always have to call Leadwerks methods on the main thread - which is false, with proper synchronization, only LoadModel seems to be failing right now. Maybe Mika could help us figure a workaround with the source?

You're suggesting C/++ methods to the wrong guy. Besides, I did have a queue on the main thread to work so far, but that turned out limiting after a while. So I really need to actually load the models on another thread. No fake, no almost.

Mm, it actually only seems to be models, now that I do more testing. Or perhaps loading in general.

I have managed to enable simple multi-threading by using a lock, or mutual-exclusion (mutex) system. Basically, I lock around all Leadwerks commands, so that none of them can be called at the same time, and forcing them to execute sequentially. This works really well for all commands. Except for the ones which create an entity, be it a body, model, mesh, light, etc.I'm wondering why that occurs, but most importantly, how can I truly create an entity on another thread. I know I could invoke the entity to be created on the main thread (using a delegate that gets executed at the next loop), and this is the approach I've used so far. However, for many reasons, I would like to create entities on other threads. How can I *truly* create entities on other threads without Leadwerks crashing?

Ew, strings as possible values?! Haven't you heard of enums or constants? Please. If you write a new renderer, you'll have to compile it anyway.

Official C# in LE3 will be such, such a relief.

I'd wait until C# is officially supported in LE3. But if really any of you need a hand with adding funcitonalities, just let me know. I might also have them already implemented in my version here.