Watch the creator’s explanation
just7 · Eclipse — Official Tutorial · Export at 2:57. This is the creator’s video, accompanying our independent written guide.
Loading the player connects to YouTube. It is a separate choice from optional website Analytics. You can read every step without loading the video.
No player is loaded. Video privacy details.
Eclipse Animator export begins with the destination
An Eclipse Animator export is useful only if it produces the kind of output your next step expects. A saved editing project, a Roblox animation asset, Blender exchange data and a scene module serve different purposes. Before exporting, write down whether you need to keep editing, play a character animation in an experience, transfer work to Blender, or use a creator-documented scene-output workflow.
The creator’s official export chapter at 2:57 is the plugin reference. The save chapter at 2:53 comes immediately before it. Their separation is important: do not assume that completing one action accomplishes the other. This source-based guide does not claim that we have verified every export dialog, output format or rig combination in the current plugin.
Keep three artifacts separate
| Artifact | Why you keep it | What it does not establish |
|---|---|---|
| Editable Eclipse project | Return to the rig, timeline and editor-specific work. | That a game can play a published animation. |
| Exported output | Pass animation or scene data to the intended next workflow. | That the receiving application interprets every feature identically. |
| Published Roblox animation, when required | Reference a Roblox animation asset from the intended experience. | That your editable project or every scene element is preserved. |
Roblox’s Animation Editor documentation also distinguishes preserving editing work from exporting or publishing for use. Its menu steps describe Roblox’s own editor, not Eclipse’s interface. Use that documentation for the Roblox side and the creator’s tutorial for Eclipse-specific actions.
If you have not yet made a reliable short motion, finish the first-animation tutorial first. Export is a poor place to diagnose a project that already looks incorrect in its source editor.
Before opening the export dialog
Make a short baseline you can recognize after transfer. For example, use one rig with a clear arm change, a known start frame and a known end frame. Keep the full production scene separate until the small case succeeds.
- Save the editable work. Use the creator-documented save workflow and verify that the saved project can be reopened.
- Confirm the intended objects. Identify the rig or scene elements the next workflow actually needs. Do not assume that a camera, physics result or helper object becomes a normal character animation track.
- Record timing. Write down FPS and the chosen frame interval. Two seconds at 30 FPS span 60 frame intervals; the timing calculator helps check other rates.
- Inspect the motion. Scrub start, middle and end, then play the whole interval. Fix visible issues before judging the export.
- Choose the destination and owner. Know whether you are testing in a personally owned place, a group-owned experience or another application.
This list is a general preflight method. It does not add a new export setting or imply that the plugin automatically handles every destination.
Follow the current Eclipse export workflow
Open the creator’s export chapter, then compare its workflow with the current installed interface. Read the output choices and confirmation text rather than selecting an option solely because its label contains “animation.” Record which option you used and what it produced: an object, file, asset reference or another documented result.
The creator’s official store description lists a module exporter among the features. That does not mean every exported module is a standard uploaded character-animation asset. Follow the matching creator instructions for that output. We have not published an unverified loader script or guessed a generated module API.
Keep the editable project unchanged while inspecting the export. If a dialog asks about a destination, creator or permissions you do not understand, resolve that choice through the current documentation before overwriting an existing asset. A successful dialog is one checkpoint; playback in the destination is the next one.
When the next step is Roblox publishing
Roblox’s animation publishing instructions describe publishing through its Animation Editor and selecting the appropriate Creator, including a group when the animation is intended for a group-owned game. Those instructions apply to that documented Roblox workflow. Do not copy its menu labels into Eclipse and assume they exist there.
After you have the appropriate Roblox animation asset, use Roblox’s Use animations guide for playback and scripting. Check the exact asset ID and the target experience, then test there. An animation previewed by its creator can still require further investigation if the target project uses a different owner, rig or playback setup.
If the receiving editor or runtime reports a permission problem, record the message and the creators of the animation and experience. Do not repeatedly republish under random accounts, share credentials, or interpret a failed asset as evidence that the original plugin installation is corrupt.
When the next step is Blender or video
For Blender exchange, follow the dedicated Blender tutorial and the developer’s current add-on release. Its transfer and armature workflows are separate from obtaining a Roblox animation ID. Check a simple rig and a short interval before transferring a complex scene.
The Eclipse Video companion supports a separate creator-documented workflow associated with video reference. Its existence does not prove that the plugin’s export button renders a movie. Likewise, a good camera preview is not a guarantee that camera playback, audio and effects have been packaged into a particular output. Verify each required component in the destination.
Compare the result with the baseline
Use the same small test before and after export. Check the starting pose, the main change, the ending pose and total duration. If the destination has different frame or time display units, compare seconds using the recorded FPS instead of assuming the same frame number represents the same instant.
For a looping motion, inspect the transition back to the beginning. For a camera workflow, compare framing as well as movement. For a rig transfer, inspect the hierarchy and the specific parts that were supposed to move. A successful result should be described in terms you can observe, not simply “export worked.”
Isolate a failed export
| Result | Next check |
|---|---|
| Wrong motion in the source editor | Selection, keyframes, layers and the original project. |
| Correct motion but wrong duration after transfer | Recorded FPS, interval and destination timing. |
| Output exists but the game cannot use it | Asset ID, creator, target experience and Roblox playback setup. |
| A camera or scene feature is missing | Whether the selected output supports that feature in the documented workflow. |
| Simple rig works but a complex one fails | Reduce the difference and report the smallest reproducible case. |
Use the creator support route with your versions, output choice, exact error and a non-sensitive reproduction. Your export is complete when you retain a reopenable editable project and have tested the required output in its real destination.