deadboy Posted December 9, 2011 Share Posted December 9, 2011 OK, first off Adultery's new plugin is sweet. Unfortunately it's exposed a problem for me.I'm running a machine with two displays, one over the other. Typically I run GameEx with Game Extender but this error crops up even when I load the game from a DOS prompt so I'll just talk about it from there.When I try to load any dual screen game on just one screen it runs fine.From here out the cmd line I am running is:mame64 punchout -numscreens 2 -logWhen I run the same game on two screens it runs ok, except the displays are reversed. Meaning what should be on the main screen is on the secondary screen.I can fix that thru the TAB menu in MAME from inside the game and it works fine till I close it.Next time I try to run any game with more than one screen MAME crashes as soon as I open it up. Just get the message saying Multiple Arcade Machine Emulator has experienced an unexpected error and has been shut down. The error.log file contains one line which says "Physical Height 1920 Physical Width 1080", which is of course the resolution to which my main display is set.I tried changing the resolution to every setting between 1920x1090 and 640x480. Same result with only the specifics numbers in the error.log being different.I've tried using command promts to force it to run at particular aspects/resolutions with the same result. I've run it with different -video options and aside from it looking crappier and running slower it doesn't seem to remember how I had the screens so it defaults back to the switched displays which, as I said, runs fine.Once I have set the screens to show on the correct display and the error starts the only way I can fix it is to run the mame64 -cc to reset the mame.iniAny help is greatly appreciated.Thanks. Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 9, 2011 Share Posted December 9, 2011 Please post your MAME.ini after a crash so I can see what's going on. Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 9, 2011 Author Share Posted December 9, 2011 Does it log information there? Dunno why it's not in the error.log... grumble grumble. I'll post it as soon as I get home.Thanks. Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 9, 2011 Author Share Posted December 9, 2011 Ok, here goes.Well, not permitted to upload the actual file so...From error.logPhysical width 1920, height 1080Mame.ini:## CORE CONFIGURATION OPTIONS#readconfig 1writeconfig 0## CORE SEARCH PATH OPTIONS#rompath romshashpath hashsamplepath samplesartpath artworkctrlrpath ctrlrinipath .;inifontpath .cheatpath cheatcrosshairpath crosshair## CORE OUTPUT DIRECTORY OPTIONS#cfg_directory cfgnvram_directory nvrammemcard_directory memcardinput_directory inpstate_directory stasnapshot_directory snapdiff_directory diffcomment_directory comments## CORE STATE/PLAYBACK OPTIONS#state autosave 0playback record mngwrite aviwrite wavwrite snapname %g/%isnapsize autosnapview internalburnin 0## CORE PERFORMANCE OPTIONS#autoframeskip 0frameskip 0seconds_to_run 0throttle 1sleep 1speed 1.0refreshspeed 0## CORE ROTATION OPTIONS#rotate 1ror 0rol 0autoror 0autorol 0flipx 0flipy 0## CORE ARTWORK OPTIONS#artwork_crop 0use_backdrops 1use_overlays 1use_bezels 1use_cpanels 1use_marquees 1## CORE SCREEN OPTIONS#brightness 1.0contrast 1.0gamma 1.0pause_brightness 0.65effect none## CORE VECTOR OPTIONS#antialias 1beam 1.0flicker 0## CORE SOUND OPTIONS#sound 1samplerate 48000samples 1volume 0## CORE INPUT OPTIONS#coin_lockout 1ctrlr mouse 0joystick 1lightgun 0multikeyboard 0multimouse 0steadykey 0offscreen_reload 0joystick_map autojoystick_deadzone 0.3joystick_saturation 0.85natural 0joystick_contradictory 0coin_impulse 0## CORE INPUT AUTOMATIC ENABLE OPTIONS#paddle_device keyboardadstick_device keyboardpedal_device keyboarddial_device keyboardtrackball_device keyboardlightgun_device keyboardpositional_device keyboardmouse_device mouse## CORE DEBUGGING OPTIONS#log 0verbose 0update_in_pause 0debug 0debugscript debug_internal 0## CORE MISC OPTIONS#bios cheat 0skip_gameinfo 0uifont defaultramsize confirm_quit 0## WINDOWS DEBUGGING OPTIONS#oslog 0watchdog 0debugger_font "Lucida Console"debugger_font_size 9## WINDOWS PERFORMANCE OPTIONS#priority 0multithreading 0numprocessors autoprofile 0bench 0## WINDOWS VIDEO OPTIONS#video d3dnumscreens 1window 0maximize 1keepaspect 1prescale 1waitvsync 0syncrefresh 0menu 0## DIRECTDRAW-SPECIFIC OPTIONS#hwstretch 1## DIRECT3D-SPECIFIC OPTIONS#d3dversion 9filter 1## DIRECT3D POST-PROCESSING OPTIONS#hlsl_enable 0hlslpath hlslhlsl_ini_read 0hlsl_ini_write 0hlslini %ghlsl_prescale_x 0hlsl_prescale_y 0hlsl_preset -1hlsl_write hlsl_snap_width 2048hlsl_snap_height 1536shadow_mask_alpha 0.0shadow_mask_texture aperture.pngshadow_mask_x_count 320shadow_mask_y_count 240shadow_mask_usize 0.09375shadow_mask_vsize 0.109375curvature 0.0pincushion 0.0scanline_alpha 0.0scanline_size 1.0scanline_height 0.7scanline_bright_scale 1.0scanline_bright_offset 0.0scanline_jitter 0.0defocus 0.0,0.0converge_x 0.0,0.0,0.0converge_y 0.0,0.0,0.0radial_converge_x 0.0,0.0,0.0radial_converge_y 0.0,0.0,0.0red_ratio 1.0,0.0,0.0grn_ratio 0.0,1.0,0.0blu_ratio 0.0,0.0,1.0saturation 1.0offset 0.0,0.0,0.0scale 1.0,1.0,1.0power 1.0,1.0,1.0floor 0.0,0.0,0.0phosphor_life 0.0,0.0,0.0yiq_enable 0yiq_cc 3.59754545yiq_a 0.5yiq_b 0.5yiq_o 0.0yiq_p 1.0yiq_n 1.0yiq_y 6.0yiq_i 1.2yiq_q 0.6yiq_scan_time 52.6yiq_phase_count 2## PER-WINDOW VIDEO OPTIONS#screen autoaspect autoresolution autoview autoscreen0 autoaspect0 autoresolution0 autoview0 autoscreen1 autoaspect1 autoresolution1 autoview1 autoscreen2 autoaspect2 autoresolution2 autoview2 autoscreen3 autoaspect3 autoresolution3 autoview3 auto## FULL SCREEN OPTIONS#triplebuffer 0switchres 0full_screen_brightness 1.0full_screen_contrast 1.0full_screen_gamma 1.0## WINDOWS SOUND OPTIONS#audio_latency 2## INPUT DEVICE OPTIONS#hide_cursor 1dual_lightgun 0 Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 10, 2011 Share Posted December 10, 2011 Hmm.. d3d problem? Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 10, 2011 Author Share Posted December 10, 2011 So you don't see anything in the .ini explaining why it's happening?I just can't figure out why it'll load with the displays set default and works with them switched but crashes when I've set them to load the otherway. I'd think if it was strictly a d3d thing it would fail when I switch them in game. I may try a different ver of MAME and see if it's just a proablem with this build. Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 10, 2011 Share Posted December 10, 2011 Well the only thing I see being an issue is it can't initialize your display properly. Can you run it on default and put up the log so I can do a quick comparison? Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 11, 2011 Author Share Posted December 11, 2011 default as in no command changes?## CORE CONFIGURATION OPTIONS#readconfig 1writeconfig 0## CORE SEARCH PATH OPTIONS#rompath romshashpath hashsamplepath samplesartpath artworkctrlrpath ctrlrinipath .;inifontpath .cheatpath cheatcrosshairpath crosshair## CORE OUTPUT DIRECTORY OPTIONS#cfg_directory cfgnvram_directory nvrammemcard_directory memcardinput_directory inpstate_directory stasnapshot_directory snapdiff_directory diffcomment_directory comments## CORE STATE/PLAYBACK OPTIONS#state autosave 0playback record mngwrite aviwrite wavwrite snapname %g/%isnapsize autosnapview internalburnin 0## CORE PERFORMANCE OPTIONS#autoframeskip 0frameskip 0seconds_to_run 0throttle 1sleep 1speed 1.0refreshspeed 0## CORE ROTATION OPTIONS#rotate 1ror 0rol 0autoror 0autorol 0flipx 0flipy 0## CORE ARTWORK OPTIONS#artwork_crop 0use_backdrops 1use_overlays 1use_bezels 1use_cpanels 1use_marquees 1## CORE SCREEN OPTIONS#brightness 1.0contrast 1.0gamma 1.0pause_brightness 0.65effect none## CORE VECTOR OPTIONS#antialias 1beam 1.0flicker 0## CORE SOUND OPTIONS#sound 1samplerate 48000samples 1volume 0## CORE INPUT OPTIONS#coin_lockout 1ctrlr mouse 0joystick 1lightgun 0multikeyboard 0multimouse 0steadykey 0offscreen_reload 0joystick_map autojoystick_deadzone 0.3joystick_saturation 0.85natural 0joystick_contradictory 0coin_impulse 0## CORE INPUT AUTOMATIC ENABLE OPTIONS#paddle_device keyboardadstick_device keyboardpedal_device keyboarddial_device keyboardtrackball_device keyboardlightgun_device keyboardpositional_device keyboardmouse_device mouse## CORE DEBUGGING OPTIONS#log 0verbose 0update_in_pause 0debug 0debugscript debug_internal 0## CORE MISC OPTIONS#bios cheat 0skip_gameinfo 0uifont defaultramsize confirm_quit 0## WINDOWS DEBUGGING OPTIONS#oslog 0watchdog 0debugger_font "Lucida Console"debugger_font_size 9## WINDOWS PERFORMANCE OPTIONS#priority 0multithreading 0numprocessors autoprofile 0bench 0## WINDOWS VIDEO OPTIONS#video d3dnumscreens 1window 0maximize 1keepaspect 1prescale 1waitvsync 0syncrefresh 0menu 0## DIRECTDRAW-SPECIFIC OPTIONS#hwstretch 1## DIRECT3D-SPECIFIC OPTIONS#d3dversion 9filter 1## DIRECT3D POST-PROCESSING OPTIONS#hlsl_enable 0hlslpath hlslhlsl_ini_read 0hlsl_ini_write 0hlslini %ghlsl_prescale_x 0hlsl_prescale_y 0hlsl_preset -1hlsl_write hlsl_snap_width 2048hlsl_snap_height 1536shadow_mask_alpha 0.0shadow_mask_texture aperture.pngshadow_mask_x_count 320shadow_mask_y_count 240shadow_mask_usize 0.09375shadow_mask_vsize 0.109375curvature 0.0pincushion 0.0scanline_alpha 0.0scanline_size 1.0scanline_height 0.7scanline_bright_scale 1.0scanline_bright_offset 0.0scanline_jitter 0.0defocus 0.0,0.0converge_x 0.0,0.0,0.0converge_y 0.0,0.0,0.0radial_converge_x 0.0,0.0,0.0radial_converge_y 0.0,0.0,0.0red_ratio 1.0,0.0,0.0grn_ratio 0.0,1.0,0.0blu_ratio 0.0,0.0,1.0saturation 1.0offset 0.0,0.0,0.0scale 1.0,1.0,1.0power 1.0,1.0,1.0floor 0.0,0.0,0.0phosphor_life 0.0,0.0,0.0yiq_enable 0yiq_cc 3.59754545yiq_a 0.5yiq_b 0.5yiq_o 0.0yiq_p 1.0yiq_n 1.0yiq_y 6.0yiq_i 1.2yiq_q 0.6yiq_scan_time 52.6yiq_phase_count 2## PER-WINDOW VIDEO OPTIONS#screen autoaspect autoresolution autoview autoscreen0 autoaspect0 autoresolution0 autoview0 autoscreen1 autoaspect1 autoresolution1 autoview1 autoscreen2 autoaspect2 autoresolution2 autoview2 autoscreen3 autoaspect3 autoresolution3 autoview3 auto## FULL SCREEN OPTIONS#triplebuffer 0switchres 0full_screen_brightness 1.0full_screen_contrast 1.0full_screen_gamma 1.0## WINDOWS SOUND OPTIONS#audio_latency 2## INPUT DEVICE OPTIONS#hide_cursor 1dual_lightgun 0The time stamp on the file doesnt reflect a change when I flip the displays but if I DONT flip them it has no prob with the -numscreens 2 switch.Very odd... Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 11, 2011 Share Posted December 11, 2011 So it's only games you had to change what displays on what monitor games, not all games? Like the -numscreens switch is crashing it only on games that use a single monitor, or like if you manually reassign a monitor? Sorry, I get lost easy. Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 11, 2011 Author Share Posted December 11, 2011 No worries. The only time it crashes is on games with multiple screens AFTER I've already successfully loaded them and switched the displays. The numscreens 2 itself doesnt kill it. If I leave the displays where the want to be (backards) then it never crashes. It's only after I tell screen 1 to display the video for screen 0 and vice versa. Even then it works fine till I shut down the game. Then the next time it crashes on load. Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 13, 2011 Share Posted December 13, 2011 Could you please try the latest version of the plugin and see if it fixes the problem? I rewrote the function that calls the command line.There was a whitespace bug I fixed. If it doesn't run the log in the MameCommander folder will show me what its running. Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 14, 2011 Author Share Posted December 14, 2011 Right now the system is down because I'm replacing the control panel with a new 4 player box. HOPEFULLY I'll have it up and running again in the next couple days.Did I make it clear that it's not your app? It does the same thing from a DOS prompt. I mean I REALLY appreciate the help, I just don't want you pulling out your hair thinking it's your plug-in messing up. Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 14, 2011 Share Posted December 14, 2011 You did but if I had extra blanks in the command line it would certainly cause a bug in GameEx (I'm kinda surprised no one noticed it actually). Tha at least will keep MC from fubaring your MAME integration. Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 19, 2011 Author Share Posted December 19, 2011 OK, my machine is back up and running and on a lark I opted to switch the inputs for the monitors, just to see if that did anything. It did. Now I can't load ANY game with the -numscreens 2 option. Even with a freshly made -cc mame.ini it crashes right off the bat. I'm now wondering if it's something it doesn't like with the particular monitor driver... Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 19, 2011 Author Share Posted December 19, 2011 Out of curiousity, is this correct syntax for specifying which display screen1 and screen2 go to?## PER-WINDOW VIDEO OPTIONS#screen autoaspect autoresolution autoview autoscreen0aspect0 autoresolution0 autoview0 autoscreen1 //.DISPLAY1aspect1 autoresolution1 autoview1 autoscreen2 //.DISPLAY0aspect2 autoresolution2 autoview2 autoscreen3 autoaspect3 autoresolution3 autoview3 auto Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 19, 2011 Share Posted December 19, 2011 Um... shouldn't that be DISPLAY1 & DISPLAY2? Windows monitor enumeration typically starts at 1 not 0. Is this what happens when you assign specific monitors in the tab menu? Quote Link to comment Share on other sites More sharing options...
deadboy Posted December 19, 2011 Author Share Posted December 19, 2011 Is it? I am trying to piece this stuff together from tidbits I find here and there. I'm a far better wirer and woodworker than I am coder so this is all kind of trial and error for me.so rather than //.DISPLAY0 it would just be DISPLAY1 and //.DISPLAY1 would be DISPLAY2? Quote Link to comment Share on other sites More sharing options...
Adultery Posted December 19, 2011 Share Posted December 19, 2011 Yeah I would try that first. If you want to see your display names you can also run mame.exe -verbose but unless you changed them yourself it's typically \.\\DISPLAY1 and \.\\DISPLAY2In games that I run two screens and want to flip the images (like PunchOut), I add this to the command line:-numscreens 2 -screen0 \.\\DISPLAY.1 -screen1 \.\\DISPLAY2If you output to \.\\DISPLAY0 my guess is that MAME can't find/initialize that display. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.