Josh

Maybe that's too big? I have experienced it just silently failing if my image did not meet requirements.

Ah, I see what you meant. Don't worry about offending me, I like to entertain all manner of suggestions. Doesn't mean I'll do it, but I like to know what people think.

This is the Leadwerks3D particle system. It may be possible to set up a new graphics module based on Leadwerks Engine 2. The particle class is just calling surface creation commands, so it's not that different.

And you're setting up terms that are less favorable to them, if they do expect to do well.

Fortunately we don't have investment bankers breathing down our necks, so we won't ever have to charge that much.

It will cost less than Unity Pro.

I first started with projection shadow mapping, but it has many problems. When the light direction and camera direction are close to matching, there's no way to skew the perspective to get everything into the view, and you get very very low shadow resolution. After playing with this for a long time, seeing the same problem in NVidia's demos, and lots of reading, I decided perspective shadow mapping is only good for academic papers, and cascade shadow mapping is much more robust, which is why everyone uses it.

Most open-source software is written around what makes things easy for the programmer, not what makes things easy for the user. 3D World Studio was written to make things easy for the user. Leadwerks Editor was written to make things easy for me. I think it shows.

In other news, "moneybags" Xaron is now my only customer. I only need to make one sale! XD

I made a fake one in LE2, but I don't like doing that.

I had Hammer, UDK, and Crysis Sandbox open all day yesterday. I took ideas from each: Hammer: Standard Windows interface, four viewports, objects dropdown boxes, texture browser search filter. UDK: Asset browser, asset edit windows. Crysis Sandbox: Tabbed side panel.

According to MS, in America laptops account for like 76% of PC sales. I won't ever buy one myself, because I can always get a better desktop for less money, and I find them awkward to use.

Yeah, I'm going to make all dockable elements derived from a DockableElement class for future-proofing. There are some big challenges there. Would plugins be script or code? If code, the engine API would have to be re-exposed through the editor, because objects your code creates won't be the same engine instance the editor is using. If I use script, then I need to provide a binding for BMX and the engine. It's probably possible, but the debugging isn't as good as the engine's debugging features.

Yeah, I asked Chris and he pointed out that one method required me to draw an arrow to show what to do, and the other didn't. It's good to get a second and third opinion on these things.

Each tabbed item can be moved to the left, right, bottom panels, or popped open in its own window. The left, right, and bottom panels can be hidden and shown by click on the edge, or they can be resized by clicking and dragging. Here I have the asset browser popped open in its own window, maximized in a second monitor:

Please stop by this thread and give me some feedback: http://www.leadwerks.com/werkspace/topic/4987-interface-concept

Tell me what you think. Everything is customizable:

We've had a lot of discussion with the community about the Leadwerks3D script system. The current design is based on a combination of user feedback, lessons learned from Leadwerks Engine 2, stealing ideas from other game engines, and my own judgement. Our goal is to make a really easy and powerful game scripting system, without overwhelming the user with complexity. With that said, I thought I would let you in on how the script system presently is working in our own builds, and the process of using it. To attach a script to an entity, open the Properties Editor. Click and drag the script file from the Asset Browser onto the Properties Editor. A tab appears where all the script properties are displayed: Here's an alternate approach we are playing with. Here, the properties editor is embedded in the scene tab in the side panel. Since assets can't be dragged from the Asset Browser to the Properties Editor (since they are in different tabs) we just right-click on the entity in the Scene Browser, and a standard file request dialog appears, allowing you to choose a script file: Which do you like better? The visual logic editor in Leadwerks3D is called "Synapse". To add an entity into Synapse, drag the entity from the Scene Browser into the Synapse window. The entity will appear as a block, with its attached script components displayed below it in order. The color of the logical block corresponds to the object color in solid and wireframe viewports: You can see the script defines the output and input functions that are displayed in Synapse. Next I'll show you how entities in Synapse can be strung together to make sequences of events and gameplay logic.

So this is fixed?

FYI, even if Leadwerks experiences 0 market share growth (which I don't think will be the case!) we'll be doing just fine. There's a lot of Leadwerks Engine and 3D World Studio users out there. This time around is a little different because I am trying to put something out that is more polished at release.

It's possible for the ray cast algorithm to fall in between triangles and go through an edge where two surfaces meet.

That sounds like the Xcode 4 layout, which isn't bad. What I don't like is that a huge chunk of screen real estate will be empty and wasted when nothing is selected.

It actually worked out this way because of the need for multiplatform support, and the incredible scalability that involves. It's easier to account for everything from the start and design an engine once I know all the constraints on all platforms, keeping the high-end requirements in mind.

It's hard to make an objective test, but I think it will definitely be faster. The engine has no garbage collector (except for Lua, of course) and is written entirely in C++.

As I always do when making design decisions, I tried out several approaches to the properties dialog. Previously, I wrote about embedding it in the side panel, below the scene browser. I liked being able to quickly modify object properties, but I couldn't drag assets like textures and materials from the Asset Browser to the Properties Editor, because they were under different tabs in the side panel. Because of that, I popped the Properties Editor back into its own tool window. The experience of using the Properties Editor in the side panel gave me the idea to have an "Instant Update" mode, in addition to the default "OK", "Cancel", and "Apply" buttons. When "Instant update" is checked, any changes to the Properties Editor are immediately sent to the selected objects, giving you more immediate visual feedback. To add a script component to an entity, drag a script file from the Asset Browser to anywhere on the Properties Editor and release. A new tab with the properties for the script component will appear. Parsing scripts and getting their exposed variables is the next step I will work on.