was working perfectly and had been putting off updating to 15.5 from 15.2 .
updated to 15.5 and it now crashes after building shaders ???
I can’t post the apple log cuz it is too long . any help ?
first few lines of the crash report
can confirm it crashes with 1.1.7 with similar report!
ran apple system diagnostic and hardware came back fine!
Translated Report (Full Report Below)
Process: VDMX6 [1316]
Path: /Applications/VDMX6.app/Contents/MacOS/VDMX6
Identifier: com.vidvox.VDMX6
Version: 1.1.8 (1.1.8)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2025-07-09 03:28:39.7452 -0400
OS Version: macOS 15.5 (24F74)
Report Version: 12
Anonymous UUID: 706ED163-3B1E-E072-A842-F669731A4138
Time Awake Since Boot: 220 seconds
System Integrity Protection: disabled
Crashed Thread: 21 CVDisplayLink
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: VDMX6 [1316]
Thread 21 Crashed:: CVDisplayLink
0 libsystem_kernel.dylib 0x185f6d388 __pthread_kill + 8
1 libsystem_pthread.dylib 0x185fa688c pthread_kill + 296
2 libsystem_c.dylib 0x185eafc60 abort + 124
3 libsystem_c.dylib 0x185eaeeec __assert_rtn + 284
4 Metal 0x19153cb3c MTLReportFailure.cold.1 + 48
5 Metal 0x191511bfc MTLReportFailure + 576
6 Metal 0x1915077bc _MTLMessageContextEnd + 876
7 Metal 0x1913abd38 -[MTLTextureDescriptorInternal validateWithDevice:] + 2380
8 AGXMetalG14X 0x11922f310 -[AGXTexture initWithDevice:desc:isSuballocDisabled:] + 56
9 VVMetalKit 0x104e6c4c4 -[VVMTLPool _generateMissingGPUAssetsInTexImg:] + 1784
10 VVMetalKit 0x104e69c5c -[VVMTLPool textureForDescriptor:] + 176
11 VVMetalKit 0x104e69d4c -[VVMTLPool bgra8TexSized:] + 80
12 VDMX6 0x1045dcd24 0x104428000 + 1789220
13 VDMX6 0x104435d68 0x104428000 + 56680
14 VDMX6 0x10443de30 0x104428000 + 89648
15 CoreVideo 0x18f93b3b8 CVDisplayLink::performIO(CVTimeStamp*) + 308
16 CoreVideo 0x18f93a37c CVDisplayLink::runIOThread() + 660
17 libsystem_pthread.dylib 0x185fa6c0c _pthread_start + 136
18 libsystem_pthread.dylib 0x185fa1b80 thread_start + 8
fixed it by doing a full wipe of vdmx as per the fixing common vdmx issues !
now running perfectly !