DOCS
Reference

Dependencies

What the package needs and what belongs to your project.

Currently testing with Unity 6.3.

DependencyWhy it is used
2D Sprite (com.unity.2d.sprite, built-in 1.0.0)Sprite import/export metadata APIs in the editor
IMGUI and UIElements modulesEditor windows and controls
JSONSerialize moduleSource/export metadata
ImageConversion modulePNG output
Animation moduleExported AnimationClips
Unity SpriteRendererScene and runtime rendering

The standard Unity modules above are present in normal projects. If you maintain a stripped-down package manifest, retain them. Install 2D Sprite through Package Manager.

Pixart does not require URP, HDRP, Input System, TextMeshPro, Burst, Collections or the Test Framework. Use a sprite-compatible material for your game's render pipeline and lighting setup.

Assemblies

IE.Pixart.Runtime contains the imported asset types, renderer and playback code. IE.Pixart.Editor contains the editing tools and references the runtime assembly and Unity.2D.Sprite.Editor. Code namespaces start with IE.Pixart; the installation path remains Assets/InanEvin/Pixart.

Exported PNGs and AnimationClips can be moved to a project without either Pixart assembly. Editable .pixart sources still need the importer.

Tablets

Pen input and pressure use Unity's editor events. No Input System package or tablet plugin is needed. Install the driver for your tablet, then use Tools > Pen Settings… to check its pressure in Pixart. See tablets & pen pressure.

macOS trackpad support

The package includes IEPixartTrackpad.bundle for native editor pinch gestures on Apple Silicon and Intel Macs. It is editor-only and excluded from player builds. Other platforms can use Ctrl+wheel; native Windows pinch support isn't implemented.

The package has no external managed DLL dependencies.

On this page