Shaders not working in Hyperspin

[avisioncame]

So, I have finally gotten the HSLS shaders to work in the MAME.exe via editing the Mame.ini file. Works great and I like the look so far.

Problem is, when I launch in Hyperspin, no shaders.... Same path to the emulator...it's like it is not seeing my .ini file.

Is there something I'm not seeing?

Thanks!

[gigapig]

Have you set HLSL to true in HLHQ? If your unsure watch my video guide.

[avisioncame]

Now we are getting somewhere! But It see it in HLHQ.... And which tutorial do you speak of? Thanks.

[gigapig]

Now we are getting somewhere! But It see it in HLHQ.... And which tutorial do you speak of? Thanks.

The ones in my signature, above the fat pig.

[avisioncame]

Thanks Gigapig, I will check it out. But I typically like to learn through forums/reading, and have learned a great deal of information so far thanks to the forums. I feel fairly fluent in hyperspin now.

I typically like to steer away from tutorial videos, as I can easily lose information in a timeline. And you can't really skim through a video if you are looking to fix a specific issue.

Do you think you could just tell me the menu it is in? That way future "Googlers" might be able to fix the issue easily, as I couldn't find anything in search results regarding the issue.

[gigapig]

Thanks Gigapig, I will check it out. But I typically like to learn through forums/reading, and have learned a great deal of information so far thanks to the forums. I feel fairly fluent in hyperspin now.

I typically like to steer away from tutorial videos, as I can easily lose information in a timeline. And you can't really skim through a video if you are looking to fix a specific issue.

Do you think you could just tell me the menu it is in? That way future "Googlers" might be able to fix the issue easily, as I couldn't find anything in search results regarding the issue.

Thanks all fine, there are links and my HLSL settings are there also, but obviously I can post those here it you need them.

What version of Mame are you running?

If you have hlsl enabled in the ini that won't make a difference when run through Hyperlaunch, you need to navigate here and change the HLSL setting to true.

Here are the settings I use.

hlsl_enable               0
hlslpath                  hlsl
hlsl_prescale_x           0
hlsl_prescale_y           0
hlsl_preset               -1
hlsl_write                
hlsl_snap_width           2048
hlsl_snap_height          1536
shadow_mask_alpha         0.12
shadow_mask_texture       crt_slot_mask.png
shadow_mask_x_count       320
shadow_mask_y_count       240
shadow_mask_usize         0.18750
shadow_mask_vsize         0.21875
curvature                 0.09
pincushion                0.120000
scanline_alpha            1.5
scanline_size             0.95
scanline_height           1.0
scanline_bright_scale     1.1
scanline_bright_offset    0.6
scanline_jitter           0.00
defocus                   0.005,0.005
converge_x                0.2,0.0,0.0
converge_y                0.0,0.0,0.0
radial_converge_x         0.2,0.0,0.0
radial_converge_y         0.0,0.0,0.0
red_ratio                 0.85,0.15,0.0
grn_ratio                 -0.1,1.1,0.0
blu_ratio                 -0.075,0.0,1.075
saturation                1.0
offset                    -0.15,-0.18,-0.18
scale                     1.15,1.18,1.18
power                     1.1,0.9,0.7
floor                     0.01,0.0,0.01
phosphor_life             0.0,0.0,0.0

And the detail for the rounded corners taken from my youtube channel.

If anyone has lost the rounded corners after the recent update, I have found the answer. This was really bugging me, it's apparently it's related to the post.fx file in the HLSL folder. I found the original settings, made a backup of the original and copy and pasted the new and saved. Bingo, back to normal.

The code can be found here http://www.aep-emu.de/PNphpBB2-file-viewtopic-t-18991.html look near the bottom at Jesse post.

[avisioncame]

Thanks all fine, there are links and my HLSL settings are there also, but obviously I can post those here it you need them.

What version of Mame are you running?

If you have hlsl enabled in the ini that won't make a difference when run through Hyperlaunch, you need to navigate here and change the HLSL setting to true.

[ATTACH=CONFIG]41726[/ATTACH]

[ATTACH=CONFIG]41727[/ATTACH]

Here are the settings I use.

hlsl_enable               0
hlslpath                  hlsl
hlsl_prescale_x           0
hlsl_prescale_y           0
hlsl_preset               -1
hlsl_write                
hlsl_snap_width           2048
hlsl_snap_height          1536
shadow_mask_alpha         0.12
shadow_mask_texture       crt_slot_mask.png
shadow_mask_x_count       320
shadow_mask_y_count       240
shadow_mask_usize         0.18750
shadow_mask_vsize         0.21875
curvature                 0.09
pincushion                0.120000
scanline_alpha            1.5
scanline_size             0.95
scanline_height           1.0
scanline_bright_scale     1.1
scanline_bright_offset    0.6
scanline_jitter           0.00
defocus                   0.005,0.005
converge_x                0.2,0.0,0.0
converge_y                0.0,0.0,0.0
radial_converge_x         0.2,0.0,0.0
radial_converge_y         0.0,0.0,0.0
red_ratio                 0.85,0.15,0.0
grn_ratio                 -0.1,1.1,0.0
blu_ratio                 -0.075,0.0,1.075
saturation                1.0
offset                    -0.15,-0.18,-0.18
scale                     1.15,1.18,1.18
power                     1.1,0.9,0.7
floor                     0.01,0.0,0.01
phosphor_life             0.0,0.0,0.0

And the detail for the rounded corners taken from my youtube channel.

Thanks pig. I eventually found these setting last night after messing around. So you are saying the MAME .ini file that is found in Hyperspin>Emulators>MAME> is in no way used by Hyperspin?

Last night I was just being "scientific" and took the ini from the aforementioned directory, and overwrote the one in HyperSpin>HyperLaunch>Modules>MAME (I named the .ini that already resided there to MAMEold.ini, as a backup)

I was getting errors/blank screens. So I went back with the old file. Then I figured out how to set HLSL to "true" in HLHQ. but after setting that to true, I get this:

(Regarding my specific setup, typically, this would just be MAME in fullscreen, no borders, shaders, etc---and that's not even my desktop wallpaper....)

Now....what the hell happened there?

I went back into HLHQ, set EVERYTHING I could find back to false, restarted, and it is STILL there! The roms won't even load. It just goes to a black screen. What did I do? I was so proud of myself for finally getting everything to work, all the artworks, video snaps. ARRRGGGHH!!!

EDIT: Disregard everything posted above... I suppose at some point I played with the "bezel" settings..... Woopsy

Everything is working great now, shaders and all thanks pig!

One last thing though that I am confused of. Is HLHQ pulling these settings from the mame.ini in EMULATORS, or in MODULES? because I didn't edit anything in the MODULES ini, and it appears to be using the settings I had already used when running from mame.exe (btw, I am using MAME version 0.152b 64bit)

[gigapig]

I haven't seen the nag screen for a while

You get a black screen if you set bezels to true and also to layout. If no mame artwork exists you get a black screen.

To not answer question, not sure, it may be in the module. It's not from the mame ini because you can switch it off in the ini and it will still work.

[Fromlostdays]

I don't personally have any interest in scanlines etc, but a nice super eagle shader... count me on.. so Giga... can this method be used to get me some blur action or do I have to keep using an old version of mameplus? Awesome tutorial by the way.

Thanks

[avisioncame]

I don't personally have any interest in scanlines etc, but a nice super eagle shader... count me on.. so Giga... can this method be used to get me some blur action or do I have to keep using an old version of mameplus? Awesome tutorial by the way.

Thanks

Was never the biggest fan of scanlines myself, but lately, I have seriously been considering just putting an LCD in my upcoming MAME cab and be done with all the crap that comes along with CRTs. The scanlines in MAME are insanley realistic, (CHECK THIS FORUM)... and I wish there was a way to just apply them globally - To Hyperspin, emulators, even Windows (like an external program that runs in the background...does this exist even....)

The problem is, every emulator has their own version of shaders, so they are all a little different.

Looking at these shaders, imaging my LCD under a piece of lightly tinted glass.... It might fool some people, that's for sure.

[gigapig]

Was never the biggest fan of scanlines myself, but lately, I have seriously been considering just putting an LCD in my upcoming MAME cab and be done with all the crap that comes along with CRTs. The scanlines in MAME are insanley realistic, (CHECK THIS FORUM)... and I wish there was a way to just apply them globally - To Hyperspin, emulators, even Windows (like an external program that runs in the background...does this exist even....)

The problem is, every emulator has their own version of shaders, so they are all a little different.

Looking at these shaders, imaging my LCD under a piece of lightly tinted glass.... It might fool some people, that's for sure.

Are you using settings from that site you linked to? On Mame 0.153 they don't look that great at least to my taste, maybe it's a version thing.

Also be careful because the OP on that forum hasn't separated the yiq values to the ntsc post-processing section.

[avisioncame]

Are you using settings from that site you linked to? On Mame 0.153 they don't look that great at least to my taste, maybe it's a version thing.

Also be careful because the OP on that forum hasn't separated the yiq values to the ntsc post-processing section.

Yeah they look a little washed out...kinda makes it just look like monitor going bad LOL! But I am still playing with it. I think the coding was a bit different in that version, but I made sure to separate it.

Has anyone happened to come across any presets others have been using in the latest version?

[gigapig]

Yeah they look a little washed out...kinda makes it just look like monitor going bad LOL! But I am still playing with it. I think the coding was a bit different in that version, but I made sure to separate it.

Has anyone happened to come across any presets others have been using in the latest version?

Have you tried what I posted on page 1 post #6 of this thread? Make sure you look at the post processing fix also.

[avisioncame]

Have you tried what I posted on page 1 post #6 of this thread? Make sure you look at the post processing fix also.

I meant to, but I got caught up with all that bezel crap. I'm trying them now. I noticed you didn't post NTSC POST-PROCESSING OPTIONS....are these not really needed?

Odd, I am not having issues with curvature, but I'll translate the page anyway, looks like good info. Thanks!