SarperSoher

Physics have a fixed timestep, they are not updated every frame. When framerate drops, physics update intervals increase, rigidbodies and other physics stuff gets updated less. Rigidbodies start to move erratically, collision events on moving rigidbodies do not happen correctly etc.

Graphical quality boils down to having good art assets and shaders. One can make the ugliest looking game even in Unreal Engine if one has no high quality assets and shaders. With deferred rendering, dynamic shadow maps, anisotropic texture filtering, post processing support, OpenGL 4.0 level shaders support, megatextured terrain amongst other things, Leadwerks 3.1 gives you a very good foundation to build a game on graphically in my opinion. Question is, how much time, experience and budget one has.

Josh stated before that the trial will be updated to 3.1 once it's out

Oh you misunderstand, I didn't ask you to duplicate how Unity does it. Since you thought we were asking you for plugins I wanted to clarify what we meant by asking for an API to develop our own tools. And it's always good to know what your competitors did and how they did it...

This is how Unity does what I meant, please take a look when you are available http://docs.unity3d.com/Documentation/Components/ExtendingTheEditor.html

Thanks for pointing those out, can't wait for 3.1 now! Wish there was a roadmap though, I would love to read on these planned features from a single official source.

Textures are looking terrible at oblique angles right now. Especially geometry like ground and walls in corridors. Up to 16x Anisotropic Filtering would increase the visual quality of the textures a lot.

Ah yes, the thread title is misleading, these suggestions are meant for any version in the 3.x line of updates.

I have spent some time today creating a list of features I would love to have in Leadwerks 3. I have a strong Unity engine background and most of the features I suggest here may sound familiar if you 've used it. Some of the features here would take a lot of effort to implement I know so please note that I did let my imagination run wild while writing some of those. So here are my suggestions assorted in different categories. Hope these help! Editor - Make it so that FPS mode in the 3D viewport only gets activated while the right mouse button is held down. That would free the Q W E R keys. These keys are well known by artists for they are used for Move, Rotate, Scale tools and switching between Local/World space coordinates respectively. This may seem very simple but it would speed up the map design by orders of magnitude. It is just not intuitive to click the buttons from the toolbar above when you have to place a lot of models. - When an item is selected in any of the viewports, other windows like the scene browser should also focus to that item. - Windows and tabs should be dockable and user has to have the ability to save different layouts. - "Go to" command needs a keyboard shortcut. For example Unity engine has F for "frame selection" which does pretty much the same thing. - Speaking of keyboard shortcuts, customizable keyboard shortcuts for most of the tools is required. Especially being a programmer myself, I do everything using just my keyboard much much faster than using mouse and menus. Once you learn the shortcuts, you do things much faster, imagine doing an extrude operation in your favorite modelling application through the menu each time, painful. - Wireframe, solid, textured & lit modes are great. It would be even better to have viewport render modes like light only, overdraw, mipmap etc. - Ability to edit the scene in the editor while the game is running. Ability to edit and see the effects of lua scripts without re-running the game. Script Editor - Auto-completion and suggestions in the script editor - CTRL+Arrow keys should move the caret to the previous or next upper case letter like in all text editors. - Ability to customize, save and load color themes for background, variables, loops etc. White background is bad for your eyes - Auto-closing of open braces, paranthesis etc. CSG - Boolean tool would help creating different shapes of geometry. Right now we are limited with a couple of fixed shapes. - Texture locking, right now when a bsp piece is moved the offset of the texture changes. It requires extra effort from the developer to fit it again as intended. Programming - Support for later releases of Microsoft Visual Studio. Especially the Visual Studio 2013 as it brings nice C++11 features natively. - Ability to get debug information on drawcall count, rendered triangle count, time spend drawing the last frame, number of batched and non-batched models, these all would help optimizing the game. - Access to terrain API for runtime modifications (like generating craters etc.) - Access to timescale for slow-motion effects - Ability to expand the editor with custom tools and windows (Number one reason why Unity Asset Store got so huge) Physics - Physics materials with customizable bounciness, friction etc. Shaders - Support for shader model 4.0 and 5.0. As far as I understand the renderer uses OpenGL 4.0 so why limit the developers with OpenGL 2.1 level shaders. - Support for custom tesselation shaders. - Support for geometry shaders for effects like fur - Ability to access more textures than 8 in a shader (6 if you use lightmaps and light vector maps) (You may ask why, let's say I want to use the 4 vertex color channels as masks for 4 different set of textures -diffuse, normal and specular- to create models with unique details. That makes 12 textures.) Terrain - Ability to have multiple terrains in a single scene - Ability to load, enable and disable terrains at runtime to be able to create huge worlds like in Skyrim - Ability to carve holes in the terrain mesh to be able to put caves, underground structures etc. seamlessly - Built in filters like erosion, perlin etc. - Spline based road and river editor - Vegetation system with uniform wind force and character controller collision Lightmapping - Global Illumination calculation and baking would add a lot to lightmaps - Hard shadows. The current lightmaps look terrible with no blur - Dual lightmaps. A range around the camera would render dynamic shadows while it fades into the lightmap in the distance. Right now we have to use either full dynamic shadow or baked lightmap shadows. They are nice but if one chooses the lightmap route, when a dynamic object goes under a shade of a tree for example, it won't receive any shadow. Renderer - HDR and tonemapping Tools - Node based shader editor. People with an artist background, people coming from engines like UDK, people with little shader programming knowledge would really appreciate this. These people create awesome stuff in those engines. - Runtime profiler detailing where the CPU, GPU and Memory resources are spent in detail. - LOD generator. This tool would take our model and generate simpler versions with lower polycount based on a numerical or percentage input - Vertex painter (Very very useful for shaders which utilize vertex colors, see the last item in Shaders category) - Visual 3D/2D GUI editor, something like a very simple version of ScaleForm

As a newcomer to Leadwerks engine I'm finding it hard to understand the technical features, known bugs and planned features. Right now I have to bug people asking a lot of questions and it's hard for other people and myself. It would be great to have a version histroy to see the added features with version numbers and fixed bugs. And a release notes info on either the forum, website or the updater. And finally a roadmap of planned features throughout the 2014 would rock. The bug reports forum section is not suited for this, a clean organized bullet list would be best. Even a text file in the leadwerks folder would do. What do you think?

Works just fine now, thanks!

Hi, I'm a long time Blitz3D and Unity developer. I just purchased the Leadwerks 3 for Windows. I've been testing the trial version for some time now and I liked what I saw. Also I had no problems with the trial version at all. I uninstalled the trial, downloaded the updater, did a clean install. But I'm having a ton of problems building a clean project or the Darkness Awaits project. Any help would be very much appreciated. Thanks in advance. 1) I installed the engine in "D:\Applications\Leadwerks" path initially. This caused the Darkness Awaits not to compile at all because the library path was set to "C:\Leadwerks..." I guess. It couldn't find the "Leadwerks.h" header or any other headers in that matter. 2) Moved the engine to "C:\Leadwerks" with everything included, ran the updater again in this path. This time upon trying to build it, it couldn't find the zlib headers. I have taken a look in "C:\Leadwerks\Engine\Source\Libraries" path and there are a bunch of libraries but no zlib. Updated does not download it. 3) I'm trying to run or debug the project in Leadwerks editor, I'm immediately getting a "Failed to lunch" error. I guess it's due to project being not build in Visual C++ I'm using Microsoft Visual C++ 2010 Express while trying to build the solutions (Visual Studio 2013 support would be huge though ) . I have all the required redists. I have the latest OpenAL. It is very important for me to be able to install the engine in any partition of my harddisk I like, I generally just keep the C: for OS and D: for everything else. It shouldn't break anything in solution properties in Visual Studio imo. I searched the forums and the web and couldn't find any similar problems. Again any help would be greatly appreciated, thanks!