Irrlicht Engine

Here's what I would do:

1. We're dealing with .obj files so in order to make the corresponding .mtl files to work (also include the texture files), I would put them all in a .zip file on the server.

2. Then I would have the server read the .zip file (IMPORTANT: Make sure it reads in binary mode ...

Well, first of all you probably should use time-steps so your movements aren't frame dependent. (Just multiply all your speeds for moving/rotation etc with how long it took to loop through one frame in seconds using the irrlichtdevice->getTimer()->getTime(), in case you didn't know that). This ...

I don't know about the source code for that demo, but here's what you can do:

1. Create a meta triangle selector.
IMetaTriangleSelector* tri_sel = smgr->createMetaTriangleSelector();


2. Get all the triangle selectors for each model and attach them to the node.
ITriangleSelector* sel1 = smgr ...

Here's how I would do it.

//First get the position and rotation.
vector3df opos = mynode->getAbsolutePosition();
vector3df orot = mynode->getRotation();

//Now apply translation/rotation.
float movement_speed = 1 * time_step; //time_step is the time since the last frame in seconds.
float turning ...

Here's an example code of how I would do it (tested and working):

#include <iostream>
#include <irrlicht.h>
#include <cstdlib>

using namespace std;
using namespace irr;
using namespace core;
using namespace scene;
using namespace video;
using namespace io;
using namespace gui;

int main ...

...Perhaps it's because I somehow changed the f32 variable declaration before the above mentioned lines to s32. Will report back if it fixes anything. I once again have to wait until I get to the computer.

I keep getting the error "HLSL vertex shader compilation failed." in the console. You say it fixes it for OpenGL at least. Does this fix not work with DirectX 9?

mikkis wrote:In EffectCB.h line 91, 94, 97, 100. These four f32 change to s32. Then opengl works right for me, at least.

Thank you! I will be sure to try it when I get access to one of the "faulty" computers, Monday.

As moongose7 said you must send s32 uniforms instead of f32 for texture uniforms eg:
f32 TextureID = 0.f; // BAD
services->setVertexShaderConstant("SamplerName", &TextureID, 1); // BAD
-------------------------------------------------
s32 TextureID = 0; // GOOD
services->setVertexShaderConstant ...

The only thing I could find was to change EffectCB.h, line 90 from irr::u32 TexVar = 0; to irr::f32 TexVar = 0;, thus preventing a int to float typecast failure... or at least that's what I understand. As of now, I have no idea if this will fix it, as I won't have access to this kind of computer ...

Nadro wrote:Orginal XEffects uses float interface for send texture id uniforms. Use int interface and all should works fine.

Uh... this is somewhat embarrassing, but I am not much of a graphics programmer. I may need a little more guidance to try this. I don't even know where to begin.

It is unlikely to be the graphics card. Are you running the same executable on both systems? Have you fixed XEffects for Irrlicht 1.8?

Yep, exact same .exe.

I don't know what you mean by "fixed". It works perfectly fine on all the computers I've tested with graphics cards, and not at all on the ...

So I'm using the XEffects library for lighting and shadows and I have strange issue. On certain computers, on the effectmanager->update(), all I get is a black screen. I am using DirectX 9 as my driver. Here are the specs of the computer that causes this:

------------------
System Information ...

I realize this is an old bug, but it's something that REALLY needs fixing. Until I found this thread, this bug caused me a LOT of grief and frustration, therefore I worry for others that may also encounter this bug.

Actually, Irrlicht uses a left-handed coord system as well. And in case you still have to convert: You can switch from right-handed to left.handed by negating any one coord, so you have to check the exact coord orientation. Irrlicht has y-up, which gives z-axis into the screen. So check where your ...