Thread: Fusion Brain Version 6 -- Beta Testing

Originally Posted by waltersaegir

So is FuseGL output accessible externally to FuseGL from HTML5-Java Script-XML?

I think you have a typo/tautology there "FuseGL output accessible externally to FuseGL". Everything in FuseGL is accessible to external compilable C# code. Which means that it can be externally accessible from anything depending on what you put in the *.cs file.

I am working on an official implementation of web control/display similar to the MDX version.

Took a quick look at RRFusion. It looks to use fusionbrain_winusb.dll. Is that still viable or did I miss something?

That DLL does not work with Version 6, only Versions 2, 3, and 4. RRFusion I believe has or will have V6 support, but Sonic is the one to ask there. But it is completely separate from FuseGL, they share nothing but the DLL that I supply.

Been a while since I tried FuseGL. Windows 8 didn't *seem to like it*. Sorry for the vagueness here. Maybe I just forgot how to install it.

Windows 8 is not public, it is in developer preview. I cannot support developer previews that do not even support basic extension functionality. You will need OpenGL and .NET 4.0 to run FuseGL. It does work on Windows XP, Vista, and Win7 in x86 and x64 flavours. It will run but look funky on a system that does not support at least OpenGL 2.0 polygons. So a 10 year old Win XP box might not play well unless the video card vendor has a driver update to render OpenGL 2.0 polygons in software which some do for older hardware. But that onus is on the video card vendor.

Yes, I understand that you need to bound your support universe.
As I make time again, I will look at Windows 8 for support/install of OpenGL and .NET 4.0.
Also, like I said that it's been a while since I've installed FuseGL and the drivers. So, I might have screwed-up. Should probably look through the postings. I'm sure there are directions around.

Originally Posted by Sonicxtacy02

That version is not v6 compatible. A V6 compatible version will be released tomorrow. I'm actually putting the finishing touches on it now.

Since I wasn't planning on using Ride Runner as such, will the dll functionality be available from some subset core of Ride Runner or some other less comprehensive software?

Originally Posted by waltersaegir

Yes, I understand that you need to bound your support universe.
As I make time again, I will look at Windows 8 for support/install of OpenGL and .NET 4.0.
Also, like I said that it's been a while since I've installed FuseGL and the drivers. So, I might have screwed-up. Should probably look through the postings. I'm sure there are directions around.

FuseGL just needs the exe, found on the software page of the website. Double click and you're done. It will spew files and folders wherever you click it, so it is advised to keep it in a subfolder somewhere.

Originally Posted by waltersaegir

Since I wasn't planning on using Ride Runner as such, will the dll functionality be available from some subset core of Ride Runner or some other less comprehensive software?

If you just want DLL functionality, then you can use the C# core of FuseGL.

Originally Posted by waltersaegir

Since I wasn't planning on using Ride Runner as such, will the dll functionality be available from some subset core of Ride Runner or some other less comprehensive software?

Forgive me for not looking too far back into this but what exactly are you trying to get done with the fusion brain? I mean, when i started RRFusion i just wanted relay control within RR, it turned into a dynamic platform that while gives 99% of users what they want, doesnt harness ALL of the fusion brains power admittedly. 2k1 has created a platform that allows us developers to use any and all of the FBs power, but if you dont want all of that, it can be a little complicated.

Basically what i'm saying is list what you want to be able to do with your fusion brain(s). If its something as simple as digital output control, analog input reading/conversion, and maybe a little xml based automation, then perhaps i can expose the methods used in RRFusion in an external dll. This is kinda redundant, but in the interest of helping out when possible i'll give it a go.

Sounds like a reasonable (and generous) tac.

Now that I'm revisiting this, I need to more clearly understand what FuseGL is actually doing and what it might be capable of doing.

I just fired it up and I do get output from the temperature sensor that came with it, but clearely the values (0.797, 0.794 with the 0.10 Button==off and 0.819. 0.813 with the 0.10 Button==on) are not degrees of temperature.

I'll browse around in the postings and hopefully I will see this addressed. Also, I will look for the F10 et-all menu selections being addressed as they generally provide behavior that seems somewhere between uncontrollable-surprising-cryptic.

Originally Posted by waltersaegir

I just fired it up and I do get output from the temperature sensor that came with it, but clearely the values (0.797, 0.794 with the 0.10 Button==off and 0.819. 0.813 with the 0.10 Button==on) are not degrees of temperature.

Can you clarify this statement?

Do you have actual hardware hooked up? The 0.10 button is a digital output, it has nothing to do with what I am assuming is a raw voltage label?

I'll browse around in the postings and hopefully I will see this addressed. Also, I will look for the F10 et-all menu selections being addressed as they generally provide behavior that seems somewhere between uncontrollable-surprising-cryptic.

As previously mentioned, the configuration is what is still under development. Supplying custom code files, and fully implementing the button menus.

If you don't know what a screen is for, then do not move the mouse for a few hundred milliseconds and a box will appear telling you what it is expecting. I can change this behaviour to something else if you prefer. Perhaps show the box until mouse starts to move or something?

I make software for you guys, so you tell me what you want, and that is what I do.

Originally Posted by waltersaegir

Sounds like a reasonable (and generous) tac.

Now that I'm revisiting this, I need to more clearly understand what FuseGL is actually doing and what it might be capable of doing.

I just fired it up and I do get output from the temperature sensor that came with it, but clearely the values (0.797, 0.794 with the 0.10 Button==off and 0.819. 0.813 with the 0.10 Button==on) are not degrees of temperature.

I'll browse around in the postings and hopefully I will see this addressed. Also, I will look for the F10 et-all menu selections being addressed as they generally provide behavior that seems somewhere between uncontrollable-surprising-cryptic.

I know you said you dont wish to use RR, but if you are interested in how the v6 compatible version of the RRFusion plugin works it is now available here


2k1... in finally completing RRFusionV6 i've run into a rather strange issue. I know i got an early "beta" brain so it could be because of that, but whenever i write to toggle the state of port 6 the fusion brain disconnects then reconnects, almost as if i've pulled the USB plug. All other ports work fine. Should i just attribute it to being an early beta brain? I "think" i have the latest firmware, but i'm honestly not positive.

Originally Posted by Sonicxtacy02

I know you said you dont wish to use RR, but if you are interested in how the v6 compatible version of the RRFusion plugin works it is now available here


2k1... in finally completing RRFusionV6 i've run into a rather strange issue. I know i got an early "beta" brain so it could be because of that, but whenever i write to toggle the state of port 6 the fusion brain disconnects then reconnects, almost as if i've pulled the USB plug. All other ports work fine. Should i just attribute it to being an early beta brain? I "think" i have the latest firmware, but i'm honestly not positive.

The early beta brains will disconnect if you have too much power draw from USB and are only powered from USB. This is because the power limiting resistors on the LEDs for the outputs are way too small (manufacturing BOM error). Does it happen when wall powered too? I hanvent heard of that before and doesn't happen on my end.