Also not getting sound on the .cia version, although I get sound on the .cia version of Blarg. I'm on Luma3ds
Homebrew SNES9x for Old 3DS
- Thread starter bubble2k16
- Start date
- Views 789,946
- Replies 2,478
- Likes 146
The CIA are completely instable quit the app with home crash the 3ds on dragon quest 6 freeze before a fight ff5 doesnt load not fullscreen mode and not sound it need many more improvement i stay at blargvc for the moment
Here are some what I have tested what doesn't work properly in blargsnes:
Dragon Ball Z Super Butoden 2 : Works perfectly, minor graphical bugs
BsZelda : Doesn't boot.
Mortal Kombat 2 : Doesn't boot.
Street Fighter Alpha : Unplayable due terrible graphical bugs.
Street Fighter II : Doesn't show up the title screen, but work perfect after that.
Super Punch Out : Work Perfectly, minor graphical bugs
Edit: forgot Super Mario Kart, works perfectly but lacks of mode 7.
Dragon Ball Z Super Butoden 2 : Works perfectly, minor graphical bugs
BsZelda : Doesn't boot.
Mortal Kombat 2 : Doesn't boot.
Street Fighter Alpha : Unplayable due terrible graphical bugs.
Street Fighter II : Doesn't show up the title screen, but work perfect after that.
Super Punch Out : Work Perfectly, minor graphical bugs
Edit: forgot Super Mario Kart, works perfectly but lacks of mode 7.
Last edited by Billy Acuña,
3dsx, I'll not use the cia until we get a stable version with improved compatibility.
Add that UMK3 also works but a little bit slower than blargg.
Star Fox 2 Boots until after the intro.
Yoshi's island can go to main menú.
Super Mario RPG Doesn't work, stays on black screen.
Mario All stars + World works almost perfectly (with some mini slowdowns).
I just noticed the smdh i made last night is enterely fucked up (curse me for using another smdh as a base). I made a new smdh from scratch and this one works fine (title, description and author).
With some slowdowns and graphical errors but otherwise working alright.
it runs at 60 fps in some areas (well, 59.5 but it's almost the same) but in ship deck it drops at under 50 fps and the sprites start to glitch themselves. It still runs at a nice playable speed so no complains here
it runs at 60 fps in some areas (well, 59.5 but it's almost the same) but in ship deck it drops at under 50 fps and the sprites start to glitch themselves. It still runs at a nice playable speed so no complains here
There's something that I also didn't considered, BlargSnes uses frame skip in some areas to keep the speed as fast as possible on DKC2.
Last edited by AtlasFontaine,
I think blargsnes runs it at 60 fps, but the music plays so slow to even enjoy it while playing
the game doesnt run at a stable fps on snes9x_3ds but at least the music depends on the game speed itself (if it is running at 59.5 fps the musics sounds like it should sound)
Hi DiscostewSM,
Thanks for the heads up. The 1024x1024 view port limitation is quite shocking... I had a look at BlargSNES. Correct me if I am wrong, but you did it in a slightly different way I suppose. You actually ray-traced every scan line to see which tiles you hit, and then you cache those tiles in software into the large texture?
Instead of doing the four corners, I think it might be better to divide the entire 1024x1024 into 4 vertical strips, each addressed by a 512x512 view port. Fortunately, since all the 8x8 tiles of the texture are morton-interleaved but the tiles themselves are laid out in sequence, this actually makes things slightly easier.
To the rest, yes I know there are teething issues. Let me have some time to work out mode 7 and the other kinks. Thanks to everyone who helped feedback on the games that don't boot!
Thanks for the heads up. The 1024x1024 view port limitation is quite shocking... I had a look at BlargSNES. Correct me if I am wrong, but you did it in a slightly different way I suppose. You actually ray-traced every scan line to see which tiles you hit, and then you cache those tiles in software into the large texture?
Instead of doing the four corners, I think it might be better to divide the entire 1024x1024 into 4 vertical strips, each addressed by a 512x512 view port. Fortunately, since all the 8x8 tiles of the texture are morton-interleaved but the tiles themselves are laid out in sequence, this actually makes things slightly easier.
To the rest, yes I know there are teething issues.
Let me have some time to work out mode 7 and the other kinks. Thanks to everyone who helped feedback on the games that don't boot!
- Joined
- Feb 10, 2009
- Messages
- 5,484
- Trophies
- 2
- Location
- Sacramento, California
- Website
- lazerlight.x10.mx
- XP
- 5,489
- Country
Hi DiscostewSM,
Thanks for the heads up. The 1024x1024 view port limitation is quite shocking... I had a look at BlargSNES. Correct me if I am wrong, but you did it in a slightly different way I suppose. You actually ray-traced every scan line to see which tiles you hit, and then you cache those tiles in software into the large texture?
Instead of doing the four corners, I think it might be better to divide the entire 1024x1024 into 4 vertical strips, each addressed by a 512x512 view port. Fortunately, since all the 8x8 tiles of the texture are morton-interleaved but the tiles themselves are laid out in sequence, this actually makes things slightly easier.
To the rest, yes I know there are teething issues.
I think you're looking at an old method I used for hardware rendered Mode 7. Before, it traced what tiles would be visible according to how the layer was set, which is slow when the layer is zoomed out. The method I spoke about involves rendering a pre-made list to the 4 corners of what is to be the Mode7 layer texture (doing 4 corners because of the limitations of the 3DS hardware), then using that layer for the actual rendering to the screen, where zooming in or out won't have nearly an impact on performance. My new method also optimized a little, rendering to this big buffer only if the corner to be rendered has changes made (whether by the tilecels themselves, or the tile map).
