owlbert's picture

Status: 

Vuo version: 

OS version: 

  • macOS 10.15

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. sorry if this is more of a VUo in VDMX question will ask vidvox as well..
  2. keep getting complete crashes in VDMX - have taken my free frame VUo Plugins out of the free frame folder but still getting this error message in crash reports..
  3. "vertex plane to world". keeps getting a mention..not sure if this is in my vuo comps running in vdmx. eg. Crashed Thread: 41 CVDisplayLink

Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4 Termination Reason: Namespace SIGNAL, Code 0x4 Terminating Process: exc handler [75460]

Application Specific Information: BUG IN CLIENT OF LIBDISPATCH: Queue type doesn't support dispatch_sync t= 20.2301s VuoCompiler.cc:3312 loadModulesAndSources() Loaded into user environment: [b663cd02] /Users/ed_mundio/Library/Application Support/Vuo/Modules/MM.Points_0.vuonode t= 20.2303s VuoCompiler.cc:3312 loadModulesAndSources() Loaded into user environment: [e557e542] /Users/ed_mundio/Library/Application Support/Vuo/Modules/owlbert.generatorSetUp.vuo t= 20.2303s VuoCompiler.cc:3312 loadModulesAndSources() Loaded into user environment: [f0385869] /Users/ed_mundio/Library/Application Support/Vuo/Modules/owlbert.randomNonRCustomExtendRange.vuo t= 20.2304s VuoCompiler.cc:3312 loadModulesAndSources() Loaded into user environment: [a99cbd33] /Users/ed_mundio/Library/Application Support/Vuo/Modules/owlbert.randomNonRepeat2.vuo t= 20.2498s VuoCompiler.cc:1634 compileModulesFromSourceCode() Compiling owlbert.generatorSetUp t= 20.2499s VuoCompiler.cc:1634 compileModulesFromSourceCode() Compiling owlbert.randomNonRCustomExtendRange t= 20.2499s VuoCompiler.cc:1634 compileModulesFromSourceCode() Compiling owlbert.randomNonRepeat2 t= 20.4379s VuoCompiler.cc:3223 loadModulesAndSources() Removed from user environment: owlbert.generatorSetUp t= 20.4400s VuoCompiler.cc:3312 loadModulesAndSources() Loaded into user environment: [e557e542] /Users/ed_mundio/Library/Application Support/Vuo/Modules/owlbert.generatorSetUp.vuo t= 20.4895s VuoCompiler.cc:3223 loadModulesAndSources() Removed from user environment: owlbert.randomNonRepeat2 t= 20.4928s VuoCompiler.cc:3312 loadModulesAndSources() Loaded into user environment: [a99cbd33] /Users/ed_mundio/Library/Application Support/Vuo/Modules/owlbert.randomNonRepeat2.vuo t= 20.4953s VuoCompiler.cc:3223 loadModulesAndSources() Removed from user environment: owlbert.randomNonRCustomExtendRange t= 20.4988s VuoCompiler.cc:3312 loadModulesAndSources() Loaded into user environment: [f0385869] /Users/ed_mundio/Library/Application Support/Vuo/Modules/owlbert.randomNonRCustomExtendRange.vuo t= 40.3680s VuoGlPool.cc:1511 VuoGlProgram_use() Oval Shader (with halo): WARNING: Output of geometry shader 'vertexPlaneToWorld' not read by fragment shader

t=496.1272s VuoGlPool.cc:1511 VuoGlProgram_use() Image Shader (Lit): WARNING: Output of geometry shader 'vertexPlaneToWorld' not read by fragment shader

t=554.9701s VuoGlPool.cc:1511 VuoGlProgram_use() Shade Edges with Color: WARNING: Output of geometry shader 'vertexPlaneToWorld' not read by fragment shader WARNING: Output of geometry shader 'fragmentNormal' not read by fragment shader

t=668.2783s VuoCompositionState.c:100 vuoCopyCompositionStateFromThreadLocalSto Warning: Couldn't find the composition state in thread-local state.

Thread 0:: Dispatch queue: com.apple.main-thread

Have you found a workaround?: 

not yet- love creating vuo generators and might be doing something silly just not sure.. THANKS for any suggestions /leads cheers Paul

Compositions: 

AttachmentSize
Binary Data TerrainParticles.vuo5.8 KB
Binary Data SpookyDOtFrogSpawn.vuo10.48 KB

Crash reports: 

AttachmentSize
File crashReportText.rtf186.71 KB

Comments

Can you try moving all your

MartinusMagneson's picture
Submitted by

Can you try moving all your custom nodes out of your modules folder and then start VDMX? For an untrained eye, it seems like it crashes when it tries to initiate the custom modules. You could also open the system console to see any error messages when opening VDMX with the custom nodes present. You should filter it to something like "Vuo" "VDMX" as it can be quite crowded with messages from anywhere.