StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20229569
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-26T22:43:53.467
FavoriteCount
0
LastActivityDate
2013-11-26T22:43:53.467
LastEditDate
LastEditorUserId
0
OwnerUserId
85306
ParentId
18244996
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The double vision effect of the two images not merging doesn't have anything to do with the modelview matrix. The separation of the modelview matrix makes the two images slightly different so that they give a sense of depth, but without the separation, the view through the Oculus should ideally be very much like staring at a non-3D monitor. The reason you're seeing double is because you're centering the two images in the center of each viewport (I render each eye view individually, so I have a viewport that covers the left eye, and then one that covers the right eye). If the view of what is directly ahead of the player is in the center of the eye view, the viewer will always see double. This is because each lens is not centered over the middle of it's half of the display panel. Instead they're offset towards the center. In order to properly display content on the Rift you have to account for this offset. There are a number of ways to do this. The best way is to alter your projection matrix so that the center of the frustum is no longer looking directly ahead, but is instead off to one side. This is the method used in the SDK samples. Another method is to leave the projection matrix alone and instead push the rendered view for each eye inward toward the center of the screen. The reason this isn't the best approach is that it means you will be cropping parts of the interior edges of the image as they get pushed outside the viewport (this isn't really an issue with the view, mostly an issue with performance, because you've already spent part of your performance budget rendering those now cropped pixels). It also means that part of the screen on the outer edges of the display won't be rendered at all, which will reduce the overall field of view of the rendered scene. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I calculate my 3D View Matrix for the Oculus Rift in XNA?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJherico
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do I calculate my 3D View Matrix for the Oculus Rift in XNA?
 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
 VTUpMod
2. 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.