In D2133#68263, @Danrae Pray (spockTheGray) wrote:

Hey @Joey Ferwerda (TheOnlyJoey), I just dropped a patch for the HMD viewport oversampling / undersampling, buuuut... drumroll (major #fail coming) I accidentally created a completely separate revision for it D:
I thought just mentioning this revision's number (D2133) in the title would automatically link it - but it didn't, so I tried putting D2133 in the body after to no avail lol...
Anywho - it's out there - https://developer.blender.org/D2902
Let me know if you think I need to change anything!
Cheers,
Danrae

In D2133#63824, @Shannon Massman (blendyshannon) wrote:

Joey,
First, support for the idea. I was looking for this a while back, I just found out this exists. I just bought a couple of junk HMD modelling tools, really pretty awful. Wish I had Blender in my Oculus. Granted, it's still early for a good quality experience, but IMO this sort of functionality is the real utility of HMDs.
Second, I feel your pain, thanks for the work. Unfortunately C isn't one of my strengths. C#, Web here. If I can help anyway, let me know. I see one reviewer is a little harsh in the phrasing. Please don't take it hard, some engineers just lack tact during review; on the bright side his comments look like good effort was expended and good info was collected as a result.
Lastly, I was sadly unable to get the 4-18 11:18 build functioning properly on Windows, NVidia. Here's my experience:

• I tried starting without changes first. After "Start Session", the HMD window opens fullscreen on my main display, and (non-positional) head tracking is reflected there.
• When I don the headset, the Oculus application manager starts in the HMD. I figured that can't be good, so I looked around. Hints were hard to find, but eventually dug through the comments here, and so tried stopping the OVR Service and running DirectDisplayConfig. I hear device enable/disable chimes in Windows, but after trying various sequences, wasn't able to get the viewport directly into the HMD, or get the HMD into an "extended" state where I can drag Windows to it.

I'd love help diagnosing this so I can try it out.

Please don't change the status of a task yourself, confirmed status is for when blender developers are able to confirm the task by reproducing, i have not been able to do this yet on my Ubuntu system with Intel gpu.

Can you provide a minimum working blendfile to reproduce this error?
I am not able to reproduce this on my Windows 10 installation with a cube scene.

Are you running this in a virtual machine?
What is your GPU and driver?

This is a known issue, being worked on at this moment by lukas.

What is the Mesa version and driver you are using, i was not able to reproduce this on my similar Intel GPU on Ubuntu with Mesa 17.

It is hard to triage or reproduce this error without a minimum test file that this happens with.
Please submit a file that reproduces this error.

.dvd is not a valid extension for MPEG and AVI Raw as far as i know.
when rendering in Avi, try the .avi extension.

Please provide a full bug report based on the template provided when creating, just a vague title is not enough.
We need all information asked (Operating System, GPU, RAM, Blender Version, Description of the error and Exact steps to reproduce the error including blendfile or asset).

• Use projection matrix from OpenHMD even if "Rotation from HMD" is disabled
• OpenHMD update, disables OVRService upon starting the device, only when run with administrator.
• Fixes Oculus CV1 Lens Correction
• msvc fix in packet.c in PSVR driver
• Merge branch 'master' into HMD_viewport
• Fix HMD panel not visible after recent changes in master
• Disable zooming/pannig of HMD view while in camera perspective
• Updated Vive lens correction values, is a decent approximation, needs extra sample points when looking down
• Numeral small fixes from upstream 0.3rc
• Fixes for Windows compile, fixes crashes when trying to open locked devices
• Merge branch 'master' into HMD_viewport
• Fix for building without HMD
• Use max_ff
• Correct last commit, also quiet warnings
• use 'use_' as an RNA prefix
• Sync with master and minor formatting
• Remove ifdef check for file versioning
• Clear hmd window when no loaded
• Merge branch 'master' into HMD_viewport
• Cleanup: tabs
• Special Blender-managed cursor drawing for HMD view
• Add WM level utility check for active HMD view
• Make interactions in HMD view work nicely
• Fix Multi-view drawing interfering with HMD view drawing
• Remove unnecessary check
• Cleanup: Naming, use util function
• Fix HMD view drawing black if device is set to 'None'
• Fix crash when closing HMD window during running session
• Re calibrated the vertical position for the Vive lens distortion shader
• Fix projection matrices not taking focal length of HMD into account
• Fix lens separation applied wrongly onto projection matrix
• Force using HMD parameters instead of camera ones in camera perspective
• Fix manipulator interaction not using correct projection matrix

First of all i want to mention that all LazyDodo's testing is done on the Oculus CV1 on Windows, one of the 6 current devices supported by the OpenHMD version in Blender, and the most problematic case over all.

In D2133#60417, @LazyDodo (LazyDodo) wrote:

1. The custom hidbranch had bad sloppy bugs, causing my cv1 not to be detected at all, wasted most of friday evening on this.

I found this odd, after your feedback i fixed the issue and it is working out of the box right now, i know the code is not perfect, but it is functional and hopefully a temporary fix.

In D2133#59616, @LazyDodo (LazyDodo) wrote:

In D2133#59615, @Julian Eisel (Severin) wrote:

In short: If we want a multi-platform HMD support in Blender that's all we can get for now. For Linux users that's a big step forward, for Windows users not so much. (Not sure how HMD support in OSX is doing in general.)

I do recognize this is a leap forward for some platforms, and I'm not flat out rejecting the differential, I'm just saying we shouldn't ship oculus support on windows (and should really investigate the vive status) because support on this platform does not reach the quality bar. If if works properly on other platforms, there's no reason to hold those back.

Regarding the projection issue you mentioned... it's of course hard to tell, but I'd guess this happened while in camera view? The projection matrix is still wrong in that case, one of the 4 things to fix before pushing. If this happens outside of camera view and if you don't get this in other apps, it's a bug that needs to be addressed.

I just dragged in a monkey, and clicked start hmd session. if that's not the right way, some other tweaks to the ui might be needed to prevent users from doing the same?

Please fill in a bug report using the provided form. This means Operating System, Tested blender version, pc specifications, a blend file to reproduce the issue and a good reproduction case.
Thanks,

You are not providing enough information, also please repost this question using the form provided by the bug report (operating system, specs, blender version, screenshots etc) in English.

Closing for being duplicate of T50773

Due to inactivity for over a week closing because of bug tracker policy

Due to inactivity for over a week closing because of bug tracker policy

Due to inactivity for over a week closing because of bug tracker policy

Due to inactivity for over a week closing because of bug tracker policy

This is not really a bug, more of a design suggestion.
As this is on right click select, it will get looked at and discussed by the developers.

This is not a bug report, and we do not take suggestions on the Bug Tracker.
If you are interested in the game engine, please check the UPBGE project.

So, HD 4000 is not supported and never has been as of now.
Intel's OpenCL implementation is not at a level where it can be used for GPU rendering, so if it did turn up it was a bug since it should not.

Can confirm, this is a quite specific issue though, windowing is a bit complex so i don't know if this will be a trivial fix.

This is not something we can fix, I have tried reproducing this on a Laptop with 16.04 (Both with Unity and GNOME 3) and can not reproduce this.
I would suspect this being either a hardware specific bug or a issue with external bindings through a third party application.

Can confirm, tested on 278b, seems to be a regression.
Can you test this on latest buildbot version please?

Thanks for the report, though if this is working on some Distro's and Operating Systems and not on others, this could be a missing or different driver or application and is not a bug or regression within Blender.

You are reporting this with version 2.77a which is not our latest release, please re-test with Blender 2.78b and see if this is reproducible.

No problem.

Looking at the description its a simple out of ram issue.
Some things can get quite out of hand when it comes to ram use.

Ok closing then.

Has this functionality worked for you in the past on older versions of Blender?
If so, which versions?

Jups closing for being duplicate of T50638

I think all current patches in master are staged for 2.79.
2.78b had a very specific set of fixes that were allowed for a 'b' release. I would suggest using a buildbot version at the moment or be patient for 2.79 which is due in a couple of months.

This is not a bug and expected behavior.
Blender only receives events for active windows, and windows only get activated when clicked on.
On Linux there are ways to make windows active on hover, but on Windows i don't know if this functionality exists.

Cool will archive the report then, thanks for the report!

I get that, but even when using a 'regular latin' path you can not render with your blend file example, the blend file does not render at all (missing camera,light etc) so please update your blend file to a render-able result and i will test your case.

Can confirm, tested on Ubuntu 16.10 rendering on CPU.

So Cloth is actually undergoing a complete redesign by the amazing @Luca Rood (LucaRood) for 2.8.
The boundaries in the settings are mostly to prevent things going horribly wrong.
As this is not a bug, closing the topic. If Luca wants to add anything, please do!

Is this still a issue?
I have tried checking the values of the rendered png's and they seem to be identical throughout renders.

I think this had a total overhaul, but since it is infra, still a thing? @Francesco Siddi (fsiddi)

Closing since website overhaul has deprecated this task

I think this TODO has been finished or removed, will report resolved, please re-open if this still occurs.

Report has not been reacted on for 7 days, closing due to bug tracker policy.

No reaction from the original commenter on last reaction for a while, archiving.

Report has not been reacted on for quite a while, closing due to bug tracker policy.

Report has not been reacted on for 7 days, closing due to bug tracker policy.

Report has not been reacted on for 7 days, closing due to bug tracker policy.

Report has not been reacted on for 7 days, closing due to bug tracker policy.

Report has not been reacted on for 7 days, closing due to bug tracker policy.

Report has not been reacted on for 7 days, closing due to bug tracker policy.

Report has not been reacted on for a long time, closing due to bug tracker policy.

I tried this on Blender 2.78a and current buildbot but can not reproduce this case.
Removing the Shapekey resets the curve for me as well.

These things are difficult to test without a test scene.
Can you reproduce the case on a simpler scene?

Can confirm, used 2 different applications which can open 3ds and Blender seems to struggle with this particular asset.

I can test this for you but your test blend file seems not to work at all.
Can you retry setting up the case with a render-able result and re-upload the blendfile?

Tested. seems to work for me.
Anyone else wants to pitch in?

No problem, can happen.
Will close.

This is probably a issue with a old driver, and is not something we can solve.
I would recommend updating your MESA and try again.
Blender 2.8 will also remove compatibility for 2.1 devices, so i would suggest updating to a more recent device in general.

Also please attach the Blend file so we can reproduce the case.

"Fix incoming." Are you patching this yourself?
Can confirm in any case!

Thanks for the report.

This is resolved in the current buildbot version, closing report.

Thanks for the report.

Thanks for the report, this is something we can not handle ourselves though.

Allright closing.

Thanks for the report, please provide a blend file for testing.

This report has passed the limit of inactivity, will be closed as archived.

@Gaia Clary (gaiaclary) Any chance to look into this? Task has been open for a month now.

Can confirm report, waiting for @Adam Dominec (emu) as maintainer to respond.

As this is not a regression, this is not priority to fix at the moment.
For BGE fixes i would recommend submitting to UPBGE https://github.com/UPBGE/blender.
Archiving.

Has been fixed as part of r6f40579d5bd2 please try with latest buildbot.
Closing.