Severity: High

TXT, DAT or GRP files cannot be loaded if they are generated with SmileBASIC for Wii U then overwritten with SmileBASIC (for Nintendo 3DS)

SmileBASIC may stops responding with each of the following condition

• Use FORMAT$ instruction to display more than 1024 digits of a real number
• Attemp to load any of TXT, DAT or GRP files which are generated with SmileBASIC for Wii U then overwritten with SmileBASIC (for Nintendo 3DS)
• Execute FFT/IFFT in a low memory room
• Do SHIFT or POP a string which was computed to multiple a number by a null string
• A name of a function is referred by VAR() as an array element is given to READ instruction’s parameter
• ‘%’ character is used in a caption string as attempting to display a file-name entry dialog by DIALOG instruction
• Execute RUN command after GOTO or GOSUB instruction is executed to jump to a specific label within a DEF clause where any error happens beforehand
• Execute CONT command after terminating a running program in the direct mode. RUN command should never been executed in this circumstance
• Huge number of characters like 1M characters are given to BGMPLAY instruction as a parameter
• PCMSTREAM instruction is given a null array
• Execute RUN command after a particular COMMON DEF is called in the direct mode. The SMILE TOOL has to be run after a program which calls a COMMON DEF clause in a different program slot was executed
• A particular user-defined instruction is called in the direct mode after executing CLEAR command. That user-defined function has any global array
• Execute SPHITRC to DISPLAY 0 which is the touch screen after all 512 sprites were assigned on DISPLAY 0 which is the upper screen

Severity: Middle

Decimal is also displayed by attempting to display integer

Content displayed on the screen goes wrong and the editor does not work after executing PRINT instruction in the DIRECT mode while the online help being displayed

‘Syntax Error’ happens instead of ‘Incompatible statement’ by executing XON WIIU instruction

GCIRCLE or GPIE instruction takes longer time to process a gigantic radius and a program cannot be terminated while it is in process

PROJECT instruction can take ‘.’ as a project name but it should not

PROJECT() returns a string ‘###’ while a working project is a default one

Contents of an array or string functions are unexpectedly permutated as repeating to create/release huge size of arrays or string functions

‘Subscript out of range’ error occurs as attempting to copy an array with no elements (zero-element) by COPY instruction

Leaking memory happens when DEF instruction has a wrong sentence structure

SPCHK cannot detect a termination of an animation which has no sprite setting parameter changes between frames specified by SPANIM instruction

Noise is made periodically while PCMSTREAM instruction is being executed

In case a movement speed for sprite collision detection is not set by SPCOLVEC the movement speed, which was calculated automatically for sprite collision detection is not cleared up after an XY-axis animation set by SPANIM ended

Severity: High

Vulnerability due to checking given parameters found in BGSCREEN instruction

Screen display is corrupted if a GRP file is loaded by LOAD instruction with a strings or an array specified in the second or third arguments then the application stops responding as it goes

In an infinite loop with WHILE or GOTO instruction a LOAD function with an nonexistent file and FALSE parameter specified causes a program unstoppable by pressing the STOP or START button in an error dialog

RINGCOPY instruction may bring SmileBASIC a forced termination if an negative number is set to a “copy destination offset” argument

Severity: Middle

PRGNAME function returns a corrupted file name if a program is loaded with a length of both a project and a file is 14 characters long

MIN or MAX function returns unexpected values if an array with zero elements is specified

CHKFILE function returns incorrect value if any file(s) included in a DLC project which does not exist or not yet purchased are specified

BACKTRACE instruction does not work properly in the DIRECT mode

FILES and LOAD instruction fails if PROJECT instruction points to the SYS folder as a default project

Severity: Middle

Incorrect characters on “á” key top

Incorrect definition of the standard sprite #166

Severity: High

If a DIALOG instruction with 1 frame timeout is used in an endless loop, the program does not stop with the START button, and the HOME button must be used to forcibly stop the program.

Severity: Middle

In the keyword suggestions, a keyword that does not exist, ‘CONVOL,’ will appear.

If the 3DS cover is opened or closed while a processing is stopped for a long time with the WAIT or VSYNC instructions, the executed WAIT/VSYNC instruction is cancelled.

If an array saved as graphic data with GSAVE is saved in DAT format, when attempting to load it as GRP format using LOAD, it cannot be loaded successfully.

When executing DIALOG, ACLS, and so forth, the cursor momentarily appears at the top of the screen.

Severity: High

The editing color for the Option screen cannot be changed.

Severity: Middle

When a program is executed from Browse Projects, and the program ends in an error, until Ver. 3.2.1 you could press the A button to return to the TOPMENU, but in Ver. 3.3, that is not possible.

You cannot use the Sort feature when the copy destination is selected with file copy.

About the Smile Tool

The Smile Tool program is old.

Severity: High

The system variables become faulty by specifying the system variable in INC and DEC instruction. This causes the system to get crashed when any of the system variables are referred

The system crashes or the screen layout is disordered when the TOPMENU buttons are pushed right after a program runs (The larger program the higher probability)

The system is likely to crash when a length of a calculated strings is resulted to be extraordinary long (more than 4,000,000 characters) by multiplying a string and a value

Severity: Middle

“An integer DIV a real” gives a result of “An integer / INT (a real)” not “An integer DIV INT (a real)”

Writing a line to call an undefined instruction/function in a program and CHKCALL is executed before that line then it gives TRUE in spite of the instruction/function is undefined.

RSORT is not executed as expected with specifying a starting position.

Wrong character is assigned to &H1F0, &H387, &H2014 and &H2018.

In the editor mode TO, STEP and a minim sign to a negative number is not color-coded.

Occasionally SmileBASIC does not quit by pushing HOME button while a program is running.

SPHITINFO does not result correct information when SPHITSP or SPHITRC specify the lower screen. (SPHITINFO works correctly to detect One-to-One collision)

The error message is vague when there is insufficient space in the SD card to download a program.

VAL function gives a different result by supplying a particular string consisting of numbers and non-numbers following after. The result is different between a length of the string supplied is less than 10 and more than 11.

While the screen mode is set to 4 with XSCREEN, Clipping range becomes broken when the clipping range is cleared by either GCLIP, SPCLIP or BGCLIP. This can be prevented by setting the clipping range to the whole screen manually.

Severity: Middle

In NETWORK MENU the file list shows a public key in garbled characters when a published program is revoked.

Severity: High

When loading and executing another program in the slot currently being executed with the EXEC instruction, if the BACKTRACE instruction is used after stopping the program with the STOP key, the normal trace information is not output, and at worst SmileBASIC may hang.

When stopped due to an error in the DEF definition or using STOP, if referencing or assigning the local variables in the DEF after calling the DEF instruction/function in DIRECT mode, SmileBASIC will hang.

In a program that jumps across multiple slots with the EXEC instruction, if the program jumps to the EXEC call slot two or more slots before a slot with the EXEC instruction and uses the GOTO/GOSUB/DEF instruction call at the jump destination, SmileBASIC will hang.

(For example, if the DEF instruction is used in EXEC “PRG1:FOO”→EXEC “PRG2:BAR”→EXEC “PRG1:FOO”→FOO, SmileBASIC will hang.)

On a New 3DS, if the BEEP instruction is frequently* called, SmileBASIC may hang.

* “Frequently” refers to a specification such as WHILE 1:BEEP:WEND

Severity: Medium

When drawing an arc using GCIRCLE, in some cases the arc is not drawn as intended.

(There are no issues with drawing a full circle.)

If the end of an OUT parameter in a statement is omitted, the program does not function correctly.

Workaround: Do not omit the end of the argument in the OUT parameter (do not end an OUT parameter with a comma.)

Names consisting of more than 32 characters cannot be used for variable and label names in user-defined instructions and functions.

In constant literals, the values for #BGROT90, #BGROT180, and #BGROT280 are incorrect.

When attempting to use SPCHR to turn additive synthesis off for a sprite that has the additive synthesis attribute turned on, it will not be turned off.

(There is no problem resetting SPSET.)

After a program is aborted using the STOP instruction or STOP key, if an instruction is executed and continued in DIRECT mode, an error occurs with instructions that cannot be executed in DIRECT mode.

Severity: High

If you press the HOME button after opening the SmileBASIC Web Tutorial in your browser and quit the program without restarting SmileBASIC, SmileBASIC does not quit and the 3DS must be restarted.

(There is no problem with returning to SmileBASIC from the browser.)

Severity: Medium

If you press the L or R buttons while searching or replacing on the Editor screen, the button for search/replace is replaced by the Function key icon.

When copying from the FILE MENU, the Skip and Change buttons on the Select Process dialog box do not respond when there is an existing file.

About the Smile Tool

The Smile Tool cannot be used with WIDTH 16.

Severity: High

(Workarounds are temporary.)

SmileBASIC hangs when assigning internal variables in MML.

If a constant character string is used in an argument for a function, and that argument is used directly as the first argument for the INC instruction in the function, SmileBASIC will hang.

Workaround: After copying the argument to a different variable, specify that variable in the first argument for the INC instruction.

When 0 or 4 are specified in the third argument of the XSCREEN, and BGPAGE is executed on a display that no BG is assigned to, SmileBASIC will hang.

When a coordinate value of greater than 32768 or less than -32768 is used on GLINE and a normal drawing is not drawn, SmileBASIC may hang.

When a user-defined statement or function is called in DIRECT mode and an error occurs in the statement or function, if the same user-defined statement or function is called again in DIRECT mode, SmileBASIC will hang.

When the DEF instruction is executed using the same name as a loaded instruction or function, SmileBASIC may hang.

When a syntax error occurs in a user-defined statement or function, if the erroneous user-defined statement or function is used again in DIRECT mode, SmileBASIC will hang.

If the width in the function for the BGLOAD instruction is wider than the BG screen width, SmileBASIC will hang.

If the COPY instruction is executed without a function while the program is running, SmileBASIC will hang.

If a large program or a program with a large number of DEF and DATA statements is executed, memory will be corrupted and SmileBASIC will hang.

(The criterion for occuring data corruption is as follows: a program size of one megabyte, 900 DEFs, 200,000 actual and 340,000 integer DATA statements, and one million character strings per slot.)

Severity: Medium

(Workarounds are temporary.)

The SPSET function type does not run correctly with DISPLAY 1.

Workaround: When using a function type, run it on DISPLAY 0 or XSCREEN 0, 1, or 4.

If a comment with REM is attached to the end of an IF statement, the next line will be interpreted as the THEN continuation.

Workaround: Attach a comment with an apostrophe (‘).

If 0 or 512 are specified in the second argument in the XSCREEN instruction, the BGPAGE settings will be ignored on the display for which a sprite has not been assigned.

Workaround: Avoid specifying 0 or 512 in the second argument.

After specifying or assigning a constant string for a user-defined statement or function argument/OUT variable is a character string, if the first argument of PUSH, POP, SHIFT, or UNSHIFT is specified directly, a type mismatch error will occur

If the magnification is actual size on GPUTCHR (the scale value has been omitted or 1,1 is set) and the right side of the drawing range is bleeding from the draw clipping, the drawing will not be as intended.

When the Z coordinate is obtained using BGOFS, in the value returned the actual value and the sign are inverted.

If SPCLR is performed on a sprite for which the Z coordinate was specified on SPOFS, and SPSET is then performed again, even though Z = 0, the Z coordinate is displayed as the Z coordinate set previously.

Workaround: After performing SPSET, set the Z coordinate again on SPOFS.

When using GCIRCLE, if attempting to draw a circle that is outside of the drawing range, part of the circle may be broken and an irregular arc may be drawn.

If character strings specified as parameters stop as an error inside statements or functions, memory leak may occur.

If a CONTINUE instruction is used between a REPEAT instruction and an UNTIL instruction, rather than jumping to the location of the UNTIL instruction, the code will jump to the location of the REPEAT instruction.

If FORMAT$(“%D”,&H80000000) is set, the correct result will not be returned.

(Only occurs when &H80000000 is displayed on %D.)

In DEF, global variables and local arrays with the same name cannot be defined.

If three Y coordinates using GTRI have the same value, an abnormal color may be drawn.

If the resource type is specified when using FILES, a memory leak will occur.

If the resource type is omitted and the project is specified when using FILES, only TXT type files are obtained

Up to eight tracks should be able to be played at the same time using BGMPLAY, but only up to four tracks can be played.

If the assessment range was specified using SPHITSP and SPHITRC for DISPLAY 1, collision detection may not function correctly.

During wireless communications, the value with the repeat function cannot be obtained correctly with the BUTTON function.

Severity: High

(Workarounds are temporary.)

On the screen displayed when selecting a file from “Browse Projects,” touching “TXT” at the touch screen while touching the Y button at the same time will cause the program to forcibly stop.

If a file name is changed multiple times using “Rename” from the FILE MENU, the program will forcibly stop.

(If the file name is changed more than 20 times, the program is likely to forcibly stop.

If a dialog box is repeatedly displayed in an extremely high speed loop, the program cannot quit.

Severity: Medium

(Workarounds are temporary.)

In EDIT mode, if the keyboard is switched to Graphic Character mode after touching the Search button, the Search End button is replaced by the Search button.

When displaying a long file name on a dialog box, the file name may bleed from the screen.

When attempting to download a file from the server that has a filename that already exists, the rename file button may not respond.

If DAT is pressed immediately after switching to the Select File screen and Y is then pressed, the display layout will break.

When using MPSTART, if acting as host system for the second time in a row or more, terminal names may display abnormally in the dialog box when waiting for terminals to connect.

Severity: High

(Workarounds are temporary.)

When using the GCOPY instruction, if specifying both start and end point coordinates outside the graphic page area, SmileBASIC may hang.

If the UNSHIFT instruction is used for string arrays, memory may be corrupted and SmileBASIC may hang

If the length of the result in an expression that strings*numerical values is longer than 1073741824, SmileBASIC will hang.

If you use the SPSET instruction in the sprite specified in the first argument in the SPLINK instruction and specify the argument in the SPLINK instruction again, the link will break and if you operate the sprite after that, SmileBASIC will hang.

If a variable definition or DEF…END are specified between a label name and a DATA statement, when attempting to restore and read that label, an internal error may occur and SmileBASIC may hang

Workaround: Do not write code other than DATA statements immediately after a label for RESTORE.

SmileBASIC hangs when assigning internal variables in MML.

Severity: Medium

An illegal MML error may occur for music that uses MML, even though the syntax is correct.

When the volume is set to 0 using BGMPLAY, music is played at the default volume.

An error will not occur even if an expression that is not a variable name is specified in a location for a variable name by assigning an array.

(In previous updates, an error would occur after patching.)

If the POP and SHIFT instructions are used for string arrays, a memory leak will occur.

After pressing the START button on the 3DS, if “Create Programs
with SmileBASIC” is selected from the TOP MENU, the RUN command is executed immediately after SmileBASIC is displayed

If the CHKFILE instruction is used from the program that is assigned to the Smile Tool, an out of range error will occur.

Workaround: Specify a SLOT, such as “PRG0:”, in the file name.

An error does not occur for a sprite that does not have SPSET set even if various operations are performed.

When a variable (SPRITE variable 7) is specified for a SPANIM instruction animation target, SmileBASIC does not function correctly.

When a string array is declared in a FOR…NEXT loop or other loop syntax, a memory leak will occur.

Workaround: Move the array declaration outside of the loop.

If a GPAGE instruction is used after executing the GCLIP instruction, the drawing clipping area is reset.

When the border color is specified with the GPAINT instruction, the filling of complicated shapes may fail.

Part of the settings at the touch screen (console color and various graphic settings) will not reset with the ACLS instruction

Severity: High

On the Select a File screen, the OK button may be enabled even if a file is not selected, and if it is pressed, SmileBASIC may hang.

Severity: Medium

(Workarounds are temporary.)

If you upload a project that contains a file with a file size of 0, it will fail to download.

Workaround: Delete the file with a file size of 0 from the project, and upload the project again.

Periods cannot be entered in file names.

On the menu from which a project and/or a file can be selected, a file selection made with the Control Pad cannot be confirmed with a double touch.

On the menu from which a project can be selected, it is sometimes not possible to press Select File.

If a file with a 14-character file name is uploaded to the SmileBoom server, the last character will be deleted.

(There are no issues when uploading projects.)