search

LumaTeam / Luma3DS

Nintendo 3DS "Custom Firmware"
GNU General Public License v3.0
5.2k stars 556 forks source link

Gba virtual consoles screen issues #355

Closed jcmejia closed 7 years ago

jcmejia commented 7 years ago

Gba virtual consoles have screen issues on luma3ds 6.6 firmware 11.3.0-36u

Margen67 commented 7 years ago

What is the allocation unit size of the SD card?

jcmejia commented 7 years ago

128gb

jcmejia commented 7 years ago

On new 3ds

jcmejia commented 7 years ago

It was working fine on 11.2 on luma3ds

piratesephiroth commented 7 years ago

what's even a screen issue?

jcmejia commented 7 years ago

After I updated Luma to 11.3 it started having issues

jcmejia commented 7 years ago

Try a gba virtual consoles on Luma3ds on firmware 11.3

jcmejia commented 7 years ago

The resolution is messed up I'd post a pic of it but I don't know if I could

cheatfreak47 commented 7 years ago

@jcmejia

128GB

Bingo, I've found the issue.

Basically, GBA games sometimes have an issue where the screen is mapped improperly when using a card that is too slow. This is not a Luma issue, this happens even on stock systems. 128GB cards tend to not be as fast as smaller size cards, which may be the cause here.

As @Margen67 was asking, the allocation unit size (sometimes called cluster size) can also have an impact on this, so your only hope of fixing this issue is to change it.

The best course of action is to backup your entire SD card to your computer and format the SD card using this tool.

When formatting set the Allocation Unit Size to "32768", and make sure you pick your SD card and not some other important drive, and from there, if you are lucky, the GBA issue will disappear, otherwise tough luck, it's nothing we can just fix.

Then restore the backup of the SD you made before formatting.

In the meantime, this is not only a non-luma issue, but also a duplicate of an issue that was already closed, and thus this should also be closed.

shinji257 commented 7 years ago

Duplicate: https://github.com/AuroraWright/Luma3DS/issues/142

jcmejia commented 7 years ago

The cluster size I don't know but I will check it later but I think it's a 32kb cluster

On Feb 7, 2017 11:36 AM, "Matt" notifications@github.com wrote:

@jcmejia https://github.com/jcmejia

128GB Bingo, I've found the issue.

Basically, GBA games sometimes have an issue where the screen is mapped improperly when using a card that is too slow. This is not a Luma issue, this happens even on stock systems. 128GB cards tend to not be as fast as smaller size cards, which may be the cause here.

As @Margen67 https://github.com/Margen67 was asking, the allocation unit size (sometimes called cluster size) can also have an impact on this, so your only hope of fixing this issue is to change it.

The best course of action is to backup your entire SD card to your computer and format the SD card using this tool https://cdn.discordapp.com/attachments/265713680560160768/278579320287395840/guiformat.zip . When formatting set the Allocation Unit Size to "32768", and make sure you pick your SD card and not some other important drive, and from there, if you are lucky, the GBA issue will disappear, otherwise tough luck, it's nothing we can just fix.

In the meantime, this is not only a non-luma issue, but also a duplicate of an issue that was already closed, and thus this should also be closed.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278077313, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgR5ZOx-pjFjOQAnCS0k4ZXYywh5Zlks5raKuSgaJpZM4L5r-0 .

jcmejia commented 7 years ago

Besides that it was working fine until I updated Luma to 11.3

On Feb 7, 2017 1:39 PM, "jean claude mejia" claudemejiajean@gmail.com wrote:

The cluster size I don't know but I will check it later but I think it's a 32kb cluster

On Feb 7, 2017 11:36 AM, "Matt" notifications@github.com wrote:

@jcmejia https://github.com/jcmejia

128GB Bingo, I've found the issue.

Basically, GBA games sometimes have an issue where the screen is mapped improperly when using a card that is too slow. This is not a Luma issue, this happens even on stock systems. 128GB cards tend to not be as fast as smaller size cards, which may be the cause here.

As @Margen67 https://github.com/Margen67 was asking, the allocation unit size (sometimes called cluster size) can also have an impact on this, so your only hope of fixing this issue is to change it.

The best course of action is to backup your entire SD card to your computer and format the SD card using this tool https://cdn.discordapp.com/attachments/265713680560160768/278579320287395840/guiformat.zip . When formatting set the Allocation Unit Size to "32768", and make sure you pick your SD card and not some other important drive, and from there, if you are lucky, the GBA issue will disappear, otherwise tough luck, it's nothing we can just fix.

In the meantime, this is not only a non-luma issue, but also a duplicate of an issue that was already closed, and thus this should also be closed.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278077313, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgR5ZOx-pjFjOQAnCS0k4ZXYywh5Zlks5raKuSgaJpZM4L5r-0 .

cheatfreak47 commented 7 years ago

Look, I know exactly what your issue is and I've done research into it personally, and I'm telling you the issue is definitely related to SD card speed and has nothing to do with the update, nothing to do with Luma, and nothing to do with hacking either.

Nintendo hasn't touched AGB_FIRM since ~they added it with the ambassador program back when it was introduced~ firmware update 6.0, which was well over 2 years ago.

You probably just never encountered the issue before, because it's not entirely consistent. It happens seemingly randomly with different SD card sizes and cluster sizes.

jcmejia commented 7 years ago

So what do you recommend

On Feb 7, 2017 1:44 PM, "Matt" notifications@github.com wrote:

Look, I know exactly what your issue is and I've done research into it personally, and I'm telling you the issue is definitely related to SD card speed and has nothing to do with the update, nothing to do with Luma, and nothing to do with hacking either.

Nintendo hasn't touched AGB_FIRM since they added it with the ambassador program back when it was introduced.

You probably just never encountered the issue before, because it's not entirely consistent. It happens seemingly randomly with different SD card sizes and cluster sizes.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278117987, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgRwqduoAOsFcVKKQ15LbFt7z4Bu6dks5raMm4gaJpZM4L5r-0 .

cheatfreak47 commented 7 years ago

What I said above, reformatting the card as FAT32 with 32,768 bytes per allocation unit (cluster size) and hoping the issue goes away.

If it doesn't either deal with it or get a 64GB SD card instead and deal with the spacial limitations that comes with.

Those are the only options for fixing it, unfortunately.

Margen67 commented 7 years ago

Or you could use a GBA emulator

Rust-and-Sunset commented 7 years ago

Obviously, this isn't a Luma issue- but I have noticed that this issue only crops up in certain titles.

Kurukuru Kururin, for example, exhibits the issue- whereas, say, FF Tactics Advance doesn't. Might explain why @jcmejia didn't notice the issue previously - if they're trying a VC inject they hadn't used prior to upgrading Luma version, and it happens to be one of the unlucky ones, they wouldn't have any idea what prompted the change.

If you'd like some confirmation, try some other games.

jcmejia commented 7 years ago

Actually it was happening with sonic advance 2 and 3 on emunand but not on system nand

On Feb 8, 2017 6:39 PM, "StateOfException" notifications@github.com wrote:

Obviously, this isn't a Luma issue- but I have noticed that this issue only crops up in certain titles.

Kurukuru Kururin, for example, exhibits the issue- whereas, say, FF Tactics Advance doesn't. Might explain why @jcmejia https://github.com/jcmejia didn't notice the issue previously - if they're trying a VC inject they hadn't used prior to upgrading Luma version, and it happens to be one of the unlucky ones, they wouldn't have any idea what prompted the change.

If you'd like some confirmation, try some other games.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278509905, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgRwL1m6711tWBHpKu8s0oUGxumGMwks5ramAjgaJpZM4L5r-0 .

jcmejia commented 7 years ago

But I did notice a slight fix by pressing the home button a couple of times

On Feb 8, 2017 6:40 PM, "jean claude mejia" claudemejiajean@gmail.com wrote:

Actually it was happening with sonic advance 2 and 3 on emunand but not on system nand

On Feb 8, 2017 6:39 PM, "StateOfException" notifications@github.com wrote:

Obviously, this isn't a Luma issue- but I have noticed that this issue only crops up in certain titles.

Kurukuru Kururin, for example, exhibits the issue- whereas, say, FF Tactics Advance doesn't. Might explain why @jcmejia https://github.com/jcmejia didn't notice the issue previously - if they're trying a VC inject they hadn't used prior to upgrading Luma version, and it happens to be one of the unlucky ones, they wouldn't have any idea what prompted the change.

If you'd like some confirmation, try some other games.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278509905, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgRwL1m6711tWBHpKu8s0oUGxumGMwks5ramAjgaJpZM4L5r-0 .

Rust-and-Sunset commented 7 years ago

But I did notice a slight fix by pressing the home button a couple of times

...Strange. This does actually have an effect- rapidly tapping the Home button shifts the output up by a certain interval on each press. Seems to take place during the transition time between the back-to-Home-Menu dialog being called and its pop-in animation completing.

This is the result:

vcinterval

By repeatedly doing that, it's possible to make the output loop all the way around, making it output correctly. Takes about a minute or so of tapping, tops.

Peculiar bug.

(It also doesn't seem to trigger if you force pixel-perfect output by holding Start as you boot the title- definitely an option worth considering, if you don't want to bother with the above solution.)

jcmejia commented 7 years ago

Yes that's exactly what I did but for me it was less than a minute

On Feb 8, 2017 6:49 PM, "StateOfException" notifications@github.com wrote:

But I did notice a slight fix by pressing the home button a couple of times

...Strange. This does actually have an effect- rapidly tapping the Home button shifts the output up by a certain interval on each press. Seems to take place during the transition time between the back-to-Home-Menu dialog being called and its display animation completing displaying.

This is the result:

[image: vcinterval] https://cloud.githubusercontent.com/assets/13955128/22764253/6ba6a592-ee61-11e6-83e2-818d16ce16e2.jpg

By repeatedly doing that, it's possible to make the output loop all the way around, making it output correctly. Takes about a minute or so of tapping, tops.

Peculiar bug.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278511667, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgR59THh03PLRGa3adZJHGy7IaUbnvks5ramKHgaJpZM4L5r-0 .

Margen67 commented 7 years ago

This is why you shouldn't use emuNAND.

Rust-and-Sunset commented 7 years ago

It's not just an EmuNAND issue, @Margen67 - I can reproduce it from SysNAND.

Not really a big deal, I suppose. Would be nice to have some kind of way of preventing it happening, but that moves well out of bug report territory into feature requests.

jcmejia commented 7 years ago

So should I use system nand

On Feb 8, 2017 6:54 PM, "Margen67" notifications@github.com wrote:

This is why you shouldn't use emuNAND.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278512570, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgRwG8Z1ZWADRs3aF3MPowk0lhWsnfks5ramOygaJpZM4L5r-0 .

Rust-and-Sunset commented 7 years ago

@jcmejia This isn't really the correct place to ask for general tech support. I recommend asking in /r/3dshacks' Q&A thread.

(But, yes- you should transfer your EmuNAND setup to SysNAND. Ask in the Q&A thread if you're not sure how that's done.)

urherenow commented 7 years ago

So... yes, the screen scrolling with the home button IS a bug.

But for future reference, VC titles from emunand pose a problem on a variety of setups (hacky reboot patches required to work AT ALL in the case of GBA stuff) so it is best practice to use sysnand for VC. The latest guides for a9lh don't even bother telling you to make an emunand anymore.

Margen67 commented 7 years ago

it is best practice to use sysnand for VC.

It's best practice to use sysNAND for everything not just VC unless you're a developer, want to bypass the 300 title limit, or region change. Otherwise it's just a waste of SD card space.

jcmejia commented 7 years ago

I will probably stick with emunand cause I haven't installed a9lh before I heard it's very risky due to random bricks I'm actually more skilled with wii/wii u modding I'm actually still learning on 3ds modding I'm actually a fast learner when it comes to modding besides that thanks for letting me know about a9lh I might install it sometime in the near future.

On Feb 8, 2017 8:08 PM, "urherenow" notifications@github.com wrote:

So... yes, the screen scrolling with the home button IS a bug.

But for future reference, VC titles from emunand pose a problem on a variety of setups (hacky reboot patches required to work AT ALL) so it is best practice to use sysnand for VC. The latest guides for a9lh don't even bother telling you to make an emunand anymore.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AuroraWright/Luma3DS/issues/355#issuecomment-278525420, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMgR0O_stU-FIDCKonSHW106Eq0Kt7vks5ranUMgaJpZM4L5r-0 .

Margen67 commented 7 years ago

@jcmejia All bricks are due to user error. As long as you follow the guide you won't brick. https://3ds.guide/