Hey Y'all, I think I found a bug on the builder when duplicating geometries. It seems that a random integer is being assigned to values that are 0 when getting duplicated. Screenshot 1 is the original selection and screenshot 2 is the new geometry after selecting Duplicate Selection from the dropdown. You'll notice random integers now in the X and Y Posiion areas, the rotations seem to be fine. Cheers! MattG

Hey Petr! Thanks for the response. This right here answered what I was looking for! Disregard the second thing for now, it's a bigger picture topic that more light will get shed upon on hopefully in a week or so, but who doesn't love Free beer and wings!!! haha! Thanks for your thougts on this Petr! Hopefully one day we get to meet! Cheers! MattG

Hey Petr! Nah, I'm talking about the location that the Continuous attributes are defined, as they seem to be under control right now, which per manufacturers, those are not a control function, they are still defined as a position attribute. What is the thinking behind this for putting it in the control attribute? As of right now, certain visualizers will not read this as an option with where it is attribute wise. Yea, we all understand that the builder is not a visualizer, which should be addressed because anyone can make anything right now, and say it's "good" without checking it unless you have access to a physical MA3 somewhere which seems to be the ONLY piece of software that can read GDTF files that has a visualizer. Things can get outta control fast it feels right now haha! Thoughts? ?

In regards to this, a friend of mine showed me that I was using the references wrong for the "multi instance" features. I didn't make the Pixel side of the fixture. So general note, use the references to save time haha! It would be nice to have a grid or a "calculater" for lack of a better term when dealing with large amounts of identical reference objects, maybe something that can have how many objects with an address field of X and then increment name by 1 or something like that. Cheers! MattG

Hey Y'all, Are there any thoughts about creating some sort of population grid for when there is the same attribute being used on numerous pieces of geometry, i.e. multi cell fixtures that all use RGB or RGBW etc etc attributes. It's becoming way too tedious to have to assign the same attributes over and over on pieces of geometry, ends up just being a huge time suck. Are there any thoughts on how to make this a little more efficient? I understand that of course you have to assign different DMX values to the attriutes, but on the Web GUI at the current moment, going through 3x pop up's and drop downs to assign (multiplied by however many pieces of geometry) just isn't very fun haha! I tried to do copy and paste but of course the error is that that attribute is already assigned to the same piece of geometry, rightfully so. Any thoughts? Cheers! MattG

Hey Y'all, I was wondering when we might be able to expect the good ol fun functions for all the fixtures with Continuous Rotation Capabilities. Not seeing it as of right now but was curious where it was on the road map for the builder. Cheers! MattG

Hey Y'all, Are we going to see the implementation of texture mapping for 3DS files on the builder? Currently doesn't seem to be implemented with simple color textures, is this a function that's being worked on? Cheers! MattG

Thanks Petrvanek! Understood on this. yea, with how many programs users can make models in, it would be cool to have a dropdown for what unit the model was exported from for the import. Thanks for the update! Cheers! MattG

Hey Guys, So, Rex is correct in this because I'm getting the same result. I exported a 2m x 2m x 2m cube, very standard, and used the same export setting's I have been using for years with C4D MA3D, solidworks, and 3ds Max, and the import function for models seems like it's 1x 0 off every time. I can bring this 3DS object into all other programs and it retains its correct size and position. Here are 3x screenshots of the 3x different exports I did into the builder

I'm with Rex, I've had to create a workaround in C4D just to get the actual dimensions of each piece of Mesh and then insert them manually. Is it in the pipeline for a future release to accept information from the 3ds like we have been doing with MA3D since it's beginning? Cheers! MattG

Hey Petr, Awesome stuff, is SVG still the preferred method to use for the 2D information? Cheers! MattG

Hey Y'all, I was wondering if the 2D "symbol" for lack of a better term is a feature yet for programs such as Vectorworks and AutoCad. MVR has come along quite nicely which is awesome! So was curious what the timeline might be for this feature if it's still planned! Cheers! MattG

Hey Jim! I hope this finds you well. Wanted to see if I could help with your thoughts above. The overall goal for the GDTF database is to help find a common ground between any application that wants to use the info stored in these files by utilizing a certain naming scheme. I'm not a developer so I can't really speak of anything to any coding and such haha! In regards to the lighting manufacturers needing to find more users for their products, GDTF isn't meant to be a marketing tool for them, but merely a better way for them to put all the information about their product into one place and not having to rely on a 3rd Party to correctly understand the functions of their product. (best way I could say it haha!) The building of a GDTF file is still only an option for them, because if certain platforms whether it be a visualizer, CAD program, controller software, etc etc don't have GDTF implemented, then it is on the developer of the application platform to build their own script per their specifications. This is where a lot of info can get lost in translation between the manufacturer and developers, which is why GDTF came about which is great. A wonderful thing about GDTF is that it's not only limited to lighting, it's limited to anything that doesn't utilize the current DMX512 control standard which is toally fine. This could be anything from lighting to video to lasers to well, anything that can be controlled remotely if implemented by DMX512. In regards to an application that utilizes timeline based programming, I'm sure there could be something developed if not already which would then just need to add in the GDTF libraries to their program and then get all the benefits from it. There's a lot of other uses for products out there than just for lighting directors. The market for architectural lighting, large TV shows, special events, etc etc utilize these products as well so GDTF isn't merely being designed for lighting manufacturers only making things for concert lighting. But I agree, I'm sure GB can make a bad ass light show as well ? From what the article was saying about the workflow and increasing efficiencies, with MVR and GDTF implemented into different styles of workflows, this is a small step to a larger vision in getting information to clients in a lesser timeline (pending any circumstances on the project) and more accurately. I hope this helps about why the GDTF library and MVR were put together. Cheers! MattG