|
Post by lanman31337 on Dec 1, 2007 17:41:27 GMT -5
I tried on my Nvidia chipset pc, and no problems with this one booting whatsoever. Getting my guns to work is going to be a whole different story though.
|
|
|
Post by hkems on Dec 2, 2007 21:40:27 GMT -5
So, your Nvidia Chipset PC could boot up with TopGun connected ? It's nice. Are you using Smog's GunCon2PC driver ?
|
|
|
Post by lanman31337 on Dec 19, 2007 14:32:30 GMT -5
Yes, I'm using smog's driver on both machines.
|
|
|
Post by hkems on Dec 19, 2007 20:09:26 GMT -5
I see, seems this problem is related to the type of chipset used.
|
|
|
Post by Same Problem on May 14, 2008 21:25:15 GMT -5
i AM HAVING THE SAME PROBLEM.
iF i PLUG IN the guns before booting, then it takes a long time to Boot up and even worse, MAME32, the Mame with the GUI runs Choppy and the sound is choppy as well, it runs very slow. Interestingly, Daphne Emulator Runs at regular speed.
If I boot up without the guns plugged in, everything works great
|
|
|
Post by hkems on May 15, 2008 20:35:13 GMT -5
Well, it's likely that this problem is related to the type of chipset used. By the way, please kindly try our latest driver and see if this problem still occur. latest TopGun driver for XP: www.hkems.com/files/TopGun%20driver%20(beta,%20for%20XP).zip note: it is not likely that the new driver could fix this, but you may have a try. Thanks
|
|
|
Post by ZigRiz on Jun 9, 2008 2:28:05 GMT -5
I too have the same Boot/Mame32/Mame sound problems. I have tried all driver options and still hit the same issue. I can get around it if I udate the driver every time I want to use the gun, but it's locked in a Arcade cabinet and is becoming quite frustrating. It's great when it works but just not a workable solution.
As others have said, other emulators appear not to have the sound/performance issue of mame 32 when the topgun is having the problem.
I have tried the latest drivers, but they did not help.
I hope we can find an answer soon.... :-[
|
|
|
Post by ZigRiz on Jun 10, 2008 3:06:13 GMT -5
Ok, perhaps my problem was not exactly the same, but it was very similar (problems following a boot with the topgun connected). I struggled to get this going, but eventually did, so I will share my experience.
When I first bought the Topgun I set it up with no problems and used it for about 5 days problem free (and loved it). Then I upgraded from Mame .117 to Mame .125. That was the start of my problems (I should have taken a backup!) . I could not get mame .125 to see the lightgun at all. Thinking it could be a diver issue, I tried updating it (I think this was my big mistake and should have just resolved the mame issue). I also think I tried installing on different USB ports, again I think this is a big mistake and the gun should ALWAYS use the same port. Eventually I got the gun working and recognized in Mame, but then I hit my problem.
My problem was not a slow boot, but MAME stuttered (other emulators were fine) if my PC/Cab was booted with the Topgun plugged in. This is why I thought it was the same issue. If I booted without the Topgun connected everything in MAME was fine.
Ultimately I think my issue was driver clash/crash. I used the XP 'System Restore' in system tools to go back to a day before I started.
First I tried the v3.2 drivers, same problem. I could make the gun work, but on the next boot with the gun connected, mame would stutter (slow with sound issues). I also used SMOGS drivers, same result.
To cut a long story short. I rolled back to the day before any changes were made and I installed the new XP drivers (released May 9th 2008). Bingo, it worked.
Now a little more information. The first time I went into Mame it came up as Mouse 3. The next time it came up as Mouse 2. Odd.
I hope this helps someone.....
|
|
|
Post by ZigRiz on Jun 10, 2008 3:11:01 GMT -5
Further to my last mesage.
Dear EMS Admin,
It seems clear that driver code and settings are being left behind following a driver uninstall.
Is is possible that you could post a detailed list of the changes your drivers make i.e. Files/Locations, registry keys updated etc. So that we can manually fully delete the drivers should we need to? I think this would greatly assist with any driver clash/crash issues.
Many Thanks.
|
|
|
Post by d**n on Jun 11, 2008 2:46:43 GMT -5
Ok. After two more reboots I'm back to MAME stutter when the gun is left in during a boot. I hope someone find a fix.... Very,very, very frustrating........
|
|
|
Post by Gsampson35 on Feb 21, 2014 12:00:09 GMT -5
Im having this problem as well. I bought a mame cabinet that had a Pentium 4 laptop in it. Ran fine. Even with the gun connected at boot. Upgraded the laptop to a desktop. Asus M2A-VM motherboard. 2gb DDR2-800. 1tb Western Digital 5200rpm Sata 2 hdd. 1gb Nvidia GTX 260 PCI-E video card. AMD Athlon 64 5200+ CPU 2700mhz Dual Core. Windows XP 32bit. With the gun connected to this system at boot the post takes a extra 30 seconds. And mame runs incredibly slow. With the gun disconnected everything runs fine. Ive tried different compiles of mame with no luck yet. Ive tried Windows XP 64 bit same problem. And with Windows 7 the gun is not supported.
I do believe ill just have to wire some usb ports to the control pannel. Or the side of the cabinet to make it easy to access. Gun does work great tho. Plays fine with all games. Point Blank, Duck Hunt, Area 51. T2 Judgement Day, Alien 3 The Gun, Revolution X, Hogans Alley. I never even calibrated it yet and its pretty accurate.
One question tho. I have a neogeo cabinet with a 19 inch samsung monitor. I find that i need to put the right sensor bar 3.5 inches away from monitor. And the left one to 1 inch away from monitor for the gun to beable to move around the whole screen. Is there any specs on bar placement? Its a Topgun 1 wired.
Thanks.
|
|
|
Post by hkems on Feb 27, 2014 20:21:00 GMT -5
You could mount the two bars beside the screen. You don't need to care much about the position of the LED bars. The accuracy of the gun depends on the calibration process. If the gun is not accurate enough, please re-calibrate it.
|
|