klizine Posted October 25, 2014 Posted October 25, 2014 It takes time and patience. My wife did not want to be around me while i was working on this. I was so frustrated. Now we play all sorts of light gun games in utter bliss. Well, as with most computer related issues, it doesn't make any sense as to why it stopped working for me. For multiple versions, I was using Jumpstile's compiles. They worked great with two aimtraks, no nag, etxras, etc. One day I updated around version 153, it stopped working for me. Direct or non-direct input. I had the issue that sreisig1 is having. And everyone would give great advice, but it wouldn't make it work. On the verge of giving up I tried just a the regular version of mame as a control subject, but then i realized that the two guns worked!! I then taught myself to compile, so I could get no nag and get my highscores (which was a lil frustrating; but i can assist anyone that needs help) Long story short, don't give up. Don't you dare give up. There's a strangely VERY supportive community here. sreisig1 YOU ARE GOING TO GET TWO GUNS SETUP.
sreisig1 Posted October 25, 2014 Posted October 25, 2014 dougan, I'll get those pictures to you a little later on. Klizine, where should I download the regukar version of mame for the 0.155 set? Fingers are crossed. I've said it many times, but I wouldn't be where I'm at without the help of this community. Responses are quick. I look more forward following into the forums more than social media sites like Facebook. Hopefully we can get these guns working and other people experiencing problems will have something to help them troubleshoot.
sreisig1 Posted October 25, 2014 Posted October 25, 2014 It takes time and patience. My wife did not want to be around me while i was working on this. I was so frustrated. Now we play all sorts of light gun games in utter bliss. Haha yea, my fiancé is starting to get fed up. We'll be watching a movie and I'll get up, she'll say why. I just wanna check on something and end up missing the whole movie messing around with Hyperspin
klizine Posted October 25, 2014 Posted October 25, 2014 dougan, I'll get those pictures to you a little later on. Klizine, where should I download the regukar version of mame for the 0.155 set? Fingers are crossed. I've said it many times, but I wouldn't be where I'm at without the help of this community. Responses are quick. I look more forward following into the forums more than social media sites like Facebook. Hopefully we can get these guns working and other people experiencing problems will have something to help them troubleshoot. http://mamedev.org/release.html It doesn't really matter which one, just pick mame0155b_i686.exe if you have a 32bit system or mame0155b_64bit.exe for a 64bit. Run it, then pick a temporary place to test. If will asl for a mame.ini files so just use the one dougan provided. Next you'll need a game. So just throw any non-CHD-requiring-gungame, I chose bang.zip. Then just run your mame.exe (or mame64.exe) start your game, get past the nag, then hit tab. Try to set gun1 and then gun2 via the player 1 & 2 inputs, and hopefully they will show up. Let us know your results!
dougan78 Posted October 25, 2014 Posted October 25, 2014 If you use bang make sure you copy that area51.ini to bang.ini? Or whatever the rom name is.
sreisig1 Posted October 25, 2014 Posted October 25, 2014 Not the result i was hoping for. i really thought that would be your answer. Hmm that is all i did once they both worked in windows. You said the cross hairs are the same color in mame? If so can you send pics of the aimtrak utility. 1 each for each device id?
sreisig1 Posted October 25, 2014 Posted October 25, 2014 Tried with bang, an when i hit tab then go to setup the axis's, it comes up as mouse and not gun this time. But just mouse x/mouse both for player 1 and player 2. So not only is it assigning the same for both players but it's saying mouse instead of gun. Also, just a side note, when I launch area 51 from hyperspin it says now loading on the screen but get's stuck on that fade screen. I have to hit the escape button to bring up the game? Anyone know why? It launches the other games fine still. Never had this problem.
potts43 Posted October 25, 2014 Posted October 25, 2014 Tried with bang, an when i hit tab then go to setup the axis's, it comes up as mouse and not gun this time. But just mouse x/mouse both for player 1 and player 2. So not only is it assigning the same for both players but it's saying mouse instead of gun.Also, just a side note, when I launch area 51 from hyperspin it says now loading on the screen but get's stuck on that fade screen. I have to hit the escape button to bring up the game? Anyone know why? It launches the other games fine still. Never had this problem. Always turn off fade until the game has proven to run successfully - sometimes there will be a window hidden by the fade screen that tells you what's going wrong....
potts43 Posted October 25, 2014 Posted October 25, 2014 Also turn on logging to troubleshoot and read the hyperlaunch.log it will also tell you why it's not loading(usually)
sreisig1 Posted October 25, 2014 Posted October 25, 2014 Took that area51.ini out of the ini folder as a test, and launched hyperspin and area 51 launched fine without having to hit escape. So the problem was with the ini. Anyway, still having issues with the guns, that was just a side thing.
klizine Posted October 25, 2014 Posted October 25, 2014 Tried with bang, an when i hit tab then go to setup the axis's, it comes up as mouse and not gun this time. But just mouse x/mouse both for player 1 and player 2. So not only is it assigning the same for both players but it's saying mouse instead of gun.Also, just a side note, when I launch area 51 from hyperspin it says now loading on the screen but get's stuck on that fade screen. I have to hit the escape button to bring up the game? Anyone know why? It launches the other games fine still. Never had this problem. so for the regular mame, you won't need a ini folder, just mame.ini in the main folder where it's located. Try this mame.ini: # # CORE CONFIGURATION OPTIONS # readconfig 1 writeconfig 0 # # CORE SEARCH PATH OPTIONS # rompath roms hashpath hash samplepath samples artpath artwork ctrlrpath ctrlr inipath ini fontpath . cheatpath cheat crosshairpath crosshair # # CORE OUTPUT DIRECTORY OPTIONS # cfg_directory cfg nvram_directory nvram input_directory inp state_directory sta snapshot_directory snap diff_directory diff comment_directory comments # # CORE OUTPUT DIRECTORY OPTIONS # hiscore_directory hi # # CORE STATE/PLAYBACK OPTIONS # state autosave 0 playback record mngwrite aviwrite wavwrite snapname %g/%i snapsize auto snapview internal statename %g burnin 0 # # CORE PERFORMANCE OPTIONS # autoframeskip 0 frameskip 0 seconds_to_run 0 throttle 1 sleep 1 speed 1.0 refreshspeed 0 # # CORE ROTATION OPTIONS # rotate 1 ror 0 rol 0 autoror 0 autorol 0 flipx 0 flipy 0 # # CORE ARTWORK OPTIONS # artwork_crop 0 use_backdrops 1 use_overlays 1 use_bezels 1 use_cpanels 1 use_marquees 1 # # CORE SCREEN OPTIONS # brightness 1.0 contrast 1.0 gamma 1.0 pause_brightness 0.65 effect none # # CORE VECTOR OPTIONS # antialias 1 beam 1.0 flicker 0 # # CORE SOUND OPTIONS # samplerate 48000 samples 1 volume 0 # # CORE INPUT OPTIONS # coin_lockout 1 ctrlr mouse 1 joystick 1 lightgun 1 multikeyboard 0 multimouse 1 steadykey 0 ui_active 0 offscreen_reload 1 joystick_map auto joystick_deadzone 0.3 joystick_saturation 0.85 natural 0 joystick_contradictory 0 coin_impulse 0 # # CORE INPUT AUTOMATIC ENABLE OPTIONS # paddle_device keyboard adstick_device keyboard pedal_device keyboard dial_device keyboard trackball_device mouse lightgun_device lightgun positional_device keyboard mouse_device mouse # # CORE DEBUGGING OPTIONS # update_in_pause 0 debugscript # # CORE MISC OPTIONS # drc 1 drc_use_c 0 bios cheat 0 skip_gameinfo 0 uifont default ramsize confirm_quit 0 ui_mouse 0 autoboot_command autoboot_delay 2 autoboot_script http 0 http_port 8080 http_path web console 0 # # CORE MKChamp OPTIONS # disable_hiscore_patch 0 disable_nagscreen_patch 0 disable_loading_patch 0 # # OSD DEBUGGING OPTIONS # log 0 verbose 0 debug 0 debugger auto oslog 0 watchdog 0 # # OSD PERFORMANCE OPTIONS # multithreading 0 numprocessors auto bench 0 # # OSD VIDEO OPTIONS # video d3d numscreens 1 window 0 maximize 1 keepaspect 0 unevenstretch 1 waitvsync 1 syncrefresh 1 # # OSD PER-WINDOW VIDEO OPTIONS # screen auto aspect auto resolution auto view auto screen0 auto aspect0 auto resolution0 auto view0 auto screen1 auto aspect1 auto resolution1 auto view1 auto screen2 auto aspect2 auto resolution2 auto view2 auto screen3 auto aspect3 auto resolution3 auto view3 auto # # OSD FULL SCREEN OPTIONS # switchres 0 # # OSD SOUND OPTIONS # sound 1 audio_latency 2 # # WINDOWS DEBUGGING OPTIONS # debugger_font "Lucida Console" debugger_font_size 9 # # WINDOWS PERFORMANCE OPTIONS # priority 0 profile 0 # # WINDOWS VIDEO OPTIONS # prescale 1 menu 0 # # DIRECTDRAW-SPECIFIC OPTIONS # hwstretch 1 # # DIRECT3D-SPECIFIC OPTIONS # filter 1 # # DIRECT3D POST-PROCESSING OPTIONS # hlsl_enable 0 hlslpath hlsl hlsl_prescale_x 0 hlsl_prescale_y 0 hlsl_preset -1 hlsl_write hlsl_snap_width 2048 hlsl_snap_height 1536 shadow_mask_alpha 0.0 shadow_mask_texture aperture.png shadow_mask_x_count 320 shadow_mask_y_count 240 shadow_mask_usize 0.09375 shadow_mask_vsize 0.109375 curvature 0.03 pincushion 0.03 scanline_alpha 1.0 scanline_size 1.0 scanline_height 1.0 scanline_bright_scale 1.0 scanline_bright_offset 0.0 scanline_jitter 0.0 defocus 0.0,0.0 converge_x 0.3,0.0,-0.3 converge_y 0.0,0.3,-0.3 radial_converge_x 0.0,0.0,0.0 radial_converge_y 0.0,0.0,0.0 red_ratio 1.0,0.0,0.0 grn_ratio 0.0,1.0,0.0 blu_ratio 0.0,0.0,1.0 saturation 1.4 offset 0.0,0.0,0.0 scale 0.95,0.95,0.95 power 0.8,0.8,0.8 floor 0.05,0.05,0.05 phosphor_life 0.4,0.4,0.4 # # NTSC POST-PROCESSING OPTIONS # yiq_enable 0 yiq_cc 3.59754545 yiq_a 0.5 yiq_b 0.5 yiq_o 1.570796325 yiq_p 1.0 yiq_n 1.0 yiq_y 6.0 yiq_i 1.2 yiq_q 0.6 yiq_scan_time 52.6 yiq_phase_count 2 # # VECTOR POST-PROCESSING OPTIONS # vector_length_scale 0.8 vector_length_ratio 500.0 # # BLOOM POST-PROCESSING OPTIONS # vector_bloom_scale 0.3 raster_bloom_scale 0.225 bloom_lvl0_weight 1.0 bloom_lvl1_weight 0.21 bloom_lvl2_weight 0.19 bloom_lvl3_weight 0.17 bloom_lvl4_weight 0.15 bloom_lvl5_weight 0.14 bloom_lvl6_weight 0.13 bloom_lvl7_weight 0.12 bloom_lvl8_weight 0.11 bloom_lvl9_weight 0.10 bloom_lvl10_weight 0.09 # # FULL SCREEN OPTIONS # triplebuffer 1 full_screen_brightness 1.0 full_screen_contrast 1.0 full_screen_gamma 1.0 # # INPUT DEVICE OPTIONS # dual_lightgun 0
dougan78 Posted October 25, 2014 Posted October 25, 2014 That looks right i set the button 2(left) to the same as off screen both guns. Can you post your mame.ini too?
klizine Posted October 25, 2014 Posted October 25, 2014 I think we need to coordinate this better? don't wanna confuse the poor guy. I just think trying out the box mame would be a good start (as pre-compiled one's aren't working as they should)
dougan78 Posted October 25, 2014 Posted October 25, 2014 That is my bad. Klzine you have a crack at it. Good luck. I will monitor as i am excited for it to work. We WILL get there! I agree on the mame i just had the same issue on all versions. Drove me nuts too. Stock mame is best place to start. Cant tell you how many times i made a new mame folder. Ran mame -cc and started grom scratch. ; )
sreisig1 Posted October 26, 2014 Posted October 26, 2014 so for the regular mame, you won't need a ini folder, just mame.ini in the main folder where it's located. Try this mame.ini: # # CORE CONFIGURATION OPTIONS # readconfig 1 writeconfig 0 # # CORE SEARCH PATH OPTIONS # rompath roms hashpath hash samplepath samples artpath artwork ctrlrpath ctrlr inipath ini fontpath . cheatpath cheat crosshairpath crosshair # # CORE OUTPUT DIRECTORY OPTIONS # cfg_directory cfg nvram_directory nvram input_directory inp state_directory sta snapshot_directory snap diff_directory diff comment_directory comments # # CORE OUTPUT DIRECTORY OPTIONS # hiscore_directory hi # # CORE STATE/PLAYBACK OPTIONS # state autosave 0 playback record mngwrite aviwrite wavwrite snapname %g/%i snapsize auto snapview internal statename %g burnin 0 # # CORE PERFORMANCE OPTIONS # autoframeskip 0 frameskip 0 seconds_to_run 0 throttle 1 sleep 1 speed 1.0 refreshspeed 0 # # CORE ROTATION OPTIONS # rotate 1 ror 0 rol 0 autoror 0 autorol 0 flipx 0 flipy 0 # # CORE ARTWORK OPTIONS # artwork_crop 0 use_backdrops 1 use_overlays 1 use_bezels 1 use_cpanels 1 use_marquees 1 # # CORE SCREEN OPTIONS # brightness 1.0 contrast 1.0 gamma 1.0 pause_brightness 0.65 effect none # # CORE VECTOR OPTIONS # antialias 1 beam 1.0 flicker 0 # # CORE SOUND OPTIONS # samplerate 48000 samples 1 volume 0 # # CORE INPUT OPTIONS # coin_lockout 1 ctrlr mouse 1 joystick 1 lightgun 1 multikeyboard 0 multimouse 1 steadykey 0 ui_active 0 offscreen_reload 1 joystick_map auto joystick_deadzone 0.3 joystick_saturation 0.85 natural 0 joystick_contradictory 0 coin_impulse 0 # # CORE INPUT AUTOMATIC ENABLE OPTIONS # paddle_device keyboard adstick_device keyboard pedal_device keyboard dial_device keyboard trackball_device mouse lightgun_device lightgun positional_device keyboard mouse_device mouse # # CORE DEBUGGING OPTIONS # update_in_pause 0 debugscript # # CORE MISC OPTIONS # drc 1 drc_use_c 0 bios cheat 0 skip_gameinfo 0 uifont default ramsize confirm_quit 0 ui_mouse 0 autoboot_command autoboot_delay 2 autoboot_script http 0 http_port 8080 http_path web console 0 # # CORE MKChamp OPTIONS # disable_hiscore_patch 0 disable_nagscreen_patch 0 disable_loading_patch 0 # # OSD DEBUGGING OPTIONS # log 0 verbose 0 debug 0 debugger auto oslog 0 watchdog 0 # # OSD PERFORMANCE OPTIONS # multithreading 0 numprocessors auto bench 0 # # OSD VIDEO OPTIONS # video d3d numscreens 1 window 0 maximize 1 keepaspect 0 unevenstretch 1 waitvsync 1 syncrefresh 1 # # OSD PER-WINDOW VIDEO OPTIONS # screen auto aspect auto resolution auto view auto screen0 auto aspect0 auto resolution0 auto view0 auto screen1 auto aspect1 auto resolution1 auto view1 auto screen2 auto aspect2 auto resolution2 auto view2 auto screen3 auto aspect3 auto resolution3 auto view3 auto # # OSD FULL SCREEN OPTIONS # switchres 0 # # OSD SOUND OPTIONS # sound 1 audio_latency 2 # # WINDOWS DEBUGGING OPTIONS # debugger_font "Lucida Console" debugger_font_size 9 # # WINDOWS PERFORMANCE OPTIONS # priority 0 profile 0 # # WINDOWS VIDEO OPTIONS # prescale 1 menu 0 # # DIRECTDRAW-SPECIFIC OPTIONS # hwstretch 1 # # DIRECT3D-SPECIFIC OPTIONS # filter 1 # # DIRECT3D POST-PROCESSING OPTIONS # hlsl_enable 0 hlslpath hlsl hlsl_prescale_x 0 hlsl_prescale_y 0 hlsl_preset -1 hlsl_write hlsl_snap_width 2048 hlsl_snap_height 1536 shadow_mask_alpha 0.0 shadow_mask_texture aperture.png shadow_mask_x_count 320 shadow_mask_y_count 240 shadow_mask_usize 0.09375 shadow_mask_vsize 0.109375 curvature 0.03 pincushion 0.03 scanline_alpha 1.0 scanline_size 1.0 scanline_height 1.0 scanline_bright_scale 1.0 scanline_bright_offset 0.0 scanline_jitter 0.0 defocus 0.0,0.0 converge_x 0.3,0.0,-0.3 converge_y 0.0,0.3,-0.3 radial_converge_x 0.0,0.0,0.0 radial_converge_y 0.0,0.0,0.0 red_ratio 1.0,0.0,0.0 grn_ratio 0.0,1.0,0.0 blu_ratio 0.0,0.0,1.0 saturation 1.4 offset 0.0,0.0,0.0 scale 0.95,0.95,0.95 power 0.8,0.8,0.8 floor 0.05,0.05,0.05 phosphor_life 0.4,0.4,0.4 # # NTSC POST-PROCESSING OPTIONS # yiq_enable 0 yiq_cc 3.59754545 yiq_a 0.5 yiq_b 0.5 yiq_o 1.570796325 yiq_p 1.0 yiq_n 1.0 yiq_y 6.0 yiq_i 1.2 yiq_q 0.6 yiq_scan_time 52.6 yiq_phase_count 2 # # VECTOR POST-PROCESSING OPTIONS # vector_length_scale 0.8 vector_length_ratio 500.0 # # BLOOM POST-PROCESSING OPTIONS # vector_bloom_scale 0.3 raster_bloom_scale 0.225 bloom_lvl0_weight 1.0 bloom_lvl1_weight 0.21 bloom_lvl2_weight 0.19 bloom_lvl3_weight 0.17 bloom_lvl4_weight 0.15 bloom_lvl5_weight 0.14 bloom_lvl6_weight 0.13 bloom_lvl7_weight 0.12 bloom_lvl8_weight 0.11 bloom_lvl9_weight 0.10 bloom_lvl10_weight 0.09 # # FULL SCREEN OPTIONS # triplebuffer 1 full_screen_brightness 1.0 full_screen_contrast 1.0 full_screen_gamma 1.0 # # INPUT DEVICE OPTIONS # dual_lightgun 0 OK! Progress! (just a side note before I get into this: my first gun is blue color, my second gun is red color, due to how i setup my control panel overlay. blue is left side red is on right side) Klizine, made another mame folder for the test. Installed that version of mame you suggested. Used your mame.ini. Run hyperlaunch and area 51. Go to setup the axis's. Using device 1 blue gun, it registers as gun 2 for both x and y. Using device 2 red gun, it registers as gun 1 for both x and y. For whatever reason its doing gun 1 and 2 backwards idk, but idc. Because how mame is, or just how area 51 is idk, gun 1 is red crosshair, and gun 2 is blue crosshair. So it actually works out cause of the actual color of my guns. Only problem is the health on screen is opposite color, but idc, as long as crosshairs are correct color. Now. Playing the game. Blue gun shoots and reloads fine. Red gun doesn't shoot the enemies or reload, although i have set the red guns trigger button in mame. Answers? Making headway guys! I think! (still would like no nag and highscore eventually)
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Correction on the not shooting for second gun. Both guns working and reloading! Ill just have to make due with have my blue gun (left) having the red health due to how my control panel is setup. Now...how to get no nag and highscore. Also, for when I move everything from my test mame folder, when it comes to it should I just get rid of everything in my real mame folder and move the test folder stuff over?
klizine Posted October 26, 2014 Posted October 26, 2014 The "Gun 1", "Gun 2" thing is how widows deals with identifying them... i've had it Gun 7 and Gun 8 odd, cause I don't have that many... but regardless.. AWESOME!!! ok. so good news. you can change the colors of the crosshairs. In game hit Tab, then go down to Crosshair Options. You can then change the color to whatever you have in your crosshair folder for P1 and P2 crosshairs!!!
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Sweet man! Yea I'm ok with the cross hairs. It's actually using them correctly per gun color. Red and blue health onscreen of backwards but that's only because me blue is oneft side instead. I'll deal
sreisig1 Posted October 26, 2014 Posted October 26, 2014 What about the no nag and highscore now? And also my other question about switches all the info over to my MAME folder.
klizine Posted October 26, 2014 Posted October 26, 2014 Correction on the not shooting for second gun. Both guns working and reloading! Ill just have to make due with have my blue gun (left) having the red health due to how my control panel is setup.Now...how to get no nag and highscore. Also, for when I move everything from my test mame folder, when it comes to it should I just get rid of everything in my real mame folder and move the test folder stuff over? It's really up to you. But I would get rid of anything that hasn't worked up to this point. (Obviously don't junk your roms!) So I was hoping this "technique" worked for you, and I can't explain why Jumpstiles don't work for us... but now... You get to compile your own MAME!!!! I don't mind writing something up. It's not too hard, so give me a lil bit. ** To switch the player 1&2 you'd have to change the Device ID with the Aimtrak utility. both my guns are black, so It doesn't matter to me.
sreisig1 Posted October 26, 2014 Posted October 26, 2014 That would be awesome if you could compile one for me. Thanks man! I don't know how to do that
klizine Posted October 26, 2014 Posted October 26, 2014 That would be awesome if you could compile one for me. Thanks man! I don't know how to do that Give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime. But I'll do both. I'll post my 64bit version on my folder on the ftp...
sreisig1 Posted October 26, 2014 Posted October 26, 2014 Ok. So I swapped device Ids in the aimtrak utility. But when I hit tab in Mame, now they are gun 3 and 4 for some reason and still same colors for health and crosshairs. So pretty much, nothing switched. Just gun 3 and 4
Recommended Posts
Archived
This topic is now archived and is closed to further replies.