Lorenzo Gaifas

I think we can close this one and put it on hold. @jni, should I open another PR to mark this a retracted, or else "paused", or something of sorts?

Hi @AdvancedImagingUTSW! I still think this is not the full stack trace; where are you running tis from? Can you provide a minimal reproducible example so I can try it...

Ok, so it seems that indeed the issue is the same as #1100. Your traceback shows this: ``` GLError: GLError( err = 1285, description = b'out of memory', baseOperation =...

Yeah, no doubt your GPU is (a lot) more powerful; but clearly it advertises its `MAX_TEXTURE_SIZE` as much smaller. I don't know how/if this relates *directly* with VRAM size... Maybe...

> 8192 is not that small ;) It's the maximum size for each dimension [8192^3]. Oh wow, ok. Then I have no clue o.o. > In the mean time, I...

@psobolewskiPhD It seems that once again the traceback is misleading :P your error has nothign to do with this issue. Yes please, open an issue over there, this is definitely...

Yes, that's unfortunately because we're using "private" stuff from vispy (implementation details of the shader), and those things were changed in a incompatible way. This is a recurring problem, because...

@joaomamede it seems like a similar issue. I suspect your vispy version is out of sync with your napari version. Can you paste here the output of `napari --info`?

For future visitors: `napari 0.4.14` was too optimistic with its dependencies while using private `vispy` stuff, so it will install `vispy 0.11` despite being incompatible. So you'll have to either...

I opened tlambert03/setup-qt-libs#57 to address that. Hopefully that's correct :P