Errors opening MediaPipe or CEF.Stride with newest preview

Hi,
I cannot open MediaPipe and CEF.Stride with the newest preview 6.7 - 220. It still works with 6.7. - 178

please tell us more exactly what you’re doing. step by step.

I open preview 220 with the gamma launcher and are getting this

the first time I opened mediapipe help patch with preview 220 it did open ok. Just with the “ToStrideRenderer” red. Now I installed vl.CEF.Stride and the help patch opens like you see in the screen shot.
in the beginning I couldn’t reference CEF.Stride to a blank patch without an errror. After trying out some other gamma version it does work, but mediapipe doesn’t. Just referencing the mediapipe already is cursing the errors

any chance that you’re running VL.CEF as source package there?

no.

any difference if you launch vvvv directly (ie. not via gamma launcher)?

No. Did try this. Did delete an old cef version and deleted the cef. Stride nuget. Because before installing that one. Media pipe was working, just the cef.stride nuget did through error, when starting dependencies

Does it help deleting %TMP%\vvvv-package-cache folder?

this helps. mediapipe is running and CEF.Stride is running. Thank You. Never looked for this folder. Good to know.

Guess I should add a quick access to this in GammaLauncher 🙃

1 Like

It’s where the system places the pre-compiled assemblies. If for any reason (which is now impossible to figure out) the package setup / dependency tree was somewhat broken it might end up with a broken assembly as well. We could forbid this by saying only error free packages get placed there but to our knowledge errors even in packages are quite common and often ok / author of package doesn’t mind, therefor doing so would break the whole gain we have from pre-compiling. Other option would be to do deeper checks on the dependency tree and invalidate them in case it changes. Since we have some upcoming changes planned regarding package management we should wait that out first.

2 Likes