Homebrew Official Citra - New 3DS Emulator

  • Thread starter Thread starter bunnei
  • Start date Start date
  • Views Views 3,859,173
  • Replies Replies 7,211
  • Likes Likes 175
Last edited by Dragios,
@Dragins nice work ^^ I try to play Bravyl default in Citra Edge and our Build but I'm stuck at Issue # 1822 https://github.com/citra-emu/citra/issues/1822. I hope the emulator will rise and rise ^^
You build sadly has this issue too. But I the future ^^ Thanks for your work
 

Attachments

  • Citra.png
    Citra.png
    30.7 KB · Views: 221
@Dragins Nice thanks. PS, .pdb files are just junk not really needed for the package and just adds to size of.

They are not, they might actually be useful in many cases. However, in this context they might not.
@Dragios should follow / use our build tools for security/compatibility. If we still kept in pdb then he should keep it, otherwise I agree.
(There were some discussions about these in the past and I believe we removed them as we can just have supportive users recompile for debugging)

@Dragins nice work ^^ I try to play Bravyl default in Citra Edge and our Build but I'm stuck at Issue # 1822 https://github.com/citra-emu/citra/issues/1822. I hope the emulator will rise and rise ^^
You build sadly has this issue too. But I the future ^^ Thanks for your work

Expected.. it's the same codebase as for the official nightly build, the official bugtracker still applies. Until somebody looks into it or fixes the underlying problem don't expect any progress.

View attachment 67696got a new kid icarus decripted and I still get this. On official i get the error spam

Don't post errors with unofficial builds here (+ likely a missing home folder dump / however, do not respond to me in this thread, it's offtopic).

Only post bleeding edge problems here (but don't expect help, as it's officially unsupported, so if you get help, you are in luck).
You can also, as a temporary exception, post errors with @Dragios build (+ limited support!) until we notice something to be different from our builds (which are temporarily unavailable).
Note that builds by @Dragios are only considered semi-official, while we tolerate posting those links on official channels and will provide limited support, we can't say anything about security etc.
As soon as our official distribution channels are back to normal, we will only allow bleeding edge (no support) and nightly build (support by contributors) discussion again.
 
  • Like
Reactions: drwhojan
They are not, they might actually be useful in many cases. However, in this context they might not.
@Dragios should follow / use our build tools for security/compatibility. If we still kept in pdb then he should keep it, otherwise I agree.
(There were some discussions about these in the past and I believe we removed them as we can just have supportive users recompile for debugging)



Expected.. it's the same codebase as for the official nightly build, the official bugtracker still applies. Until somebody looks into it or fixes the underlying problem don't expect any progress.



Don't post errors with unofficial builds here (+ likely a missing home folder dump / however, do not respond to me in this thread, it's offtopic).

Only post bleeding edge problems here (but don't expect help, as it's officially unsupported, so if you get help, you are in luck).
You can also, as a temporary exception, post errors with @Dragios build (+ limited support!) until we notice something to be different from our builds (which are temporarily unavailable).
Note that builds by @Dragios are only considered semi-official, while we tolerate posting those links on official channels and will provide limited support, we can't say anything about security etc.
As soon as our official distribution channels are back to normal, we will only allow bleeding edge (no support) and nightly build (support by contributors) discussion again.
Sure, however your build gives me error too so... you can help too
 
okay, kid icarus works.

When one gets to a massage yes are no, chose no, are stuck on crate name, no for your default systems name
---

Fixing left right eye in Stereoscopic worked well, now the 3d will bool left and right to the eye - big green list in renderer_opengl.cpp
https://github.com/Jhno591/citra-bleeding-edge/commit/8439f07cb45453e90619ce011cbd4a59f8b384a6

but still no red screen fix for games like rune factory 4, apart from budging the slide bar up a touch about 0.1% that fixes it , anyone know why ?, effects very few games only.

If can be fixed ?, please edit it into the source url , I'll compile and test it.

MI2m3Dn.jpg

2G0Di86.jpg
 
Last edited by drwhojan,
It's playable on Bleeding Edge 0.1.45
Thank you for the info. Do you happen to know at what framerates it runs? As well do I have to run a decrypted backup?
Specs are:
AMD FX 6200 OC'd to 4.2GHz
GTX 750 TI Superclocked
16GB ddr4 RAM (32gb readyboost, for lulz)
I have build 0.1.45 as well.
 

Site & Scene News

Popular threads in this forum