FCC Uber MDX Bugs

2k1Toaster · 12-12-2001, 01:06 AM

Quote: Originally Posted by bratnetwork

weird... i didnt touch it all night then when i got home it worked.

It could have been installing directx, which needed some time to get the environment variables setup correctly. At least it works now. Do both the main program and configurator work for you?

h3rk · 04-22-2008, 04:40 AM

I know that the software is supposed to be 100%, and I really haven't had many problems with it so far

, but there have been a few problems here and there.

One of them has been a mismatch between the area of the button as it is visible, and the area of the button as it is clickable. I don't know why, but there seems to be about a 30-40 pixel height difference. The clickable area is outlined in blue. There's a large portion of the top of each button that wont react to clicking. Maybe it has something to do with the height of the title bar up on top of the actual program.

maybe it's just me.
(I have a video of it. It's not uploaded presently, but in it you can see where the mouse pointer is clearly, with visual and audio evidence that the button either is (primary/secondary, and relays clicking) or isn't toggling. I wasn't sure if it would be that useful.)

This one is not a bug really, but I thought I'd mention it. When trying to run zdsoft screen capture to make a video of some problems I'm seeing, I got the big red X on the FCC uber MDX window. With an unhandled exception error (which I have saved if you want it). It must be shy

. So my video is externally recorded.

Another is that I've been having hang-ups after leaving the screen idle for a long period of time...But if I'm messing around with the computer, I've been checking like once every hour or two and the program and brain seem to respond nicely.

I didn't see another centralized thread for the actual software's bugs, so I started a new one. If you want though, just file it back in with the feature requests.

Oh, and just to move it out of the configurator thread, I still have no "pushed" state indication in the software.

2k1Toaster · 05-12-2008, 02:21 AM

Quote: Originally Posted by h3rk

One of them has been a mismatch between the area of the button as it is visible, and the area of the button as it is clickable. I don't know why, but there seems to be about a 30-40 pixel height difference. The clickable area is outlined in blue. There's a large portion of the top of each button that wont react to clicking. Maybe it has something to do with the height of the title bar up on top of the actual program.

maybe it's just me.
(I have a video of it. It's not uploaded presently, but in it you can see where the mouse pointer is clearly, with visual and audio evidence that the button either is (primary/secondary, and relays clicking) or isn't toggling. I wasn't sure if it would be that useful.)

This one is not a bug really, but I thought I'd mention it. When trying to run zdsoft screen capture to make a video of some problems I'm seeing, I got the big red X on the FCC uber MDX window. With an unhandled exception error (which I have saved if you want it). It must be shy

. So my video is externally recorded.

Another is that I've been having hang-ups after leaving the screen idle for a long period of time...But if I'm messing around with the computer, I've been checking like once every hour or two and the program and brain seem to respond nicely.

I didn't see another centralized thread for the actual software's bugs, so I started a new one. If you want though, just file it back in with the feature requests.

Oh, and just to move it out of the configurator thread, I still have no "pushed" state indication in the software.

yes the video would be helpful. Is this with the main program only or with the configurator too? If you set the title bar to hidden, does the same thing happen?

As for hanging up after a long time, I am still not sure. It hasnt happened to me yet, but I am sure this is all releated to the "shy" behaviour of the program too.

I am not sure what is wrong but there must be something.

And pushed state seems sort of related as well. I am going to try and switch the input over to DirectInput instead of relying on the GDI+ input controls.

2k1Toaster · 05-18-2008, 04:21 AM

Fixed. It will be in the next release.

I was not accounting for the form's title bar height and border width. All my tests I use no border, so it was not showing. Once I put the title bar on, I saw what was happening and got it to work.

bratnetwork · 05-19-2008, 08:29 PM

i downloaded the installer and ran it, also i tried to install everything separately and no matter which way as soon as i open the program it give me an error and says it must close.

Running XP Pro SP2 Build 2600

It doesn't give me any error codes

2k1Toaster · 05-20-2008, 12:48 AM

Is it the "this program has stopped responding" thing or is it a non-standard message?

Have you tried to run it through the debugging shortcut? (Just add "-debug" to the command line parameters) (There is also a pre-made shortcut in the Start--Program folder)

bratnetwork · 05-20-2008, 04:21 PM

weird... i didnt touch it all night then when i got home it worked.