scoodidabop Posted April 6, 2016 Posted April 6, 2016 Just upgraded from MAME 158 to 172 this morning to take advantage of the updates and MUCH better HLSL settings. There's a couple issues though. First off the .cfg files (all the button remapping I've done) don't seem to be working. For example I copied over my "mk2.cfg" from MAME 158\cfg into MAME 172\cfg and the button remappings aren't showing up in the 'tab' menu. One other problem is that vertical.ini seems to have no effect on maintaining proper aspect ratio on vertical titles (keepaspect 1). Any ideas on fixing these issues? Thanks!
kylecp1979 Posted April 6, 2016 Posted April 6, 2016 The new .172 suggest you make new .ini files. Here is a link with more details http://forum.mamedev.org/viewtopic.php?f=12&t=61
scoodidabop Posted April 6, 2016 Author Posted April 6, 2016 So I made new .ini files and they work fine on MAME standalone but Hyperlaunch is bypassing my system-specific and game-specific ini.s (ie: dkong.ini, namcos22.ini). I put Hyperlaunch in Legacy mode and that fixed my vertical.ini issue but the other types are still deffering to raster.ini (I think) for everything. All the .cfg files are working now. Seems to be no change in the code there, just a user error on my part.
gigapig Posted April 6, 2016 Posted April 6, 2016 So I made new .ini files and they work fine on MAME standalone but Hyperlaunch is bypassing my system-specific and game-specific ini.s (ie: dkong.ini, namcos22.ini). I put Hyperlaunch in Legacy mode and that fixed my vertical.ini issue but the other types are still deffering to raster.ini (I think) for everything. All the .cfg files are working now. Seems to be no change in the code there, just a user error on my part. I've not had any problem with hlsl only the new bgfx which does nothing so far in mame and mameuifx. Do you have the hlsl and video mode settings in the module set to ini or hlsl, d3d respectively?
scoodidabop Posted April 7, 2016 Author Posted April 7, 2016 I've not had any problem with hlsl only the new bgfx which does nothing so far in mame and mameuifx. Do you have the hlsl and video mode settings in the module set to ini or hlsl, d3d respectively? Here's what HyperLaunch is sending to MAME: mame64.exe vf -window -hlsl_enable -cheat -video d3d -artwork_crop -nouse_bezels -use_overlays -use_backdrops -nouse_cpanels -nouse_marquees -rompath Somehow that's skipping over game specific and system specific ini files. When I launch a MAME window and select a game within its UI everything works fine, so I know MAME has the necessary files. The game I'm testing is "Virtua Fighter"(vf.7z), in which I've decreased the "scanline screen height" since the model 1 games draw too many scanlines. I've tested a 'vf.ini' and a 'model1.ini' independently and successfully within standalone MAME. When I use HyperLaunch to launch vf.7z it looks like the hlsl settings are reverting to default, thereby ignoring/skipping the additional game/system specific ini. So it looks like the problem is coming from HyperLaunch but trying the various 'True/False/default' settings on everything in the module isn't helping. One other thing I just noticed - some games that work in standalone MAME don't launch in HyperLaunch. In this case "Gauntlet Dark Legacy" (gauntdl). I presume there's an issue with HyperLaunch fetching and assigning the right version. Is there any workaround for this? Also encountered the issue with "willow" but changing the XML to launch "willowu" fixed it.
gigapig Posted April 7, 2016 Posted April 7, 2016 Here's what HyperLaunch is sending to MAME: mame64.exe vf -window -hlsl_enable -cheat -video d3d -artwork_crop -nouse_bezels -use_overlays -use_backdrops -nouse_cpanels -nouse_marquees -rompath Somehow that's skipping over game specific and system specific ini files. When I launch a MAME window and select a game within its UI everything works fine, so I know MAME has the necessary files. The game I'm testing is "Virtua Fighter"(vf.7z), in which I've decreased the "scanline screen height" since the model 1 games draw too many scanlines. I've tested a 'vf.ini' and a 'model1.ini' independently and successfully within standalone MAME. When I use HyperLaunch to launch vf.7z it looks like the hlsl settings are reverting to default, thereby ignoring/skipping the additional game/system specific ini. So it looks like the problem is coming from HyperLaunch but trying the various 'True/False/default' settings on everything in the module isn't helping. One other thing I just noticed - some games that work in standalone MAME don't launch in HyperLaunch. In this case "Gauntlet Dark Legacy" (gauntdl). I presume there's an issue with HyperLaunch fetching and assigning the right version. Is there any workaround for this? Also encountered the issue with "willow" but changing the XML to launch "willowu" fixed it. First of all I can not get Gaunlet DL to work with 0.172, were 0.171 is fine. Game specific ini files. Mine initially did not work so I was thinking it was a RL issue but I then remember I had changed the ini path in the module settings because of the testing I'm doing. Setting the correct path fixed the issue. Here is what RL is sending to Mame. You mention HyperLaunch, is that what you are using? 18:20:27:080 | MD | INFO | +31 | Run - Running: J:\Roms and Emulators\Emulators\Mame 0.172\"mameuifx64.exe" darius -rompath "G:\Mame Roms;G:\Mame Roms" -window -inipath "J:\Roms and Emulators\Emulators\Mame 0.172\ini" -artwork_crop -nouse_bezels -use_overlays -use_backdrops -nouse_cpanels -nouse_marquees -nofilter -skip_gameinfo
scoodidabop Posted April 7, 2016 Author Posted April 7, 2016 First of all I can not get Gaunlet DL to work with 0.172, were 0.171 is fine. Game specific ini files. Mine initially did not work so I was thinking it was a RL issue but I then remember I had changed the ini path in the module settings because of the testing I'm doing. Setting the correct path fixed the issue. Here is what RL is sending to Mame. You mention HyperLaunch, is that what you are using? 18:20:27:080 | MD | INFO | +31 | Run - Running: J:\Roms and Emulators\Emulators\Mame 0.172\"mameuifx64.exe" darius -rompath "G:\Mame Roms;G:\Mame Roms" -window -inipath "J:\Roms and Emulators\Emulators\Mame 0.172\ini" -artwork_crop -nouse_bezels -use_overlays -use_backdrops -nouse_cpanels -nouse_marquees -nofilter -skip_gameinfo Yeah I'm using HyperLaunch. I did my entire Hyperspin setup right before RL came out and was satisfied enough with HL to not want to put time into a RL setup. So there's a way to change ini paths in the module setting in RL?
scoodidabop Posted April 11, 2016 Author Posted April 11, 2016 Grabbed some fresh roms for games that weren't working. It seems there are different versions of some games within the 7z and 172 acts appropriately when you update the rom. For example "forgottn" (Forgotten Worlds) and "willow" both have a couple versions in their 7z. My 158 roms weren't behaving for some reason despite the fact that they seemed exactly the same. Anyway Gauntlet Dark Legacy still isn't working from HL (works in MAME standalone) but Gauntlet Legends works now just fine with the updated roms/chds. One issue I noticed is that Sega X Board games aren't working in 172 - abuner, aburner2, a.b.cop, thunder blade and a couple others. As far as the .ini stuff - I think these newer MAME versions have a pecking order for the .ini files that I have to consider. With my system specific ini files I deleted everything but the HLSL settings from them and now they're being responsive.
scoodidabop Posted April 11, 2016 Author Posted April 11, 2016 Thanks for testing those, agent47. Retried all three x board games - now they're working! Seriously, wtf? Anyway I'm not sure what the problem was but we're good to go! Thanks for your help fellas.
Metalzoic Posted April 11, 2016 Posted April 11, 2016 Yeah, those games work for me to. Maybe a combination of not using a split set and the set being so old?
Styphelus Posted April 18, 2016 Posted April 18, 2016 I've not had any problem with hlsl only the new bgfx which does nothing so far in mame and mameuifx. Do you have the hlsl and video mode settings in the module set to ini or hlsl, d3d respectively? Hi Gigapig, Can you post your hlsl settings for 1.172. Can't get it to work. I just get a black screen.
kylecp1979 Posted April 18, 2016 Posted April 18, 2016 I could'nt get HLSL to work or 2 lightguns at the same time. Many others couldn't either. I guess this build of mame isn't very stable
Guest Posted April 18, 2016 Posted April 18, 2016 Make sure to generate a new MAME ini file guys when moving to 172. Backup existing mame.ini first. Then open command prompt, navigate to mame folder - then run 'mame.exe -cc'. Finally, open the new ini file and go through the settings, to get it to your liking. This is necessary as there have been major changes to the ini file in this latest version.
gigapig Posted April 18, 2016 Posted April 18, 2016 Hi Gigapig, Can you post your hlsl settings for 1.172. Can't get it to work. I just get a black screen. Here you go. mame.7z
Styphelus Posted April 18, 2016 Posted April 18, 2016 Here you go. mame.7z Thanks. Got it working in straight Mame but it refuses to work on MameUIFX I got from this site. It always gives me a black screen. I had to go to the official mameUIFX site and use that version. Also a word of caution. The new Mame 172 rom set replaces the aes.zip file. You won't be able to run Neo-Geo AES anymore so keep the old aes.zip bios file.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.