Release Notes

This is a fully functional version of the product. Software registration is not required. Effective with release version 2.0, Kisekae UltraKiss is open source software released under terms of the GNU General Public License.

License expiry date: December 31, 2008.

System Requirements

A minimum configuration for Kisekae UltraKiss requires a 450 Mhz processor with 256 megabytes of memory. The UltraKiss system is processor and memory intensive. Limited memory systems may experience poor performance due to excessive memory management, particularly if large images are loaded.

If you install UltraKiss using the standard InstallAnywhere installer you may have to edit the program control file to increase the available memory pool size.

Note: Effective with UltraKiss release 3.0c, an expanded memory configuration is installed by default.

On Windows or Linux systems, edit the UltraKiss.lax file in your program installation directory with any text editor. Add the following line to the end of the file if it does not exist:

lax.nl.java.option.additional=-Xmx200M

This will request a 200MB memory buffer pool.

If you start Java manually, use:

java -Xmx200M -jar ultrakiss1.jar

Failure to follow this procedure can result in poor performance or Out of Memory faults.

Kisekae UltraKiss Problem Reports

Java Web Start Known Issues

Microsoft Windows systems can fail with Java 1.4.1 and ATI video cards. See Sun Microsystems Bug ID 4749817 BSOD in WebStart: Win2k/XP with ATI graphics. A workaround has been implemented with Java Web Start to eliminate this problem. The Java command line option -Dsun.java2d.d3d= false can be used to disable direct 3d support for Java 1.4.1. Alternatively, the system environment variableJAVAWS_VM_ARGS=-Dsun.java2d.d3d=false can be set to disable direct 3d operation.

UltraKiss Known Issues

Cursor may not change state until the cursor is moved. A mouse movement event is necessary before the cursor can change state.
Attempts to reclaim memory through the memory utilization dialog are not immediate. These requests invoke the Java garbage collection system.
File Save and File Load dialogs do not currently support filename filters. This is a Microsoft and Java incompatibility problem.

Text Editor Known Issues

Edit OVERTYPE mode does not work.
Line numbers may not be rendered correctly if a text document is scrolled. The line numbers are drawn correctly on a screen repaint if the mouse is clicked within the document text.
Rich text documents may exhibit errors. Rich text document support is not mature.

Color Editor Known Issues

Color selection using the eyedropper tool may not be accurate when using magnified images. The selected color may not always be the color beneath the eyedropper.
Poor performance may occur while moving objects in the preview window.

Image Editor Known Issues

There are no known problems. The image editor is not fully developed. Limited image editing capability currently exists. Images can be loaded and saved in different formats.

FKiSS Editor Known Issues

FKiSS breakpoints are not retained across a program restart if the configuration has been edited or changed.
Breakpoints are not functional on initialize(), begin(), or version() events.

Archive Manager Known Issues

ZIP and JAR files may not be saved in an uncompressed form.
Adding multiple elements to an archive file through ctrl-selecting new elements returns the scrollable selection list to the first element selected.

Media Player Known Issues

Poor performance may occur if video media playback is not started from the beginning. The video screen and audio track may not immediately synchronize.
Java Media Framework sound and movie file positioning may not work correctly. The media position control slider does not always size correctly to the frame layout.
The position tracking slider may stop moving if the Media Player frame is refreshed through menu displays or other actions.

Next Document: Installation Notes
Prior Document: Registration Notes