GroovyMAME 0.227 - Switchres v0.017t

[cbcduna]

Hi,

i have a doubt about use the ipp system (joysticks and buttons connected per paralel port) of controls with the lastest versions of mame. Is possible use the version GM 0.178 with this without modifications? I need aditional action of compilation in standart version of 0.178 for use IPP controls?

Thanks in advance...

[m.andrade1]

Hello haynor666
I managed to work with neogeo games, with good results, i created a neogeo.ini forcing the resolution to 304x224, it seems now the neogeo games are fullscreen without the junk black side bar or the, random blocks on the borders, the good thing itīs mainting the aspect without loosing the smooth, it works with the same Hz from the 320x224, so thatīs what i did.
Thanks Marcos

[haynor666]

Some games will still have junk or black bars: Zupapa, Gururin or Cyber-lip (should be cut 16 from right edge).

I almost finished my build with more modifications including neo-geo resolution changes.

[tom5151]

Thanks @Calamity, @haynor666 and @ozfalcon for your help about res switching on win7+.
I've indeed tried wcbowl, and I have the same issue I have with Shienryu.
I use super resolutions on win 10 (35 modelines), I only have 1 output, so the last thing I can try is to replace my system shell.

[peterson65]

i have groovymame 0178 working fine but still getting the there are known problems with this game  ect is ther no way to bypass that? i have it compilled with the supression patch and skip game info at 1
!!never mind got it working!!

[keropi]

Some games will still have junk or black bars: Zupapa, Gururin or Cyber-lip (should be cut 16 from right edge).

I almost finished my build with more modifications including neo-geo resolution changes.

any chance you could share this compile for X64 haynor666?

[haynor666]

Sure - https://mega.nz/#!ckc3xYAI!R_NQQrmhtUVD9SFsizqm02vnsPNZmpHjDdTk8Ed8lm0

It would be nice if you can look at neo-geo visible area modifications. Maybe something can still be improved.

[keropi]

thanks for sharing that haynor666! 
I will be gone for ~10 days starting tomorrow in a trip to Germany - once I return I'll test it in my setup , finally doing some progress completing my wood cab 
I also have a real neogeo board with mslug1/aof1 - the garbage on the side are visible in them too , there was a time I though my board had an issue or something 

[peterson65]

Anyone have any ideas how I can go about finding out why groovymame 0.178 is crashing? I am running game-ex for my front end and it demos what's in my favorites and at some point it crashes in the background . I assume maybe a particular game but I am not sure because game-ex keeps going to the next game and when I close it I see on the desktop the errors. I am running crt 2.0 on win 7 64.

[Calamity]

GroovyMAME 0.179 is out (SwitchRes v0.016 alpha 2).

[Jonny G]

GroovyMAME 0.179 is out (SwitchRes v0.016 alpha 2).

Cheers Calamity!!! Back up to top speed!

[mdd45]

I have a working groovymame 177 winxp32 build on a hd2400. I have tried 179 32build on the same machine with new mame.ini and i have framerate problems (frames hovering from 95-105%) with sound problems. Also neo geo games give me an out of sync picture.  I'll stick to 177 build.

[Calamity]

I have a working groovymame 177 winxp32 build on a hd2400. I have tried 179 32build on the same machine with new mame.ini and i have framerate problems (frames hovering from 95-105%) with sound problems. Also neo geo games give me an out of sync picture.  I'll stick to 177 build.

From now on, all log-less bug reports will be sent to this purgatory thread.

Thanks for your collaboration.

[mdd45]

added

[Calamity]

added

The out of sync issue is probably due to not forcing the dotclockmin option for your HD 2400. The speed issue is similiar to a previous one we had caused by baseline moving time functions to the std library, but this one was fixed in GM. It'd be nice to have another XP user confirming this.

[haynor666]

I'm affraid problem is valid. This time speed issue is even more bizarre.

[mdd45]

added

The out of sync issue is probably due to not forcing the dotclockmin option for your HD 2400. The speed issue is similiar to a previous one we had caused by baseline moving time functions to the std library, but this one was fixed in GM. It'd be nice to have another XP user confirming this.

You are right about the dotclock, i forgot to force it to 8. The speed issues though are still there.

[Calamity]

Just tested on my XP32 system (Pentium 4 HT), no speed issues here, all games running smoothly here.

I'm wondering if you have frame_delay enabled.

[mdd45]

frame_delay is 0 at mame.ini

[haynor666]

Without frame delay speed is constantly switching between 101 and 95 %. Very noticable with sound. With frame delay 2 it's even worse.

[ozfalcon]

Without frame delay speed is constantly switching between 101 and 95 %. Very noticable with sound. With frame delay 2 it's even worse.

I have encountered this in the past.

Out of interest, What's your OS & CPU type?

[haynor666]

G3258 overclocked to 4,2 GHz, XP x32.

Problem is as I read only on XP.

[Calamity]

G3258 overclocked to 4,2 GHz, XP x32.

Problem is as I read only on XP.

Would you mind checking this test build? https://drive.google.com/open?id=0B5iMjDor3P__WEFqU1JyTThrSVE

[ozfalcon]

G3258 overclocked to 4,2 GHz, XP x32.

Problem is as I read only on XP.

Sorry, Misread the previous post's in the thread.



 

[haynor666]

Would you mind checking this test build? https://drive.google.com/open?id=0B5iMjDor3P__WEFqU1JyTThrSVE

Still the same.

[Doozer]

The groovymame 0.179 Linux builds are available.

[Calamity]

Would you mind checking this test build? https://drive.google.com/open?id=0B5iMjDor3P__WEFqU1JyTThrSVE

Still the same.

Ok, I've confirmed the issue.

But there's something odd going on. If I build GM from my main PC (i7-4771 - Windows 8.1) then the speed issue on XP happens. However if build GM from my laptop (i7-2670QM - Windows 10) then there's no speed issue, provided I add the patch for the chrono library.

[mdd45]

Is there a new 179 build to test for winxp users? You think the problem is due to win8.1? My advice though is that you should update to windows 10. They are great and better than 8.1.

[Calamity]

SwitchRes v0.016 alpha 3 (October 2016):

- Attempt at fixing erratic speed issue on Windows XP, by replacing std::chrono::high_resolution_clock by std::chrono::steady_clock.


Please check if this fixes the issue (it does here).

[Calamity]

My advice though is that you should update to windows 10. They are great and better than 8.1.

As I said I'm already running W10 on my laptop. Boot takes way longer than it did on W7. Until the anniversary update, the hd was 90-100% busy most of the time, doing unknown background stuff, even after disabling all the telemetry crap. After the anniversary update, it feels more robust and faster. Windows 8.1 on the other hand is the most solid OS I've experienced so far, it's great once you hide all the metro stuff. I'm running it on a SSD so the comparison isn't probably fair, but when I get to the office and press the power button the desktop is ready before I have time to hang my jacket.

[haynor666]

Alpha3 works fine for me. Tested with frame_delay 2 and 0 ans couple games with different frequencies.

[mdd45]

Alpha 3 works for me too. With Frame_delay set to 0-2 i had no issues. I haven't figure out yet  if it is better for my configuration to have frame_delay at 0 or lets say 2. (pentium 4 2.8ghz, 2.5gb ram, Winxp 32b with hd2400)

[Calamity]

I haven't figure out yet  if it is better for my configuration to have frame_delay at 0 or lets say 2.

Frame_delay must be zero in mame.ini. Then, if you want to enable it for some game, you need to determine the highest value that offers a stable performance for that specific game on your specific hardware, and create an .ini file for that game.

[tom5151]

Hi all,
I would be nice if someone could share a no-nag patched window 64bits version (xp / linux as well) when a new GM version is out.
Thanks,

[javierluisbravo]

Hi my friends,

In GM 0.179 when i load the rom from the command line or with a frontend.. the blue "loading" pointer of Windows 10 appears over a black screen... just a second before the nag screen and after hitting enter.

In GM 0.149 it does not happen at all.

Am I the only having this blue circle pointer of the mouse appearing between hitting enter and the nag screen? 

Or is something common since a couple versions ago?  (As i just updated from 0.149 to 0.179 alpha3)

[Calamity]

The Windows loading pointer has happened since I have memory.

[haynor666]

Some frontends have some ability to hide pointer.

[schmerzkaufen]

Just to re-confirm please; 0.171 was the last build where D3D9ex worked, right ?

[keropi]

^ I believe so, after that it's BGFX

I've been meaning to ask, what happened with the F10 behavior in recent mame builds? For example in 0.171 it unlocks framerate but in 0.179 it does nothing for me (in all games). Is there a new mame.ini option I missed? 

edit:
it appears that "FAST FORWARD" works for me but "THROTTLE" does nothing at all.

[Calamity]

I've uploaded a new Direct3D 9Ex build to the drive:

groovymame64_0179.016_alpha3_d3d9ex.7z

There's also a new diff file to add Direct3D 9Ex support to GroovyMAME. It must me applied after the usual GroovyMAME patch:

d3d9ex.diff

Notice this build is 9Ex-only, you can't switch from D3D9 to D3D9Ex anymore, so just use -video d3d or simply leave the default -video auto setting. The old -video d3d9ex won't work!. This build won't work on XP either (Direct3D 9Ex requires Windows Vista+).

The key is now we need separate builds for either D3D9 or D3D9ex, both using the same option -video d3d.

I'm providing this diff and build temporarily, I'm not sure if I'll be mantaining it. In case I do, only the 64-bit build will be released. I could aswell integrate this diff into the main one, but that would mean dropping support for XP. Maybe I should post a poll about this.

Pro memoria: Direct9Ex is used to reduce video latency to the minimum possible allowed by the system, before or without using advanced technics (=hacks), namely frame delay and/or direct polling of scanlines.