[Models based level design]

CSG modeling isn't the best for advanced artists, but it allows those of us who aren't expert modelers to quickly sketch out a map.

[Entity:SetElasticity and Entity:SetSoftness]

Agreed.

[Projected shadow performance (not physics)]

Like I said, it seems rather high.

[Request for shader documentation and concrete question]

I think deferred rendering is much more straightforward and simple. Lighting in forward renderers is always a hack. People complain about transparency lighting problems, but with forward rendering you NEVER have correct lighting.

[terrain self deleting]

I recently fixed a bug where the editor would not show the map as changed after modifying terrain, so unless you saved it your changes would be lost. This has not made it into the current build yet.

[Projected shadow performance (not physics)]

It isn't slow due to physics. It's slow due to the projected shadow rendering. Though that still seems excessive.

[Request for shader documentation and concrete question]

Good idea.

 

FYI:

vec4 color = vec4(entitymatrix[0][3],entitymatrix[1][3],entitymatrix[2][3],entitymatrix[3][3]);

[Projected shadow performance (not physics)]

Will check it out, thanks.

[Deleting Entity with velociy]

It should not matter. It should even be safe to delete them within a collision callback, now.

[Texture position]

It was easy to get it to compile, but all I've got right now is a blue screen, so I am talking to Canonical about the driver situation in 13.10. I have someone else who is going to handle the remaining GTK stuff, which is the real grunt work, but this part is something I have to stay on top of. Also writing the GL4 renderer right now.

[Editor warnings]

This is a very difficult situation because there is no way to detect what vertex attributes exist, and ATI cards on Mac always put out this warning if a non-existent attribute is set.

[Texture position]

I understand this is a feature that will make life easier (and I want it ASAP, too) but there are over 300 Linux users who expect to have Leadwerks running on Ubuntu in December.

[shadows]

I really think that is the answer. That is the command the Map::Load function calls.

[BSP level design]

I love the style. Together with the reusable elements, it provides a consistent theme and allows a non-expert level designer (like me) to create compelling scenes.

[TouchDown]

Thank you. It is possible something is funky here.

[Leadwerks 3 for Windows via wine]

You won't need to use WINE at all, soon enough. I'm building it to run natively on Linux.

[What is Terrain?]

Terrains render a series of repeating patches (for LOD levels) and render the area around the camera dynamically. The height date is stored in a 16-bit luminosity texture so a 4096x4096 terrain can be fit in just 33 mb of memory. If this were a model, the memory usage would be hundreds of megabytes.

 

So the advantages are:

• They render faster.
  
• They use less memory.
  

[Continuous trigger collision]

Yes, this was something I did fairly recently.

[Game Tournament 3: A Machine for Penguins]

Need some inspiration? Here are some physics puzzles from different games:

 

At 9:25 a box is blocking the engine from moving:

 

Turn two wheels to open a door:

http://www.youtube.com/watch?v=awbiL7He-pc

 

At 8:17 the player turns a wheel to move a crane and bridge a gap so they can get across:

 

At 2:00 various gears are assembled to make an engine:

 

Other ideas:

• Turning electricity on and off to make an area passable.
  
• Controlling a crane to move objects around.
  
• Running through a Halloween horror machine and dodging moving spinning blades.
  
• And of course, your own off-the-wall ideas that go beyond this.
  

 

The best approach is probably a simple idea with good execution.

[shadows]

Try Entity::SetShadowMode(Light::Dynamic)

[Continuous trigger collision]

This should occur every single physics update. The trigger will keep the entity awake and keep firing until it stops colliding.

[Terrain not pickable]

Camera picking is a different overload, actually. There is an internal Entity::Pick command used by all the pick routines.

[project manager update]

Are there any messages in the console like saying it failed to copy a specific file?

[Terrain not pickable]

You are correct. Will fix.

[Terrain heightmap loosen 2 :]

Maybe you really only forgot to save manually since the editor does not mark the map-file as changed as soon as you change anything on the terrain. You can see that at the asterisk in the titlebar beside the filename.

That is quite possible...fixed for the next build.