StHiryu

All fixed with your later commits. Big Thanks!!!!

Corrected the comma for the semi-colon, was a typo in the post. The relative paths in swpath worked until 270, is in 271 when are crashing. Actually setting paths via mameui gui also crashes the emu too, so will try in another computer if the behaviour is the same.. Edit: Tried in another computer with fresh install. The swpath is completely broken. Anyway don't mind, I'll use the command line.

Setting relative paths in ini files crashes the emu when selecting affected system. For example megadrive PAL at megadriv.ini: swpath ..\..\MegaDrive This feature worked fine in 0.270. Also trying to set up a software path from software tab in gui freezes the emu. EDIT: After more testing, seems some changed in latest mame about managing sw list paths. If you set at mame.ini: swpath software TO swpath null the emu won't crash, but mame couldn't find the sw files anymore. Another fix is the set the megadriv.ini to: swpath software;..\..\MegaDrive But the emu only will look at the software folder... Actually I'm launching games via command line.

MAME, WOLFMAME AND MAMEUI 0.271 32bit available (Xp compatible). Download from: RETRODANUART MAME XP

I've been busy the last months, but some releases ago I've reported a bug about the behaviour of the mouse pointer when using windowed mode, so I will report again with more detail: And again I remark is not intended behaviour, it's a bug since it works fine in mame. If you set at your mame.ini the following options: # # OSD VIDEO OPTIONS # window 1 # # OSD INPUT OPTIONS # mouseprovider win32 When the game is launched with win32, the window captures the pointer, making it no visible and letting you control the gun crosshair (In this example with Operation Wolf). Has been this way in mame and mameui forever, but since some releases ago, MameUI doesn't capture the mouse pointer, making the game unplayable with that devide since you can't move the gun crosshair. It's the same behaviour like setting mouseprovider to dinput. I provide this little video as a example launching the game in both mame and mameui 0.270 versions. https://www.mediafire.com/file/4ql6omgyebblw6l/MameAndMameUIMousePointer.mp4/file

MAME, WOLFMAME AND MAMEUI 0.270 32bit available (Xp compatible). Download from: RETRODANUART MAME XP

MAME, WOLFMAME AND MAMEUI 0.269 32bit available (Xp compatible). Download from: RETRODANUART MAME XP

MAME, WOLFMAME AND MAMEUI 0.268 32bit available (Xp compatible). Download from: RETRODANUART MAME XP

MAME, WOLFMAME AND MAMEUI 0.267 32bit available (Xp compatible). Download from: RETRODANUART MAME XP

HBMAME and HBMAMEUI 0.245.20 32bit avaliable (Xp compatible). Download from: RETRODANUART MAME XP

MAME, WOLFMAME AND MAMEUI 0.266 32bit available (Xp compatible). Download from: RETRODANUART MAME XP

HBMAME and HBMAMEUI 0.245.19 32bit avaliable (Xp compatible). Download from: RETRODANUART MAME XP

MAME, WOLFMAME AND MAMEUI 0.265 32bit available (Xp compatible). Download from: RETRODANUART MAME XP

Yes it's intentional since some releases ago, but using win32 as userprovider it hides. Still works in the normal mame and worked that way in 264 mameui. Know that Happ was messing around with the mouse pointer, so who knows... Anyway, anyone can confirm the controls for mouse are working properly in shooting games like operation wolf? Edit: Can't move the crosshair in mame, so it's a mame bug too...

Noticed what it seems a little bug in Mameui. The mouse pointer does not hide anymore when entering windowed mode using mouseprovider win32. Also the mouse is nos synced with the crosshair in games like Operation Wolf or Crossbow.