Main > Software Forum

hiscore diff (with no nag/white box removal)

<< < (197/250) > >>

ayjanu:
Yes, it would seem that you and I are having the same results, kmi.  Perhaps these consistent results can be helpful, at least, in the debugging process...  It is certainly strange.  What could have changed since 0.159, that could be causing these issues?

nitrogen_widget:

--- Quote from: kmi on April 08, 2015, 04:36:41 pm ---
--- Quote from: chubsta on April 08, 2015, 04:16:47 pm ---well, this sure is odd - compiles fine now with the latest patch but when i run a game there is no video! The game seems to play blind fine, have tried with a few different ones and it is the same...

although i normally run a front-end i have tried just running the executable and it does not bring up the usual mame menu so it is not a problem that just affects games, the issue appears from the first running.

have tried a basic compile again and that is ok, just the patched one has the problem - thanks for your continuing work on this...

--- End quote ---

I have the same problem, compile fine with the hi_160_3.txt but no video signal, the screen goes black.

The terminal returns this.

--- Code: ---[ArchLinux ~]$ mame
Value 1 not supported for option sound - falling back to auto
[ArchLinux ~]$
--- End code ---

--- End quote ---

I get the same also on PCLinuxOS with both 160_3 & 160_4.

MKChamp:
Ok...I compiled a SDL version (in windows) and believe I've got it sorted out. Someone apply this patch (to a clean build) and let me know how it looks.

Thanks!

ayjanu:
I'll try it now.  Will edit my post and report back whether it worked or not.

EDIT: I can confirm that it's working here!  Starts up normally, and I'm able to save high scores for games just fine again.  Thank you.  (Now, if I could only get GLSL shaders working, but that's a whole different topic...)

chubsta:
Not sure what is happening here - compiles fine, no nag screen but i tried with Juno First and Joust and both crash mame after a couple of minutes play - not sure if that is a problem with the patch or just coincidental...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version