If I only have a text prompt, what do MAV3D and 4D-fy actually show, how were they evaluated, which one can I run, and how good is the motion?

Partially verified: the curator re-read none of the cited sources; S1, S3, S4, S19, S8, S16, S9, S5 rest on the producer's pinned reading. Two papers cover text-to-4D with score distillation. MAV3D (Meta, January 2023) optimises a six-plane dynamic NeRF against a text-to-video model in three stages (about 6.5 h on 8 A100) and shows an R-Precision of 83.7 against adapted internal baselines of 6.2-10.6; no code is available. 4D-fy (arXiv v2, May 2024) blends 3D-aware, image and video diffusion priors, takes about 23 h on one 80 GB A100, and ships a repository with run instructions. In 4D-fy's own user study (26 evaluators, 28 prompts) users prefer 4D-fy for appearance (92%) and structure (89%) but only 41% prefer it for motion, and the motion difference is the one comparison that is not statistically significant. 4D-fy says motion is limited to simple movements and that current metrics are not sufficient; MAV3D says quality depends on the text-to-video model across views. Diffusion4D reports an 8-minute text-to-4D result but its generator is not released. Curator correction 2026-10-23 (discovery audit record C3-B588-07; sources re-fetched 2026-10-23, excerpts re-located by curator GET): Correction (unsupported by the cited source). C3-B168-W33-03 and W33-04 give Diffusion4D an '8 minutes' text-to-4D time and MAV3D about 6.5 hours on 8 A100. In the cited arXiv pages (Diffusion4D 2405.16645v1, MAV3D 2301.11280v1) the text extracted says only that Diffusion4D generates 4D assets 'within just several minutes' and contains no A100 or hours figure for MAV3D. The 4D-fy time is supported: the three optimisation stages take roughly 2, 2 and 19 hours (23 hours total) on an A100 with about 80 GB of VRAM. Treat '8 minutes' and '6.5 h on 8 A100' as unverified (tables or later versions may carry them). Version/date. Fetched 2026-10-23. Curator qualifications: Partially verified: the curator re-read none of the cited sources; S1, S3, S4, S19, S8, S16, S9, S5 rest on the producer's pinned reading. Curator GET 2026-10-23 of the sources not re-read (mechanical source evidence, not semantic verification): S1: HTTP 200, bytes equal to the producer pin; S3: HTTP 200, bytes equal to the producer pin; S4: HTTP 200, bytes differ from the producer pin; S19: HTTP 200, bytes differ from the producer pin; S8: HTTP 200, bytes equal to the producer pin; S16: HTTP 200, bytes equal to the producer pin; S9: HTTP 200, bytes differ from the producer pin; S5: HTTP 200, bytes equal to the producer pin. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://arxiv.org/html/2301.11280v1",
      "note": "candidate evidence excerpts"
    },
    {
      "url": "https://arxiv.org/html/2311.17984v2",
      "note": "candidate evidence excerpts"
    },
    {
      "url": "https://github.com/sherwinbahmani/4dfy",
      "note": "candidate evidence excerpts"
    },
    {
      "url": "https://huggingface.co/cerspense/zeroscope_v2_576w",
      "note": "candidate evidence excerpts"
    },
    {
      "url": "https://arxiv.org/html/2405.16645v1",
      "note": "candidate evidence excerpts"
    },
    {
      "url": "https://arxiv.org/html/2503.16396v3",
      "note": "candidate evidence excerpts"
    },
    {
      "url": "https://github.com/VITA-Group/Diffusion4D",
      "note": "candidate evidence excerpts"
    },
    {
      "url": "https://arxiv.org/html/2406.10324v1",
      "note": "candidate evidence excerpts"
    }
  ]
}