AR Foundation and the Lightweight Render Pipeline

Hi all, any ideas on how to get the lightweight render pipeline (LWRP) working with AR Foundation?

If we use the ARCameraBackground script without Override Material checked, then the default platform specific material/shader fails to render on the LWRP, and our AR content leaves never ending trails of previously rendered frames ghosting behind it.

If we set the Override Material to a basic material with a shader from the LWRP, then we just get blackness behind our AR content, and no camera feed.

Any pointers would be greatly appreciated!

 

Bump! We're having the same problem. Which is a shame because it means we can't use ARFoundation in conjunction with Shader Graph, for example.

 

Sorry to tag directly, but any ideas on this, @timmunity or @jimmya ? It's a pretty major blocker on our project moving forward. Thanks in advance!

 

Seeing as 2018.2.0f2 has just came out with updated LWRP features and shader graph, touting that it is best for XR based mobile apps.. it's going to be a shocker if it doesn't work for it - testing soon

 

I couldn't get it to work either, so I submitted an issue here : https://github.com/Unity-Technologies/arfoundation-samples/issues/17

 

Any luck, @rob_ice ?

 

Hi all. We are investigating the problem will update you when we have something actionable to share.

-Thanks,
Mike

 

Haven't been able to test as was rushed off my feet yesterday, hoping to get a moment to look today but it definitely sounds like Unity Staff will be looking into it as it looks like the phrasing about it in the 2018.2 release blog post has changed the way they explain the use of LWRP and now it has a warning about AR use -

"Please note that LWRP is currently not supported for handheld AR, like ARCore or ARKit, or HoloLens or Magic Leap devices. New product plans will be communicated at a future date."

It is a shame because it sounds ideal for AR!

 

Any news or estimates on a timeline for getting this fixed?

We're hoping to be ready to publish our AR optional game in about a month or so, and we're wondering if we'll have to delay either the release or the AR functionality due to this issue.

Thanks!

 

We've implemented a temporary fix for this issue. You can read about it here if you're interested.

 

Hi, lads! Do you have any news about official fix ?

 

Would be interested in an official fix since a workaround has been made

 

A fix is currently being tested. It should be in the next ARFoundation release (along with a sample in the github repo).