Yesterday, I had a perfectly functioning set of gauges...Today, they will load, but consistently crash FSX with a "BEX" error (whatever that is!) when trying to click on a mousepoint... <sigh>I was going to add keyboard support, but can't until I figure out this problem. :(

The joys of gauge design. :( Did you get my PM BTW?

Bill,may be you find here some helpfull infos. http://www.google.com/search?q=BEX++error&...;rlz=1I7ADBR_deDietmar

Bill,may be you find here some helpfull infos. http://www.google.com/search?q=BEX++error&...;rlz=1I7ADBR_de

Thanks. Man do I ever feel foolish!What do you suppose would happen if you make a call to a .dll that hasn't been loaded or initialized? :( I am (re)building a set of gauges for a specific project, one for which certain sub-gauges do not need to be included. While I remembered to move parts of one gauge's initialization routines, I completely forgot to move the start/configure/stop code for GaugeSound.dll.When I loaded the new, cut-down gauge package, of course any mouse click would cause a crash!It's amazing how much a day off "playing" and two good night's sleep will clear up mysterious things...

The joys of gauge design. :( Did you get my PM BTW?

Yes I did, Ed. I just have been too busy to reply. Unfortunately I'm bound by an NDA not to disclose the details. Sorry! It isn't really that difficult to accomplish, but does require quite a bit of experimenting to get it working...

Ah, but the agonizing saga didn't end there!After beating my head against the wall wondering why my keyboard .ini file wasn't being loaded, or if it was loaded it wouldn't work...I loaded up another gauge that I KNEW worked......same thing, no keyboard support! What the heck???It turns out that when I set up my new FS machine, I forgot to update the path for Hypergauge.dll in my stinking dll.xml file!!! <Argh!.Of course, now everything works splendidly! :(