Grrrmachine

Ive also found that if I make a configuration file with the Ninja I get a screenshot of what it SHOULD look like in MDXC. If I save it and then immediately reload it, the grey button graphic where the read data should be has turned into a pure white square. Is this related? Has anyone else suffered this too? Im 24 hours in and not even on Step One yet And this is testing with two Brains and two sensors.

If I tell the configurator I have a Virtual Brain then I get that to display in all its glory in MDX, although I still get a blank screen in the MDX main window.

MP3Car.com

 

2k1Toaster

Wait wait...

If you use a Virtual Brain it works, if you dont it doesnt work? Screenshots? The 2 parts on non-related at all. Completely seperate. Only time it would error is if it is erroring all the back at config time.

__________________

Grrrmachine

No, if I use a Virtual Brain I get the virtual brain window that allows me to inject values, but either way (virtual or real) the MAIN MDX window remains blank, white, empty, like the last screenshot I gave.
It suggests the main MDX application is running: it knows I want to use the brain, but its just not finding the graphic files it needs, even though there's a valid Content folder for the configuration file.

greenman100

do you have access to a different computer you can try it on?

Grrrmachine

Yeah, I'll try the virtual and real system on a clean laptop I have, but it'll mean downloading the ultimate package (286mb) which will take a while.

So whilst I do that, is there any way a previous installation of MDX is corrupting things? I can't believe its my graphics driver as everything else on this system works fine. Any other dependencies I ought to update?

Grrrmachine

OK, so a clean laptop with not much on it self-downloaded all the dependancies (the .NET versions and DirectX) and MDX worked fine, which means there's something on this system conflicting with MDX. Im uninstalling all the .NET stuff and putting it back on to see if any of that is corrupt, but any other ideas of what might affect the Uber software would be appreciated.

I love these little boards though I still have so many cool ideas of what to do with them.

Grrrmachine

And this is where Im stuck on the main system. New DirectX, new .NET, new Uber MDX, and a very basic configuration, and the MDX software gives me this:



That's it reading data from a real Brain with a temp sensor connected. No idea why no graphics are showing.

2k1Toaster

Do you have 4 or 5 dll's in your MDX folder that have the phrase "DirectX"?

Can you use the updater and get it to refresh all good files. A previous version has older dlls and such, could be conflicting if it is a new exe and old dlls.

I would delete the entire Fusion Control Centre folder in your Program files, saving your skin if you have made one. Open up the registry editor, (start-->run-->regedit), then hkey_local_machine/software/ and delete the fusion control entry.

Restart.

Download the installer (a new one, not what you have, it is only 8Mb). Then Run it, and restart. Then try. That should be fresh

__________________

MP3Car.com

 

Grrrmachine

Deleted the folder and registry entries, redownloaded. This time it downloaded DIrectX 9.0c November 2007 (although I had the August 2008 edition already.) Tried to load a virtual brain, same story - blank MDX screen, no info. Used the v4 updater, which added some files, and still no joy.

And I only have 4 DirectX dll's in the MDX folder - DirectX, Direct3D, Direct3DX and DirectInput. Should there be five?

Grrrmachine

It's a directX problem! I turned off Hardware Acceleration on my graphics card (an old Geforce 4) and now when I load MDX I get the default blue screen, white text, grey button background, everything!

WHY this problem occured, I can only blame DirectX, but I'll let this stand in case others come across the same problem.

EDIT: Watching these flickering voltage readings is weirdly hypnotic...

Grrrmachine

Yep, rolling back to the manufacturer's original drivers rather than NVidia's package cured the display problem.

Next on the list is the USB - why does it not find the brain on reload? If I find the brain in configurator, close configurator and then re-open, it says there is no Brain present and can only be solved by unplugging and reconnecting the USB cable. I have tried this with both Da Fusion Brain and Fusion Brain v3 drivers, same problem on both.

2k1Toaster

Ok, I made a typo in post 7. It is not "basegui" it is "basicgui". Sorry about that. I edited the above post for future reference.

Now that we know it is a DirectX issue, MDX can bypass DirectX alltogether, by using the "basicgui" switch.

Try that as a parameter in your shortcut, and you can have your old settings, with MDX!

That should work as it uses GDI+ like the Configurator. It is a bit slower, but as long as you dont have a huge huge skin file with lots of transparency on a slow system it should be ok. Or ofcourse you can leave it as you have it since it works

__________________

MP3Car.com