Irrlicht Engine

Don't see why it should be so difficult, at the moment every time the player changes his view resolution he needs to reset the game... very inefficient.

Anyone know how to change the main FB resolution in DX mode without resetting and reloading meshes and textures?

Exactly, it would take me weeks to update 1.8.3 with my additions/changes, and that's if I didn't have any complications with the newer release. The COctree node in 1.8.3 has additional external functions and variables that don't exist in 1.7.3, and the 1.7.3 version in it is buggy when enabling har...

yes, these things are ..painfully complicated! :) take a look at their 30MB video, there is a model of a woman in a spanish-style dress, as the woman moves, the dress flys around her, it looks absolutely real, gravity and momentum of the material looks perfect. One life is too short for doing that s...

Yes. I guess there is no easy solution.

Have you seen this idea, its really neat, a "cloth" mesh falling into a vase where the code detects the vase edge and deforms the cloth in real-time, running on the GPU.

http://gamma.cs.unc.edu/CSTREAMS/

Found the link here: http://www.michaelzeilfelder.de/irrlicht.htm#Models

What's useful is that it also creates the triangle selector list.

Thanks for the link, interesting project.

They are using 1.8.2. though...

Someone had a new Octree class that handled the triangle hit list in a much more efficient manner, thought it was on one of the irrlicht admin's website, but can't remember which...

Anyone know if there is an improved version of COctreeSceneNode compatible with 1.7.3?

I´ve activated hardware buufers and there is a problem with clean-up on LighMapMeshes.

Thought I saw someone had posted an improved version of their website but can't remember where that was.

Thanks.

Strange that this information can't easily be found on the web, makes programming much more trial and error than it should be, but that's computers for ya!

Well, W is definitely not 1 in the vertex shader on my Windows 10 PCs with nvidia and another with amd drivers, that's for sure!

"W is generally not 1." - generally, is that like sometimes?

Did you find any exact references on this topic for modern GPUs under HLSL 3.0 ?

FOrgot to mention, that dividing by .w resulted in a very dark gray scale range, so:- Out.Depth.x = 1.0 - (Out.Position.z/farDepth); // farDepth same as camera far depth float This produces a grayscale from white (at camera) to black (at far point). So what value is stored in .w, and how should it b...

For depth calculation, used for fish collision avoidance. I´ve been trying to find an HLSL reference that gives a good overviews of these values, .z range from -1 to +1, and how .w is calculated, but so far haven't found much. depth = (z/w - near)/(far - near) sounds interesting, the near and far va...

Thanks Mongoose7! Sometimes I go code-blind, you know, staring at the same thing so much I miss the obvious! :D Using Out.Depth = (Out.Position.z * Out.Position.w) / canFarZ; Where camFazZ was the depth-camera's far depth, caused incorrect assignment of depth to some objects, but results in a very n...

Thanks, I totally missed that!! This is code from another example, where the divide is made as you mention. VS_SHADOW_OUTPUT RenderShadowMapVS(float4 vPos: POSITION) {     VS_SHADOW_OUTPUT Out;     Out.Position = GetPositionFromLight(vPos);     // Depth is Z/W.  This is returned by the pixel shader....

All looks okay, standard proj * view * world. In the vertex shader for depth, I used Out.Depth = (Out.Position.z * Out.Position.w) / canFarZ; Render that in the pixel shader in r g and b for gray scale. Anyone any idea what might cause scaled objects to result in a reduced Out.Depth value, although ...