feat(viewport): camera navigation and framing parity with Maya 2027 (tumble, track, dolly, viewFit)

Aperta
#392 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start with src/viewport_ui.rs, .project-docs/development.md policy rows 24–27, and mcp.md; compare the implemented input mappings and camera operations with the cited Maya commands. First map which gaps are already represented in the viewport and MCP interfaces, then identify the missing behavior and its acceptance checks. Done means documented mappings cite their command flags, unsupported tools remain visibly unsupported, and any new operation has MCP coverage, schema sync, protocol tests, and a native visual check.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/mcp area/viewport effort/m impact/many priority/p2 severity/medium triaged type/feature urgency/this-quarter

Problem

Orbit, pan and dolly (mouse and MCP orbit_camera, pan_camera, dolly_camera), set_camera_pose, View > Default View, Frame Selected (F, Ctrl+F) and Frame All (A, frame_all) are implemented. No open issue owns the gaps between them and the documented Maya 2027 navigation tools: #48 covers panels, orthographic views and display menus, and #292 covers bookmarks only. Navigation gains and the pitch limit are provisional constants (policy rows 24 to 27 in .project-docs/development.md).

Gaps

  • Mouse mappings: Alt+Left tumble, Alt+Middle track, Alt+Right or Alt+Left+Middle dolly; Shift constrains tumble and track; Ctrl+Alt+left drag draws a marquee to dolly into an area [S1][S2]. Check each against src/viewport_ui.rs; the Shift constraint and the box dolly are not implemented.
  • Zoom versus dolly: Dolly moves the camera; Zoom changes the focal length without moving it [S1]. AztecCraft's wheel dollies; record the mapping.
  • Tumble Tool settings: Tumble scale default 1 (range 0.01 to 10); Tumble camera about the centre of interest (default) or the tumble pivot; Orthographic tumbling Locked (default on) and Stepped [S3] (2024 page via search; PROVISIONAL for 2027). tumble -pivotPoint, -localTumble, -azimuthAngle, -elevationAngle, -rotationAngles [S4].
  • Dolly Tool: dolly -distance, -absolute, -relative, -dollyTowardsCenter, -orthoScale [S5]. Dolly towards the pointer versus the centre of interest is not implemented.
  • Track: track -left, -right, -down (and -upDistance01/02) [S6]; pan_camera should document the mapping.
  • Framing: viewFit -fitFactor, -animate, -allObjects, -center, -noChildren, -fitClipPlanes, -namespace; no default fit factor is stated [S7]. Frame Selected, Ctrl+F (with children) and Frame All should name their viewFit equivalent; -noChildren corresponds to F framing parents only (#338).
  • Shift+F and Shift+A frame in all views [S8]; this needs several panels (#48).
  • View history: [ back and ] forward, View > Undo/Redo View Change [S9]. #292 leaves these out of scope; this issue owns them.
  • Default view: Alt+Home or View > Default View [S9] (implemented); viewSet -home is the scripted form [S10].
  • Other camera tools: Roll, Azimuth Elevation, Yaw-Pitch, Fly (Ctrl+drag), Walk (Alt+X), 2D Pan/Zoom [S1]; visibly unsupported until done.
  • Camera attributes for MCP reads: camera -focalLength, -nearClipPlane, -farClipPlane, -horizontalFilmAperture, -centerOfInterest, -orthographic, -orthographicWidth [S11]. inspect_scene reports field of view and clip planes but not focal length or centre of interest.
  • Preferences "Animate camera transitions" and dolly-to-pointer wording: unsourced; do not add them until sourced.

MCP and scripting equivalents

AztecCraft MCP Maya
orbit_camera tumble -azimuthAngle -elevationAngle [S4]
pan_camera track -left/-right/-down [S6]
dolly_camera dolly -distance (relative) [S5]
set_camera_pose camera -e -position -rotation, viewPlace (page not fetched) [S11]
frame_selected, frame_all viewFit, viewFit -allObjects [S7]

Version history (Maya 2011 to 2027)

Dates come from comparing command-reference pages; 2015 and 2021 pages could not be fetched.

Feature Version Change Source
tumble, track, dolly flag sets 2013 or earlier to 2027 unchanged [S12]
viewFit -allObjects, -animate, -fitFactor 2013 or earlier present [S13]
viewFit -center absent 2014, present 2016 added in 2015 or 2016 [S14]
viewFit -noChildren absent 2020, present 2022 added [S15]
viewFit -fitClipPlanes absent 2023, present 2024 added [S16]
Alt+mouse mappings 2016 page (search) and 2027 page unchanged [S17][S1]
viewSet -side 2027 deprecated, use -rightSide [S10]

Compatibility-version note: Ctrl+F with children and F parents-only behaviour should be checked against -noChildren (2022); under an earlier compatibility version the parents-only distinction may not apply (PROVISIONAL).

Acceptance

  • Each implemented mapping cites its Maya command and flag in mcp.md.
  • Unimplemented tools and modifiers stay visibly unsupported with a reason; no dummy tools.
  • MCP coverage, schema sync and real Editor protocol tests for any new operation; native visual check.

Sources

Lingua principale
Rust
Stelle
4
Fork
2
Merge medio
16h 19m
PR unite (30g)
196

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cristim/AztecCraft

Tutte le issue di cristim/AztecCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.