Screenshots without Miiverse

Does anybody own a capture card? That could make screenshots for submissions?

Does anybody own a capture card? That could make screenshots for submissions?

The current news is that the next update of SB (3.7?) will contain a native screenshot feature. SmileBoom's tests indicate that it will use JPEG and have a similar (if not exact) quality to Miiverse, so they're probably leveraging a system API feature. At any rate, there are far less expensive methods of obtaining screenshots, though perhaps less consistent, than a capture device.

Just homebrew your 3DS and you can not only do screenshots but you can do live game capture over WiFi and it's pretty fast and reliable.

You can also use pmodem to transfer your graphics (sprites and what not) to your computer then create a "screenshot" of what the game would look like or some game art using an image editor like gimp or paint. For text games you just need the font.

Just get/use the Rosalina menu (With a 3DS that has CFW) to take screenshots. You definitely don't need to buy a capture card and pop open the 3DS and start smoldering stuff. Just hack it, it's cheaper and quicker. It's really easy, but if you don't think you can handle it, then you might be able to find someone in your area who can, check craigslist, I've seen ads before of people offering to hack it for $20. (If you do have CFW, remember to just press (all at once) L + DOWN + SELECT to open the Rosalina menu, and then select "Take screenshot")

Just get/use the Rosalina menu (With a 3DS that has CFW) to take screenshots.

Oh, I didn't know that existed! Thank you thank you

https://twitter.com/notohoho/status/971035860077563904 This tweet says that version 3.6 will be releasing next Wednesday (in Japan, one can assume) and it contains a screenshot function. Someone else can badger about an overseas update date, I hate using Twitter. They also added one new function, CHKMML(). This function validates an MML string; it returns -1 if the string is valid MML, or the character index of the first MML error it finds. It's like INSTR(), but it looks for MML errors instead of text. Really good.

https://twitter.com/notohoho/status/971035860077563904 This tweet says that version 3.6 will be releasing next Wednesday (in Japan, one can assume) and it contains a screenshot function. Someone else can badger about an overseas update date, I hate using Twitter. They also added one new function, CHKMML(). This function validates an MML string; it returns -1 if the string is valid MML, or the character index of the first MML error it finds. It's like INSTR(), but it looks for MML errors instead of text. Really good.

Ooh that will definitely help a lot. Did they mention anything about bug fixes and how the screenshot will be output?

https://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Fsmilebasic.com%2Fdebug%2F here's the update page google-translated. don't know about an overseas date yet, has anyone asked?

In the image data of DEFBG, the color of the edge of characters included in (0, 16) - (511, 47) was changed in Ver.3.5.2

seems like they fixed the unholy "some of the characters in the SYS tile GRP became transparent" bug

I'm hyped for the v3.6.0! Hopefully it comes out tomorrow, since there's not really anything to translate. ^{Wait a minute...}

The update will be here really soon The dev (@notohoho) responded to my Tweet saying Regarding the US version and the EU version, the translation is over and the application is being prepared. Please wait a moment as the screening will be delivered as soon as the screening is done! Thank you for enjoying SmileBASIC. https://twitter.com/notohoho/status/974038004846141440?s=09

Hopefully the start button lag isn't too unbearable... I'll have to see what other people think before updating. EDIT: also how did this become the 3.6 discussion thread?

EDIT: also how did this become the 3.6 discussion thread?

When snail mentioned the update with the new screenshot function being relevant.

I updated Japanese Smile BASIC to ver 3.6.0 this evening. The game screen shot and editor can be captured with single SELECT button press.(holding SELECT will capture 1 screen shot) Both upper and lower screen shot are saved separately as compressed JPG format on SD card (DCIM folder) (by the way, SELECT button capture doesn't work on TOP MENU screen.) Here is screen shot of my (gasp!) Slime Vs Ninja ver 2!!! Use zoom-in feature in your favorite picture editor to see JPEG compression. If lower screen is not used, black picture is saved. Here is new CHKMML command It points out the position of error in MML.(it returns -1 if there is no error) START button starts program instantly. When ptogram is running, hold the START button about 0.5 second to stop the program. 0.5 second seems too short, but it may prevent accidental quitting. No more accidental quitting now. Yay! BUTTON() command returns 1024 when SELECT button is pressed.(but at the same time, it saves current screen shot to SD card.) START button can't be detected by BUTTON command at all.

uncompressed picture from other capture device

Here is Nisetro capture card screen shot. use it to compare with above JPG screen shot. When Select button is pressed, lower screen shows the spinning saving/loading icon.

Nice, screenshots seem to be of comparable quality to Miiverse, if not better. About half a second seems alright for the START delay. I find it weird that they didn't make the START delay slightly longer and allow you to read it from BUTTON() instead of SELECT. I can only assume they did this for compatibility. Since every press takes a screenshot I can't imagine detecting SELECT will ever be useful. Is it fast to take a screenshot?

Awesome! But it kinda sucks that it's JPEG and not PNG

You could use this technique to measure the exact time required to hold the START button: Put this code in the editor and start it. Then, hold START and some other button (preferably not A, since that's also Enter) until the program quits. The last number is the time in milliseconds you have to hold START until it exits.

VAR M%

WHILE TRUE
 IF BUTTON() THEN
  IF M% THEN
   ?MILLISEC-M%
  ELSE
   M%=MILLISEC
  ENDIF
 ELSE
  M%=0
 ENDIF
WEND

here is result from old 3DS here is result from new 3DS both are around 250 milliseconds. also, I was holding R button and spammed SELECT and got several screen shots. 940 -> 3047 -> 5187 it seems saving screen shot takes about 2100 milliseconds on old 3DS and got 490 -> 2345 -> 4083 -> 5838 on new 3DS. about 1700 milliseconds on new 3DS. also, saving causes slight delay on old 3DS.

Hmm very cool, can't wait for it

Well, I'm definitely not updating. 0.5 seconds is a very long time... I was expecting something like 10 frames, but half a second to end a program is not ok.