The issue could be somehow related to the drivers, although we are not yet able to reproduce it on Windows 10.As a workaround that should also fix the issue we can suggest to run PhotoScan 1.3.3 in ANGLE compatibility mode using --opengl angle parameters from the command-line:Code: [Select]photoscan.exe --opengl angleAnother way to run it is to modify the shortcut properties:
photoscan.exe --opengl angle