I would suggest to have good connection and good computing device when working with the Builder. Depending on your usecase, you may be transferring lots of data, requiring some reasonable internet quality, also the device will need you decent screen space, it is not a mobile app. The fact that it is built with web technologies is to allow more direct access, not require installation, have better update paths and so on, still it is a complex application and it needs a proper computer to run on. Kind regards Petr

Hello, best would be to approach VW directly with questions about their implementation... Kind regards Petr

Manufacturers have the same tool you have - the Builder, here. GDTF is just a zipped folder, you can open it and edit the description.xml by hand or by custom tools...

As for the Beams definition, i will have it to be checked, some of the data seems not correct, thank you. The Min/Max... values are related to DMX Profiles, that is curves defining relation between linear DMX and (nonlinear) behavior of the physical element. This is not physical from/to, that is in the PhysicalFrom/To. The (Minimum Physical Value that will be used for the DMX Profile. Default: Value from PhysicalFrom). As for the LuminousFlux value in the beam, this is just an indication of the output of the device to have some reference, then there is more precise data, such are the Emitters/Filters sections. As far as spectral power distribution of emitters, all of Robe color measurements are consistent, taken at a consistent distance, taking square root law into consideration and so on, to ensure that spot/wash/linear devices come with measurement that are possible to be used. For more detailed beam description, LDT or IES (or the new TM 30-18 description) will need to be used, which is planned for GDTF for the future. The description of the beam is (say LDT) is still providing an information about one particular setting (for example zoom).

Hello and welcome, i would suggest that you contact the device manufacturer and ask for GDTF from them. What GDTF provides them is a tool do create the file, distribution platform, documentation about the format, documentation about files creation and so on. You could make the files yourself, but then the device manufacturer never knows that there is a need for GDTFs. As far as converting MA2 to a basic GDTF structure, i am not aware of such tool. Given product similarities, i would think it might be more interesting to start from and existing GDTF file for a device from the same manufacturer + product category and modify it for the required device. As for the 3D, convert it to glb, rather then 3DS. Hope this helps Petr

GDTF does specify the following primitive types: “Undefined”, “Cube”, “Cylinder”, “Sphere”, “Base”, “Yoke”, “Head”, “Scanner”, “Conventional”, “Pigtail”, "Base1_1", "Scanner1_1", "Conventional1_1"; and it also provides models for these primitive types (here) with the exception of the basic 3D shapes like cube, cylinder, sphere and pigtail, which (pigtail), in the default implementation by the GDTF Builder, is being provided by a cube. Again, some internal implementation by specific software will vary slightly as i mentioned, this is why it is better to talk to the vendor directly if needed, as for example getting a precise vertex count depends on the software library you choose to use.

I presume you mean the Resource Manager in VectorWorks? Let me add @klinzey here, maybe he has an idea, or knows if this is planned for the future. Cheers P.

FYI, we have cut some parts of the model and decimated the model slightly more, to get under the MA limit to get their default 3D view with our custom meshes. You can see the result on the Share. Have a good weekend 🙂

Interesting... I cannot see where i can set the limit to be below/above 1200 vertices in MA, i only can see Standard/High/... settings, including in their documentation, where can you see this? As per your and mine calculations, the total vertex count of what we provide for the Spiider is still below the recommended 1200 limit, considering the pigtail should be a generic cube, which is what we add when we create the file. On the side note, the GDTF recommended 1200 limit is for a traditional moving head with base, yoke, head and one beam, rather then for a fixture with 19 beams. It is a good conversation, but as this is about specific software behavior, i would suggest that you discuss this behavior of the MA software with MA as i have no inner knowledge of their system...

Thank you for confirming that the Spiider comes up OK for you. At the end of the day, we don't control software defaults and even if we try to micro-optimize the Spiider, if you for example add Tarrantula you will have the same issue, so LOD setting will be needed anyways. As far as details of the multiplixel multilayer based devices, this is work in progress for better visualization. You will have to ask MA about the details of their software. Petr

> not being too familiar with GDTF or MA3 it's unclear to me Thank you for your feedback, much appreciated. The GDTF provided limit is more then enough for us to provide nice models and also the lens shapes. And if we needed more, there are now three levels of details in GDTF itself to provide really high quality meshes. The Spiider uses less then 900 vertices: models/gltf/yoke.glb 202 models/gltf/head.glb 302 models/gltf/pixel3.glb 20 models/gltf/base.glb 298 models/gltf/pixel2.glb 10 models/gltf/pixel1.glb 12 total vertex count: 844 As for MA, you need to get at least a bit familiar with how to use the software you want to use for the testing. MA requires you to change level of detail for rendering, as sometimes they change the models to look like packing boxes. Once the setting is done, what you will see is this: When at full, they look like this: Hope this helps, Petr

All currently available Robe GDTF files have been converted to use the glTF mesh format, in the form of glb files. You can read more about it here https://gdtf-share.com/user-page?name=Robe+Lighting+s.r.o.&page=home . This change has happened already in October/November, together with many other improvements and changes like converting the Connectors into Wiring Objects, adding 2D and also including the above mentioned more streamlined linking of channels to particular geometries. Let us know in case of any issues.

Signing into the builder seems to work OK here. I would presume that you have forgotten your password, you can reset it on the https://gdtf-share.com/forgot-password link. Hope this helps Petr

Hello, if you figure it out, we would also love to know. Also, 5.1 has been crashing consistently on my computer so it's harder to test now. P.

Thank you, reported to developers.

Thank you, reported to developers.

Hello, post the offending file here please, thank you, P.

Hello, sorry about the issue. Does it happen with every type of file? Please post a file and a step by step procedure to replicate it, so we can try to reproduce it. Thank you. P.

And Pablo, just for your information... it may depend on console/software implementation to choose the RDM related field, but for auto matching, Software Version ID from DEVICE_INFO would make sense. For the user matching it, it may be different... so this depends on the implementation. Have a good weekend, P. edited for clarity.

Hi Pablo, you enter the values in hex, this is defined in the DIN Spec, see here all relevant sections (they are close to each other, but i linked them anyways): https://github.com/mvrdevelopment/spec/blob/main/gdtf-spec.md#rdm-section https://github.com/mvrdevelopment/spec/blob/main/gdtf-spec.md#softwareversionid https://github.com/mvrdevelopment/spec/blob/main/gdtf-spec.md#table-72-dmxpersonality In the DMX mode the software version is a version that is sent via RDM and the RDM Mode Id the ID of the mode your software sends when querying the DMX Modes via RDM. The software version linked to the dmx mode id in the GDTF builder indicates from which software is this DMX mode available in the fixture. So for you, it would be, as per the image example above: Software version 1 (taken from boot software id) and the 1, 2, 3, 4 for modes Basic, FX, Standard, Extended Hope this helps P.

Thank you, reported. P.

Hi Paolo, I think some of the issues have already been fixed and we will push then with next update but thank you for the list, this is very helpful, i will pass this to the devs. cheers Petr

Hello, this would indicate some network connectivity issues on your side, upload and download seem to be working OK when we are double checking it here. Kind regards Petr

Hi Paolo, yes, this is if you start from the empty template. If you start from another template, all is OK. We have already fixed it and will push this fix to the live Builder when we are back from LDI. Please let me know in this thread if you experience any other issues, thank you Petr

Hello, sorry, this is not the right place. You are using MA2 while this forum is about GDTF which can only be used on MA3. Please get in touch with your MA support or try using the MA forum, Kind regards Petr