Jump to content
Welcome Guest!

Join us now to get access to all our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, and so, so much more. It's also quick and totally free, so what are you waiting for?

  • Announcements

    • thatman84

      Uploading Content   12/15/2017

      Please Read Before Uploading.... Thank You to everyone that shares their creations in the Upload Here section. There is some outstanding contributions to check out. Some simple things to help people find your content and admins to manage uploads. Post a topic in HyperStudio forum before uploading Upload to the correct Sub Section Use tags Please add details to your Title Good Title: -   World of Warcraft (PC Games) (16:9)
      Bad Title: -   World of Warcraft Aspect Ratio = (16:9), (16:9ST), (4:3)
      System = (Hyperlist Names)
      Details = Main Menu, System Default, +Wheel, Animated BG, Universal Theme.......
        Peace Out Thatman84


Sign in to follow this  

Everything else until we make a category for it.

83 files

  1. Instant Sheller

    A one click utility to change the windows shell to any application or front end and completely hide the windows environment.
    Use at your own risk, if you have problems post on the forum, but make sure you understand what you are doing here.
    What's New in Version 0.8 (See full changelog)
    •13th November 2012 - Version 0.8
    •◾A step forward with Windows 7. This version hides the Welcome.. and Shutting Down text
    The article below was taken from the MAMEworld forums, in case it ever becomes lost.
    In addition to the guide below I have developed a small application that automates all the process called InstantSheller. It allows you to one click shell GameEx or any other front end. It does “everything” in the guide below automatically. Its for Windows XP Service pack 2 and above, Vista and Windows 7 although for full functionality XP is required. It also requires the .net framework 2 service pack 1 or above. It now also features a one click ‘Undo’.
    Use at your own risk, if you have problems post on the forum, but make sure you understand what you are doing here.
    How to completely hide windows, and SHELL directly into a Front-End
    Okay, I finally succeeded in hiding windows completely this morning. I’ll give you a quick heads-up!
    The first thing that you need to do is get a CmdLine MAME up and running with a good FrontEnd. I use The Dragon King by Howard Castro (mainly coz’ it looks feckin’ awsome and it’s easy to skin! Also, it supports automated shutdown of Windows, YOU REALLY WANT THIS TO HIDE WINDOWS COMPLETELY!)
    I run this setup under WinXP Pro, simply because the USB support is second to none, you’ll find out what I mean if you stick an I-pac into it! NOTE: this quick guide assumes you are using XP Pro, if not I don’t really know how accurate it will be!
    Right, now you’ve got your actual emulator up and running, lets hide that OS!
    Right, now that’s outta’ the way, on with the show!
    Google for a cursor editing package (shareware will do, you’ll only be using it once!). Install and leave it for the time being. I used this one:

    There’s two ways to get ride of that bootscreen. Use a package designed for it, or make your own.
    1. The safest way is to get a program and screen from the net. If you’re not a fan of trial and serious error, this is the way to go, although if you create a custom skin for your FE, you may want them to match! Download BootSkin from Stardock:
    And get a decent skin. Either google, or try this one:

    After you install BootSkin, simply double click the downloaded skinfile and apply it. Simple!
    2. The second method. Caution, SCREW THIS UP AND YOU MAY BE LOOKING AT A REFORMAT! REMEMBER TO BACK UP YOUR NTOSKRNL FIRST! Now download and install BootEditor. This will give you your custom boot screen. Be aware that you will certain runtime files for this! One of them that I can remember off the top of my head is CMDCTL32.OCX I think. Run the program in compatablily mode for Win2K and any errors will be reported on screen, then just google for the files you need.
    **UPDATE** I Just DL’d Ultimard I-Pac utility, and it seems like all the runtime files you need come with it! Just download and install! **Update**
    To create your bootscreen you will need a decent art package. Believe it or not I use Ulead PhotoImpact. Okay, it’s cheap, but it does for most of the basic stuff! The instructions included with BootEditor (you’ll find a readme in the extracted folder, FOR GOD’S SAKE, PRINT, READ, AND READ AGAIN! This can really screw your system up if you cock up!)
    Once you’ve created an NTOSKRNL that you’re happy with (by the time you’ve got this far, you should know what I mean!), the only thing you have left to do is actually hide windows itself. Start by going into control panel\sounds and make sure that your default scheme is set to NOSOUND (silent). Open your cursor editor and create a cursor 1pixel in size, and in a dark colour (remember that you may need to be able too see it, a shade of gray will do). Export the cursor you’ve made with a name you can remeber, and place it in the \windows\cursors\ folder, we’ll be coming back to that later!
    Now we’re going to disable the startup\shutdown screens.
    Change from the default windows XP welcome screen to the older style by going to Control Panels>User Accounts>Change the way users logon or off. Deselect the “Use Welcome Screen” checkbox.
    To get rid of the startup and shutdown messages, enter regedit (Start>Run>Type “regedit” without the quotes.). Using the tree on the left, browse through to the following entry:
    HKEY_LOCAL_MACHINE >Software>Microsoft >Windows>CurrentVersion> Policies>System
    If there’s a DisableStatusMessages dword there, change it to 1, otherwise add it (right click, add dword) and change it to 1.
    Now you’ll have to change the background colour of the login screen. Even though you’ve disabled the login, the screen will still load up in blue as it laoding the personal settings. Again, this is a registry hack like before. Browse to the following entry:
    HKEY_USERS>.DEFAULT>Control Panel>Colors>Background
    The default value of this is an RGB value. For the sake of ease, if you change this to 0 0 0, you will get a black screen.
    While you’re in regedit, here’s the final hack:
    HKEY_CURRENT_USER \Software\Microsoft\Windows NT\CurrentVersion\Winlogon
    Look for a string entry called ‘Shell’. If it is not there, create a string entry and name it ‘Shell’. Set the value of this entry to the name and location of your Front-end. For Dragon King, the shell entry may be “C:\MAME\The Dragon King.exe” or wherever your Frontends executable is located. To repair this if anything happs, bbot via safe mode, go into regedit, and change this value to “explorer.exe”. When you reboot, you will find that you enter windows, and not your frontend! Simple!
    Right, now for the cursor! If this isn’t changed at the logon level, you’ll see the mouse cursor for around five seconds while windows loads your personal settings. This really spoils the effect! Download TweakUI:
    NOTE: I got a newer version of this from MS and it was missing the option that I needed!
    Once this is installed, go to Control Panel>Mouse>Pointers and change all of your cursors to the one that you created earlier. Save this scheme as “MAME Single Point Cursor Set” or something. Don’t apply this yet, it’ll make things bloody hard to do!
    Right, the last thing to do is finish off making the cursor invisible. Go back to the cursor screen in control panel, load your scheme and hit apply. It’ll be hard to see your cursor, which is why I left this till last! Squint your way into your start menu and open TweakUI. Go to the LOGON option, and somewhere there is the option to copy your wall paper etc. across to the Logon Screen. Hit apply and you’re done!
    Restart your machine, and you should no longer notice windows at all! The only thing that really gives it away is the status bar scrolling on the boot screen, but you can get rid of this using BootEditor, but I think it’s handy to have a guide as to whether or not the systems crashed! While you’re in the front end, if you need to revert back to windows, press CtrlAltDelete, enter the task manager (you will have you mouse back at this point, if you can see it, or simply use the keyboard), end your Frontends, click on New Task, and type in explorer.exe. Taa Daa! Windows! Simply navigate to control panel with your invisible cursor (once you hit the start
    button things get easier!), and change your scheme back to the windows deault! Do your maintenance, and restart the machine. Back into your FE! Y ou like!?!
    Well, that’s how I did it. I think that using TweakUI would be able to sort the screens out the same way as it did the mouse, but I haven’t tried it. If anybody has the time, creating something in VB to make this a ‘Tick The Box’ process should be quite easy I would have thought?
    Whilst most of this was put into my own words,I can’t take credit for most of this guide, I found it whilst trying to do the same thing myself! The links were all active at the time of writing this. The original guide can be found here, as well as a full WIP report for a scratch-built cab. It’s indispensible! Check it out, sign the guestbook, and tell ‘im Ritchie sent ya!
    If anyone has any corrections for this, PM me and I’ll edit the post, and give credit of course!



  2. Controller Mapper for JoyToKey

    I share here an Excel tool I made that helps creating JoyToKey config files for different systems. With this tool, you can configure JoyToKey profiles for up to 12 systems and 6 pairs of physical controllers for each system. It semi-automates the process, preparing the text for the cfg files.
    I have a cab with 2 Ultimarc U360s (each one as a joystick with 8 buttons), and I also have several retro usb controllers that I use with different emulated systems. This tool helped a lot in the tedious process of making the JoyToKey profiles for all the possible combinations of controllers - system.
    I attach in this post the instructions (also copied below), an example file in pdf, the actual Excel file (zipped), and the JoyToKey profiles and RetroArch config files that I use in the example.
    I hope you find it useful, please feel free to use it, improve or re-distribute it.
    PS: the spreadsheet is initially protected so you can only enter data in the allowed cells, you can unprotect in the Review pane, it has no password.
    With this spreadsheet, you can configure JoyToKey profiles for up to 12 systems and 6 pairs of physical controllers.
    Step 1: Configure Key bindings for each "System"
    First you should configure each emulated system, you can configure up to 12 systems.
    In the "Main" worksheet, between rows 1 and 27, you must complete 3 columns for each system.
    On the light gray column, you must specify which "Emulated Buttons" the system uses, and name them. On the Player 1 and 2 columns, you must enter which "Key" binds to each Emulated Button for players 1 and 2 in the selected System.
    E.g., for NES you need the Pad plus buttons "B", "A", "Select" and "Start". First enter the names of each "Emulated Button" on the light gray column (in this case, I chose "B", "A", "Select" and "Start"). Then enter which "Key" corresponds to each "Emulated Button" for each player in your designed emulator, for example in Retroarch in my case.
    The "Keys" you enter should match one of the available standard Windows keys, which you can find in the "Key Codes" worksheet. If you enter a "Key" that is not found, the cell will turn red. Look into "Key Codes" for the names I chose for each key.
    Step 2: Configure each "Physical Controller"
    Next you should configure each "Physical Controller", up to 6, in the "Main" worksheet, between columns A and D, rows 28 to 100.
    In my case I use Ultimarc's U360s with 8 buttons each for my arcade cabinet, Logitech F710, and some RetroLink imitation controllers and adapters.
    For each controller, you should name each "Physical Button" in column C, and enter in column D which actual button number it is. You can configure up to 10 buttons for each controller (plus the Pad), numbers 1 to 10. (Sorry if you need more!)
    To find out which number corresponds to each Physical Button, plug your controller, go to "Set up USB Game Controllers" in Windows, select the controller and go to "Properties". You should get to the window you see on the right. Then press each button and see which number lights up in this window.
    Here you can also optionally chose a button for each physical controller that will always work as "Escape" (in all systems) when pressed for more than half a second. You enter the "Escape button" number to the right of the controller name, on column D. Leave it blank if you do not want to use this feature.
    Each physical controller will use 2 Joystick tabs in JoyToKey, always the same number in all the system. In order for this to work, you should map each Physical controller to a Joystick Number in JoyToKey. With your joystick/s plugged, in JoyToKey got to "Settings", "Configure Joysticks", "2.Advanced Setting for each device". Then select your plugged joystick in "Please select a device", and "Specify a preferred number when this device is connected". Now JoyToKey will always assign the selected Joystick number when this device is selected. (This is stored in the JoyToKey.ini file)
    Step 3: Map each "Physical button" to each "Emulated Button"
    You then need to map each "Physical Button" of each "Physical Controller", to the different "Emulated Buttons" in each system. (the direction Pads are always mapped to the same keys)
    This is done between columns E and AN, rows 28 to 100. For each "System"-"Physical Controller" pair, you need to complete only the light gray column: enter the name of the "Emulated Button" that is assigned to each "Physical Button". The Keys the correspond to that Emulated Button are completed automatically.
    Step 4: Create the .cfg files.
    When you are finished mapping, you have to create the JoyToKey .cfg file for each system. This is a semi-automatic method.
    With RocketLauncherUI, create an empty JoyToKey Profile for each system (or emulator), and locate the file .cfg it creates. Then go the "JoyToKey cfg" spreadsheet, enter the system number (1-12) in cell C1, select column A (go to cell A1, and press Ctrl+Shift+↓), and copy paste into your .cfg file.
    Alternatively, you can print the "JoyToKey Maps" spreadsheet, and enter profiles manually.
    Works with JoyToKey v 5.7.
    Spreadsheets are protected for your convenience. If you want to Unprotect them, just go to the Review Pane in Excel and press "Unprotect Sheet". There is no password.



  3. UltraStik 360 Programmer

    I share a script I made for Rocket Launcher that programs UGC files (e.g 4-way, 8-way, 2-way, analog, etc.. ) to Ultimarc's UltraStik 360 Joysticks before launching a Rom, without requiring LedBlinky. It uses the User Function feature of RL. (Updated to new script language as of RocketLauncher v1.2, Jan-2017)
    (Note: RocketLauncher can now handle UltraStick directly from RLUI. However, it requires you to enter the profile for each system / game manually. The only advantage of this script is that it allows you the define the profile for each system / rom using a .ini file)
    UltraStik 360 Programmer
    You can define a different UGC file for each Rom or System. It also programs the Joysticks when you exit a Rom, allowing you to define a UGC file for the Front-end. UltraStik 360 Programmer can replace LedBlinky if you are using it only to program you U360s (as I was doing!).
    UGC files (UltraStik Game Configuration) tells the UltraMap.exe program which maps to download to which joysticks (numbered 1 to 4). For example, 4-way.ugc tells UltraMap to program the 4-way Map (4-way.um, located in the Maps subfolder of the UltraMap program folder) to both joysticks 1 and 2. In this pack I include 6 UGC files: 2-way, 2-way-vertical, 4-way, 4-way-diagonal, 8-way, analog.
    With the UltraStick 360 Programmer, you can specify a system (MAME, Nintendo Entertainment System, Atari 2600, etc..) to use a different UGC file per Rom (a "Per Rom System"), or to use the same UGC file for all roms. I include UGC files for most MAME games in the default ini file, with the default as 8-way.
    Copy "Global.ahk" to the "Rocket Launcher\Lib\User Functions" folder. WARNING: If you have other User Functions already programmed in User Functions.ahk, do not overwrite your file. You should edit it and add the code provided here. Copy "UltraStik 360 Programmer.ini" to the "Rocket Launcher\Lib\User Functions" folder Edit "UltraStik 360 Programmer.ini" to specify the location of the UltraMap software (in the UltraMapExe key). If you don't have it installed, please download it from http://www.ultimarc.com/ultrastik_prog.html and install it. By default, it installs itself in C:\Program Files (x86)\UltraMap. Copy the provided UGC files to the UltraMap program folder (in the same folder where UltraMap.exe is in). Also copy the Maps that are in the Maps folder to your UltraMap/Maps folder. Feel free to modify these UGC files with the UltraMap software. That's it, enjoy! You can further edit the ini file to better suit your needs
    Ini File
    In the ini file (UltraStik 360 Programmer.ini, located in Rocket Launcher\Lib) you define a global default UGC (typically 8-way). This UGC is used when there is no specified UGC for either the System or the Rom.
    In the [PerRomSystems] section of the ini file, enter "System Name"=true for systems that can have a different UGC files for each Rom. (e.g. MAME=true). If a system is a PerRomSystem, the script looks for a specific UGC for each Rom. If it does not find it, it looks for a default system UGC in the [systems] section. And if it does not find it either, it uses de global default UGC.
    In the [systems] section, enter the ugc file for each system (without quotes and without the .ugc extension, e.g. Nintendo Entertainment System=8-way). If the current System is a Per Rom System, this UGC will be used as default when no rom UGC is specified. If the current system is not a Per Rom System, this UGC will be loaded for all roms of the system. If a system is not specified in this section, UltraStik 360 Programmer will use the global default.
    The system "FrontEnd" is the system name assigned to the front end. This UGC is loaded each time you exit a rom.
    The system "Pause" is the system name assigned Rocket Launcher's Pause. This UGC is loaded each time you enter Pause. When exiting Pause the programmer reloads the Rom's UGC.
    In the [Roms] section, enter the UGC file for each rom, for all PerRomSystems (without quotes and without the .ugc extension, e.g. invaders=2-way). If a rom is not specified, the script will use the UGC given in Systems, or the global default.
    Credits: I used rom UGC configs prepared by EMDB for HyperMap (http://forum.arcadecontrols.com/inde...,134128.0.html), and took the main idea of this Programmer from byancey (http://forum.arcadecontrols.com/inde...tml#msg1483682). Thanks to both!
    Change History
    v2.0 - Compatible with RocketLauncher v1.2 (new location and scripting language)
    v1.01 - Works with RocketLauncher 1.01, takes advantage of the new Pause Features: StartPauseUserFeatures and StopPauseUserFeatures.



  4. Daemon Tools Lite

    Here you find version 10.2 of Daemon Tools Lite. Currently version 10.3 does not work with RocketLauncher.
    Care must be taken when installing this product as the "Free" version as it will install other software onto your PC.
    Please see the screen shots for the best way to install.
    Remember to set your DT Lite path in RocketLauncher UI to "C:\Program Files\DAEMON Tools Lite\DTAgent.exe" or wherever you installed it.



  5. MAME 0.165 x64 Hi Score + No Nag

    MAME x64 0.165 Hi Score + No Nag



  6. MAME 0.166 x64 Hi Score+No Nag+Direct Input

    Here is MAME 0.166 x64 Hi Score+No Nag+Direct Input



  7. mameuifx64 0.166 No Nag

    Here is mameuifx64 0.166 with No Nag



  8. mameuifx64 0.166 No Nag+light gun working

    mameuifx64 0.166 nonag + light gun sight ok with this one.



  9. MAME 0.167 x64 No Nag+Hi Score+Direct Input

    Here is MAME 0.167 x64 No Nag+Hi Score+Direct Input.



  10. mameuifx 0.167 x64 No Nag

    Here is mameuifx 0.167 x64 No Nag.



  11. MAMEuifx 0.169 no-nag, raw-input, 64bit

    MAMEuifx 0.169 no-nag, raw-input, 64bit
    didnt see one made so i uploaded mine to share



  12. mameuifx64 w/No Nag

    Here is mameuifx64 0.170.1



  13. MameUIFX 64bit + NoNag - Directinput

    Patched with forced Directinput and no nag screen with removed white windows



  14. Main Menu Changer

    New Version: Main Menu Changer [bETA 3]
    Now you can use the new MMCLauncher app to launch all your apps including HyperSpin, this fix various issues and is the recommended way to use MMC now.
    1- Edit MMCLauncher.ini with your Hyperspin path.
    2- Add more apps fallowing the same format if you need. This way the apps you need run once and not every time MMC relaunch HyperSpin.
    3- Delete any app from HyperHQ startup app. (Yes, quit killExplorer as start app And let MMCExit as exit app)
    4- Run MMCLauncher every time you need to run HyperSpin, so all needed operations like changing wallpaper or kill Explorer.exe, occur before Hyperspin launch.
    This change is not present it Video Tutorials or other Documents, so the old setups are still possible for retro-compativility.
    If you setup is working fine, don't touch it
    Windows 10 aparently don't need Wallpaperchange enabled, just RestoreExplorer will kill windows explorer and hidde the wallpaper.
    This app lets you change your main menu, filtering the entries stored in one XML file and allow you to create multiple level setups (HyperSpin allows a 2 leves setup normally).

    Note: The setup and MMCHQ part of the program needs more testing, as the version says it's still BETA, please fallow the setup tutorials and report any problems in the support topic.
    This app Works in 3 modes:
    MODE 1 - Normal Mode:
    A subwheel contains all the Filter Items, you can chose to Close Hyperspin Automatically or just configure the Main Menu with the selected filter and go back manually using normal FE controls.

    MODE 2 - SubWheels Mode:
    The filters are in the main menu Wheel and HS is closed and open again to load the results of the filtering process. You must scroll until you found a "BACK" item that will lead you to the previous main menu.
    MODE 3 - SubWheels Mode with NO "BACK" entry:
    The filters are in the main menu Wheel and HS is closed and open again to load the results of the filtering process. You can use the Frontend back key to go back, no special item need to be added to databases.

    What's New
    MainMenuChanger HQ: New app that let you edit xml files with diffrent apps and take care of save the modifications to the correct places.
    MainMenuChanger "First Run" Wizard: If you are making a new install of MMC, the app will copy the necesary files and tell you what needs to be done to make MainMenuCHanger work.
    Wallpaper Change: Change the wallpaper by a black one and back to a file of your choise on HS launch/close.
    Ini version check: If you are updating from 2016-04-04 version, the new ini options will be added and, so you current ini should work with this 0.0.1 version.
    Wheels and art included (Some wheels by spotUP)

    Download MainMenuChanger_0.0.1.1_BETA.7z For all setup modes. Set Antivirus exeptions. Set all exes included to run with administrator provileges (right click -> propieties -> compativility -> run as administrator) Set all exes as secure (in propieties) so Windows dont ask before execute any of them. [*]Mode 1 and 2 have diffrent video tutorials.
    Mode 3 setup is almost identical to mode 2 with the fallowing diferences:
    In settings you must select mode 3, not mode 2 ( ) In setings you must set RestoreExplorer to True (This kills and restore windows explorer to avoid the desktop to flash for a seccond when you go back a level of wheels) Optionally you can set the option WallpaperCHange to true to change you wallpaper to a black one on HS launch.  

    Mode 3 Tutorial (By maabus)
    Here is a text based instructions on how to setup sub wheels in Mode 3 with no back button. I only went over one level of wheels and sub wheels, and one category. Just follow the steps again to add more. It looks like a lot of work, but it really isn't. It should only take about 5 minutes to setup at least on category. I tried to explain what everything does to my understanding so that also added to the length of the instructions. Try out the instructions and let me know if anything is not clear.



  15. RocketBlinky

    RocketBlinky is a 3rd-party tool that can, in a matter of minutes, auto-generate an LEDBlinkyControls.xml supporting over 160 HyperSpin systems. Translation: It takes 99% of the work out of setting up LEDBlinky.
    Demo Video:



  16. Killer Instinct Windows 10 bat to exe launcher

    This isn't anything special but I took the liberty of creating a bat file that will launch Killer Instinct and converted it to an exe which will work for the PC Launcher in RL. Or at least it should. I've tested the exe many times and it launches as expected. I REALLY hate metro/modern apps.



  17. MameUIFX 64bit + NoNag - Raw-input 0.172.1

    patched with no nag and updated to 0.172.1



  18. Mame .173 64bit + NoNag + Hi-score + Forced Directinput

    64bit MAME 173 patched with no-nag, no white windows, hi-score and forced direct input. Couple of key items with this release:
    MAME has once again updated files in the installation package, specifically in the "plugin" directory. As such, just overwriting your old pre-v173 mame64.exe with this new one will cause a lua script error at boot. At the very least, you must install the 173 package from the mamedev site, then overwrite your mame64.exe with the one included here. The mame.ini file has ALSO changed AGAIN, with some mame-induced changes and some from the no-nag patch, so re-create it with a mame64 -cc command and adjust accordingly if you don't like the included one. Remember, too, that the HLSL settings for raster and vector games (which covers just about every arcade game ever made) are in the "presets" folder. Changing them in the mame.ini won't do much, as the presets "raster.ini" and "vector.ini" take priority over any common settings. A "hi" folder must be created for your high-score storage, and a "hiscore.dat" must be placed in the MAME root directory.
    To help make this even easier, and based on some requests last time I posted this, I zipped the entire package for you and it's ready to go as-is. NO ROMS INCLUDED, OF COURSE. Unzip it somewhere safe, populate it with the contents of your current artwork, cfg, nvram, diff, roms, and preset folders and you're off and running. MY HLSL settings are here in their full glory if you want them, or trash them and use your own - what ever you prefer. If you've slaved over your current video settings to get them "just right" or like BGFX, then don't use my preset folder, generate a new mame.ini with the 173 mame64.exe and populate manually it as needed with your current mame.ini contents.
    2 Last things:
    I had some requests after my v172 post to compile versions with raw input, or in 32bit. I'll be honest - I compile this for my system and dinput/64 bit is what I got. 'Nuff said.
    Secondly - I'm not a huge fan of this release. I actually had to pull the folder from my recycle bin after reading a post discussing the release earlier. IM(Humble)O, there are few reasons to upgrade from 172, and the speed of 173 seems to be slightly slower (about 1% on average) on the most demanding roms. I use mmpork, ibara, and pinkswts to test the speed of the emulator, and typically come in at 99% with v172. v173 is coming in about 98%, even with autoframeskip enabled, etc. I would COPY your critical folders to this version, then test a few roms with it before fully committing to it. If you've got an older system and you're a classic arcade purist, you won't care because you're not rocking CAVE roms, anyway. And you've got a banging MAME PC, then you won't care, either. My mame setup uses a Core i5 with 8g ram and a GTX 560 Ti graphics card. Not a gaming rig, but no slouch, either. So bear this in mind before you upgrade. And if 173 works great for you, that's great. EDIT - After running this on a similar PC with a slightly faster CPU (Core i5 3.3g vs Core i5 2.5g), I couldn't get any of my three test roms to drop below 100% emulation with the setting included in the DL. So no worries if your PC is decent.
    Final parting thought - BACK UP YOUR CURRENT MAME FOLDER AND COPY THE KEY FOLDERS INTO THE ATTACHED VERSION, NOT THE OTHER WAY AROUND. The only folder I DIDN'T do this with was my roms folder, as it's WAY too big. That way, you get a working version AND there's no risk of losing hard work.



  19. MameUIFX 64bit + NoNag - Raw-input 0.173

    no nag code added,
    must be install over a fresh install of 0.173 setup, NO PREVIOUS INSTALL can be used
    - Added support for all core options related to INTEGER SCALING in the GUI
    - Added support for all ProgettoSnaps screenshot packages in the GUI
    - Increased refresh rate in Nebulas Ray to "fix with an hack" MAMETESTERS bug ID 3488 [dany777]



  20. MameUIFX 64bit + NoNag - Directinput

    patch with no nag, replace original exe on the fresh install of mameuifx 0.174.1



  21. Mame .174 64bit + NoNag + Hi-score + Forced Directinput

    64bit MAME 174 patched with no-nag, no white windows, hi-score and forced direct input. Key items with this release:
    I promised an emailer earlier that I would put this out, and if I say I'm going to do it...it's gonna happen. So here it is. PLEASE stop asking for x86 versions, MAMEUIFX, etc. My rig doesn't use either one, so I don't compile them. Not being a jerk (at least, not deliberately).
    The good news:
    I don't THINK you need to update your file structure with this release. So you should be able to just overwrite your MAME 173 with the attached .exe and you're off and running. If you're upgrading from 172 or prior, do a full install from the MAME DEV website, then the overwrite the main program with the attached .exe. You might want to back up your mame.ini file and generate a new one, as the nonag diff used for 174 is much more integrated and KISS than ever before. EDIT - Skipgameinfo needs to be set to "1" in the mame.ini for all messages to be suppressed. The nonag allows you to keep the gameinfo if you still want it, but removes the "click OK or go LR" dialogue.
    The bad news?:
    On a minor note, the HLSL programming has changed, AGAIN. So the video settings you tweaked for hours to get "just right" might not look exactly the way they did in 173. The description of the changes was accidentally left out of the "whatsnew" file for this version, but can be seen at the very bottom of the Change Log below. Apparently one of the devs forgot to update that part of the .txt file when it was sent out to the dev team 2 days prior to release date. Not saying the changes are bad - it's just that your screen might not look exactly the same as it did in 173. If you're using 172 or earlier, you should already know the new file structure has completely changed the way HLSL settings are handled. Read my 172 or 173 download descriptions for more details on that.
    6/8/2016 - IMPORTANT EDIT - The post.fx file in this release had an error that has since been corrected in the .git. Not my fault - it was part of the 174 source. MAME devs have since corrected the error and uploaded it to github. But if you don't want to wait for 175, I've already gotten it for you. It's now included as a second attachment - just overwrite the 174 post.fx file in the HLSL directory with this one and you're GTG.
    On a major note...
    Oh I'll just come out and say it... Who really cares about this release? It's not faster. If anything, the restructuring of the drivers, carts, etc continues to slow down the emulation. YES, I KNOW IT'S MORE ACCURATE TO THE WAY THE REAL HARDWARE WORKS. But when you just want to play the games do you really care?
    And what's new? MINOR bug fixes. Yet another incredibly-obscure title that now works on the Tiger Game handheld MESS emu and some improvements to the Apple 2 driver? More clones added? The improvement to Golden Tee Fore is notable, but it's really just a fix from the break that occurred from 172 to 173. The better support for DirectInput 8 is great and appreciated, but if your rig already works you don't care about this.
    The work on the MAME project is vast, requiring hundreds, perhaps thousands, of man-hours to produce. And to think of how far it's come in the last few years...astonishing. As a simple end-user, I am humbled and grateful to the MAME dev team. But guys...how about fixing Sega Model 1? Virtua Fighter is still broken. YEAH, IT RUNS, but look at it - shameful. HydroThunder? Or get Sammy Atomiswave / Naomi / Sega Model 2 to play at full speed? Who doesn't love some Capcom VS SNK? MetalliC over at Demul has done an EXCELLENT job with some of these. And Bart and Ian dev-ing Sega Model 3 over at SuperModel continue to pioneer development in the true spirit of bringing old games back to life.
    I told my emailer I wouldn't rant on this post, but it has to be said. This compile works great, so feel free to use it. And if you're using 173 already, I guess there's really no reason not to upgrade aside from the potential HLSL issues and romset updating. But personally, I'm still using 172 and couldn't be happier.



  22. Arcade64 0.177 *Reborn Mameuifx*

    first release of the project thanks to Robert for continuing where Mamesick has left off. Mamesick is not gone but just not greatly active
    this has my personal patching for no nag



  23. Mame v0179 no nag screen

    here is anther mame0.179 update no nag screen
    hope you enjoy this .



  24. Lightgun-MameUIFX-0166_No_Nag-No_MSG

    includes preset main files setup for lightguns.. with the compiled MameUIFX mods
    Important note: do not enable dual lightgun; it will actually disable 2x lightgun if turned on



  25. MAME 0.168 x64 No Nag+Direct Input+Hi Score

    Here is MAME 0.168 x64 No Nag+Direct Input+Hi Score



Sign in to follow this  
  • Recently Browsing   0 members

    No registered users viewing this page.