Shmupmame 4.2: Lagless Mars Matrix, Strikers 1945, Galaga 88

[BPzeBanshee]

DonPachi is available in MAME, and perfectly playable, just remember the sound quality really is that lame and you won't get facepalm reactions from members here upon asking them such (I once read from a previous thread that the same question pops up every four months).

The sound effects are fucking awesome and I even like the distorted music as it sounds like played by a gramophone and output by a loudhailer, which reminds me of World War I&II films. With Sennheiser HD 495 headphones, I like it a lot.
The PSX port doesn't sound quite as charming to me.

The sound effects themselves are just fine in MAME (ie explosions), and I don't particularly hate the lame BGM quality or anything but it is inferior in a lot of regards and just pointing out there's been a lot of people that mark it as a bad point or think "oh I must've bought a bad PCB".

On ANZAC Day I watched old WWII videos of much the same quality, and then take a guess at the first shmup I played afterwards.

[Barrakketh]

you'll be missing out on Lagless Batrider

What makes you say that?

Well I suppose that's a matter of opinion. I take it you don't like Batrider much?

Why are you saying that Batrider isn't lagless? The sprite buffer is disabled for Batrider and all of the toaplan2 games. It's disabled in VIDEO_START (toaplan2), but the other games (like bgaregga) call that with the VIDEO_START_CALL macro.

Batrider actually has the sprite buffer disabled in upstream MAME by default.

[BPzeBanshee]

What makes you say that?

Well I suppose that's a matter of opinion. I take it you don't like Batrider much?

Why are you saying that Batrider isn't lagless? The sprite buffer is disabled for Batrider and all of the toaplan2 games. It's disabled in VIDEO_START (toaplan2), but the other games (like bgaregga) call that with the VIDEO_START_CALL macro.

Batrider actually has the sprite buffer disabled in upstream MAME by default.

Oh, I thought you were talking about Batrider not being significant.

I could've sworn in running your alternate build the toaplan2.c games were not lagless though, I counted Batrider and Garegga and they were all on the three/four frames ala normal MAME as opposed to two in Shmupmame v3.0b. Have I missed something here?

[nujie273]

Ketsui doesn't work on (my) Lagless Mame V3.0B
what should i do to fix it?

[nahucirujano]

Ketsui doesn't work on (my) Lagless Mame V3.0B
what should i do to fix it?

+1... Although I can run the game from the "All games" list, when I refresh de "Available" games list, Ketsui doesn´t appear...

[peat]

EDIT: Lagless driver source for 142u1.

I compiled this under OS X 10.6*, and I'm getting corrupt graphics in Donpachi and DDP. Haven't had time to test much other stuff, but Darius Gaiden and ESPGALUDA worked fine, at least.

See:

DDP


DP

I've tried clearing the NVRAM, but no dice. I compiled with -march=core2 and PTR64.

Any ideas?



* Kind of a pain in itself, since the 0.142 -> 0.142u1 patch has Windows-style newlines, and patch under Unix doesn't like that much...

[Barrakketh]

I compiled this under OS X 10.6*, and I'm getting corrupt graphics in Donpachi and DDP.

I can confirm that with DDP.

EDIT: Actually, I'm getting this even without the lagless patch. MAME 0.142 runs fine, 0.142u1 exhibits the same problem as in your screenshot.

[AWJ]

It's a bug in (upstream) 0.142u1 that was fixed in u3. It affects all games in cave.c.

[nujie273]

+1... Although I can run the game from the "All games" list, when I refresh de "Available" games list, Ketsui doesn´t appear...

mine doesn't work that way, I tried to run it but
b04701w064.u1 not found
I have another question, how do you write a review like in all the games listed in favorite folder?

[Barrakketh]

It's a bug in (upstream) 0.142u1 that was fixed in u3. It affects all games in cave.c.

Ah, good news.

I had went to MAMETesters to search for bug reports but got a SQL error whenever I tried to view the list, and looking at whats new that would've been bug #04326. It says "most games", I know ESP Ra.De worked fine for me.

EDIT: 0.142u3 32-bit

[Zeether]

I've been getting the stupid 0xc00000005 error even though before I was perfectly able to run Shmupmame, and I've tried the DEP thing. I guess I can't play it anymore, unless I can figure out if it's either RAM related or something else.

[BPzeBanshee]

Have you installed any updates recently? I'm starting to think this may be a Microsoft update thing for Win7 machines that XP is missing out on or something weird.

I dont suppose you're up for a TeamViewer session so I can peek at your computer settings?

[peat]

EDIT: 0.142u3 32-bit

Oop, didn't notice this before. Thank you!

[Zeether]

Have you installed any updates recently? I'm starting to think this may be a Microsoft update thing for Win7 machines that XP is missing out on or something weird.

I dont suppose you're up for a TeamViewer session so I can peek at your computer settings?

It might be some update I installed. Windows 7 made me download a shit ton of updates recently.

[mortified_penguin]

It might be some update I installed. Windows 7 made me download a shit ton of updates recently.

I'm starting to wonder. The old version of shmupmame started giving the 0xc00000005 error today so I went ahead and installed 3.0b. Worked fine until I had to reboot. Now I'm getting the same error. DEP Exception fix didn't help either.

[BPzeBanshee]

I'm kinda grasping at straws here in terms of solutions for your issues guys, and I'm probably repeating crap that's been posted in this thread before but I've come across a few threads regarding other programs having similar issues and there seems to be two theories as to the exact problem:

1) The program is using 16-bit material and thus will run in Windows 7 32-bit due to 16-bit support, but not 64-bit

2) It's an old program and therefore will have issues, emulating it in Win7 is like the only way

The first option seems more likely to me considering we're dealing with an older MAME base version here. I dont exactly have programming experience in MAME or anything, just grasping at straws, so all you guys having issues and not getting solutions are basically guinea pigs until I can find a Win7 64-bit machine that I can tinker with. In all seriousness if anyone's willing to do a remote access thing with me at some point so I can get more details on the problem computers exhibiting this error PM me.

In the case of option 1, on the developer's end they'll have to look at what the base version does differently from the current versions of MAME. Easier said than done I imagine, but if GareMAME can run on these machines just fine (it ran on the only computer with the 0xc00005 error I could find which was a Win7 64-bit laptop) then there must be something else that triggers off the error. Maybe that may help narrow it down to the exact problem. For now one will have to try and emulate XP using some kind of virtual machine thing like VMLite and see whether it works there. Since there's evidence that updating may be the cause check to see whether there's updates in regards to "legacy" or "16-bit" or "32-bit" application support.

If its option 2, than virtual machine emulation of Shmupmame is the only way short of using Barrakketh's Lagless builds which I understand is based on Shmupmame's v2.2 code.

Help me help you guys. I can try and help via some chat place ie MSN if you're online at the same time as me (5 PM AUS CST) for any of the above options to some extent, but just complaining about the error without knowing the exact cause isn't going to get us a real solution anytime soon.

[AliceMargatroid]

I use Shmupmame 3.0b on W7 64-bit and I just got the 0xc0000005 error for the first time.
Restart -> worked again.

Maybe you should end ALL other tasks before starting it or start it right after a system restart.
0xc0000005 usually happens when a task can't start due to the activities of other tasks.

Edit: It also may happen if your RAM is having problems or one of the sticks doesn't quite work anymore, but I don't think that is the case because the 0xc0000005 would happen on almost every program.

[ZOM]

7zip seems to have the 0xc0000005 error code on my win7 machine now... shmupmame won't run even after a restart.
(luckily, I have other machines to play)

[AliceMargatroid]

7zip always worked fine for me.
There might be something wrong with your RAM then.

I can't help you with that unless I could inspect your PC.
I have first-hand experience with repairing hardware and software.

[ZOM]

There might be something wrong with your RAM then.

Nah, it worked before I let win7 catch up on updates the whole night... Also, new version of 7zip I just downloaded doesn't show me the error anymore. I'm guessing BPzeBanshee isn't all too far away about that "16-bit components in some software"-story.

[AliceMargatroid]

Nah, it worked before I let win7 catch up on updates the whole night

Updating Windows is one of the biggest mistakes you can do unless it's a new SP.

[StarCreator]

Updating Windows is one of the biggest mistakes you can do unless it's a new SP.

This is the attitude that allows internet worms to propagate. Update constantly, especially if an update is released out of cycle (normal update schedule is the second Tuesday of each month) or you're putting everyone around you at risk.

[Narroo]

Well, I just downloaded ShmupMAME so I could try out ESPGaluda.

I managed to figure out how to set the controls, and got through a run of ESPGaluda. Quite a pain since there was no documentation, and you have to boot the game up first. Really?

But anyways, I've been playing with visual settings. Is there anyway to make the game not look blurry? Additionally, there seems to be a slight input lag, just enough that on the High Score Name screen I can get my joystick to neutral as the cursor starts to move. Any possible fixes for that?

Thanks guys!

(Merged into Shmupmame discussion thread /mod)

[BPzeBanshee]

Well, I just downloaded ShmupMAME so I could try out ESPGaluda.

I managed to figure out how to set the controls, and got through a run of ESPGaluda. Quite a pain since there was no documentation, and you have to boot the game up first. Really?

But anyways, I've been playing with visual settings. Is there anyway to make the game not look blurry? Additionally, there seems to be a slight input lag, just enough that on the High Score Name screen I can get my joystick to neutral as the cursor starts to move. Any possible fixes for that?

Thanks guys!

(Merged into Shmupmame discussion thread /mod)

Yes, really. The control setup is the exact same as other builds of MAME, get in-game, Tab > Control settings etc. If you're using multiple joysticks you handle them within the UI tab settings. It's not ShmupMAME's fault.

For visual settings, turn off any filters and use Direct3D as opposed to DirectDraw and that should help, since DirectDraw makes things seem blurry. Personally I like the blurriness, and in my experience DirectDraw is faster (but that's for another topic).

As for the input lag, the PGM driver itself is completely lagless (at least for me), maybe take a look at your deadzone settings in the Joystick(controls?) tab for the game.

There might be something wrong with your RAM then.

Nah, it worked before I let win7 catch up on updates the whole night... Also, new version of 7zip I just downloaded doesn't show me the error anymore. I'm guessing BPzeBanshee isn't all too far away about that "16-bit components in some software"-story.

For 7-Zip, maybe try and download their newest beta version at http://sourceforge.net/projects/sevenzi ... ic/4492007

My idea about 16-bit components is based on what I Googled for other programs getting the same error in Windows 7, the main thing in common being that they seemed to be older programs. However based on people's feedback in this thread it's more likely something within Window 7's updates are doing it, whether the two possible suspects I pointed out are one and the same or not I've yet to figure out.

Nah, it worked before I let win7 catch up on updates the whole night

Updating Windows is one of the biggest mistakes you can do unless it's a new SP.

I've never had issues with updating Windows but I wouldn't do it with Windows 7 right now. I'm old-skool though, I still believe Windows XP is the best thing Microsoft's got out and the amount of problems with people getting games to work (or even basic things like Java) in Vista and 7 support my stance.

[IseeThings]

My idea about 16-bit components is based on what I Googled for other programs getting the same error in Windows 7, the main thing in common being that they seemed to be older programs. However based on people's feedback in this thread it's more likely something within Window 7's updates are doing it, whether the two possible suspects I pointed out are one and the same or not I've yet to figure out.

I don't think that there is any 16-bit code in MAME.

It's much more likely it's just doing something that it shouldn't be doing. Newer versions of Windows are a lot more secure, exploits, and ways to run unsafe code which are actively being exploited are closed off, if older versions of MAME were inadvertently using such techniques (and I believe some of the blit code may have been) then it's inevitable that it gets shut off too. Likewise updates to the system libraries mean that if MAME was using them in an unsafe / incorrect way, it could also break.

Not updating however is stupid, these holes are closed for a reason, and it's not just petty 'stop homebrew/piracy' ones like on consoles / phones. By not updating you're running the risk of your machine being exploited for god knows what, fancy being part of a kiddie porn hosting ring without your knowledge? Good luck explaining that when the FBI kick your door down even if you are innocent

[BPzeBanshee]

My idea about 16-bit components is based on what I Googled for other programs getting the same error in Windows 7, the main thing in common being that they seemed to be older programs. However based on people's feedback in this thread it's more likely something within Window 7's updates are doing it, whether the two possible suspects I pointed out are one and the same or not I've yet to figure out.

I don't think that there is any 16-bit code in MAME.

It's much more likely it's just doing something that it shouldn't be doing. Newer versions of Windows are a lot more secure, exploits, and ways to run unsafe code which are actively being exploited are closed off, if older versions of MAME were inadvertently using such techniques (and I believe some of the blit code may have been) then it's inevitable that it gets shut off too. Likewise updates to the system libraries mean that if MAME was using them in an unsafe / incorrect way, it could also break.

Not updating however is stupid, these holes are closed for a reason, and it's not just petty 'stop homebrew/piracy' ones like on consoles / phones. By not updating you're running the risk of your machine being exploited for god knows what, fancy being part of a kiddie porn hosting ring without your knowledge? Good luck explaining that when the FBI kick your door down even if you are innocent

What you say makes sense, but if its something with the blitters why the hell does ShmupMAME cause issues when GareMAME (which is based off an even older base of MAME, 0.90 from what I have) works on the problem machines?
Definitely rules out 16-bit incompatibility and crap and definitely sounds more like a security thing, but if its not the MAME base what's Nimitz doing differently that Win7 doesn't like?

[Barrakketh]

For all you know it could have been introduced between 0.90 and 0.99. Or by the changes added between MAME 0.99 and MAMEPlus! 99.

[TrevHead (TVR)]

I personally think its partly Win7's fault as to why I get the DEP fault on my machine as I only encountered the problem now and again which is easily solved with a reboot. But it was during one of Win7s round of updates that the DEP fault really kicked in.

Its really annoying that we have to put up with all these updates both in Windows and the browsers but its a small price to pay for the added security from malware.

I suppose the DEP fault isnt helped due to the fact PC manufacters like HP & DELL are nowadays putting cheap RAM into their PCs. I have a HP which has just run out of warrenty, I think im gonna take the back off my tower and have a good peek inside.

[BPzeBanshee]

For all you know it could have been introduced between 0.90 and 0.99. Or by the changes added between MAME 0.99 and MAMEPlus! 99.

Exactly. This is the million-dollar question I'd like to be able to answer but I dont have the know-how or the resources so I'm throwing ideas until someone DOES find out the true source.

[BuckoA51]

Gah, just got the same crash here on my Windows 7 64 rig, interestingly I have another program that needs excluding from DEP and that is working exactly like it always did.