LCD + GROOVYMAME + HLSL = Crash to Desktop

[jrose78]

I am so frustrated.  I have an LCD and the breakdown is this

New version of mame (ahh 0.149 I think) Runs fine with or without hlsl enabled
New Version of Groovymame is fine until I turn on HLSL then it crashes to desktop 

I created a new config file for groovymame -cc  . So that's out .  Any ideas.    Need some HLSL LCD love.   

Using Powerstrip to keep refresh close to original if that helps.
I will attach a log file tomorrow as it late.

[Calamity]

Yes, please get a log, something must be wrong.

I've got GroovyMAME 0.149 working here in several LCDs with HLSL and it's working great. New HLSL filters are much better than the older versions.

[jrose78]

OK, I admit it was my mistake. I had installed the non-64 bit version of mame and then the Groovy 64bit file.  I got past the crash but now I have a new problem.  The game is small within the screen itself.  I have attached the log file. Can you take a look? Thanks

Windows 7 64 bit
Powerstrip 3.9
Monitor is a HP LP2065

Thanks Calamity!

[Calamity]

Had you possibly rotated the game manually before from MAME's internal menu? Go into the cfg folder and delete mspacman.cfg. Then run the game again. If you want to run it on a vertical monitor, run it with the option 'orientation vertical', you may place it in mspacman.ini.

[jrose78]

That worked! I use the monitor in both horizontal and vertical so I guess since I use it most in the vertical I will change the mame.ini to vertical and for each horizontal I will create a separate game.ini that says orientation horizontal?  Is there some sort of auto detect option? I have a cocktail table with a 3rd control panel so that's why I use it in both vertical and horizontal.

[Calamity]

Or... you can create a vertical.ini file.

This will apply to all vertical games, leaving the horizontal games alone with the default settings in mame.ini.

[jrose78]

That sounds like a better idea. I ran into the crash again and figured out it was when I set hlsl ini write and read to 1 BUT it did the same thing on regular mame so its not Groovymame there. Its always something.   Thanks again Calamity.

EDIT: looks like mame is aware of this bug http://mametesters.org/view.php?id=5218 

[mamenewb100]

Same thing happens in XP.