Al Crate

Yup died straight away, when I removed the handler for the message type. ``` #0 0x00007ffff7308280 in caf::actor_system::scheduler() () from /builds/actor_framework/0.17.2/cbb634ff98/lib64/libcaf_core.so.0.17.2 #1 0x00007ffff73e581d in caf::scoped_execution_unit::exec_later(caf::resumable*) () from /builds/actor_framework/0.17.2/cbb634ff98/lib64/libcaf_core.so.0.17.2 #2 0x00007ffff73d3d9a...

Ah ta, I see, yeah that'd probably work, as my atoms are used external of Qt as well as in it, i'd have to apply the same default offset. Custom...

It shouldn't segfault, as that could be triggered accidentally by a remote actor sending an unknown message id ?

Ah, cheers I didn't realise it allocated the array fully, I had a quite sizeable offset in there..

I've dropped the default image cache to 1Gig, this is more reasonable until we implement something a bit smarter.

Sounds like you're deep into the code, you have my sympathy :). Anyway if you're implementing a C++ plugin you could look at the Shotgun DNeg plugin src, this implements...

This is a CMake macro we wrote, it should be in the cmake/macros.cmake file. Not sure why you're build isn't picking it up though.

Make sure you've set the PYTHONPATH in the shell you're launching from, to include the build dir with the python module in, it should be there in the build docs....

This was originally supported, but I think the backend changed, and the python code hadn't been updated. I'll log a ticket internally to get this fixed.

Looks like whatever GFX driver is being used doesn't support the version of the GLSL that we need. I'm not up on what WSL actually uses here, or how you...