Posts by Rex

BECOME PART OF THE COMMUNITY - Sign up here

    Thank you, Lars. I have viewed your video on this subject. I saw your 3rd party DMX controller activating an executor in Dot2 onPC. I'm attempting to do this as to have physical faders for HID. In your presentation, I was wondering if you were outputing DMX to some device under control of the executor fader? Where you attempting to do this same subject? To utilize a 3rd party physical fader to activate an executor to control a device somewhere?


    Thanks again!

    I'm gonna try this since the device is relatively inexpensive and I'm wondering if anyone has tried this solution before.


    I'm going to take a stream of DMX from a DMX 6-12CH controller as a remote input through my DMX King device to have physical faders...will this work with a DMX King?



    Thanks!


    If it won't thru-put, I'll have a cheesy little DMX tester to output some DMX quickly.

    Profile needs to be edited[in text editor as .XML fileType] to a "Conventional" fixtureType and it will project a beam[then change fixtureType or Patch in the new fixtureType, or try just selecting the fixture in MA3D and RightMouseClick---Change Model; if it's a single instance fixture to a 3D model that has a 'Beam' object or multiple Beam objects in it. If it's a 4/5 beam fixture on all at once; will take a custom model to visualize the fixture as you desire. Doesn't seem too hard a model to build....if the fixtureType is a multi-Instance fixture where you have a Main Module and multiple 'pixels'; this will take much more work to get visualizing in Dot2...


    Good luck!

    I make these types of fixtures! I've constructed 3D 'fog' jets that visualize. I have constructed confetti cannons that visualize a large dispersal pattern of 'confetti'. I have constructed moving scenic elements [drapes, wagons, etc ...]. I make whatever you want that is visualized in MA3D. PM me [Rex] at MA-Share site. I think my terms are reasonable.


    Cheers!

    You need to create the gobo wheel to populate the previews / thumbnails ..... that is where you 'load' the gobos into the scene to render in Smart Windows and the Programmer to activate and visualize.



    The red box is important to build into the profiles in the FixtureBuilder. Much easier way to generate the channelsets,;) .....






    Here's the MA2 gobo wheel and how to load it in the wheel manager just under the module manager .... clown face :( can lead to dmx and ranges to overlap, another sad clown face ...when you build channelsets by hand.


    The "WHEEL" is the start of the process after the attributes, then you go back and link to each set of channels. You seem to have started to use the resources. This is why you can not preview the GOBOS! Edit Row and Add are your helpers when building ....


    Cheers!


    Rexy


    Apologies for the odd translation ...... totally mashed my sentences.

    Here ya go...give this a try. Very Quick and Dirty.


    Got everything to visualize excepting Prism1_Rot?? Every time I call it up with the console, the multiple beams snap back into a single?!? Tried giving each one it's own Subattribute but no go...


    GoboWheel spins, Gobo1 individuals rotate each direction and stop.


    Shutter works as DMX channels are schedules[DIM first, then Strobe, then the Shutter Open, just need to go to RAW values to fine the SMART BUTTONS...all work with Fader, just all on one handle[the bane of 'split channels' of control].


    Good luck with the PRISM1_ROT Function/Channel Sets!! I'd say you're 90%+ to visualizing the fixture as intended!!! FTW!


    Rexy


    PS: do NOT open this.XML from the console in FixtureBuilder....use the console to edit! <info> has my notes!

    This seems to be a more accurate DMX chart to build a fixture from...cheers!


    Rex

    This may be how your fixture needs to be set up in the way of a 'SHUTTER / DIM' ......to follow the DMX chart.

    Well ... Visualizations in dot2 3D are created from the 'SUBATTRIBUTES' of 'ATTRIBUTES' in the profile and the PHYS FROM and PHYS TO entry fields. There are only a few 'keywords' that function as a SUBATTRIBUTES in dot2 3D and they must be Exactly named, otherwise they will not visualize / render in 3D dot2, but may be the actual fixture on the stage .


    Looking at the image you have provided, I would say why you are not seeing the 'effect'.


    Try changing the name of EFFECTROTATE to "PRISMA1_ROT". This makes PRISMA1 rotate in dot2 3D ...
    The other visualization for the PRISMA1 'effect' is "PRISMA1_POS". This 'should' allow for non-continuous indexing of the effect for alignment.


    I think the visualization you want is PRISMA1_ROT. The keyword of EFFECTROTATE as a sub-attribute is NO visualization that I know of.


    Good luck!
    Rex


    Your SHUTTER issue may be solved with more clear Phys From and Phys To data in the entry fields ... from the information in the image, you are telling the SHUTTER to go from 0 to 10% as DMX goes from 129 to 230. A SHUTTER subattribute should either 0 or 1 , Closed or Open . During the DMX [129-230], change both PHYS FROM and PHYS TO 1 , if the SHUTTER is meant to be CLOSED during DMX [129-230] change both PHYS FROM and PHYS to 0 .


    There are not any in the Fixture Builder about what is an actual 'visualization' subattribute and what does not render in dot2 3D.


    So, your ENCODER ranges are wacky. Within each Channel set, the encoders should be divided into ranges as the DMX values are, unless you want each section to start at zero to each individual end ... never done that before.


    Apologize for strange translating text from what I typed in English ...

    As volumetric fog, no. You can have a this as a visualizable effect, however. It takes a custom model and some work in the .XML profile of the fixtureType. I've created this type of visualization...

    In Settings: make certain web remotely is checked ON. It will show the IP address below the Web Remote heading. Password protection with Change.


    Good luck!

    I would say read up on the topic here: List Since Dot2 is based upon the same architecture, the List Cmd is the same; just doesn't have an entry in the Glossary. Since you can't 'write' a Macros outside of a Cue, I assume that CmdLine operation in the Dot2 schema isn't expected?

    Looking back into my basic computer programming from eons ago; a 'list' is an array of data with multiple components...by asking for a 'list' you're asking the 'machine' to 'print' all data associated with the object on screen when the command is executed.


    good luck!

    I do not believe you will see the 'Node' in the Network settings, I myself look for mine and never find it. I believe that only 'MA products/nodes' will be shown in that dialog. I, myself, utilize a DMX 'node' to output DMX from the E-port of my laptop. My E---DMX adapter does not show in the Network dialog[DMX King pro 1], yet still functions perfectly; perhaps not your particular E--DMX adapter. I check both Art-net and sCAN output formats.


    Here's a German language video of perhaps your particular E--DMX node, hope this is of help:

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    I do not believe you can edit this value in the Fixture Builder. You can edit this in a copy of the profile in MA2 onPC or an .XML editor/IDE. The value to edit is, "Minimum 3D Time", last column of the subattribute needing editing[PAN/TILT] inside the console-Patch.


    If you edit the .XML in an IDE, you will need to add the assignment statement ' phystime="N" ' where N= some integer between 0.0 and 10,000 after the "phys from/to" assignments. This assignment affects the 3D model. An example appears below of a PAN having a 25 second travel speed:


    XML
    <ChannelFunction index="0" from="270" to="-270" min_dmx_24="0" max_dmx_24="16777215" physfrom="270" physto="-270" phystime="25" subattribute="PAN" subattribute_user_name="Pan" attribute="PAN" attribute_user_name="Pan" feature="POSITION" feature_user_name="Position" preset="POSITION" preset_user_name="Position">

    Notice the ' phystime="25" ', this would cause the PAN attribute to take 25 seconds to travel the entire range of rotation values you supply for the fixture in physfrom/physto.


    Rex