Irrlicht 1.2 D3D fix

dwmitch · Post by **dwmitch** » Sun Apr 08, 2007 2:37 am

I know I'm late on this, but I never could get 1.2 to work, my VS dll is corrupt, and I can't download 1.3.

I've searched the forums and haven't got a clue about how to fix the D3D problems in 1.2. In one thread it seems that it will only create a 24 bit driver, another one said that it will work with 24 and 32 bit colordepths, but 32 bit fails on my system, even though everything else will run at 32 bits.

I've looked over the source files and the D3D related files from 1.2 look the exact same as 1.1. What file is the problem in so I can correct it and recompile?

omar shaaban · Post by **omar shaaban** » Sun Apr 08, 2007 9:19 am

what is the error or the problem!?

omaremad · Post by **omaremad** » Sun Apr 08, 2007 1:23 pm

Most ATI cards operate at 24 bits (as musch colours as your eyes can see) but nvidia still perfers 32bit for shading accuracy.

Maybe other app have a fallback option and quitely switch to 24bits while irrlicht keep trying till it fails.

hybrid · Post by **hybrid** » Sun Apr 08, 2007 7:00 pm

You have to update the CIrrDeviceWin32 as well, but it might be easier to switch to 1.3 directly.
However, to really get some help you should describe the symptoms of your problem, not what you think might be the reason of the problem. That's what Omar tired to tell you.

dwmitch · Post by **dwmitch** » Mon Apr 09, 2007 12:55 am

hybrid wrote:You have to update the CIrrDeviceWin32 as well, but it might be easier to switch to 1.3 directly.
However, to really get some help you should describe the symptoms of your problem, not what you think might be the reason of the problem. That's what Omar tired to tell you.

Really the only symptom is that the 1.2 demos crash when using D3D drivers. I can't remember what the popup says, as I'm not on my computer, but the console window says "failed to create device" or something to that effect.

It's the same problem everyone complained about when 1.2 was first released, but none of those posts contained solutions and my forum searches didn't even bring up those posts.

1.3 won't be an option until I get DSL or the development team starts releasing the libraries, DLLs, source code, and examples as seperate downloads. Really all I need is the VS dll, as it's the only one that's corrupt but also the only one I can use.

hybrid · Post by **hybrid** » Mon Apr 09, 2007 10:54 pm

Try to use SVN. It downloads the sources and media only, no binaries. And you can resume failed downloads as all files are fetched separately.
The problem with 1.2 was that it did not use 16bit depth. That's why the window creation should be checked. However, I do not remember anymore when I fixed this stuff.

dwmitch · Post by **dwmitch** » Tue Apr 10, 2007 1:09 am

hybrid wrote:Try to use SVN. It downloads the sources and media only, no binaries. And you can resume failed downloads as all files are fetched separately.
The problem with 1.2 was that it did not use 16bit depth. That's why the window creation should be checked. However, I do not remember anymore when I fixed this stuff.

I've never been too clear on what SVN is. Is it a sourceforge specific download manager? If it is, does it require access to the registry or could I put it on a flash drive and use it? If not, how do I access it?

hybrid · Post by **hybrid** » Tue Apr 10, 2007 11:08 am

Please read the bug forum entry on SVN, or google it. It's a versioning system which allows for concurrent access to a data repository (which is in fact often a code repository).