Is it normal to only be able to use shaders by activating a GLSL preset?

Hi.

Sorry if the question sounds strange, but the what is the normal way to activate a shader?

I’m only able to activate a shader by selecting a GLSL preset. GG presets doesn’t work either.

I’m using Ubuntu 14.04

Thanks and sorry for my English.

You can only activate presets via the ‘load shader preset’ option. You can manually load single-pass shaders by incrementing the number of shader passes and then navigating to the cg/glsl shader you want to load and then hitting “apply shader changes”.

If Cg presets won’t work, verify that your build supports Cg shaders by running retroarch --features from a command line. Also, make sure you have nvidia’s cg toolkit library installed. If it still doesn’t cooperate, try switching to another menu driver in settings > drivers. XMB briefly had a problem with Cg shaders but that’s been fixed in the nightlies. If you’re using an older build, the conflict may still be there.

[QUOTE=hunterk;41763]You can only activate presets via the ‘load shader preset’ option. You can manually load single-pass shaders by incrementing the number of shader passes and then navigating to the cg/glsl shader you want to load and then hitting “apply shader changes”.

If Cg presets won’t work, verify that your build supports Cg shaders by running retroarch --features from a command line. Also, make sure you have nvidia’s cg toolkit library installed. If it still doesn’t cooperate, try switching to another menu driver in settings > drivers. XMB briefly had a problem with Cg shaders but that’s been fixed in the nightlies. If you’re using an older build, the conflict may still be there.[/QUOTE]

Hi.

Thanks for your reply and sorry for the double thread.

I tried to add 1 pass and then select the cg shader but it didn’t work.

Also tried to change de menu driver and it didn’t work.

This is what i got when i typed “retroarch --features”:

Features: LibretroDB: LibretroDB support: yes Command: Command interface support: yes Network Command: Network Command interface support: yes SDL: SDL input/audio/video drivers: no SDL2: SDL2 input/audio/video drivers: yes X11: X11 input/video drivers: yes wayland: Wayland input/video drivers: yes Threads: Threading support: yes Vulkan: Vulkan driver: no OpenGL: OpenGL driver: yes OpenGL ES: OpenGL ES driver: no XVideo: Video driver: yes UDEV: UDEV/EVDEV input driver support: yes EGL: video context driver: yes KMS: video context driver: yes OpenVG: video context driver: no CoreAudio: Audio driver: no ALSA: Audio driver: yes OSS: Audio driver: no Jack: Audio driver: yes RSound: Audio driver: no RoarAudio: Audio driver: no PulseAudio: Audio driver: yes DirectSound: Audio driver: no XAudio2: Audio driver: no OpenAL: Audio driver: yes OpenSL: Audio driver: no 7zip: 7zip support: yes zlib: .zip extraction: yes External: External filter and plugin support: yes Cg: Fragment/vertex shader driver: yes GLSL: Fragment/vertex shader driver: yes HLSL: Fragment/vertex shader driver: yes libxml2: libxml2 XML parsing: yes SDL_image: SDL_image image loading: no rpng: PNG image loading/encoding: yes FBO: OpenGL render-to-texture (multi-pass shaders): yes Dynamic: Dynamic run-time loading of libretro library: yes FFmpeg: On-the-fly recording of gameplay with libavcodec: no FreeType: TTF font rendering driver: yes CoreText: TTF font rendering driver (for OSX and/or iOS): no Netplay: Peer-to-peer netplay: yes Python: Script support in shaders: yes Libusb: Libusb support: yes Cocoa: Cocoa UI companion support (for OSX and/or iOS): no QT: QT UI companion support: no AVFoundation: Camera driver: no Video4Linux2: Camera driver: yes

I’m using the 1.3.4 version

Hmm. That all looks good. I would personally suggest switching to ppa:libretro/testing and see if that fixes it.