Built around a practical first step
The intended users are game developers, artists and technical artists who need a quick procedural starting point. The current service is an early prototype, not a replacement for a full DCC package or a production VFX suite. Fire, Smoke and Sparks are available now; a browser preview, generated image and engine prefab are treated as distinct outputs.
We are testing interest in these workflows before investing in a larger service. Public guides explain both how to use the current prototype and how to identify problems after export. They are written for working artists and developers, not as promises that every engine feature is already supported.
Current scope
The editor imports self-contained GLB, FBX and OBJ models, creates procedural PNG flipbooks and WAV sound, saves a versioned .2vfx project and exports Unity Built-in UPM packages. The Unity target currently tested by the project is 6000.3.21f1.
Browser-previewed subsets, Unity-only settings and unsupported scene-object references are labelled separately. Native Unreal/Niagara output, URP/HDRP packages, VFX Graph compilation and AI prompt/reference generation are outside the current implementation. Unity is a trademark of Unity Technologies; 2VFX is not affiliated with or endorsed by Unity Technologies.
How the guides are maintained
Articles distinguish verified product behaviour from suggested artistic experiments. Technical references point to official Unity or Khronos documentation. Publication dates describe the article revision, not the freshness of every external reference. If a workflow depends on a specific pipeline or version, that constraint is stated rather than implied away.