bkenobi

The attract mode info on the bottom is only available in MAME because it has the ability to show overlays (bezels, etc). Other emulators don't have that ability since there's no such thing as a bezel on a console. It might be possible to do something for portable systems like Gameboy or Game Gear in emulators that put a system image around the game screen, but it's not likely to be implemented due to limited desire and potentially extensive complexity. MAME was pretty easy for HK to put together (it was a small extension from the CPWizard project he was working on at the time), but these other systems are VERY different in complexity...

The official divx codec should work fine. At some point there was a problem with the system tray icon stealing focus from GameEx upon initial launch. I don't know what codec caused it but I thought it was at least one version of the official divx codec. If it's fixed/not an issue, that's great!

You don't want to keep the bigger file, you want to keep the vertical file. If the game has a vertical resolution, GameEx will force the video snap to maintain that vertical resolution. If you have a video snap that has artwork or is horizontal for whatever reason and you try to display that with a vertical game, it will end up looking all smooshed.

I can't believe you brought my shoes into this <sulk>. I am very sensetive about what people think about my foot wear .... Yeah, it doesn't have to be exactly the same theme at lower resolutions. I would imagine things might start to get pretty cramped with so few pixels compared to a big beautiful 1280+ screen. I wouldn't worry about it for now (unless it's easy). Focus on getting it how you want it for your machine!

I didn't realize it worked correctly at one point using the same movements. If so, then something else is up. Could be a dirty/oily shaft or a bad/dirty encoder board. I'm not sure what else to check. If it's a hardware problem (which it currently sounds like it is), I would highly recommend asking on the BYOAC forums. This is the type of question they can answer quickly and correctly (by reputation anyway).

1024x768 minimum... BOOOOO My main cab is 640x480, so I guess that leaves me out in the cold again. I didn't want to use this stupid theme anyway

Just bumping in case you missed my reply. I see that you responded at the same time I was composing.

Yeah, a full GameUx solution would be sweet, but it would be a lot of work to get it there. Just add roms and configure!

In some trackballs and spinners, if you spin them too fast, they will not work correctly. There are many threads on BYOAC.com discussing a phenomenon where the device will move opposite to what you specified if moved too quickly. These problems are caused by the poling rate of the device and the rate at which you spin the encoder disk. I'm not going to get too technical here, but when you move the trackball, you spin little shafts underneath it. Those shafts have encoder wheels (like little pinwheels) attached to them at one end. Those encoders sit in-between a LED emitter and LED detector (sometimes a single unit, sometimes two components). When you spin the ball/spinner, the encoder disk spins and breaks the light beam. Depending on the direction of spin, the device will respond according to what you input. Now the problem comes in when you consider that the device only checks the light beam every so many milliseconds. If you spin the wheel fast enough that the light beam is broken and then unbroken before the device poles again, it won't know that you moved anything. If you slow down slightly, it will catch the tail end of the beam being unbroken and think you are moving backwards or maybe just twitching it. If you slow down even more, it will then see what's going on correctly and the cursor will shoot across the screen. Something else COULD be going on, but this is the most likely cause. The solution many people have looked at is using a program to increase the poling rate of their PS/2 interface devices (mouse hack), or moving to USB.

I just realized what the problem may be. If you are using -tripplebuffer, then that's probably it (as already mentioned), but if not, then it might be that successful gameplay requires a 64-bit compile of MAME and a 64-bit OS. MAME is going more 64-bit optimized as time goes on, so it wouldn't surprise me if you gained a significant amount of performance from moving to a 64-bit platform. This is just a hunch though...

Make sure you copy them in the right order. Circo's describes it in detail. Also, if you want to only have one location for your files and not lose any of the originals, I put together a procedure using linked files. It allows you to have the original files so you don't have to re-download EVERYTHING when you update AND you can also have them in a format that GameEx will accept WHILE NOT taking up any extra HDD space. Check out this thread for details.

Just because it's emulated doesn't mean that it's 100% accurate or full speed. I haven't read what the MAMEdevs remarks are on this rom ATM, but it's probably not really there yet. Remember, California Speed (among other Seattle based games) has been emulated in MAME for quite a while now and it's only just recently that top of the line systems are able to play it near full speed. It may take another generation or two for PC hardware to get fast enough to emulate it fast enough. That or the code will require optimization (which is unlikely since that's not really the goal of the MAME project).

Sorry, yes it's only available in game. This is a per game setting, so you may want to adjust the analog settings for each of the analog games you play. Adjusting this carefully can make a game that seems unplayable work almost as well as the original.

It's under analog settings as I recall. You can adjust the speed, sensitivity, re-centering speed, etc.

Doesn't the {esc} command make that emu full screen? I can't remember which one, but I know at least one of the Nintendo emus used escape to maximize/window. Is it possible that you modified another emulator to get your SNES9X config? Perhaps escape exits this one instead of maximizing? Just a though...try what Brian said!

That's pretty close, but I don't know if it's perfect. I don't remember if it would need a # or not, but yes it would be "IfWinActive, Zinc" (I think the ',' is optional in most AHK statements, but it's technically preferred). Also, you might need a #Persistent and #SingleInstance in there as well.

Careful...Tom might scold you for getting off topic

I highly recommend checking out AutoHotKey. It's free and AWESOME! Remapping is such a common task for AHK that they have put together a very nice little tutorial on how to do it here. Basically, you create a text file and put your remapping info in it as such: a::x b::y c::zWhich remaps a, b, and c keys to send x, y, and z, respectively.

Sheesh... Get a room guys

Ummm, it looks like it didn't upload. The message board only takes files of certain file extension. Either rename the file to a .txt extension or zip it and then post again.

To remap the X-Arcade, you will need to write an AHK script. It's pretty easy, so just ask if you need help.

What codec are you using? Some codecs use a system tray icon that steals focus when it launches (e.g., the official divx codec last I heard). If you use the link on the main page for the video codec Tom recommends, you shouldn't have problems with this. If you are using that codec, then post your log.txt file and we can take a look.

Yup, a driving cab shouldn't be that expensive. If you look around and are willing to drive a few miles, you should be able to get an empty cab for pretty cheap. The good thing about the 360 wheels is that they are very simple. I tore both of mine down, cleaned, and reassembled them in a couple hours. The only thing that wears out on them really is a teflon bushing. As long as the shaft isn't bent, you should be good to go. If it is, a machine shop should be able to help straighten it out for next to nothing. If they spin, then the only thing to check is the encoder board. If it's bad, you can always just build a hacked one from an old ball mouse for super cheap! And, depending on how you hook up to the computer, you may be using that mouse anyway!

Did you enable custom inputs? I think that might have caused some problems. I'm out of town now, but can check my config against yours tomorrow if you upload your ini. I have to pick up my dog from the trainer, but should have some time to take a look.

Yes it's possible, but I don't know what the image name is. It should be in the c:\program files\gameex\themes\<theme name>\media directory. Someone else hopefully can fill in...