User talk:Wildgoosespeeder/sandbox

Suggestions

This talk page or section has a conflict or question that needs to be answered. Please try to help and resolve the issue by leaving a comment.

Here are some tips based on my own experience. I suggest you read TCRF's guidelines thoroughly.
Various systems

• NO$GBA
  • on DS/i (at least) You must set NO$GBA to "poppy bright" to get proper colours
• ripped in-game video frames
  • should be marked as "sprite", not screenshot

DS/i

• NO$GBA
  • Never use NO$GBA for 3D
• capture card
  • hold start+select when capturing DS/i software via a 3DS capture card, so the software is run at native resolution

3DS

• capture card
  • make sure the software is updated, as older versions seemed to produced screenshots with dark borders

Wii U

• capture card
  • use a capture card that is suitable for high resolution images, and does not use lossy compression

--Hiccup (talk) 04:36, 10 February 2016 (EST)

This is nice things to add to the guide (especially NO$GBA-related suggestions), but this doesn't answer my original question. Internally before the rendered frame is sent to HDMI, can the Wii U produce a 1920x1080 image?

Oh, sorry. I don't actually know about the Wii U hardware's workings. I will ask at wiiubrew.org. --Hiccup (talk) 06:52, 10 February 2016 (EST)

RE: Wii U

Unfortunately I don't own a Wii U, let alone have a deep understanding of how it works. Regarding the actual draft I have several concerns:

• For starters, this page encourages the use of {{image-quality}} when the image doesn't comply with these standards. As I stated earlier, the image-quality template was created for one purpose, to mark poor quality images with high-priority. Using it for every image that simply doesn't follow these standards is an overshot, and will reduce its usefulness.
• Requiring PNG compression is also another thing that complicates the situation. Even though the compressed image has the same quality as the original image, usually, the difference in size is so minor, that it becomes a slow and tedious task to compress every image being uploaded. Forcing uploaders to use it, as the introduction implies is not something I agree with, PNG-Monstar is an unnecessary additional step to otherwise an already difficult process of capturing images following these standards and the intro should be changed to reflect that the uploader should use it, but it is not a requirement.
• Discouraging screenshots taken from YouTube videos is another huge mistake. Say a user finds an article with no image, and he doesn't have the necessary setups to take such screenshot, in that case, he should be encouraged to fix the no-image issue by getting a simple screenshot from any YouTube video he comes across, and tag it with {{image-quality}} if, and only if it has poor quality.
• N64 screenshots: As I stated earlier, I'm aware of the fact that the N64 system's internal resolution is 320 × 240. But as far as I know, if you use a capture card, you get a 640 × 480 shot. And our screenshots should reflect that fact and show the images, as the original hardware shows it, which brings me to the next point...
• GCN, and Wii screenshots: in the actual draft, this is a huge inconsistency. We can get screenshots as close as the native IR as we can by using a few settings, and I actually agree with that to an extend, but I remember discussing that with a few people a few years ago, and the general response was: there is no reason to have standards for Dolphin's screenshots, and that the higher the resolution is (even if beyond the hardware's native IR) the better the image is, but why have a complicated set of standards for otherwise a good working system.

At this point, I'm not actually supporting the draft, the GCN and Wii resolution inconsistency problem should be tackled first, and if it is not solved. Well, there is no reason to make a law that goes around the reality. It's a worthless page. Unless it was changed to a help page instead.--

09:04, 10 February 2016 (EST)