MameUIFX 64bit + NoNag - Directinput

[sevenseal]

File Name: MameUIFX 64bit + NoNag - Directinput

File Submitter: sevenseal

File Submitted: 01 Jun 2016

File Category: Other

Credits: Sevenseal

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

Click here to download this file

[Metalzoic]

Sweet, thanks man. Appreciated!

[Suhrvivor]

Thanks for sharing!

 

I love the removal of the nag screen but what does directinput means exactly?

[potts43]

It means in real terms only one mouse will show up. Raw input shows every mouse as a separate mouse eg you need raw to play ANY game that uses two player mice/spinners/guns.

Please post a raw version - stuck on 171 as it's the last fully working version. [emoji17]

[Metalzoic]

It means in real terms only one mouse will show up. Raw input shows every mouse as a separate mouse eg you need raw to play ANY game that uses two player mice/spinners/guns.

I didn't know that...

So as soon as I add the rotary joysticks and spinners to my Cab I will need Raw Input versions of MAME for them to work?

[sevenseal]

I didn't know that...

So as soon as I add the rotary joysticks and spinners to my Cab I will need Raw Input versions of MAME for them to work?

yes

[Metalzoic]

Good info. Thanks

Sent from my SM-G935V

[Metalzoic]

Having some issues with this 174 version.

Some games that are marked working don't run and instead throw the error

"Required shared pointer 'mainram' not found" then "Fatal error. Missing some required objects. unable to proceed"

I've had a few games do it now. Asylum is doing it if you guys can test for me.

Also I noticed that this version is only 83,000kb, but MAMEUIFX 172 was 133,000kb... that's a massive difference. Any idea why? Is this one simply missing some things?

I did notice that checking the properties of a rom in this new version doesn't have all the options 172 has.

[potts43]

Having some issues with this 174 version.

Some games that are marked working don't run and instead throw the error

"Required shared pointer 'mainram' not found" then "Fatal error. Missing some required objects. unable to proceed"

I've had a few games do it now. Asylum is doing it if you guys can test for me.

Also I noticed that this version is only 83,000kb, but MAMEUIFX 172 was 133,000kb... that's a massive difference. Any idea why? Is this one simply missing some things?

I did notice that checking the properties of a rom in this new version doesn't have all the options 172 has.

Only raw version working as expected is 171 as far as I'm aware.

[sevenseal]

Having some issues with this 174 version.

Some games that are marked working don't run and instead throw the error

"Required shared pointer 'mainram' not found" then "Fatal error. Missing some required objects. unable to proceed"

I've had a few games do it now. Asylum is doing it if you guys can test for me.

Also I noticed that this version is only 83,000kb, but MAMEUIFX 172 was 133,000kb... that's a massive difference. Any idea why? Is this one simply missing some things?

I did notice that checking the properties of a rom in this new version doesn't have all the options 172 has.

normally i strip the symbols out and mess which i didnt do during when i made 172, i didnt have a proper pc environment to do so...

mameuifx is meant for arcade only

[Metalzoic]

OK cool. Yeah I use it arcade only. I was just wondering if that difference in size could explain the problems 174 has with some games, but it looks like the issue is with MAMEdevs 174 itself.

Sent from my SM-G935V

[sevenseal]

OK cool. Yeah I use it arcade only. I was just wondering if that difference in size could explain the problems 174 has with some games, but it looks like the issue is with MAMEdevs 174 itself.

Sent from my SM-G935V

yes it is the issue of mame source, cant be helped lol

let me compiled one from git. might make a different

[Metalzoic]

That would be cool thanks. Maybe we'll get lucky.

Sent from my SM-G935V

[Metalzoic]

Any luck on an update?

[sevenseal]

Any luck on an update?

well i tried the git but it wouldnt compile as is

[Metalzoic]

Cool. Thanks for trying man. Maybe it will be fixed in the next release.

[Krakerman]

There is a compiler error in your build for galaxian and several other titles I found.

[Metalzoic]

There is a compiler error in your build for galaxian and several other titles I found.

I believe it's in the source

[Krakerman]

yeah think 0.174 is riddled with issues. Reason I guess to having an alternative for the ones that are broke.

Sent from my iPhone using Tapatalk

[sevenseal]

yeah think 0.174 is riddled with issues. Reason I guess to having an alternative for the ones that are broke.

Sent from my iPhone using Tapatalk

me personally would avoid 174... so much is broken

[Krakerman]

Which version do you recommend 0.173

[sevenseal]

Which version do you recommend 0.173

function/feature/stability i would go with 171

best recent one 172

[Metalzoic]

I'm hoping 175 will be good enough for me to stop on for awhile.

Jezee will have the HLSL glitch fixed that has been around for 5+ versions (maybe longer?). Hopefully they have the MAMEram crash fixed. Hopefully the have the raw input issues fixed.

If so then I'll stay put on 175 for a good long while.

[wesfranks]

Surprised I haven't seen this development being discussed.

 

http://mame32fx.altervista.org/forum/viewtopic.php?f=1&t=307

[Metalzoic]

Bummer. Hopefully the guy lands on his feet.

175.1 is so damn stable that with this news I think it's the version I'll lock my cab too.

Plus reading his other threads 175.1 also has the Neo-Geo resolution hack and the Toaplan Sound Samples hack snuck back in.

Apparently this is a problem for Mamedevs, but since it might be his final he "doesn't give a shit". Ha!

He did mention some big bug fix and he possibly may be around to do 176, but not likely.