Lars Wernlund
Lars Wernlund
This could be relevant - https://docs.microsoft.com/en-us/windows/win32/api/d3d11/nf-d3d11-id3d11devicecontext-flush
I like this idea. I have already seen files this size from our users and will likely see worse. Unless the glTF is really peppered with large extras and extensions...
I would open the glTF file in a text editor and step through the code in a debugger until I discover what is not happening as I had expected. Are...
Looks solid to me! Here are a few thoughts; How will the extension setup callback know what it is setting up? - One callback per object type? `VENDOR_ext_setup_asset(..)`, `VENDOR_ext_setup_node(..)`, etc...
My 2 cents would be that it's only meaningful with human-readable error output if the user can reasonably be expected to fix the error. If the glTF is referring to...
Fair enough, I've been there myself. I used https://github.khronos.org/glTF-Validator/ then though.
Classes are a VectorWorks thing.
Here it is vital that there is some contract in place for the type of IES/LDT files used. Ie. which zoom level, focused or defocused, with or without frost or...
There's lots to think about when making IES/LDT files and we come across a lot of troubled files, but I don't think it's really relevant to GDTF. One thing could...
Unless the barndoors are motorised (DMX controlled) and an integral part of the fixture, ie. not an accessory, I would not include them in the GDTF. Instead I would focus...