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)

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

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.

I'm having similar problems. Most examples get unhandled memory errors(01 works). I deinstalled, reinstalled etc.
When i comment out this line:

device.getCursorControl().setVisible(False)

many examples start working.

Maybe this could be a hint to you i hope

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.

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

Will install Bmax and stuff tomorrow and look see. This is all my fault, Gforce chip extra £100, so..... do I buy it, no, buy stupid SiS, worse chips since chips were invented. Stuck with computer thats lightening fast at opening Office, but rubish as games machine. (OK so justification for buying it was as portable work machine, but still anoying)

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

thx for your patience on this.