Jump to content

GDTF Forum

David "Rex" Whalen

Members
  • Content Count

    97
  • Joined

  • Last visited

  • Days Won

    8

David "Rex" Whalen last won the day on July 2 2020

David "Rex" Whalen had the most liked content!

Community Reputation

11 Good

2 Followers

Recent Profile Visitors

1383 profile views
  1. If you are referencing 'bracket' as a 'rotational' component of a fixture type...whether you want the vector to be 'Pan' or 'Tilt'--never really a 'Roll'/3rd rotation vector on real world fixtures...unless you've created something really funky, or like the S4 barrel 'roll'... Give the 3D model a Geometry Type of [Axis], that will make the 3D model/Geometry a 'rotational' object in the visualization. Now...depending upon your 3rd party visualizer, how that 'movement/rotation' is accomplished[manually--outside of DMX patching], remains to be seen[GUI encoder, entry field, etc]...the sp
  2. Illustrator, Photoshop, Dreamweaver...can open these files. Web browsers....GIMP...what exactly are you trying to utilize them for? The webBuilder for the fixtureType icon?
  3. GDTF seems to provide metaData for visualizers to render...so if there is an obvious rendering issue in your visualizer, I would begin inquires at the rendering software sites..."Vision", et al; ask what they say about how their software is rendering the GDTF data.... It could be that your 'Physical Value' range is borked, but even if it's 0-1[DMX 0-255], there should be a curve over the encoder range of DMX values...just a quick thought without examining the provide example. I'm using MA3, at the moment, to visualize the GDTF data...and at this point in MA3 builds, not all visual
  4. Strange, but true...that the same file was read in different ways?!? I went ahead then and constructed the entire fixture in MA3, and it all rendered out well--using the same 3DS files that came in with the GDTF Import. I like the ChannelSet range entries in MA3, you only need to input the beginning of the range, the end is automagically configured. Although, it takes about 5 times longer to construct a fixture within the console--scrolling with a tab and mouse is...ugh. And if some entry fields are not edited, the console doesn't calculate the DMX and give the fixture a DMX footprint an
  5. @petrvanek Glad to hear of an update! I'm curious, as MattG states above with regards to visualizations; what environment for visualizing do/are you utilizing? I ask because with the latest version of the builder...I'm using MA3 as a checker/visualizer since it is, without VW I believe, the only renderer of .GDTF files. I'm not suggesting that a visual upgrade is needed to the assembler[it's great!], I'm just wondering how these things are checked as the iterations roll out. The TakeAway from this: I took a newly generated GDTF file and Imported it into the current release of MA3 v1
  6. I just checked; this is very easy to get visualizing...Patch 2 MovingPath Fixtures, then use MA3D to bring into the Scene/StageView your 'screen' model and your 'moving riser' model; you can use the Plane and Box Primitives as models from the MA3D database. In MA3D, simply DragNDrop your models onto each corresponding Moving Path fixture, easy-Mcpeasy. These MP fixtures are under now control of the desk/DMX...so can be written into lighting cues, etc. Are these moving objects on the stage actual automation under control of an operator/desk/console, or being manipulated by stagehands?
  7. @helendeneb in MA2, what you describe is a MovingPath fixtureType. To get it visualizing as you describe[rotating screen-transforming box]; you'll need to do some editing to the profile...and perhaps some custom models as well, to get things really looking right.
  8. Saying you used 'default' visualizations...then. Well...again, I would have to venture a guess that it is the end user platform[Visualizer--VW--you don't diagram your control config] not correctly reading how the file is structured....and it then becomes a question to those parties...Vectorworks, Vision, etc... I am working under this axiom: This site and the share site are being produced and maintained by those parties involved with pioneering the formats and thus; if things are visualizing here and not in the end of your workflow chain...well, the problems are lying somewher
  9. When you constructed the fixture in the webBuilder...and when you Imported your 3DS files[if custom], did you see the model rendering in the builder? Did you use default fixture models? I'm gonna speculate that it's Vision and/or VW reading the MVR file incorrectly. The web builder references the 3DS files and packs them up in the MVR/suitcase/container, so, if you extract or unpack the MVR file you'll find the 3DS in a nested folder...seemingly just fine. I think Vision and/or VW is not finding the nested asset...within the MVR structure. Just my guess, though....since it is n
  10. My solution: model and export in MM....only thing I've gotten to work in the Builder to compensate for this.
  11. Currently, uploading is the only way to generate a copy of the GDTF file, it dupes the file, one for public Sharing...one for your 'desktop' or other location of storage. Upload to generate the file, then go to public Share site and delete your upload...heavy handed but the only way at the moment to get a 'hardcopy' of your work in the proper format. Good luck! NB: deleting in this manner 'should' keep your work somewhat proprietary and under your control. Once it's at 'Share', for any period of time...it's exposed to the General Public on the interWeb. Anyone can tak
  12. Yes, I have observed the same thing in how the builder does not respect the Export's Size or Dimension. You need to build/EXPORT your 3DS files in MM instead of Meters[at least in my personal experience].....the builder seems to default to MM when bringing in a file, no matter how you check the boxes. I utilize Cinema4D for all my 3D modeling work. Doesn't matter how I 'freeze' the Transforms, the web builder has a mind of it's own with respect to Units used. Good luck! NB: I have done lot's of Conversion work before....drop me a PM and we'll chat about terms?!?
  13. It makes sense to me...the Parent is the container for all sub objects...so I do think the description may mean, per model. Even with super high vert counts on models, the objects still render in the builder. I think they start to visually bork out at like ~65,000 verts[256x256,:)]...truncate groupings, etc.
  14. I agree, it's somewhat misleading if you're getting that error?!? How many Verts were you trying to stuff into the entire 'fixture'? You can get away with some really simple geometry to represent most anything. I've seen 'fixtures' with obscene amounts of geometry data[vertices/polys] in GDTF files and not seen the builder complain that badly... From the format description: Model Collect To these eyes, this reads as the total amount of vertices to be no more than a maximum of 1200 for an entire 'fixture'. That's a fairly generous amount to get a decent rendering of a mo
  15. I would venture to say that it's with the way in which the 3rd party software[Vision] reads the format. MA International is one of the leaders in this format development and I would lean towards what they are rendering as a way to validate the GDTF file you're using. If it visualizes in the web builder, if it visualizes in MA3, but doesn't visualize correctly in Vision....? H'mmmm...wonder who is odd man out? Good luck!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.