taichi-dev/taichi

[Export] Upgrade to Stop-motion-OBJ 2.1

Open

#1,589 opened on Jul 25, 2020

View on GitHub
 (4 comments) (1 reaction) (0 assignees)C++ (28,195 stars) (2,384 forks)batch import
good first issuewelcome contribution

Description

Abstract Thanks to the great work by @neverhood311, Stop-motion-OBJ has upgraded to v2.1.

TODO

Blender requires an add-on called Stop-motion-OBJ to load the result sequences. A very detailed explanation video is provided by the author on how to install, enable, and use the add-on. Just keep in mind that significant changes in the workflow were made in their most recent test releases. To follow their instruction readme and video, please use v2.0.2.

  • @archibate could you help to export your cloth simulation ply files, so that @neverhood311 can feature your simulation on his project page?
  • (any other related tasks we can do to better guide users to the Stop-motion-OBJ plugin?)

Contributor guide

Tech stack
python
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of BlenderFamiliarity with Stop motion OBJ add on
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The issue asks to update the documentation at https://taichi.readthedocs.io/en/latest/export results.html#import ply files into houdini and blender to reflect Stop motion OBJ v2.1 changes. First, review the current documentation and compare it with the v2.1 release notes (https://github.com/neverhood311/Stop motion OBJ). Update any version references and workflow descriptions. Additionally, consider if there are other ways to guide users to the plugin, as mentioned in the issue. The export task for @archibate is a separate coordination item.