Very annoying that Nintendo never fixed this bug

  • Thread starter Thread starter KelSolaar
  • Start date Start date
  • Views Views 5,177
  • Replies Replies 33
  • Likes Likes 1
No company fixes problems such as these (which, admittedly affect less than 1% of Wii U users) until lawyers file class action suits. Otherwise publicly-traded companies cannot be bothered to spend the money.
 
It affects exactly one batch of chips in the early days of the console, newer consoles are unaffected (so as ChibiMofo said: It's just around 1% of consoles having this bug, most likely more like 0.001% or less) and Nintendo RMAed affected consoles even after guarantee time. How exactly do you call that "never fixed this bug" ?
 
  • Like
Reactions: E1ite007
It affects exactly one batch of chips in the early days of the console, newer consoles are unaffected (so as ChibiMofo said: It's just around 1% of consoles having this bug, most likely more like 0.001% or less) and Nintendo RMAed affected consoles even after guarantee time. How exactly do you call that "never fixed this bug" ?

Can you show me any evidence that PAL Wii U's can run Wii games in progressive scan when using component cable?
To my knowledge the issue was never fixed in any PAL revisions of the console.
 
So I only see one problem here...the creator of the video should urgently change his thumbnail. The error shown on the thumbnail has nothing to do with the problem in the video.

Btw...what is this actually about? Is it about the resolution? Image quality? Or about this deflicker filter? Because there is a fix for this in the usb loader. But for quite a long time.

Otherwise....enlighten me.
 
  • Like
Reactions: SDIO
No company fixes problems such as these (which, admittedly affect less than 1% of Wii U users) until lawyers file class action suits. Otherwise publicly-traded companies cannot be bothered to spend the money.
In this particular case, Nintendo skimped on using reliable NAND flash chips.
 
So I only see one problem here...the creator of the video should urgently change his thumbnail. The error shown on the thumbnail has nothing to do with the problem in the video.

Btw...what is this actually about? Is it about the resolution? Image quality? Or about this deflicker filter? Because there is a fix for this in the usb loader. But for quite a long time.

Otherwise....enlighten me.

It’s explained in the video. In short: PAL Wii Us can’t run Wii games in progressive scan when using component cable.
 
  • Like
Reactions: CrazySquid
It’s explained in the video. In short: PAL Wii Us can’t run Wii games in progressive scan when using component cable.
Not sure if all units do it, heard someone saying that his NTSC unit did the same.
This maybe could be patched via DMCU.
 
Not sure if all units do it, heard someone saying that his NTSC unit did the same.
This maybe could be patched via DMCU.

I haven’t came across anyone that have gotten a PAL Wii U to run Wii games in progressive scan. This issue only affects PAL consoles. The issue is present even if you change the region of vWii.
I haven’t tried out doing a region change of the Wii U though.
 
This issue only affects PAL consoles. The issue is present even if you change the region of vWii.
That's why I said it also seems to affect NTSC units as well, can't confirm since I haven't tried, but I heard someone said on Discord that his NTSC unit wasn't doing progressive over component.
 
That's why I said it also seems to affect NTSC units as well, can't confirm since I haven't tried, but I heard someone said on Discord that his NTSC unit wasn't doing progressive over component.

I would like to know if this really affected NTSC consoles
 
I would like to know if this really affected NTSC consoles
I have an American Wii U with component cables, I might try later to see if it happens here, but I have to find where I had put those cables though. It's also a launch unit from 2012.

Well you don't exactly fix a hardware issue on older units. The issue was corrected with later consoles.
I haven't seen evidence pointing this to be a hardware issue, worst case scenario I believe it may just be a bug in the AV controller, but I'm not seeing a hardware problem unless someone points it is with some evidence.
 

Site & Scene News

Popular threads in this forum