Irrlicht Engine

Thanks will look into that

Alright, I had some time and I got a chance to download the current SVN trunk. Here are the list of changes I made to get it to build under bcc:


// bcc has macro expansion problems. See my list from earlier post
aesopt.h
line 850-851
- #define d_1(t,n,b,v) const t n[256] = { b(v##0) }
- #define d ...

Hi,

I also recently downloaded irrlicht to play around with it again. I made quite a few modifications to get it to build under free bcc5.5.1. I was wondering if these changes can be incorporated into the svn so that future releases can build with borland compilers?

Here's a list of documented ...

Just thought I'd do one more follow-up for my thread to bring this to a conclusion. I have finally resolved all of the visible crash issues.

The root cause of all these crashes, as it turns out, is because specifically borland compilers have floating point exceptions turned on when linking with ...

Thank you, I wasn't aware of that.

Ok, I got a little further in my attempts. After looking at the irrlichtdevice class, it turns out it also inherits from the IRefcount class. What I didn't realize was that IRefcount isn't really an abtract interface class -- it contains an actual implementation ...

I believe someone already has, at least for the borland compiler. A search for borland turns up ecopter and someone else on this forum who did the needed changes so that irrlicht will build properly with the bcc compiler.

Unfortunately this is not activately maintained with the main build. The ...

Hi everyone,

I'm trying to use the precompiled dll's that comes with the irrlicht SDK, either the msvc dll or gcc dll and trying to get it to work under borland's 5.5 free compiler. I'm trying to see if dll interoperability is possible when mixing different development tools. This isn't just for ...

ok I see the latest version of irrlicht has the water transparently fixed but the fog issue is still yet unresolved. Why is it taking so long to get this right?

*bump* still waiting for an answer

I don't understand, why are these two problems being ignored by everyone? How come the author hasn't done anything to fix these two problem?

hate to bring this thread back up but I notice that in the latest irrlicht 0.10 release this still isn't fixed. Any idea what the heck is going on?

Thanks!

I have one question about all this dx vs ogl debate.

If opengl is suppose to be on par with that of dx in terms of feature and performance than why is it that the ogl component of irrlicht is so incomplete compared to that of directx? I'm not prefering one over the other but this was something ...

Any idea on whether the upcoming irrlicht 0.10 will have these two problems corrected?

Thanks

I have a fix for this that works with 0.8. I would happy to port it over to 0.9 and submit it to Niko, but I would like to hear if maybe he has already been working on it himself.


Can you post your solution in bug forum?

I have this problem only with Irr08 and Irr09

I would like that as well ...

ahh sorry about the screenshots not showing. I use firefox myself too and it seems if you use a proxy for this web browser then it shows properly. Otherwise you do get that 'hosted by angelfire' image. By default I'm using a program called proxomitron with firefox so that's why it shows properly for ...