MadK9
-
Posts
554 -
Joined
-
Days Won
13
Recent Profile Visitors
7,198 profile views
MadK9's Achievements
64-Bit Supercomputer (6/7)
766
Reputation
-
You might want to use the waspi mode though, as the sound quality is so much better, and its one of the main features of mame 0.278
-
edit your mame.ini file, find 'sound auto' (around line 329'ish) and change the auto to xaudio2, save and retry. (you need to have DX9 runtimes installed) If you want to use waspi you may need to turn off exclusive mode. Press WIN+R and type control.exe mmsys.cpl sounds press enter. select your sound output device and in the bottom right click properties then the advanced tab. In the exclusive mode settings turn off the 2nd option
-
Mame No-Nag Updated Monthly, Current Version:
MadK9 commented on MadK9's file in Third-party Apps and Plugins
Just try it, i have never used/tried the Linux version so i cant say for sure it will work, but that is the main file i edit for the windows version, i do edit some other files but thats just to add support back for 2 games that were removed. Just be aware that edit is old, just get the latest diff (this could be an older version than current, but the edits are the same, but you will need to adjust the locations accordingly for each edit. -
Mame No-Nag Updated Monthly, Current Version:
MadK9 commented on MadK9's file in Third-party Apps and Plugins
I cant take the credit im afraid, it was @JoeViking245's sleuthing that found the link. -
Mame No-Nag Updated Monthly, Current Version:
MadK9 commented on MadK9's file in Third-party Apps and Plugins
We have the answer MameUI has this set and others may as well, they do it via video.cpp "str != 0, we check for str > 1" .and its a simple on/off affair. With no user feedback. So its just another no nag. The offical mame will never do it, with my version of the no-nag the nag isn't removed its moved into the esc menu, so people can still see warning information, along with the removal of the init scree for some games. Cant say i have ever used another mame thats not official/source. so its a nice catch none the less/ Heres Roberts take on it. https://www.1emulation.com/forums/topic/36827-nonag/ -
Mame No-Nag Updated Monthly, Current Version:
MadK9 commented on MadK9's file in Third-party Apps and Plugins
If you go back through my posts/versions of the no nag uploads you will find what i edit, im pretty sure the edits for linux will be the exact same, all you will need to do is then compile for linux. -
Mame No-Nag Updated Monthly, Current Version:
MadK9 commented on MadK9's file in Third-party Apps and Plugins
Can't say i have ever heard of that working like that, but if it did/does its a bonus. But i really cant see it removing hard nags. iirc mame does have a feature where nags are disabled for i think 5-7 days once you have seen it for the game you select to play (if a warning is to be shown) but will still return no matter what, and only works on the games with warnings. Also to add the no nag removes the initialising screen as well. But nice catch if that did work/does work on your currnet build. -
Mame No-Nag Updated Monthly, Current Version:
MadK9 commented on MadK9's file in Third-party Apps and Plugins
I used to do the UI version as well awhile back, but the download numbers were sometimes single digits to zero, i don't feel there just isn't any reason to use it if you are using Launchbox to launch games, i personally just use the inbuilt ui it does what i need. Unless of course you are using the UI version for overclocking. Its not a lot of effort, its just time consuming and ties up the computer for an hour while compiling. Maybe someone else can do the UI version, i have left instructions on how to compile the source in a number of the no-nag threads, its not much different to standard mame, just a small change to the ui.cpp iirc. -
And please re copy the device from the cmd line, i typed that in at like 4am, so it may not be correct, better to get it from your cmd line to be sure.
-
GUN #1 = VID_0483&PID_5750&MI_00&Col01#8&38255be8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} for Gun #1 GUN #2 = VID_0483&PID_5751&MI_00&Col01#9&23770f6c&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} for Gun ##2 so it would be something like the following for GUN #1 <mapdevice device"VID_0483&PID_5750&MI_00&Col01#8&38255be8&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}" controller="GUNCODE_x" /> set x to what button you are using, repeat this line for every button you set on this gun just change X. In your screen shot you can see Joystick 1 and Joystick 3 are your LIghtGuns, so you can also use the Device ID there so you would copy from the 3A-3H to the end of the line, do not include the close bracket at the end. so it would be something like <mapdevice device="3A-3H Retro Shooter 1 product_57500483-0000-0000-0000-594944564944 instance_d13114f0-de41-11ef-8001-4445535400000" controller=GUNCODE_x" /> again set set x to what button you are using (Please copy n' paste this ID from you cmd line again, just highlight the text you want and right click, then ctrl+v where you want it.
-
You are missing a lot of the info mame needs. Open a cmd prompt in the mame folder and make sure your controllers are on. In the cmd prompt just type mame -v and press enter, this will list all devices mame can see and use, find your controller(s) and it will give you the devicemap name you need to use. eg. here you can see my Dual Sense mame sees and can use so my map device would be <mapdevice device="DualSense Wireless Controller product_0ce6054c-0000-0000-0000-504944564944 instance_3ce5b550-d1ce-11ef-8001-444553540000" controller="JOYCODE_5" /> (Change the last part to what you are applying it for (GUNCODE/JOYCODE/KEYBOARDCODE and so on) if you look at the light gun 1 in my pic, you can use <mapdevice device>"VID_046D&PID_C539&MI_01&Col01#9&3433e605&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}" controller=GUNCODE 2" /> and this would also work Hope this helps. As an addition, not every device will have a VID/PID listed from mame, but you could also use them as well, goto Device mananger, find you device and right click for properties and goto either Details, and select Hardware IDs or goto Events and check the information widow (Details can be right click copied, Event can be highlighted and Copied)....
-
They are not equal versions of mame, one is built explicitly for your CRT needs, one is stock mame, so im trying to understand what your actually asking, as having a tearing issue is not a fault of mame, using the wrong version of mame for your environment will not give you an answer other than what you already have.
-
Groovymame is built for CRT's, if this is the version you require then i suggest downloading groovymame no nag. My builds are always stock versions of mame, there are no changes other than removal of nag screens. As @JoeViking245 mentioned the version you are using is also 4 years out of date.
-
Mame No-Nag Updated Monthly, Current Version:
MadK9 commented on MadK9's file in Third-party Apps and Plugins
Some have replied to you with the solution, if you are still seeing this same 'Press any Key' screen then you need to have skip_gameinfo either in the LaunchBox Launch options for mame or manually set the "skip_gameinfo 1" in the mame.ini file, that is an internal command for mame itself to directly skip the Press any Key screen, this no-nag does not touch that screen or its functions. If you scroll back a few posts here you will see what this no-nag actually does.
