Mario paper jam not working with new citra

i just updated citra and it works great except for one game and thats mario paper jam it seems the game could run in the older versions of citra but not the new ones i keep getting the error when i get to the opining of the game

[ 14.208118] Debug video_core\renderer_opengl\gl_shader_util.cpp:operator():91: Assertion Failed!
Shader not linked

do you know of any fix guys

Please edit your post so that it follows the template when creating a support topic. You need to state exactly what version this occurs with (see title bar), provide a screenshot along with system info and the entire log. If you don’t provide enough info, then this topic will be closed and unlisted.

I opened #2213 some time ago.

citra_log.txt (23.0 KB)

System Information for Support

Client Version                                Nightly 1598 HEAD-b4ec50b
Operating System                              Windows 10 (10.0)
CPU                                                  Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
Graphics API                                  OpenGL 3.3.0
Graphics Renderer                             Intel(R) HD Graphics 4000
GPU Driver Version                            10.18.10.4358

Here’s some issues I found with your log that might help.

GPU Driver Version: 10.18.10.4358

This driver is outdated, you need to update.

Download win64_15.33.50.5129.zip from https://downloadcenter.intel.com/download/29473/Intel-Graphics-Driver-for-Windows-15-33-?product=81499
direct link: https://downloadmirror.intel.com/29473/a08/win64_15.33.50.5129.zip

then follow this guide to install it: https://www.howtogeek.com/343287/how-to-fix-the-driver-being-installed-is-not-validated-for-this-computer-on-intel-computers/

Since you have an old GPU which can randomly crash due to a driver bug you might also need to use Nightly 1392 until you upgrade your computer: https://github.com/citra-emu/citra-nightly/releases/tag/nightly-1392

citra_log.txt (21.1 KB)

System Information for Support

Client Version                                Nightly 1392 HEAD-ddb7ead
Operating System                              Windows 10 (10.0)
CPU                                           Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz
Graphics API                                  OpenGL 3.3.0
Graphics Renderer                             GeForce GTX 650/PCIe/SSE2
GPU Driver Version                            451.67
CPU JIT                                       [x]
Hardware Renderer                             [x]
Hardware Shader                               [x]
Hardware Shader, Accurate Multiplication      [ ]
Shader JIT                                    [x]
System Region                                 -1

Here’s some issues I found with your log that might help.

  • Enabling Accurate Multiplication is recomended in certain games. If you are experiencing graphical glitches, try enabling this option.

citra_log.txt (109.4 KB)

System Information for Support

Client Version                                Nightly 1392 HEAD-ddb7ead
Operating System                              Windows 10 (10.0)
CPU                                           Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz
Graphics API                                  OpenGL 3.3.0
Graphics Renderer                             GeForce GTX 650/PCIe/SSE2
GPU Driver Version                            451.67
CPU JIT                                       [x]
Hardware Renderer                             [x]
Hardware Shader                               [x]
Hardware Shader, Accurate Multiplication      [ ]
Shader JIT                                    [x]
System Region                                 -1

Here’s some issues I found with your log that might help.

  • Enabling Accurate Multiplication is recomended in certain games. If you are experiencing graphical glitches, try enabling this option.

Can you translate that or set Citra’s UI language to English? I do not know hangul :stuck_out_tongue:

citra_log.txt (98 Bytes)

Make sure you have done step 1 correctly ( How to Upload the Log File ) regarding how to upload the log file. Your log filter is set to *:Critical which is incorrect, you must set it to *:Info

Upload a new log when you have done that.

citra-qt work well citra_log.txt (4.0 KB)

the problem is citra.exe doesn’t open . I don’t understand . how to change the filter to *:Info

I did not find anything wrong in your log file. Please wait for a moderator to assist.

that’s my citra_log.txt (98 Bytes)
when i start citra.exe

You should use citra-qt.exe. citra.exe is the command line version which you need to start with like cmd.exe or powershell. You can shift right click on the folder where citra.exe is and pick like “open powershell here” or something like that. then type citra.exe path-to-rom replace path-to-rom with the actual path like C:\games\mario.3ds

The config files are in the config folder, for citra.exe it should be sdl-config.ini so you would need to open it with notepad to edit the log filter for it.

hi, the problem will continue,

first image : cmd

second image: sdl.config.ini where is it log filter?

[Controls]

The input devices and parameters for each 3DS native input

It should be in the format of “engine:[engine_name],[param1]:[value1],[param2]:[value2]…”

Escape characters $0 (for ‘:’), $1 (for ‘,’) and $2 (for ‘$’) can be used in values

for button input, the following devices are available:

- “keyboard” (default) for keyboard input. Required parameters:

- “code”: the code of the key to bind

- “sdl” for joystick input using SDL. Required parameters:

- “joystick”: the index of the joystick to bind

- “button”(optional): the index of the button to bind

- “hat”(optional): the index of the hat to bind as direction buttons

- “axis”(optional): the index of the axis to bind

- “direction”(only used for hat): the direction name of the hat to bind. Can be “up”, “down”, “left” or “right”

- “threshold”(only used for axis): a float value in (-1.0, 1.0) which the button is

triggered if the axis value crosses

- “direction”(only used for axis): “+” means the button is triggered when the axis value

is greater than the threshold; “-” means the button is triggered when the axis value

is smaller than the threshold

button_a=
button_b=
button_x=
button_y=
button_up=
button_down=
button_left=
button_right=
button_l=
button_r=
button_start=
button_select=
button_debug=
button_gpio14=
button_zl=
button_zr=
button_home=

for analog input, the following devices are available:

- “analog_from_button” (default) for emulating analog input from direction buttons. Required parameters:

- “up”, “down”, “left”, “right”: sub-devices for each direction.

Should be in the format as a button input devices using escape characters, for example, “engine$0keyboard$1code$00”

- “modifier”: sub-devices as a modifier.

- “modifier_scale”: a float number representing the applied modifier scale to the analog input.

Must be in range of 0.0-1.0. Defaults to 0.5

- “sdl” for joystick input using SDL. Required parameters:

- “joystick”: the index of the joystick to bind

- “axis_x”: the index of the axis to bind as x-axis (default to 0)

- “axis_y”: the index of the axis to bind as y-axis (default to 1)

circle_pad=
c_stick=

for motion input, the following devices are available:

- “motion_emu” (default) for emulating motion input from mouse input. Required parameters:

- “update_period”: update period in milliseconds (default to 100)

- “sensitivity”: the coefficient converting mouse movement to tilting angle (default to 0.01)

- “tilt_clamp”: the max value of the tilt angle in degrees (default to 90)

- “cemuhookudp” reads motion input from a udp server that uses cemuhook’s udp protocol

motion_device=

for touch input, the following devices are available:

- “emu_window” (default) for emulating touch input from mouse input to the emulation window. No parameters required

- “cemuhookudp” reads touch input from a udp server that uses cemuhook’s udp protocol

- “min_x”, “min_y”, “max_x”, “max_y”: defines the udp device’s touch screen coordinate system

touch_device=

Most desktop operating systems do not expose a way to poll the motion state of the controllers

so as a way around it, cemuhook created a udp client/server protocol to broadcast the data directly

from a controller device to the client program. Citra has a client that can connect and read

from any cemuhook compatible motion program.

IPv4 address of the udp input server (Default “127.0.0.1”)

udp_input_address=

Port of the udp input server. (Default 26760)

udp_input_port=

The pad to request data on. Should be between 0 (Pad 1) and 3 (Pad 4). (Default 0)

udp_pad_index=

[Core]

Whether to use the Just-In-Time (JIT) compiler for CPU emulation

0: Interpreter (slow), 1 (default): JIT (fast)

use_cpu_jit =

Change the Clock Frequency of the emulated 3DS CPU.

Underclocking can increase the performance of the game at the risk of freezing.

Overclocking may fix lag that happens on console, but also comes with the risk of freezing.

Range is any positive integer (but we suspect 25 - 400 is a good idea) Default is 100

cpu_clock_percentage =

[Renderer]

Whether to render using GLES or OpenGL

0 (default): OpenGL, 1: GLES

use_gles =

Whether to use software or hardware rendering.

0: Software, 1 (default): Hardware

use_hw_renderer =

Whether to use hardware shaders to emulate 3DS shaders

0: Software, 1 (default): Hardware

use_hw_shader =

Whether to use separable shaders to emulate 3DS shaders (macOS only)

0: Off (Default), 1 : On

separable_shader =

Whether to use accurate multiplication in hardware shaders

0: Off (Default. Faster, but causes issues in some games) 1: On (Slower, but correct)

shaders_accurate_mul =

Whether to use the Just-In-Time (JIT) compiler for shader emulation

0: Interpreter (slow), 1 (default): JIT (fast)

use_shader_jit =

Forces VSync on the display thread. Usually doesn’t impact performance, but on some drivers it can

so only turn this off if you notice a speed difference.

0: Off, 1 (default): On

use_vsync_new =

Reduce stuttering by storing and loading generated shaders to disk

0: Off, 1 (default. On)

use_disk_shader_cache =

Resolution scale factor

0: Auto (scales resolution to window size), 1: Native 3DS screen resolution, Otherwise a scale

factor for the 3DS resolution

resolution_factor =

Texture filter name

texture_filter_name =

Limits the speed of the game to run no faster than this value as a percentage of target speed.

Will not have an effect if unthrottled is enabled.

5 - 995: Speed limit as a percentage of target game speed. 0 for unthrottled. 100 (default)

frame_limit =

Overrides the frame limiter to use frame_limit_alternate instead of frame_limit.

0: Off (default), 1: On

use_frame_limit_alternate =

Alternate speed limit to be used instead of frame_limit if use_frame_limit_alternate is enabled

5 - 995: Speed limit as a percentage of target game speed. 0 for unthrottled. 200 (default)

frame_limit_alternate =

The clear color for the renderer. What shows up on the sides of the bottom screen.

Must be in range of 0.0-1.0. Defaults to 0.0 for all.

bg_red =
bg_blue =
bg_green =

Whether and how Stereoscopic 3D should be rendered

0 (default): Off, 1: Side by Side, 2: Anaglyph, 3: Interlaced

render_3d =

Change 3D Intensity

0 - 100: Intensity. 0 (default)

factor_3d =

The name of the post processing shader to apply.

Loaded from shaders if render_3d is off or side by side.

Loaded from shaders/anaglyph if render_3d is anaglyph

pp_shader_name =

Whether to enable linear filtering or not

This is required for some shaders to work correctly

0: Nearest, 1 (default): Linear

filter_mode =

[Layout]

Layout for the screen inside the render window.

0 (default): Default Top Bottom Screen, 1: Single Screen Only, 2: Large Screen Small Screen, 3: Side by Side

layout_option =

Toggle custom layout (using the settings below) on or off.

0 (default): Off, 1: On

custom_layout =

Screen placement when using Custom layout option

0x, 0y is the top left corner of the render window.

custom_top_left =
custom_top_top =
custom_top_right =
custom_top_bottom =
custom_bottom_left =
custom_bottom_top =
custom_bottom_right =
custom_bottom_bottom =

Swaps the prominent screen with the other screen.

For example, if Single Screen is chosen, setting this to 1 will display the bottom screen instead of the top screen.

0 (default): Top Screen is prominent, 1: Bottom Screen is prominent

swap_screen =

Toggle upright orientation, for book style games.

0 (default): Off, 1: On

upright_screen =

Dumps textures as PNG to dump/textures/[Title ID]/.

0 (default): Off, 1: On

dump_textures =

Reads PNG files from load/textures/[Title ID]/ and replaces textures.

0 (default): Off, 1: On

custom_textures =

Loads all custom textures into memory before booting.

0 (default): Off, 1: On

preload_textures =

[Audio]

Whether or not to enable DSP LLE

0 (default): No, 1: Yes

enable_dsp_lle =

Whether or not to run DSP LLE on a different thread

0 (default): No, 1: Yes

enable_dsp_lle_thread =

Which audio output engine to use.

auto (default): Auto-select, null: No audio output, sdl2: SDL2 (if available)

output_engine =

Whether or not to enable the audio-stretching post-processing effect.

This effect adjusts audio speed to match emulation speed and helps prevent audio stutter,

at the cost of increasing audio latency.

0: No, 1 (default): Yes

enable_audio_stretching =

Which audio device to use.

auto (default): Auto-select

output_device =

Output volume.

1.0 (default): 100%, 0.0; mute

volume =

[Data Storage]

Whether to create a virtual SD card.

1 (default): Yes, 0: No

use_virtual_sd =

[System]

The system model that Citra will try to emulate

0: Old 3DS, 1: New 3DS (default)

is_new_3ds =

The system region that Citra will use during emulation

-1: Auto-select (default), 0: Japan, 1: USA, 2: Europe, 3: Australia, 4: China, 5: Korea, 6: Taiwan

region_value =

The clock to use when citra starts

0: System clock (default), 1: fixed time

init_clock =

Time used when init_clock is set to fixed_time in the format %Y-%m-%d %H:%M:%S

set to fixed time. Default 2000-01-01 00:00:01

Note: 3DS can only handle times later then Jan 1 2000

init_time =

[Camera]

Which camera engine to use for the right outer camera

blank (default): a dummy camera that always returns black image

camera_outer_right_name =

A config string for the right outer camera. Its meaning is defined by the camera engine

camera_outer_right_config =

The image flip to apply

0: None (default), 1: Horizontal, 2: Vertical, 3: Reverse

camera_outer_right_flip =

… for the left outer camera

camera_outer_left_name =
camera_outer_left_config =
camera_outer_left_flip =

… for the inner camera

camera_inner_name =
camera_inner_config =
camera_inner_flip =

[Miscellaneous]

A filter which removes logs below a certain logging level.

Examples: :Debug Kernel.SVC:Trace Service.:Critical

log_filter = *:Info

[Debugging]

Record frame time data, can be found in the log directory. Boolean value

record_frame_times =

Port for listening to GDB connections.

use_gdbstub=false
gdbstub_port=24689

To LLE a service module add “LLE<module name>=true”

[WebService]

Whether or not to enable telemetry

0: No, 1 (default): Yes

enable_telemetry =

URL for Web API

web_api_url = https://api.citra-emu.org

Username and token for Citra Web Service

See https://profile.citra-emu.org/ for more info

citra_username =
citra_token =

[Video Dumping]

Format of the video to output, default: webm

output_format =

Options passed to the muxer (optional)

This is a param package, format: [key1]:[value1],[key2]:[value2],…

format_options =

Video encoder used, default: libvpx-vp9

video_encoder =

Options passed to the video codec (optional)

video_encoder_options =

Video bitrate, default: 2500000

video_bitrate =

Audio encoder used, default: libvorbis

audio_encoder =

Options passed to the audio codec (optional)

audio_encoder_options =

Audio bitrate, default: 64000

audio_bitrate =

Looks like it already is set to that.

image

You didn’t provide a rom to citra.exe, check my previous reply how to do that.

After you type: "C:\Users\casa 354\AppData\Local\Citra\nightly-mingw\citra.exe" you need add the path to a rom, then you can press enter to run citra.exe and it will open that rom.

I tried to start the game with the room, but I generated this citra_log.txt (12.7 KB)