[Injury]

Take your time to rest and hurry up to get well soon

[Data]

Reading/writing text and binary files seems very easy in LUA:

http://www.lua.org/pil/21.2.html

[per item gravity]

In space you should set the world gravity to 0/0/0. Then you make a AddBodyForce loop around each planet, so they will drag objects towards them.

[Entity Type]

That's where the wiki comes in handy: http://www.leadwerks.com/wiki/index.php?title=Collision#Collisions

Actually LE doesn't have other collidable collisions than sliding collision, probably because the behaviour is then handled by physics settings (BodyFriction, BodyBounciness, etc...), I remembered it from Blitz3D which has no physics and needs to simulate that behaviour via the Collisions command. Also the recursiveness is set with EntityType.

[Entity Type]

The actual number of EntityType doesn't have a predefined meaning, it's just a number you use in combination with the Collisions() command to define which EntityTypes should collide with which EntityTypes and how (sliding, stopping, informational) and how deep (recursively all childs or just the body in question).

 

In addition you can also use the SetCollisionCallback() command to add automated program code which is executed when a collision of specifed EntityTypes happens. For example, in addition to the normal sliding collision of a rock on a slope, it would also emit a rumbling sound, and why not also some dust particles.

[Quick Q on Roads]

You don't need those lines at all, since UpdateFramework() does the same thing.

It could be also something else, like missing models or scripts.

[Quick Q on Roads]

Yes, but those lines:

        UpdateAppTime();
       UpdateWorld(AppSpeed());

might mess things a bit up.

[Quick Q on Roads]

GameLib itself is ready today (almost got it ready yesterday already), but Josh needs to update a few C/C++ files (which I sent him yesterday also) since they were missing the commands for fog range setting.

[Physics after update]

It sounds like you didn't update newton.dll in your game folder.

[Core Lua]

Those are made by code in Editor.exe.

[head shot]

It would be too much code to paste here, but the principle is that you check what was the name of the mesh which was hit with EntityPick().

[Physics after update]

Could be many reasons, for example that your Character Controller has a too big mass. Better post some short example.

[Quick Q on Roads]

You have to use the integrated framework in C++, not the Framewerk C++. Or just wait until I get GameLib 0.0.16.0 ready, then you don't have to change anything in your game code.

[LE Updater]

That's just a lot of wasted time. You would have to check each new file also, and implement the new changes to your changed files. With seperate filenames you don't have to do anything.

[Quick Q on Roads]

Yes, LoadScene() loads also roads.

[LE Updater]

You should make your own improments in different files than the original files. For example the PointLight2 I made.

[More than one target for an AI node]

You can also press the number keys to select the index before creating the link.

[Customizing 3D World Studio]

Basically you can "customize" 3DWS by adding your own custom entity keys to objects. Then you just make your code to recognize those custom entity keys, but there's no way to make 3DWS recognize them (other than just having them as keys and/or as entities with those keys prepopulated).

 

Instead of always manually adding all custom entity keys, you can also add your custom entities to the entities.def file at the end, for example if you want to add a weapon to 3DWS, you could add this:

@pointclass Weapon : "sprites\weapon"
[
firepower : 100
range : 200
delay : 10
]

[Leadwerks Community GameLib]

I started to work on gamelib 0.0.16.0. This is getting interesting... Framewerk C++ source has been removed, and LEO (which has Framework C++ classes) has been added

I think it will be ready today, as it's not too much to change, when done this way.

 

Actually there shouldn't be anything to change, if LEO's Framework works the same way as the Framewerk C++ did, which is again a good thing, because then GameLib keeps it promise that customers don't need to change their code when the engine changes and they use GameLib. That's the idea of ROI.

[Leadwerks Community GameLib]

You can't do that, since it needs the integrated framework. But I'm looking today how to get the integrated framework to work with gamelib 0.0.16.0.

[Leadwerks Community GameLib]

I'm not sure, at least it was still there when I didn't delete the old entity created with Sandbox. I guess there are still many people who have old entities in their Editor maps, since they didn't recreate all entities with Editor, so I have to make sure that gamelib supports both Sandbox and Editor sbx, even if they are mixed in the same sbx file (which is obviously quite common).

[Leadwerks Community GameLib]

The missing classname for directional light is indeed the reason:

Model {
path="light_directional.gmf"
position=-20.9827633,131.497437,2.42692709
rotation=55.0000496,0.000000000,0.000000000
scale=0.999997675,0.999998093,0.999998093
id=76090920
"class"="Model"
"intensity"="0.5"
"name"="directional_4"
}

But I can fix that in gamelib, to make it look if the "name" key begins with "directional", as I've done for ambient light in 2.3 also.

 

Line 1491 in gamelib.cpp would then look instead of:

if(uselua!=2)if(cn=="light_directional")

somehow like this (I need to test it first):

if(uselua!=2)if((cn=="light_directional")||((en.compare(0,11,"directional")==0))

[Leadwerks Community GameLib]

It worked fine the last time I tried it (2009-12-30), but from what I understood there was some update over new year which apparently broke something. I need to check if I get the same problem, now that I'm back from the new year trip.

[Leadwerks Community GameLib]

Yes, that's exactly why I need to do for the gamelib versions of the LUA scripts. In additition I also need to add some missing light settings, like shadowsoftness, additional lightmap sizes, and a bigger lightrange slider. Those things should be in my opinion in the default engine, but they are not.

[Framwerk compile warnings]

Ok, I found the reason why Roland gets those warnings. He is using Framewerk directly, and not via gamelib. When I tried to make a new project which had the Framewerk files directly included as source, then I got those warnings too.

 

I'll fix those warnings and send Josh the updated files.

EDIT: Sent new renderer.cpp to Josh