Josh

That's correct.

Can you please write your system specs in your signature? Thanks!

I wouldn't call Crysis "simple", but if you have a team of programmers working within known constraints of a specific game, it is a lot easier to program an engine.

Fixed. That's the maximum supported value.

Leadwerks is not designed specifically for one game. If it were, it would have been a lot easier to write.

You can download a package of C++ tutorials here. They include all files, and are ready to compile and run: http://leadwerks.com/werkspace/index.php?/page/resources?record=25 It's a little easier than downloading the individual lessons and copying files to make them work.

What amazes me is what you guys are able to do with it. It's still pretty early in the engine's life, so I can only imagine what people will be able to make, given some more time.

I'll pick up some more hardware tomorrow and do extensive Windows 7 testing.

I think with LE, they will be about the same, since the more intensive stuff is being done internally. In a simple app, script and C++ will even run at the same speed.

I'm putting together a real installer and testing everything thoroughly...please wait.

I need a program I can run and test myself.

If there are any problems with parenting I would very much like to see an example.

Works fine for me. Anyone else have a problem? It's not supported yet. I didn't mean to include that. I uploaded it now. The files are present. See "Models\Weapons\".

Ah, I thought you meant the DLL source. Sorry about that.

What is that?

When you parent one entity to another, if the global parameter is set to true, the global orientation of the child entity will be left intact, and the local orientation will be recalculated.

There is a self-contained installer here: http://leadwerks.com/werkspace/index.php?/files/file/145-leadwerks-engine-sdk-232/ You can also run the updater with the latest version 2.32. Version 2.32 evolved into a pretty big update. The biggest improvement is the internal entity storage system. An octree is used to store all top-level entities, and the rendering and picking routines are now recursive. The view range setting is now an integer category, instead of an arbitrary number. This allows the engine to dismiss chunks of scenery if they are far enough away from the camera, without having to iterate through each entity. Vegetation rendering was rewritten and optimized. The disappearing vegetation shadow bug was eliminated, and vegetation collision added. You can set the collision type for the layer in the vegetation properties panel in the editor. Collision trees will build much faster now when meshes are loaded. You can also use the supplied gmfprocess tool to create collapsed GMF files with pre-serialized surface data for raycasting. This will make meshes load faster. 2.32 -"Render" Lua object function renamed to "Draw". -Added Draw entity callback. -Entity draw callback and Lua "Draw" object function will only be called at most once per frame. Perform animation in this function. -Entity LOD distance parameters changed for better performance. -LoadAnimation now works without exact hierarchy matches, so LOD meshes can all use the full-res animation. -Implemented entity octree with hierarchical culling and picking. -Rewrote vegetation rendering routine. -Added vegetation collision. -Added optional terrain color map. -Fixed some problems that prevented custom buffers from working.

It sounds like your animation make the bone oriented in a way you did not intend. If you can post a demo showing your problem, someone can probably help you.

This will install ten C++ lessons, ready to run right out of the box: http://leadwerks.com/werkspace/index.php?/page/resources?record=25 Leadwerks Engine 2.32 is required.

Yes, because I said it would be free for you. I decided to let Michael rework some of the assets and sell the improved pack, and thought it would be confusing if I was giving away something similar. Since the offer was made to existing developers at that time, the pack was left up for two weeks with a notification to download it.

Well yeah, if you look at the videos of CryEngine 3 on the consoles, you can see it is limited compared to the PC, but it works.

A 4096x4096 DXTC5 .dds file with mipmaps is 21.3 mb. That only allows 30 of them, with no vertex buffers or other data. I would work with the assumption that the lowest memory capacity any GPU your game runs on has will be 256.

Well, we may be looking at an XBox port sooner than I previously anticipated.

Ten uncompressed RGBA 4096x4096 textures with no mipmaps will consume all of your video memory. In the example above, I would add a detail texture to improve resolution at near range.

You might be okay with the fake DLL approach. I'd start by returning all zeros (if the function returns anything) and if that doesn't work on, start returning indexes for textures, vertex arrays, shaders, shader uniforms, and vertex buffers. You guess correctly!