Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • OpenFlipper-Free OpenFlipper-Free
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenFlipper-FreeOpenFlipper-Free
  • OpenFlipper-FreeOpenFlipper-Free
  • Issues
  • #81
Closed
Open
Issue created Nov 21, 2016 by Christopher Tenter@tenterContributor

CameraNode broken?

There seems to be an issue with the CameraNode draw implementation. This is a screen of the CameraNode draw result for a perspective projection: camera_draw

This is the actual frustum (own render code): expected_frustum

Also, the CameraNode assumes a perspective projection, so should be reworked to accept any type of frustum matrices.

There are many redundant settings necessary to setup the CameraNode:

  • setSize()
  • setFarPlane()
  • setNearPlane()

The frustum is already fully defined by the view and projection matrix, so these are obsolete.

Assignee
Assign to
Time tracking