MAMEWorld >> EmuChat
View all threads Index   Flat Mode Flat  

uman
MAME Fan
Reged: 04/15/12
Posts: 455
Send PM
Re: Apparent Direct 3d bug in mame64 202 (non patched)
10/09/18 01:46 AM


> This is nothing to do with inis tho. This is literally the updated HLSL folder, that
> is essential for the new version to work, not being extracted even if we ship it and
> don't provide any way for people to not extract it without jumping through the hoops
> to extract only a single file (yet for any other situations people find the smallest
> hoop too much)
>
> Also MAME is a significantly more complex piece of software than VLC, with a lot more
> that can change between releases. Even VLC gets messed up too, if I upgrade to the
> latest version the video converter only outputs audio, not video, and since it seems
> to share ini files between installs it's actually *more* difficult to manage than
> MAME because I can't just have a folder and leave it be.

First i am sorry i couldnt earlier reply, but my last post was typed via a iphone 4s from my girlfriend :/
As i had no intention to write a book, i hoped you would still understand what i was trying to tell you. It seems it didnt go well.

The main point from my last post was to show you, why people tend to just copy the MAME.exe from a fresh install:

1. because it is everything you need in 95% of the cases.
2. people want to keep their settings, being it .ini´s, aspect ratios, pixel perfect resolutions, nvram or anything else, what they think is worth to keep or dont want to be altered by a major MAME update and the resulting destructive fresh install.

So if you want to see a change, you should think about those two points at least and i hope you see that these two points are also somehow connected. You need to think in DAU shoes.

I am aware that MAME is more complex vs. a VLC install, but i just wanted to give you a example, nothing more. BTW, my settings (even for encoding) in VLC always worked like intended. Version by version, no hassle, no extra work. If you want complex apps, how about Adobe CC suite?
It would be a nightmare to go through all preferences for each app again, after each update. You only do that by a version jump, which happens only once in a year.

Sadly this is not the case with MAME. A update could mean: start everything from scratch again. So this is quite the opposite from what your statement "it's actually *more* difficult to manage than MAME because I can't just have a folder and leave it be." tries to imply here.

Your case is only true, if you dont care about your past settings. But most users have serious ambitions with MAME and how it is presented on their hardware. Trying to have control over that, is not a silly task, like you maybe think and there are scenarios where this is just a pain in the ass. So this could explain a little why "yet for any other situations people find the smallest hoop too much".

I was also aware that the culprit in this case was a updated HLSL folder, but i tell you what. The same thing happened with the first major update for HLSL from Jezze (i think it was 0.162) and guess what, even you devs maked the mistake to NOT update the artwork folder and so on release the only working version, was the MAMEUIFX one. Shi.. errors happen, its human behaviour None of the users or mamesick came here, to bitch around that problem. Just saying.

Like i said, think in DAU shoes, have more empathy with users that try to have control over their collection. live and let live.







Entire thread
Subject Posted by Posted on
* Apparent Direct 3d bug in mame64 202 (non patched) Galaxian 09/30/18 02:14 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) kevenz  10/28/18 03:18 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) kevenz  10/08/18 01:18 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/08/18 01:19 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) anikom15  10/08/18 07:42 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Envisaged0ne  10/08/18 08:19 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) anikom15  10/08/18 08:56 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Foxhack  10/09/18 06:55 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) R. Belmont  10/30/18 04:05 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) ICEknight  10/11/18 09:53 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) anikom15  10/09/18 09:28 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) krick  10/08/18 08:40 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/08/18 08:44 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) anikom15  10/08/18 09:01 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) uman  10/09/18 01:46 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) TafoidAdministrator  09/30/18 02:33 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Galaxian  09/30/18 03:20 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) AHonikx  10/03/18 03:59 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Galaxian  10/07/18 01:20 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/07/18 01:22 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) uman  10/07/18 07:10 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/08/18 12:26 AM
. * Re: VLC ICEknight  10/11/18 09:54 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) uman  10/09/18 01:46 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Sthiryu  10/09/18 04:07 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) uman  10/11/18 02:55 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) LensLarque  10/11/18 05:12 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) R. Belmont  10/30/18 04:08 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) anikom15  10/12/18 03:41 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) B2K24  10/07/18 09:11 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) uman  10/07/18 09:41 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/03/18 03:28 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) RobbbertModerator  10/04/18 12:54 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/04/18 01:40 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) RobbbertModerator  10/04/18 02:15 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/04/18 11:41 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) John IV  10/05/18 12:09 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/05/18 12:55 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) John IV  10/05/18 01:43 AM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) RobbbertModerator  10/04/18 12:47 PM
. * Why does MAMEUI need to continue to exist? (nt) anikom15  10/04/18 05:39 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) sirscotty  10/25/18 03:41 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) anikom15  10/27/18 09:52 PM
. * Re: Why does MAMEUI need to continue to exist? (nt) MooglyGuy  10/25/18 04:57 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) sirscotty  10/26/18 05:47 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) RobbbertModerator  10/04/18 06:04 AM
. * Re: Why does MAME need to have a GUI frontend? (nt) anikom15  10/05/18 01:28 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) LensLarque  10/04/18 09:26 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) R. Belmont  10/04/18 03:49 PM
. * Re: Why does MAMEUI need to continue to exist? (nt) MooglyGuy  10/04/18 10:22 PM
. * Re: Why does MAMEUI need to continue to exist? (nt) LensLarque  10/04/18 08:48 PM
. * Fixed MooglyGuy  10/05/18 01:22 AM
. * Re: Fixed LensLarque  10/05/18 06:35 AM
. * Re: Fixed MooglyGuy  10/05/18 07:00 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) MooglyGuy  10/05/18 12:49 AM
. * Re: Why does MAMEUI need to continue to exist? (nt) MooglyGuy  10/04/18 11:50 PM
. * Re: Why does MAMEUI need to continue to exist? (nt) R. Belmont  10/30/18 04:20 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) CiroConsentino  09/30/18 08:18 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Galaxian  10/07/18 01:12 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Haze  10/07/18 01:19 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) Foxhack  09/30/18 09:27 PM
. * Re: Apparent Direct 3d bug in mame64 202 (non patched) anikom15  09/30/18 07:37 PM

Extra information Permissions
Moderator:  Robbbert, Tafoid 
1 registered and 435 anonymous users are browsing this forum.
You cannot start new topics
You cannot reply to topics
HTML is enabled
UBBCode is enabled
Thread views: 2215