Modern OpenGL立方体旋转异常问题排查求助

Hey there! Let's break down why your cube's rotation is acting weird—since translation, scaling, camera, and projection all work as expected, the issue is almost certainly rooted in your rotation matrix code. Here are the most common culprits to check:

• Row-major vs. Column-major Matrix Mixup
  Most graphics APIs have strict rules about matrix layout: OpenGL uses column-major order, while DirectX uses row-major. If you construct your rotation matrix in the wrong format for your API, the rotation will behave unpredictably. For example, a correct column-major X-axis rotation matrix looks like this:

  [1,  0,       0,      0]
  [0, cosθ, -sinθ, 0]
  [0, sinθ,  cosθ, 0]
  [0,  0,       0,      1]
  

  Also double-check your matrix multiplication order—since matrix multiplication isn't commutative, model_matrix = rotation * translation is very different from model_matrix = translation * rotation.

• Degrees Instead of Radians
  Nearly all math libraries (like GLM, DirectXMath) expect trigonometric functions (sin, cos) to take radians as input. If you're passing degree values directly, your rotation angles will be way off (e.g., 90 degrees becomes ~1.57 radians—passing 90 directly would result in a tiny, incorrect rotation). Always convert degrees to radians first:

  float rotation_rad = rotation_deg * M_PI / 180.0f;
  

• Rotating Around the Wrong Origin
  If your cube is rotating around the world origin instead of its own center, it'll look like it's orbiting rather than spinning in place. Fix this by translating the cube to the origin first, applying rotation, then translating it back to its desired position:

  model_matrix = translate_back * rotation_matrix * translate_to_origin;
  

• Unnormalized Axis Vectors (For Arbitrary Rotations)
  If you're implementing rotation around a custom axis, that axis vector must be unit-length (magnitude of 1). If it's not, your rotation matrix will accidentally apply scaling, causing the cube to stretch or rotate unevenly. Always normalize the axis before using it:

  glm::vec3 normalized_axis = glm::normalize(custom_axis);
  

• Floating-Point Drift with Incremental Rotations
  If you're updating your rotation by multiplying the current matrix by a small rotation increment each frame, floating-point precision errors will eventually break the matrix's orthogonality. This leads to distorted, erratic rotations. Instead, store your rotation state using quaternions—they maintain orthogonality much better, and you can convert them to a matrix when needed for rendering.

A quick debugging tip: Test rotating around just one axis first (e.g., only X-axis) and verify it behaves as expected. Once that's working, add Y and Z axis rotations one at a time to isolate which part is causing the issue.

内容的提问来源于stack exchange，提问作者ErnieB