DaDonik

Is your basic knowledge not enough to make such a room yourself? You don't need Textures or UV mapping when it should look like that example.

Haha rick, that was close

It imports nearly everything and lets you export nearly everyting. In between you can UVmap the model if you like. Thats basically UU3D. As i don't use Max, i don't know if UU3D is required for that.

The higher the framerate, the better. There is no such thing as a recommended framerate. You're graphics card is fine. The thing is that you have a high resolution and all settings on max. Keep in mind that LE is a deferred renderer and has a higher initial impact on the framerate than forward renderers do. Just let the players choose the effects and resolution they want, that way it will work on any PC which supports leadwerks. Turning down the screen resolution has the biggest impact.

I know someone who strafes with left and right mouse button and shoots with W

3DCoat is definately worth every single cent!

Well...now i'm the one standing in the corner

Dunno if i got you right, but the .sbx file is just plain text. You should be able to read out any information, without running the engine??

I also had trouble with CEGUI at the beginning. The problem was that the folder the CEGUI SDK provides is called "looknfeel", but in Laurens code it says "looknfeels". Hope that helps!

Try setting it to something lower and check if the problem occurs again. Then you know if it's the newton world size, or some kind of bug.

What you describe sounds like your vehicle is reaching the end of the newton world. Normally it is 500m in each direction (from Position 0,0,0). Try SetWorldSize(Vec3(1000)) or even a bigger value.

The LE vehicle stuff is realized using Newton joints. But that is the side of it you won't see. You just have the vehicle commands to build your vehicle. There is no possibility to give your tires mass, BUT you can use any body commands on the vehicle body itself. You can "simulate" the wheel mass by adding a constant force (equivalent to the wheel mass) to your vehicle body. In a similar fashion you can also add air resistance, depending on the vehicle speed. Hope that helps a bit =)

I would like to have some better structured shader code, where i can change things myself without being a maths genius. Actually the current shaders are ok, but the total lack of comments is a bad thing. =)

When you want to have an airplane/spaceship which is physically interactive you should have look at CalcBodyVelocity() and SetBodyVelocity(). Same for CalcBodyOmega() and SetBodyOmega(). What i tried was: Load a ship/airplane. (Ship) Create a pivot. (Piv) Every loop: // Reset the pivot position SetEntityMatrix(Piv, GetEntityMatrix(Ship)); //Move the pivot around (user input / AI) MoveEntity(Piv, SomeUserInputVector); // Calculate the ships velocity TVec3 Vec3Velocity = CalcBodyVelocity (Ship, EntityPosition (Piv, 0), 1.0f); SetBodyVelocity (Ship, Vec3Velocity, 0); // Calculate the ships angular velocity TVec3 Vec3Omega = CalcBodyOmega (Ship, EntityRotation (Piv, 0), 1.0f); SetBodyOmega (Ship, Vec3Omega, 0); That way any projectile hitting your ship will automatically affect it via physics (with zero programming)

I won't use it because i dislike Java, but "Yes, in the ideology that LE has all common languages"

Im' afraid you can't do this at all. At least not with the current version of Framework. The thing is, that the DOF shader is running after the skybox and everything else is rendered into a texture. There is no way the shader can distinguish between the skybox/background and distant mountains/models. I might be wrong, as i'm not using the latest framework...let's hope

"MyModels_Trees_Tree1.gmf" will show up in the editor as the folder "MyModels" with the subfolder "Trees" with "Tree1" in it.

I have not yet tried animation in LE, but i know DarkBasic...believe me, this engine is MUCH better So you have a very good chance that it will work

I suggest saving 4 times an hour and with an ever increasing number on the back. Test_1, Test_2, ... Also don't forget doing daily backups to at least 2 independent external HD's (if it's really important stuff).

Of course you can get the light using C++. Just give it a name in the editor and search for that name in your C++ program. As Rick mentioned, you will not see your light disabled in the editor, when using C++.

Sounds like you call AddBodyForce() every loop? If it's the case, then the problem is clear. AddBodyForce() applys the force to the force the body already has. It will get faster and faster over time. Edit: Check the CalcBodyVelocity command.

For the trigger, HideEntity() will disable any collisions with it and therefore the collision callback will not be called. You could also set the EntityType to some value that is not used in you game. Both examples require you to set up the collision callback and check in there, what collided with your trigger.

Glad it worked for you

Use the following lua script for you ball: require("scripts/class") local class=CreateClass(...) function class:CreateObject(model) local object=self.super:CreateObject(model) model:SetElasticity(3.0) end The documentation says that only values from 0.0 to 1.0 can be passed to SetElasticity, but anything below 1.0 will not make the ball bounce nicely.

Kevin is right!