DirectX 9 Stopped working

greetings H&K   my first thought, be sure you do not have any older Irrlicht.DLL files in your path that may be getting accessed before the newest one.

i did a couple of new things with this build.  i built using codeblocks as opposed to DevCPP.  im also using the OCT 2006 DX SDK directly as opposed to the devpaks version.  have you updated your DX lately?  both DX are working fine on my 3 machines.  if updating doesnt work for you (or you would like not to update) i will try and get an OCT 2005 DX SDK built and see if that helps.

given the error thats occurring, it seems like a mismatched DLL.  if you didnt have the correct DX version with the correct Irrlicht DLL you would get an error saying something like D3DX9_xx.dll not found.   another thing you can try is to rename the XXab.dll file.  if that is missing and the newest Irrlicht DLL is being used you should get an error the ab.DLL cant be found at runtime.

  please take a peek in your windows system32 dir.  you should see files named something like d3dx9_xx.dll, ie d3dx9_24.dll, d3dx9_25.dll, ... d3dx9_31.dll.  do you have any of those and if so, whats the largest one?

thx.

thx for doing that.  very interesting because while i was waiting i was installing the DX runtime on my ME box.  it also has a SiS video card and it also still failed.  did you happen to try a demo EXE and DLLs on your main PC?

in the meantime, im working on building via DevCPP for this one.  we'll see if that helps.

thx for your patience on this.

unfortunately i have to hit the sack.  we shall pick this up again tomorrow!  have a good evening... or whatever is appropriate for the time there

OK, did a total reinstal of everything, (Including Clean instal of Bmax 1.18 and removing MinGW as enviroment variable),  no Joy, niether of the dll builds work in dx9 or 8.

On my main machine everything works perfectly. I would conclude that its a problem with Irrlicht itself (ie not your mod) and SIS chips (or shared memory, which gets my vote).

Not a major hasstle as sis chips are rubbish, you need to find someone with a ati/nvidia chip with shared memory as see if they have the same problem.

I quite happy to be useing just opengl on the laptop, (Well not happy, but it still works), as it is when said and done just a development pc, and well under speced.

Thaks for the effort youve put in.

(Re version redownloaded both the 1.24 upgrade and your 12/19  today). oh and as to time, my last post last night was at 5am

I had tried al that already, having had experiances before where the windows settings messed with devolopment settings, but no joy. I changed all your examples to and from full screen and tried them all in both 16bit and 32bit win depths.

I do notice from that link that in 1.2 16bit has been dropped, but maybe I missunderstood.

Anyway I think that that blokes problem was a lack of memory in his card. A MX 440, whats that have 32Meg? or Maybe only 16Meg. His windows screen was simply taking to much memory.

Which leads back to my beleif that its a sharred memory problem.

Thanks mmhnemo.

Its interesting that you are getting an exception about the Cursor, if it happens to me Ill let you know if I find a better solution to the problem.

The problem I am having is a lot sooner in the setup though. What is happening to me, (and only on my Laptop), is that at the actual creation of the device, irrlicht is crashing out. It happens when I try to create a DX9 or DX8 device.

As you see from the link Gman posted someone else has had a similar problem, whereby the device would only create if the desktop was in 16bit mode. In my case DX8 hasnt worked ever, yet now DX9 isnt working.

Its not a major problem, as its only on a rubish Sis chip with shared memory, and it works on my main computer.

I doubt very much that its a problem with Gmans mod, and as you can see he made a special build just for me.

Fortunatly because the command set is the same in all five modes I can continue programming in the knowlege that the final program will probably still work in DX on its target machines.

Hi H&K and GMan

Thanks for answering. I see my problem isn't related to the topic.

I will try to find out what causes the error but so far i am content with whats available ( a little mousecurser in the center of the screen doesn't hurt during development).
The only other thing thats buggy is the q3 map demo which runs but only shows a small portion of the geometry depending on where you look - it seems like it's culling the geometry around the center circle(maybe 200px radius) of the screen.
Might have to do with the camera (fisheye?). I really have no idea.

I have updated DX but not my gfx(ATI X850) driver yet.
If i have some hard facts that warrant a bug report i'll open up a new topic or just keep it in here if H&K doesn't mind

greetings

mmhnemo

@mmhnemo

Hoho.
I installed C++ express and the full irrlicht package, (to see if DX9 failed in c, it does), and guess what?

My Bmax instalation started to give the exact same error as yours that is
device.getCursorControl().setVisible(False) gives unhandled memory error

I was about to do a clean anyway, and didnt think to see which was causeing it, but now that they are both gone, I dont get the error anymore.

So... somthing about the real Irrlicht install or Visual Express is causeing it. (Sorry I cannot be more exact)