6
7

DiscussionProblems using the Lab Renderer (self.learnVRdev)

trendtimer が 投稿

Hello, has anyone successfully switched to using the Lab Renderer in their games? I'm trying to switch and am having a few deal breaker issues: 1. When I have the Valve Camera script enabled, I see a lot of disorientating camera flickers (like the camera moves up 6 inches in a blink and then returns to position). I can force the issue by selecting an object in my scene, and then adjusting one of the sliders on the assigned Valve/vr_shader. This flickering also happens when I, for example, dynamically change the material of an object using a script. Obviously any kind of camera flickering makes a game unplayable.
2. I don't seem to have any shadows in my scene and can't figure out how to turn them on. ?? 3. It sucks that you need to switch the shaders on all the materials. The documentation says " If you have a mixture of Unity shaders and The Lab shaders, Unity will render shadows multiple times, which will cost perf" which isn't good, so I guess you need to make sure EVERY material is using the unity shader. The thing is, the Valve/vr_shader doesn't look very good on many of my materials. Some objects look dull, lose their height map, etc.

I'm using Unity 5.4.0p2

*** Update *** - The camera flickering problem seems to happen with 5.4.0p2, but went away when I changed to 5.4.0f3. The 5.4.0p2 patch was released just 2 days at (08/18), and evidently something about it breaks the Lab Renderer.

全 19 件のコメント
並べ替え:
ベスト
トップ新着論争中古い順Q&A

[–]trendtimer[S] 1 ポイント2 ポイント  (4子コメント)

And here's an image that shows the visual problems I'm having. The left side shows what my game looked like before. Before the game was bursting with delightful colors! After switching to the Lab Renderer, everything looks drab and dreary. I can crank the ambient light and directional light intensity all the way up, and one side of the sphere stays really dark. I must be doing something wrong, but as far as I can tell I followed all the set-up instructions.

http://imgur.com/a/ggBAE

[–]trendtimer[S] 0 ポイント1 ポイント  (3子コメント)

So in the Stream forum, someone mentioned that the Lab renderer's shaders should only replace the standard unity shader. I guess this is why so few of my materials got converted using the tool. My game has a palette of materials to choose from, but most of these use things like: Legacy Shaders/Bumped Specular
Legacy Shaders/Bumped Diffuse
Legacy Shaders/Parallax Specular

Hardly any use the standard shader, so I'm a little fuzzy about what the downside if I leave most of my materials with their current shader, and only convert the standard shader. I've reverted to a version of my project with none of the materials converted, and I guess I'll experiment with what happens when I only convert some of them.

[–]grices 0 ポイント1 ポイント  (2子コメント)

You will need to change them to the Lab Renderer Version. Otherwise you will not get the benefit of the Single pass forward rendering. It's a simple Job. ANd even if you do not end up using "Lab" renderer. The standard shader is much better (looking) than the Legacy ones anyway.

[–]trendtimer[S] 0 ポイント1 ポイント  (1子コメント)

Is "Single pass forward Rendering" the same as "Single pass Stereo Rendering"? A comment below suggests that this can cause issues and that "we have to have it disabled for now". I have confirmed that this doesn't play well with the Lab Renderer. Another question: Do you know how we can know whether we're getting the benefits from the Lab Renderer? It is the kind of thing where if the scene has a single non-Valve texture that the Lab Renderer-goodness gets turned off? How can you tell if this happens? So far, I see no increase in FPS even after converting all my materials.

[–]grices 0 ポイント1 ポイント  (0子コメント)

You maybe Right but Only way I know is from the FPS increase. Anyone out there know?

[–]trendtimer[S] 0 ポイント1 ポイント  (7子コメント)

I just tried the "4_spots.unity" test scene, and I'm also seeing this camera glitch in that scene when I move my head quickly. There is some text on the opposite wall of the turning knobs that jumps all over the place. Maybe this renderer worked better with a previous unity patch version?

[–]omgsus 1 ポイント2 ポイント  (6子コメント)

few things... did you add the valve lighting scripts to all lighting and also disable shadows in the project?

also... for text issues like z-fighting or flickering... does this happen for hand tracked objects or static ones. (lets actually ignore this question until we fix the lighting)

[–]trendtimer[S] 0 ポイント1 ポイント  (5子コメント)

Hi thanks. I'm actively working on this now, so let me check a few things before I respond properly. I think the flickering might just be happening when any input is printed to the console. I haven't verified that this is the only thing causing it, but removing Debug.Log statements seems to be clearing this up. Which is good, but also bad because I like to print a lot of Debug message. I wonder if anyone else can confirm that this is happening for them also?

I do appreciate your help. So have you used the Lab Renderer on a project?

[–]omgsus 0 ポイント1 ポイント  (4子コメント)

Yes I just converted my current project to lab renderer. It's a process ... and I get your concern where the lab material shader seems less robust than the standard unity one (as far as normal/bump maps) but it depends on you style. You can also mix and match the shader usage. To get the benefits from at least the lighting system, you'll have to disable the standard shadow system, and attach the valve dynamic light script to all lights.

As far as the text... there is a bug with text on canvas renderings position and I have a fix for that too but it only applies to text object parented to a steamvr tracked object.

Let me know I can run you through a checklist if you want.

Oh! Also, if you want to convert all materials to use the valve shader... that menu script will do it kinda but it wont change any scripts that apply materials so you'll have to manually find any of those and set them to use the shader you want.

[–]trendtimer[S] 0 ポイント1 ポイント  (3子コメント)

Thanks. I've spent the entire day banging my head on this. Here are some things that (for me) to cause the camera to flicker (split second jumping around) like crazy: 1. Debug.Log messages
2. Any warning or error messages printed to the console: 3. This code:

imagefilePath = // a path to an image
byte[] bytes = System.IO.File.ReadAllBytes(imagefilePath);
Texture2D tex = new Texture2D(1, 1);
tex.LoadImage(bytes);

I have a method that dynamically read in an image and makes a texture out of it. I can't imagine how such a thing would cause an entire different script in control of the camera position to fail. All of the above seem like bugs to me. I have the latest versions of SteamVR, Unity, the Lab Renderer and Nvidia drivers.

Have any thoughts? Also, you said "you can also mix and match the shader usage". But this would cause a performance problem wouldn't it? The docs say that if you have non-unity shaders in the mix it will attempt to draw shadows twice.

[–]omgsus 0 ポイント1 ポイント  (2子コメント)

I'll test the debug log situation on mine. I print some stuff but never noticed.

Loading a dynamic textures..... what lifecycle are you loading this in?

For the shaders and duplicate shadows and bad performance... this is why I disable shadows entirely in unity. The "valve realtime light" script added to lights will put them back per dynamic light and is smart enough to use some of the unity lighting slider values and what type of light it's attached to. I thought it still worked on their shadows if I used the unity shaderom same mats (I had some scripts setting materials that still set the unity standard shader and I since changed it to use valve's shader) But you will lose some efficiencies that come with the lab shaders.

I'll retest all.

What exact script/prefab did you use for camera? And what gameobject did you drop it on?

The ONLY thing I can think of is in unity 5.4 release, there's a bug that doesn't handle the valve temporal pose stuff when canvas objects are parented to the hands (where it moves tracked objects to the right place by rendertime for hands but camera should be fine, that always worked right for camera like since 5.3)

Oh! Also test it built. Though, I'm sure you did :(

[–]trendtimer[S] 0 ポイント1 ポイント  (1子コメント)

Maybe you could try this:

Add the following to the LateUpdate method in ValveCamera.cs: if (Input.GetKeyDown(KeyCode.A)){
string imagefilePath = "path to png file";
byte[] bytes = System.IO.File.ReadAllBytes(imagefilePath);
Texture2D tex = new Texture2D(1, 1);
tex.LoadImage(bytes);
}

I'm really curious about if someone other than myself can see this error.

[–]trendtimer[S] 0 ポイント1 ポイント  (0子コメント)

The textures I'm trying to load are save-game screenshots that get generated within the game. Maybe rather than reading the bytes I can use Resources.Load instead. I tried this:
Texture2D myGUITexture = (Texture2D)Resources.Load(texturePath) as Texture2D;

But this didn't work I think because the thing I'm loading is an image not a texture.

I added the ValveCamera script to [CameraRig].Camera(head).Camera(eye). I think this is the correct place.

Regarding "test it build", it's kind of stupid but I've been working on my game for 3 months and never got around to trying to build and run it. I tried that last night, and it wasn't working very well. I have a Tilt-brush style rotating menu on the left controller that isn't appearing. I'll need to troubleshoot this.

[–]noorbeast 0 ポイント1 ポイント  (1子コメント)

Have you properly implemented the Lab renderer, including adding the camera and real time lights, turning off project shadows and having it convert all project materials: https://www.youtube.com/watch?v=GGLnNgP8_Jw

[–]trendtimer[S] 0 ポイント1 ポイント  (0子コメント)

Yes I have done this: 1. Added the Valve Camera script to the Camera (eye) camera of my CameraRig. I'm supposed to keep the SteamVR_Camera script there, correct? I have it still enabled. 2. My project just has the environment lighting and a single directional light. I have the Valve Realtime light script attached to the directional light. 3. I went to Project-->Quality-->Shadows and selected "Disable Shadows".
4.I converted all my Materials to use the Valve/vr_standard shader.

Is there something else I need to do to get shadows working? On my directional light, I have selected both "No shadows", and "Soft Shadows", but I don't see shadows in either case.

[–]Kendrome 0 ポイント1 ポイント  (2子コメント)

The flickering might be related to Single Pass Stereo, we have to have it disabled for now.

[–]trendtimer[S] 0 ポイント1 ポイント  (1子コメント)

Good to know, but I did already have it disabled.

[–]Kendrome 0 ポイント1 ポイント  (0子コメント)

Kinda sucks because it does offer a nice boost when it works.

[–]BHSPitMonkey 0 ポイント1 ポイント  (0子コメント)

I'm on 5.4.1f1 and getting the flickering you describe during certain operations which may involve loading Resource data into memory. Planning to work on solutions to reduce these in-game loading occurrences, but I really wish the renderer was more robust against this sort of thing (it's better to drop a frame than for this to happen).