# Error linking shader FRAGMENT varying vertexIDVSOutput does not match any VERTEX varying
**URL:** https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336
**Category:** Web
**Created:** [September 13, 2022, 8:26am UTC](https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336 "2022-09-13T08:26:29Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@zaidb](https://discourse.vtk.org/u/zaidb)
#### Post date: [September 13, 2022, 8:26am UTC](https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336/1 "2022-09-13T08:26:29Z")
Hello,
My goal is to add a widget manager to my renderer.
```nohighlight
const widgetManager = vtkWidgetManager.newInstance();
widgetManager.setRenderer(this.renderer);
```
Everything works well at first. However, as soon as a Polydata (with `getVerts().setData(vertex)` added to it) is added, an error is returned saying:
`Error linking shader FRAGMENT varying vertexIDVSOutput does not match any VERTEX varying`
I tried to replicate the error using a minimal configuration, but I could not.
Any help would be much appreciated!
---
### Author:  [@finetjul](https://discourse.vtk.org/u/finetjul)
#### Post date: [September 13, 2022, 10:59am UTC](https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336/2 "2022-09-13T10:59:54Z")
Vertices are “references” to points. Did you also add points to your vtkPolyData ? poly.setPoints(…)`
---
### Author:  [@zaidb](https://discourse.vtk.org/u/zaidb)
#### Post date: [September 13, 2022, 11:18am UTC](https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336/3 "2022-09-13T11:18:47Z")
Yes, I am using `polydata.getPoints().setData(allXYZ)` to add points, but it still returns the same error.
---
### Author:  [@finetjul](https://discourse.vtk.org/u/finetjul)
#### Post date: [September 13, 2022, 11:36am UTC](https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336/4 "2022-09-13T11:36:35Z")
It is possible that the issue comes from the hardware picking. Adding a widget manager adds a hardware picker into the renderer.
[Recently](https://github.com/Kitware/vtk-js/pull/2369) the hardware picker has been improved. It wouldn’t be surprising if it does not support vertices (only lines and polys).
It might be worthwile to try a version of VTK.js BEFORE the [MR 2369](https://github.com/Kitware/vtk-js/pull/2369) and see if it still fails.
---
### Author:  [@zaidb](https://discourse.vtk.org/u/zaidb)
#### Post date: [September 13, 2022, 11:53am UTC](https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336/5 "2022-09-13T11:53:20Z")
I tried two versions: [v24.12.1](https://github.com/Kitware/vtk-js/releases/tag/v24.12.1) and [v24.13.1](https://github.com/Kitware/vtk-js/releases/tag/v24.13.1). The same error is thrown.
Here is the console logs in case it helps:
---
### Author:  [@zaidb](https://discourse.vtk.org/u/zaidb)
#### Post date: [September 13, 2022, 11:58am UTC](https://discourse.vtk.org/t/error-linking-shader-fragment-varying-vertexidvsoutput-does-not-match-any-vertex-varying/9336/6 "2022-09-13T11:58:21Z")
I have just noticed that this happens only `SphereMapper` is used.