Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sf2dlib issue: Restricting output texture coordinate to two components crashes hardware #43

Open
neobrain opened this issue Oct 10, 2015 · 0 comments

Comments

@neobrain
Copy link
Owner

xerpi/sf2dlib@26be2ea (compiled against devkitPro/libctru@b9e5ddb) moved from aemstro shaders to nihstro. However, the shader had to be modified a bit: The aemstro shader used

.out o1, result.texcoord0, 0x3

while the nihstro shader uses

.alias outtex0 o1 as texcoord0 

instead of the direct translation

.alias outtex0 o1.xy as texcoord0

This is because the direct translation caused a crash on real hardware. We're not sure why that is, currently.

@neobrain neobrain changed the title sf2dlib issue: Restricing output texture coordinate to two components crashes hardware sf2dlib issue: Restricting output texture coordinate to two components crashes hardware Oct 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant