Timeline for Compute shader: Property at kernel index is not set
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 24, 2020 at 21:47 | comment | added | Glen Pierce | I'm running version 2019.4.3f1 | |
Jul 24, 2020 at 7:57 | comment | added | TakeMeHomeCountryRoads | Can I ask what version of Unity you are running on? I find it weird that your Unity is telling you that setBuffer doesn't exist. Mine works fine, and I am running 2019.4.2f1 | |
Jul 23, 2020 at 15:26 | comment | added | Glen Pierce | What is particularly odd about these is that neither of the first arguments are ComputeBuffers. vertexBuffer.setData is being called on GetComponent<MeshFilter>().mesh.vertices and computeShader.setBuffer(computeShader.FindKernel("CSMain"), "vertices", vertexBuffer)... computeShader.FindKernel("CSMain") is an int. | |
Jul 23, 2020 at 15:17 | comment | added | Glen Pierce | Assets\MoonShader.cs(25,22): error CS1061: 'ComputeBuffer' does not contain a definition for 'setData' and no accessible extension method 'setData' accepting a first argument of type 'ComputeBuffer' could be found (are you missing a using directive or an assembly reference?) | |
Jul 23, 2020 at 15:17 | comment | added | Glen Pierce | Assets\MoonShader.cs(26,23): error CS1061: 'ComputeShader' does not contain a definition for 'setBuffer' and no accessible extension method 'setBuffer' accepting a first argument of type 'ComputeShader' could be found (are you missing a using directive or an assembly reference?) | |
Jul 21, 2020 at 5:07 | comment | added | TakeMeHomeCountryRoads | Can you post the error message? | |
Jul 20, 2020 at 16:27 | comment | added | Glen Pierce | Thank you! I'm getting errors on these two lines now: vertexBuffer.setData(mesh.vertices); computeShader.setBuffer(kernelHandle, "vertices", vertexBuffer); both of the errors are complaining: does not contain a definition for ____ and no accessible extension method ____ accepting a first argument of type 'ComputeBuffer' The first argument in one case is a Vertex3[] and next case is an int. This error is super-confusing and I don't see any reference to how it's even possible. Do you have any idea where it might come from? | |
Jul 20, 2020 at 13:21 | review | First posts | |||
Jul 28, 2020 at 5:12 | |||||
Jul 20, 2020 at 13:16 | history | answered | TakeMeHomeCountryRoads | CC BY-SA 4.0 |