I would inquire at the MA3 site about rendering of attributes in their newest software...and 3D visualizing. Again, I have some doubts if all attributes currently visualize in MA3, yet.

Dependant upon visualizer...using MA3 in 3D window?? I have found it to not yet visualize some attributes...Iris may be another.

...or at least restrict in some way, the actual 'brands' of fixture files as opposed to a GENERIC heading or the more appropriate, USERonly moniker. In that way, only actual manufacturers can upload content for their brand names and everyone else can, if they choose, to dump into separate servers/locations?? Just a quick thought on the schema of things, looking a few steps ahead to avoid mis-steps/information, ...

I agree. Proprietary content was why I began deleting versions of things I had uploaded; especially[& immediately] when I found that assets I had created were being used in similar profiles not uploaded by myself, without permission. That must end...in my opinion. This had me wondering about the concept's current/intended protocol. I believe the intent was to have the actual manufacturers provide the stewardship of profiles for their proprietary equipment; yet in current phase and practice, this leads to anyone to be able to upload a branded device's profile for the entire webiSphere to manipulate. Cheers!

Magic...it's simply magic. All is fine today. After 3 days of attempting to pop the dialogs and getting nothing; all things are back to normal. I just opened the F12 Developer window at your suggestion and both DL and Open in Fixture Builder functioned as before. Thanks for the help! Love it when things that worked, don't...and then do work again after something, something....lol.

Yea....still no go, not a game breaker....just chalking it up to Win7 and Chrome and the need to update things...worked fine since inception and up to just a short time ago... Thanks! I appreciate the info, even allowing all popups[yikes!] doesn't allow the dialogs to pop-up. Of course did not do a full reboot after changing the preference.... All works fine in Win10 for me...

Must be Win7 and Chrome not supporting Flash[is the builder FLASH based?] anymore...in this machine[Win7 desktop] the buttons simply do nothing--click all you like; no dialogs appear on either Download button or the Open File in Fixture Builder. Rebooting fresh this morning did nothing to fix the issue with the web page buttons. Odd, because I can directly open the Fixture Builder page and it all works...go figure and note to Devs. I have control in another setup I own; Win10 laptop which works just fine. Leads me to believe it's time to rebuild this desktop machine to Win10 and a better graphix card...it's worked great for 5 years now, tad beyond it's 'expected' lifespan for a modern computing device. The video card crapped out just recently and that was a gentle nudge to git movin'...lol. Got it up and rendering[black screen of NOTHINGNESS is spooky] in no time with a substitute card, but...not the most modern, just got it up to GTX 1060. Thanks!

Ya...checked on the Win10 laptop and all works; loads the fixture builder from Share site and database of fixtures. Win7 lost already...oh, no!

Perhaps it's my OS[Win7] and browser; at the moment, I cannot get the Fixture Builder to link to the GDTF-Share library of fixtures?? The only browser that I use is Chrome, namely because I can't get any of the others to render the pages correctly.... I browse the database of fixtures and try to open them with the Fixture Builder button, but no go, nothing happens. Can't seem to download any files either?? I can go to the actual builder web page and view files there... Firefox comes closest to rendering any GDTF page but won't populate the database page with fixture files, 'No Files Found!' prompt there..[Flash based viewer??], IE does the worst at any of the web pages associated with GDTF[and others, lol]. Did WIn7 crap out that fast after support ending...?!! I know Flash isn't supported by Chrome any further.

@petrvanek ...and it is taken for schema that any/every Yoke should be positioned along the X axis and thus orientate your Pigtail position[on the Base] according in regards to realWorld fixture default behavior. Is that correct, petrvanek, as per the format requirements?

There is a Model 'type' that defines a fixture's 'whip'/power input cord.....called "Pigtail", under Geometry--Primitives--Pigtail. That should be enough? I doubt that there will be an Attribute for that however[Fixture Orientation??]...I could be wrong?!? Build your 3D models to real world fixture behavior, some Yokes are 90 degrees offset from 'Pigtail' position, some aren't. I know I always ask the Programmer how they prefer the fixtures positioned.

For me, the video stops at 5:22..?!?

re-defineArray(); re-defineMatrix(); re-definePatch(); ...something, something, lol.

Don't ColorForce series of fixtures have a Left--Right or Right--Left internal mode to 'swap' the 'patch' of the fixtures? Would that be an example of such a request?

For things to parent 'correctly' inside MA2 and render correctly, you may need some specific Geometry Helpers in your base model for things to offset in a visually correct way. Perhaps if you build the GDTF fixture as you do a MA2 fixture needing parenting, you'll get a more visual result/solution...haven't tried it yet; but it's something I've been postulating inside the ole 'hardhat',;), if you know what I mean...as I consider what renders in MA2/MA3 and how fixtures are constructed with regards to 'helpers'. GDTF would seemingly make strange modeling constructs unnecessary moving forward in how we describe 'fixtures' when they render... If your target is MA2, I'd write the file in 1.5 FixtureBuilder or in a MA2 emulation/onPC...beat the Christmas rush, as it were and I often say. 'Conversion' most often does not parse 100%. Until all console manufacturers get in line with the evolving GDTF; it's a matter of keeping the 2 things separate, as we did when using custom models and Multi-Instance fixtures between v3.1.2.5 and 3.2+ and adjust accordingly. M'eh, what ya gonna do?