I’m not sure how to do that. I played around with it and googled but it’s not clear how to set full screen mode from a blueprint. Is r.FulLScreenMode meant to do something?
I did discover r.SetRes. First thing I worked out is that UE4 packaged projects respect display scaling - so setting the window size to my screen resolution made it much larger than the screen. I had to set the properties for the binary to “Ignore High DPI scaling” - then the resolution set matched the screen.
Unfortunately, doing “r.SetRes 1920x1080f” and “r.SetRes 3840x2160f” had exactly the same results as the “w” flag and sets the resolution of the window, but then stays windowed.
I think we’ve reached a point where trying a reinstall of UE would be beneficial. I’ll give it a go then create a new project. If that works, I’ll try my existing projects.
Please let me know if this helps. If not we can continue attempting to reproduce this on my end.
I’m afraid a reinstall didn’t help.
I’ve found I can use fullscreenmode 1/windowed. That seems to work. Only 0 isn’t working, but I guess mode 1 won’t work for the Oculus Rift.
I guess this is likely to be an issue with both of my workstations. One of them is a nearly clean managed build at work, the other is my home machine. I can’t think of anything I might be running that would interfere with their ability to go fullscreen.
I’ve recently gone back a version of the Nvidia Geforce drivers due to a video driver crashing issue in the editor, which resolved that. That’s about all the extra info I can supply.
Hi ,
Have you attempted to set stereo or changed this setting at all? See if that changes what you are experiencing with the Oculus.
I don’t have a rift yet, was going to order one in a fortnight. I’m planning ahead. 
Regressing the drivers didn’t help I’m afraid.
Is there some kind of debug tool I can install to get you more info?
Hi ,
I just reread your post about your drivers. Did reverting completely resolve the fullscreen issue?
Unfortunately I don’t know of any specific tools to use. At this point I am not sure there is anything I can do as we have been completely unable to reproduce this on our end. Is there any other steps or procedures you can think of that may help me to reproduce this bug here?
None at all. I guess a windows reinstall is on the cards, although that’s going to be a massive amount of work for an issue I’ve been able to reproduce on two computers with two different versions of windows, so won’t necessarily solve it.
I think if I look for this issue in a wider scope than UE I might find the answer. Thanks for helping as much as you have !
Hi ,
I will keep looking into ways to reproduce this on my end, though it may well be that a reinstall fixes the issue. For now I am going to mark this as answered for tracking purposes. If you do think of anything that can lead to us being able to repro this comment and let us know.
Another user has just posted the same issue with an identical video card to what I use - an Nvidia GTX 770. He’s on the latest drivers and I’m on the previous version. Do any of your engineers or test machines have this same video card there?
Hi ,
I am using a GTX 770 as well. I just checked to make sure and we are running the same driver (9.18.13.4052).
Holy heck I’ve solved it. I have traced the problem back to TeamViewer 9. Stand by while I do more testing.