Issues · ParaView / ParaView · GitLab

Cinema Export and Ospray raytracing don't work well together

#19644 · opened Jan 31, 2020 by Ethan Stam area:cinema priority:nice-to-have project:lanl
- 1
updated Mar 05, 2020
cinema composable image fails for 2D representations

#19249 · opened Aug 12, 2019 by David E. DeMarle area:cinema priority:required project:lanl
- 4
updated Jan 28, 2021
add "track object" option with non-composite cinema export

#18544 · opened Oct 15, 2018 by David E. DeMarle area:cinema
- 0
updated Oct 29, 2018
cinema C import occasionally will not show anything

#18542 · opened Oct 15, 2018 by David E. DeMarle area:cinema
- 0
updated Oct 15, 2018
cinema import camera and compositing mismatches

#18541 · opened Oct 15, 2018 by David E. DeMarle area:cinema
- 0
updated Oct 15, 2018
cinema export does not always fully restore initial camera, timestep and and color choices

#18539 · opened Oct 15, 2018 by David E. DeMarle area:cinema
- 0
updated Oct 15, 2018
cinema import should automatically open top level .cdb directory

#18538 · opened Oct 15, 2018 by David E. DeMarle area:cinema
- 1
updated Oct 15, 2018
make cinema export GUIs "phi"/"theta" names change to "azimuth"/"elevation" or "yaw"/"pitch" with camera model chosen

#18537 · opened Oct 15, 2018 by David E. DeMarle area:cinema
- 1
updated Oct 15, 2018
colors change in paraview after export to cinema

#17066 · opened Dec 02, 2016 by David E. DeMarle 5.10 (Fall 2021) area:cinema
- 0
updated Jan 27, 2021
Cinema exporting with "follow data" doesn't save correct camera values

#17010 · opened Nov 05, 2016 by Utkarsh Ayachit area:cinema project:lanl
- 6
updated Jan 20, 2021