[Shadow offset]

Hmm, that makes sense. Adding a "roof" solved the issue. Thanks!

[Shadow offset]

Hi everyone, I'm currently working on a scene with a lot of geometry intersections and stumbled across the issue of shadow offsets and then other shadow issues if it's set too low. Do I have to live with either the offsets (because they look like **** and sort of ruin the scene) or the shadow artifacts occuring with small shadow offset or is there a way to work around that?

 

[Deus Vult - A historical RPG with elements of RTS and first person combat]

Thanks guys! It's true that this test scene looks rather brown, but that's due to the lighting settings. Generally, we try to have a balanced and varied color palette for the game. Here's a shot of the same scene at noon, to demonstrate what I mean:

 

[Deus Vult - A historical RPG with elements of RTS and first person combat]

 

DEUS VULT

 

 

 

 

Hello Leadwerks community,

 

it took a rather long while but after many setbacks we have decided to show what has happened in the development of Deus Vult so far. Most people don't know the project yet, so here's a little introduction: Deus Vult is, essentially, a strategy game with role playing elements (or vice versa, depending on how it is played). In short, you can think of it as a mix between Mount&Blade and the Total War series. The player will be able to control his character in 3D combat while being able to give orders and arrange battle plans. However, most tactical decisions will need to be made before the battle. Only rudimentary changes are possible during the fighting because the combat itself is going to be the core of the gameplay. Beside the battlefields the game will play out on a turn based strategy map, where the player will be able to travel, plan his military campaigns and manage his fiefs. Set during the third crusade, we aim for a historical and realistic, but at the same time entertaining, playing experience. This is only a short overview, we have pages and pages of design documents and if you have any further questions about the gameplay, we will be happy to give you a more detailed answer.

 

We are, currently, a team of six: A project leader (who also takes care of animations), two 2D/3D artists (I'm one of them), a designer/writer (who has been part of the team that developed Mount&Blade and who has published several books), a composer and a programmer (with a master degree in game design). As a programming language we chose C#.

 

 

---

 

 

Download link (current release build)

• No gameplay yet
  
• Still rather unpolished, known bugs include buggy SSAO edge recognition, AA is not working and no proper animations for strafing and walking backwards
  
• Simply extract the .zip file and run Deus Vult.exe in the folder, you might have to click on the main window to have it start properly
  

 

 

 

Screenshots of the release build:

 

 

 

 

 

 

 

---

 

 

 

We are always looking for dedicated new team members, especially programmers (C#); comments, criticism and questions appreciated

[The Ocean thread (the new one)]

It should be a lot more opaque and maybe have a detail normal map for smaller ripples, because I think right now the water looks a bit too plain.

[Normal Maps Baked In Blender Are Inverted]

What version do you use? I don't see any "Best Quality" option while baking. Anyway, bake mode should obviously be "Normals", Normal Space should be Tangent and Edge splitting doesn't matter too much. Make sure you tick selected to active and select the high poly version first and then the low poly model. Using 2.6 with those settings works perfectly fine for me.

[Terrain Layer Blend]

Figured out my problem, thanks to klepto2's scene loader code.

[Terrain Layer Blend]

Been having some problems loading the terrain manually.

 

 

In some areas the layer blend well, where as other areas not at all.

 

For each layer I set the following values.

 

Texture

Bumpmap

Scale

Rotation

TerrainLayerMappingMode

Color

Blend

TextureConstraints

 

Am I missing something?

[Light Issue]

I see. I tested my material on the standard LE hands and it does work just fine, so the model is apparently the problem here... Getting art assets into the game is just so difficult with Leadwerks...

 

Thanks for your help so far, but I really don't have a clue what could cause that sort of problem with the model. Does anybody have an idea?

[Light Issue]

I do and it doesn't work okay If I drop the specular in the pixel shader only the diffuse map works. Did anyone ever have an animated character working with both specular and normal mapping?

[Light Issue]

With what shaders did you get the bumpmapping to work then?

[Light Issue]

A somewhat related question... When I use the exact same shader setup for a skinned character, I can only get the specular mapping to work. If I add "bumpmap" either in the pixel or vertex shader I don't get any normal mapping and if I add it to both shaders there's only a dark diffuse texture (similar to what gamecreator describes).

 

Here's my material file:

 

texture0="abstract::surcoat.dds"
texture1="abstract::surcoat_nrm.dds"
gloss=0.1
shader="abstract::mesh_skin_diffuse.vert","abstract::mesh_diffuse_bumpmap_specular.frag"
shadowshader="abstract::mesh_shadow_skin.vert",""

 

Any clues?

[Light Issue]

Wouldn't you need a second texture for having specular and normal mapping anyway?

[Material Bloom ?]

That looks pretty good! And you're right, that definitely gets rid of the cheesy look bloom usually has.

[Why should we avoid tree branches made out of intersecting cylinders?]

Even though you said you haven't seen any visual artifacts, having the branches intersect with the trunk usually results in awkward lighting, i. e. the shading often creates a sharp looking edge at the intersection. Depending on the type of tree that might be rather irrelevant (like a palm for example), but it can look really bad on major branches on broadleaf trees. For smaller branches and especially LOD models it usually doesn't matter that much, though.

[Projects Database]

I agree with what Scott and paramecij said. This community is relatively small so splitting interaction further up wouldn't do much good. You even said so yourself when you decided to merge the programming forums. I think a project database would be a good way to show what can be done with Leadwerks. However, I would keep the project descriptions brief and as far as media is concerned only have a few pictures and one or two videos per project. As all of those projects would have their own site, a blog or at least a thread in the showcase forum, there is a way to provide more information for those interested with a single click. This allows for a quick overview while still giving projects a chance to present themselves well.

On the topic of this being more useful for Leadwerks or the developers: While giving us indie devs another opportunity to present themselves is basically a good thing, I think the main purpose of this should be to make Leadwerks more attractive and to give the company and this community more attention. After all, getting more people to buy and use Leadwerks would be beneficial for everyone here.

[Texture lights using normals]

Not sure if this helps: http://blog.wolfire.com/2009/06/how-to-project-decals/

[Key Stuck]

Thanks for the info.

[Key Stuck]

Hi,

 

Been having problems with the KeyDown function.

When multiple keys are simultaneously held down and released, KeyDown will occasionally still return one of the keys as being held down.

Any one else come across this problem?

[Trouble importing skinned meshes - Arbuz & FBX2GMF]

Thanks a lot. Just after I posted this, I figured out that exporting only a single selected (skinned) object will cause the faces to have the proper normals (not inverted). Specifying the correct material apparently fixes the issue with the colorization.

 

I'll try to use your advice with the FBX exporter!

[Trouble importing skinned meshes - Arbuz & FBX2GMF]

Hi guys,

 

I've got a couple of problems with getting functional .gmf meshes in-game.

 

I'm using 3DS Max with the Arbuz exporter. Whenever I export a skinned mesh, it ends up corrupted (see attachment). I've tried at least a dozen different combinations of checkboxes and scene setup, but it just doesn't work when exporting skins. However, when I untick the skins checkbox, they turn out just fine.

 

The same happens when taking a skinned fbx file through the fbx2gmf exporter.

 

Anybody have similar experiences, or know what the problem might be?

 

Thanks.

[Debugging Leadwerks with C#]

Thanks, man!

As I'm recompiling the DLL myself anyway (need to add a lot of stuff that's been not implemented previously) that's a great addition!

 

[EDIT]

 

Hm, unfortunately that doesn't seem to make any difference except for scene loading being a lot slower. Still no output either in VS or in the console.

[Debugging Leadwerks with C#]

Hm, even if the output is intercepted by VS, shouldn't it be output at least somewhere? I can see it neither in the Output window, nor the Immediate, etc.

[Need c# Wrapper]

Rekindled Phoenix has been so kind as to set up a new SVN repo for Leadwerks.Net:

 

http://www.leadwerks.com/werkspace/topic/3300-leadwerksnet-wrapper/

[Awesomium in C#]

Hm, okay, so basically you're doing the same thing I originally intended to do to handle input events - that is, polling each key each Update().

Idk if that's such a good idea performance-wise. I read up a lot on the message loop of windows and thought that might've been a better solution, but if you think there's no huge trade-off in performance, that's fine.