Jump to content

MESSUI and MAMEUI 0.190 released


Robert

Recommended Posts

MESSUI 0.190 and MAMEUI 0.190 have been released and are available at the usual place:

 

http://messui.1emulation.com/

 

 

There's no release of HBMAME.

 

 

Changes:

- Lots of work was done to reduce the number of crashes that came with the last few builds.

- Fixed crash when selecting a new background (even when you hit Cancel)

- Fixed crash when unexpected data was found in mameui.ini and mame_g.ini

- Fixed problem where the last machine you had chosen wasn't remembered

- Fixed problem where it didn't remember which software tab you had chosen

- Fixed problem with splitters going crazy when trying to adjust window sizes

- Fixed problem with hide/unhide of the software area not synchronised with the setting

- The new default window size is to fill most of the screen - whatever size it is.

- You can right-click on a game and play the AntoPisa movie mp4 on your default mp4 program

- You can right-click on a game and open the PDF with your default PDF reader program

- 10 of the treeview folders (BIOS, CPU, Dumping, Manufacturer, Refresh, Resolution, Screen, Sound, Source and Year) have been made external. MAMEUI will refresh them as part of the caching process. They are stored in the folders directory.

 

 

Note:

- Unable to replicate a reported problem where softlists wouldn't show

- Unable to replicate a reported problem with fullscreen

- The new external folders (ini files) can be used as extra filters in MAME's internal UI.

- If weird stuff happens on the first run of 0.190, try deleting mame_g.ini

- Please report all bugs and crashes (especially new ones) in this thread.

Link to comment
Share on other sites

I'm facing the same trouble. The splitters walk. Every time I start and close the app, the second and third value of "splitters 152,744,1103" increase.

 

 

- Unable to replicate a reported problem with fullscreen

 

Maybe I gave you little information. Windows 10, 1920x1080 and 125% display scaling. I think that the problem is with d3d because if I change video config from auto to bgfx it works in fullscreen. My config is "video auto, window 1 and menu 1" and it works perfectly, then I hit "alt+enter" and see a white screen with the menu but if I hit "alt+enter" again it goes back well. If I start with "video auto, window 0 and menu 1" some errors are displayed about direct3d.

Link to comment
Share on other sites

It sounds more like a problem with MAME rather than MAMEUI. What happens if you turn display scaling off? I think there's a MT bug logged about that.

 

 

With the splitters, I entered the values you gave into my mameui.ini, started then quit MAMEUI, and the values did not change. So, unable to confirm.

 

Splitters can be affected by the parameters starting with window_. Do they change too?

Link to comment
Share on other sites

I think Windows itself expands the splitters when you maximise, but doesn't restore them when you un-maximise.

 

 

Now I finally had a bug reported, that being most vertical games are showing as horizontal. This has now been fixed.

Link to comment
Share on other sites

Another one: When you pick one game from SW files or Media View tab and you launch it (for example shinobi and then Master system II), when you exit the emu the game remains in the slot and you can play again launching the system. However, if you do the same with the option "File, Play and record.....avi ouput", after exitting the emu, the game is removed and you need to select it again...

Link to comment
Share on other sites

Well, I was trying and testing different configurations last weekend and

 

I think Windows itself expands the splitters when you maximise, but doesn't restore them when you un-maximise.

 

 

yes, I see that if you start/close the app maximased the splitters "walk"

 

 

It sounds more like a problem with MAME rather than MAMEUI. What happens if you turn display scaling off? I think there's a MT bug logged about that.

 

 

No, MAME works "well" (talking about this). Other thing is some emulation marked as good like cpc??? (it freezes & crashes if you load and run"***** a game, or use the command 'cat' after loading the disc, doesn't matter whether you load it with MessUI swlist panel or in-app MAME TAB menu).

 

Well, talking about the scaling, MAME works well. I guess it bypasses the DPI scaling when executing a game in full-screen mode. The problem is that if I check "override high dpi scaling behavior" for MessUI/MameUI no errors about Direct3D 9 (unable to create device or not initialised) are shown when executing a system/game but the front-end interface becomes almost impossible to be used, small buttons/icons, etc.

 

 

PS Watching the event viewer errors I realised that MessUI/MameUI internal version is 0.189 and if you put the mouse over the *.exe is shown as well.

Link to comment
Share on other sites

The cpc problem was a bug in MAME, which has since been fixed. http://mametesters.org/view.php?id=6689

 

I don't have a 4k monitor, and I don't use Windows 10, and I don't know anything about DPI scaling or what I might do to use it. So, there's nothing I can do there.

You might be better off with another front end.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...