Skip to main content
Sarcosuchas
Sarcosuchas
Participant
October 29, 2025
Question

MQDH Cinematic Casting Issue

Not a developer but instead a content creator. 

The Meta Quest Developer Hub's casting function has proven incredibly useful for the recording of gameplay footage across many games, with the cinematic 16:9 aspect ratio being the best option for this.

Recently, (as of 26/09) I've noticed that for some applications, for example, Resident Evil 4 VR; the cinematic aspect ratio is no longer working correctly. It appears to only be recording one of the eyes instead of both, meaning the view on the casting is off-centre and leaves a black bar on the side of the screen. 
In the attached image, I had the casting set to cast from the right eye; and I was aiming down the sights with my right eye, yet as we can see, the casting is only showing the left side, as if only casting from that side.
I have tried restarting everything; uninstalling and re-installing MQDH and even rolled back to previous versions to find any possible fix but have been unable to resolve the problem. 
Given that the cinematic casting works for other applications and is only broken on some, I'm going to assume there's a specific issue somewhere that my basic troubleshooting won't be able to solve.

However, I'm asking to see if anyone else has had this issue (I know a friend of mine and one person on Reddit have experienced it) perhaps have found a solution to it, as I've tried everything I could think of.

 

    10 replies

    VirtuallyARealDinosaur
    VirtuallyARealDinosaur
    Community Manager
    October 29, 2025

    Hello!

    I'm sorry to hear that an update has changed your expected functionality.

    There was another person who also mentioned using MQDH for streaming. Unfortunately, because MQDH isn't designed for streaming, you'll likely experience issues with it when doing so.

    Thanks

    Sarcosuchas
    SarcosuchasAuthor
    Participant
    October 29, 2025

    Unlike that person, I don't stream using MQDH itself.
    The 1:1 and cropped 16:9 aspect ratios function perfectly, but as you can see from the image I posted, the cinematic aspect ratio is not functioning as it is supposed to for specific applications.

    The cinematic aspect ratio does work for other applications as well as when not on any app at all.

    And to repeat, even rolling back to previous versions of MQDH does not solve this issue. 

      VirtuallyARealDinosaur
      VirtuallyARealDinosaur
      Community Manager
      October 29, 2025

      Hey! 

      Thanks for the response. Both you and them mention casting the cinematic ratio, which seems to be the root issue in both of these cases.

      Could you possibly rephrase if I am misunderstanding?

      Sarcosuchas wrote:

      It appears to only be recording one of the eyes instead of both, meaning the view on the casting is off-centre and leaves a black bar on the side of the screen. 
      In the attached image, I had the casting set to cast from the right eye

       

      brunorataque
      brunorataque
      New Participant
      December 10, 2025

      Makes no sense that this thread is marked as solved. 

      The user stated that the Cinematic Mode was working fine for months, and now it's broken. 

      The FOV is broken. The only reason for this option (Cinematic Mode) to exist in the first place.

      A lot of content creators uses MQDH Casting to create content because of the Cinematic FOV, and it is broken now.

      This affects the quality of gameplays that could help sell a lot of headsets and a lot of games.

      Sarcosuchas​ did you find a fix?

      I think that it's a problem in the compatibility between some games and the MQDH.

      If rolling back updates didn't fix it, it's something between them (MQDH <--> Game)

      Some driver or encoder problem.

      What a sad problem. You could try to reach out to the games developer to see if they can help us.

        Sarcosuchas
        SarcosuchasAuthor
        Participant
        December 10, 2025

        Yeah, it's the opposite of solved. 
        And I have yet to find a fix for it. It is still not working properly as of the recent update.

          Terms & ConditionsAccessibility statement