StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19485481
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-21T02:44:27.010
FavoriteCount
0
LastActivityDate
2013-10-21T02:44:27.010
LastEditDate
LastEditorUserId
0
OwnerUserId
2575077
ParentId
19484601
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
With my many hours of frustration implementing camera systems Id suggest its something to do with your view matrix not being ortho-normalized. Thats a fancy way of saying - the three vectors represented in the matrix are not kept to the length of 1 (normalized) and also not orthogonal (at 90 degrees to each other). The 3x3 part of a view matrix representing rotation represents 3 vectors that describe the current x,y and z axes of your view at any given time. Due to rounding off errors caused by the imprecision of float values these three vectors can stretch, shrink and diverge to cause all manner of headaches. So a general strategy is re-orthonormalize every few frames if rotating and also another thing - when strafing or moving back/forward change the position using the current value of your view/lookat vector for back/forward and right vector for strafing. e.g <pre><code>//deltaTime for all of these examples is the amount of time elapsed since the last //frame of your game loop - this ensures smooth movement, or you could fix your //timestep - Glen Fielder did a great article on that please google for it! void MoveForward(float deltaTime) { position += (deltaTime * lookAtVector); } void MoveBackwards(float deltaTime) { position -= (deltaTime * lookAtVector); } void StrafeLeft(float deltaTime) { position -= (deltaTime * rightVector); } //do something similar for StrafeRight but use a += </code></pre> Anyway for the rotations just rotate the view and right vectors, maybe re-write your class as follows <pre><code>class Camera { Vector3 rightVec,lookVec,position; void Rotate(float deltaTime) } </code></pre> You get the idea? Thats a rough example just to get you thinking.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO3D First Person Camera strafing at angle
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLloyd Crawley
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PO3D First Person Camera strafing at angle
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.