Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Robert

User Admin
  • Content Count

    11,945
  • Joined

  • Last visited

  • Days Won

    99

Robert last won the day on October 28

Robert had the most liked content!

Community Reputation

157 Excellent

About Robert

  • Rank
    Alchemist

Contact Methods

  • Website URL
    http://messui.polygonal-moogle.com/

Profile Information

  • Gender
    Male
  • Location
    Land of Oz

Recent Profile Visitors

4,452 profile views
  1. It just occurred to me that you might be a victim of a changed compile script. These don't get uploaded until release time, so you wouldn't have seen it. Here's the new lines that you wouldn't know about for messui. The reason for the lines about messvers.rc and mameui.rc is to force that stuff to be recompiled, since changes to mameui.rc are not normally detected. Also, mess does not need most of the code and icons that exist in messui, so reducing code bloat. The reason for the lines about messui.txt , mess.bak and mess.flt, is because messui only includes systems that work, not everything in mess. When compiling mess for command-line, here's the new lines The "touch" command is a unix-based command to update the "last-updated" time on a file to the current time. This causes the compiler to think the file has been updated and needs to be recompiled. Touch comes with the msys2 package, so you probably have it somewhere. If you compare ui.rc against uicl.rc, you'll see that ui.rc has the full list of menus and icons used in messui, where uicl.rc only has the menus for the NewUI. These compile changes need to be rolled out to HBMAME as well, but it hasn't been done yet. Hope this helps.
  2. I'll have a look at that. Things were changed around in messui recently. However this particular change was not done with mameui or hbmame; are you able to build and run them?
  3. Windows 10, 64 bit. It's a few months behind updates though. Not using 20H2 - I never use their bleeding-edge version, because of the bugs that they always seem to include. I'll most likely get the minimum of updates around end-of-year.
  4. I can only repeat that WinSXS should not be accessible to users. It's for system restores only, and for the TrustedInstaller. If you add command-line arguments, it causes the command-line version to run, that is normal. There's nothing more I can say, since I have not encountered this problem, and up till now, nobody else has either.
  5. The code already says InitCommonControlsEx. (mui_util.cpp, line 427, current git). I'm not sure about "DllInstall", but since it works for me it can't be an issue. Do the following: From the command line, do >mameui64 > x When it has started up (or in your case failed), exit back to the command line. >type x | find "controlversion" In my case it says Win32UI_init: Common controlversion 6 16 what does it say for you?
  6. * HBMAME 0.226.A [Arcade homebrew] - https://hbmame.1emulation.com/ * ZEsarUX 9.1 [Multi-system] - https://github.com/chernandezba/zesarux/releases * Cemu 1.22.0k [Wii-U] - http://cemu.info/ * GameEx 16.72 [Frontend] - https://www.gameex.com/news/ * uCON64 2.2.1 [Frontend] - https://ucon64.sourceforge.io/index.php * RomVault 3.2.0 [Rom Manager] - https://www.romvault.com/
  7. https://hbmame.1emulation.com What's new in HBMAME ==================== 2020-11-25 0.226.A - HBMAMEUI received lots of updates. New Games --------------------------------- - [sf2cemix] Street Fighter II': Champion Edition (Mix 0.96)
  8. I can only support what I build. See the notice at https://messui.1emulation.com/ You should tell your windows to use the comctl32.dll that is in c:\windows\system32. You might need to register the dll. On my system it says File version 5.82.18362.1139 and Product version 10.0.18362.1139 The things that are in winsxs are for system restores, and should not be accessible to the normal user.
  9. Robert

    MAME news

    If you change any settings for a game, they have to be saved somewhere so that MAME can pick them up when you run the game. Real frontends send a long string of command-line options, but since MAMEUI is actually joined to MAME, the settings get saved in the ini file instead. writeconfig is only for MAME, not MAMEUI. So, if you were playing the game, and you used the tab menu to change something, it won't get saved unless writeconfig is 1. But changing something in the MAMEUI properties will save it every time.
  10. * Emma 02 v1.37 [cosmac-based] - https://www.emma02.hobby-site.com/download.html * Romcenter 4.1.0 [Rom Manager] - http://www.romcenter.com/forum/viewforum.php?f=6 * Romulus 0.048 [Rom Manager] - https://romulus.cc/
  11. For reasons not yet determined, gmail users are not receiving the validation email. (Or maybe it's going to spam). Therefore staff will look for unvalidated gmail accounts, check that the email actually exists, and if all looks good, the account will be manually enabled. This process can take a few days, so don't just assume you'll never be able to talk here, have patience and try each day.
  12. Robert

    MAME news

    Nobody has reported issues with that. First I've heard of it.
  13. Robert

    MAME news

    The C++17 conversion was a complete success. Apart from a few minor errors all our builds compiled and ran perfectly well on Windows 10. This is what happens when proper testing is done - the implementation is painless.
  14. Robert

    MAME news

    Update... the change to C++17 just happened. It's not known yet how that affects us.
  15. Robert

    MAME news

    The release of 0.227 has been delayed. https://www.mamedev.org/?p=489 Most of that post is incomprehensible technical jargon to the average person, so let's make it simple. A change to the memory system was installed about 2 weeks ago, without any testing. It was therefore no surprise to find that many systems, particularly arcade ones, now crash at start. Or, if they started up, the graphics are bad, or the game doesn't work. Nobody knows how the new memory model works, but the logical approaches that should work no longer do, so it's now guesswork. Therefore it will take a long time to fix, or even identify many of the regressions. This also means that HBMAME cannot be kept up to date, as the new memory system breaks Neo-Geo. HBMAME is therefore on hold. MAMEDEV have released new tools for compiling - https://www.mamedev.org/tools/ In December, MAME will move to C++17. At this it is unknown what effects this may have, but it's possible that XP or 32-bit might no longer work. Another major change alluded to in the first link is that variables which by default are initialised to zero will be left at their random values, which could cause weird regressions. It's not sure when this will be done, but probably by Christmas. Now for some good news.... Major work has been done on WinUI (this is MESSUI and MAMEUI). All known bugs have been fixed. Many new adjustments have been added. Support for BGFX, OpenGL and GLSL shaders has been added. You can select plugins. The GLSL shaders that are part of the ARCADE64 package will be also supplied for all the other builds too. WinUI is no longer considered a development system, but as a production system. This means that the debugger controls have been removed. If a game had the debugger enabled, it will be deactivated at start, so the game runs normally. Some parts of WinUI have been deprecated. This means those parts are no longer supported, and will be removed soon, when convenient. Those parts are: - verbose.log and winui.log : These are leftover parts of the debugging environment, and are known to cause slowdowns - shortcut keys. These are a relic of a bygone age. Use your mouse. - inbuilt help. This hasn't been updated for about 20 years. Modern windows doesn't have any offline help, so WinUI will follow. All help text and files will be removed. - manufacturer cleanup. WinUI attempts to adjust the manufacturer names to overcome the variations on a theme from MAME. This will be removed, and the cleanup will need to be done in MAME instead. -- ARCADE64 has not yet received the upgrades, but it is planned. The M1FX button and option will be removed. One change that has been done is that the GLSL folder and support have been removed. The shader files now reside in the HLSL folder, the same as is done in WinUI. Note that ARCADE64 currently requires the shaders to be in the HLSL folder, where WinUI allows the shaders to be anywhere (although the HLSL folder is recommended). If you use ARCADE64 with shaders, you'll have to move the shaders from the GLSL folder to the HLSL folder. For those of you with 4k screens who are wondering when proper support will be added, all I can say is that I don't have a 4k screen, and have no plans on getting one. Further, I have no idea what programming is needed to add the support. However, https://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=350549&page=0&view=collapsed#Post388272 is supposed to work.
×
×
  • Create New...