HD and LW pipeline 2.0.1 cannot compile with Unity 2018.2.0b2

Unity Engine
1

Hi!

I just checked latest available hd and lw pipelines 2.0.1-preview with Unity 2018.2.0b2.
It produced a lot of errors.

I uploaded full log to cloud because it was too large: Are you not a robot?

The main errors are there about something was missing and kernel index out of range.

2

What are you referring with that 2.0.1-preview? I could find any related package that would fit that description.

Latest SRP release is 1.1.5-preview (available through Package Manager on 2018.2b2). Latest PP Stack is 2.0.5-preview (also available through Package Manager)

3

I added in manifest file “registry”: “https://staging-packages.unity.com” to enable latest preview features.
Here is my manifest.

{
  "dependencies": {
    "com.unity.package-manager-ui": "1.10.0-preview.1",
    "com.unity.textmeshpro": "1.2.2",
    "com.unity.ads": "2.0.7",
    "com.unity.incrementalcompiler": "0.0.38",
    "com.unity.postprocessing": "2.0.5-preview",
    "com.unity.render-pipelines.core": "2.0.1-preview",
    "com.unity.render-pipelines.high-definition": "2.0.1-preview"
  },
  "registry": "https://staging-packages.unity.com"
}

I added screenshot from my Package Manager in attach.

3481184--276874--SRP Cut.png

4

where does these 2.0.1-previews even come from? official git repo only has 1.1.5 on releases (same with package manager) and 1.1.6 on master.

if they exist, sounds like they are meant for some internal unity versions that are not released yet.

5

It is strange. I downloaded it from Package Manager as you can see in screenshot above. Maybe this is a bug with PM and i got access to internal stuff.
I will write about it on PM forum theme.

6

Changing the registry to staging has been mentioned in the past on these forums. But I dont think we really know what the state of any of the packages on staging is, especially since pipeline version numbers on github do not resemble the 2.x.x versions you have got.

At the moment those wanting to try the very latest render pipeline stuff have tended to be using a github version, where it is at least clear exactly what version/updates are included. As of a day or two ago the github master branch of HD pipeline was still working on the publicly available 2018.2 betas, but at some point it is likely to stop working with public betas again, so now is a good time to try it.

An official comment from unity about the state of packages on the packages staging server might be useful, since these extra layers of confusion are not helping matters in am era that is already packed with great change.