AggrorJorn

Al your models should be put inside the models folder. Wheb the sandbox is loaded, the models automaticly appear in the editing menu.I don't know if there is a models map in the trial version.

I will post the first version of the user guide somewhere this week. It doesn't contain information about Lua, but should help you out with working with the edior.

Thanks for your answer!

I'm wondering what the alpha map does when you save your scene when working with terrains. Besides the sbx and raw file you get an entirely black alpha.dds file. Where is this being used for?

Are you sure? I select my model, hold the control key and just use the mouse. I fI use the arrow keys, the object is copied per centimeter over the screen. The other suggestions: I suggested the smal pivot from in the distance before (link to topic), I hope Josh does something about it. The Selecting the field behind the gizmo (last image) is also a good one.

Due to some overwork I wasn't able to finish it today. I'm going to skip the model conversion for a while as I need to research that first before I can start writing about it. I jsut saw the edit menu in the terrain editor. Thats quite the menu as well but I'm gonna skip that for now. only thing remaining is the explanation about the deault lua menu's and special objects. index updated.

wow that was a great video Niosop. just amazing only thing I can think of is perhaps a lua menu where you choose the material and a loop true/false button.

not directly human, more like a ranger alien (Its from odworld I believe) http://image.com.com/gamespot/images/2004/news/06/16/stranger_screen001.jpg

looks real smooth and everything. very nice

The creation of prefabs would be a partial solution to this.

its looking realy nice Gandi, Did you write a new shader for this? How high do you think you can make the waves?

Its a nice idea. people could create an entire 'animation-collection' for an entire level. They can define new animation by referring to gmf's. The idea of 'level-collections' can also refer to sound, level-information etc.

This looks realy good VicToMeyZR. I haven't tried it yet (I'm gonna ) but it seems realy nice. Does it handle single animation as well?

nice!

Sorry I should have explained it a bit better. This line frame = (AppTime()/34.0) % (120-0) + 1 should be used as follow: frame = (AppTime()/speed of animation) % (endframe-startframe) + startframe In your case: frame = (AppTime()/50.0) % (500-0) + 1 I don't know more then that at the moment. I'll try to work out how this exactly works. Using the Render function like this will result in an enormous speed increase (got that line from Josh), because you can have tons of offscreen characters that don't have to be animated.

New features that improve working with engine or improve better performace is always welcom.e However when the price goes higher, a different goal of customers is being addressed. This could lead to loss of customers. I haven't seen any hardware tessalation as good as in DirectX 11. Try the demo of the benchmark of the unigine engine. You can select between DirectX 9 -10 -11 and OpenGL. With the tessalation from DirectX 11 you get some pretty cool results. You do need indeed special hardware for this. Take a look at this video for example: Skip to around 2.20. http://www.youtube.com/watch?v=PR40GwRtFyw

I use this code for looped animation: require("scripts/class") local class=CreateClass(...) function class:CreateObject(model) local object=self.super:CreateObject(model) function object:Render() frame = (AppTime()/34.0) % (120-0) + 1 model:Animate( frame, 1,0, 1 ) end function object:Free(model) self.super:Free() end end

Thanks Marley, I'm afraid I can't finish it this weekend. I'm half way done with the terrain editor and I need to do the Leadwerks SDK and model viewer. I promise that it will be availeble for download aprox 1 week.

I've updated the index. only thing left to write about are Terrain editor Model viewer Texture editor Conversion methods I think that I'll do the texture editor and conversion methods later this week.

When you are editing an objects lua file, you don't run the file(F5). You must save it. only game scripts can be run. For the basic lua menu just use: require("scripts/class") local class=CreateClass(...) function class:CreateObject(model) local object=self.super:CreateObject(model) )

When Josh is back from his weekend of I will ask him what kind of tutorials he is making. I hope to see some updated videos instead of new feature tutorials.

At first I''l just try to make a non-coding User guide. There are a few lines of code in it, but they are not explained in usage. They are just examples. I will probably only make somehting Lua. Going into another language would be suïcidale. I see that conversion of models needs more attention then I originally thought. I wrote a few lines about the conversion tools, but that probably isn't enough. I'll spend some time on how the conversions work, but i'm goign to finish the guide first, so that I can release it this weekend.

Thanks for the comments - I don't buy models from Dexsoft so I wouldn't know how this works. Maybe someone else has experience with this. This can be added later though because there a lot of people who buy these assets. - I can't program, I just try some code and see if it works. Although I understand LUA a bit better then C++, I sometimes don't know exactly how commando's work. However, when Josh makes some new tutorials I might get better at it. I think I'll make a separate Lua user Guide for this. - I'm trying to make this User guide at a way so that every one can work with the engine. It doesn't mater whether you can program, model, animate or texture. When there are chapters that are unclear to users they can report that and I'll make some adjustments. B)

I find my stuff here: http://www.freesound.org/

I'm putting together a Leadwerks 2.3 User Guide. It has all the basic functions inside and outside the editor explained. I Download the LUG here. Current version: 1.01 106 pages of useful information that helps you getting around with the Leadwerks engine 2.3. This user guide is ideal for beginners but can also be used by advanced members as a reference guide. *new in version 1.01 fixed several typos fixed incorrect explanations updating the light and shadow options (Leadwerks 2.31) Camera path road node corona edit menu better mat file explanation Explanation about shaders shader usage Things that need to be added in LUG: sounds ini file and lua representative