Irrlicht Engine

SourceForge problems started almost two weeks ago. I hope it all gets resolved soon!

In short :

FlatBuffers: less code size, less execution overhead, more memory usage.
ProtocolBuffers: more code size, more execution overhead, less memory usage.

So the choice all depends on the application.

mant wrote:I would use FlatBuffers instead of ProtocolBuffers.

Would you care to elaborate? Why would you choose FlatBuffers over ProtocolBuffers?

And if you look at the code in OculusRenderer and main, does it help you?

I don't have an Oculus here, nor I ever tried to use it's SDK, but I feel that the files in this repo are a great base on which to build from.

Searching the forums, I found this GitHub repo in this post (which is quite interesting in itself). Have you checked that?

Just a quick hint, but SEGV_MAPERR means that you tried to access memory that's not mapped to your program's address space. That's usually because :
- You dereference a null pointer ;
- You try to free the same memory twice ;
- A pointer was corrupted ;
- There's a buffer overflow in your program.

I myself usually compile the standard libraries statically. The executable grows, but it's a small price to pay for the program to be self contained.

Classic case of rubber duck effect.

Hum, the problem seems to happen inside Irrlicht.dll...

Try Christian Clavet's solution in the post you linked and see if it fixes the problem.

Are you sure you're linking with the same library version as the source files?

That could indeed have been the problem, because the '\' character is used for the C/C++ escape sequence to represent special characters. More on that here and here . Now, back to your problem... What is the rest of the 0xC0000005 error? Is it a read of write access violation? Can you paste the call...

The first parameter of the addLightSceneNode is the parent node of the new node. By setting the parent node to 0, you're creating your light at the root node of the scene graph. Just to be sure... Do you want the light to follow the model, or do you want the light to follow the camera? Note that if ...

Not sure that it's actually the culprit, but in your screenshot , you seem to have forgotten to escape the '\' character in your path. Try this :   IAnimatedMesh* mesh = smgr->getMesh("B:\\SDK\\irrlicht-1.8.4\\irrlicht-1.8.4\\media\\sydney.md2");   If that doesn't fix it, try to put a brea...

Ambiguous doesn't mean you can't. It's just that the compiler found (possibly) multiple declarations of IGUIImage, or it doesn't know from which namespace your IGUIImage (or ITexture) comes from. Try adding the namespace first :   class irr::gui::IGUIImage; class irr::video::ITexture;   Don't forget...

Here's the pyirrlicht project page : https://sourceforge.net/projects/pir/

That hasn't been updated for a long time (3 years), but you can still try to reach the authors. Maybe they kept a backup. Maxim Kosolov's profile page can be found here.

Good luck!

You might want to look at how GIFLIB does this.

Check the function DGifGetPrefixChar.