stub

I've got about a million questions and will be posting more but I figure'd I'd start with the most annoying right now for me.
I'm trying to use transparency and .png files and get them to work and look right in the actual fusion control software. It seems to work and look great in the configurator, but transparancy simply dosn't work when I run it.

So what am I doung wrong? As you can see, the images look great in the configurator.

Attached Images

 

MP3Car.com

 

2k1Toaster

Can you post a few of your PNG files so I can see what sort of coding is in it?

Also you can put "-basicgui" in the shortcut to MDX to make it run in GDI+ mode, which is how the Configurator displays it.

Default is using DirectX, and it requires your hardware to support transparent layers and such. A 10 year old video card wont render correctly so forcing it to use "-basicgui", everything will be rendered on the CPU not the GPU. What sort of hardware is it on?

__________________

stub

I'll check to see if I can geb an update for my video card. Right now, I'm running this on a home built PC. The vidio card should be about 5 years old Nvidia G-force4. I think it supports direct-x...

Sorry but you may have to spoon feed me the "-basicgui" shortcut thing. Is this a tag I should put in the FusionConfiguration.xml file?

Thanks for your help. Like I said I have a lot more questions but I'm reading up on past posts and such trying to catch up first.

Attached Images

     

stub

This is the most important one for me right now.

Attached Images

 

GadgetBandit

It works fine on my 3 yr old laptop. I was concerned that your images were on the transparent background layer in the png. I moved it up a layer but no difference. all worked fine.

GadgetBandit.

2k1Toaster

Yup, the images work fine here. It is a video card/driver problem for that.

So to run in GDI+ mode, what you need to do is right click the shortcut to MDX, go to properties. Then in the target, there should be something like


and append "-basicgui" to it so it becomes:



Notice the argument is outside the target, that way windows knows it is an argument for the program, not a continuation of the shortcut target path.

__________________

stub

Beautiful! That worked great.
I updated the drivers for my video card but it didn't help.

stub

OK. this is what I'm up to.
I'm building an electric car. I need to moniter each battery something like this http://home.earthlink.net/~evtkw/

Although I'd like to use the fusion brain and car pc so ultimately I have two screens, one for gauges, the other for MP3 player, radio, etc. The gauge screen will be behind the steering wheel, touch screen in the normal position.

More like the Holden Efigy http://www.seriouswheels.com/2005/20...l-1280x960.htm

The 12 volt cells in the 280 volt battery need to be isolated from each other to be moniterd. So the plan is to build a voltage devider circuit that will drop 9 to 15 volts down to 1.4 to 3 and drive an LED. The LED is linked by 1000um fiber cable (aka 1mm light pipe) to an opticalresister datasheet; http://pdf1.alldatasheet.com/datashe...OED-ST-8L.html
Use one for each analog port to display the voltage on the EQ looking bar meter I posted above.

I've built a breadboard circuit and it sort of works. The opticalresistor to analog port side works great and I can display full off to a bright light as a bar meter in fusion control with a flashlight or led pointed at it. The fiber or light pipe seems transparent in that it is working beautifully.

The trouble I'm having is the individual circuits for each battery. I'm currently playing with a red LED, a 2 resistor voltage divider driving the "adjust" pin on an LM317T voltage regulator. Vout goes to the LED, Vin direct to + of the battery.

It's sort of working. The display isn't linear, and it's more like 5 - 25 volts to dim the LED.

Anyone have any ideas? a more simple way? better? I'm not an engineer and am pushing the limits of my geekedness building this circuit.

MP3Car.com