Thank you for the reply!
I had access to a single fixture with blades for a night myself, so I thought I would do some interesting tests with DMXC!
This was a great help.
I did not know about the right-click feature! It was the missing link 
I'll continue to post updates and findings!
I am working on a bundle of testing before I move to the BugTracker.
Also. DMXC 3.3.0 RC5
Hello Again Everybody.
I am trying to create a DDF for a fixture containing blades.
I have Checked the DDF Syntax many times, and even tried copying the code linked here:
Blades (DDF syntax) DMXC3 - Deutsches DMXC-Wiki
Blut I cannot get the Blade angles to function at all.
When I enter a manual number in the Device Control, I more often than not get a 'Non Format' error, even though I am giving the correct input format.
The GUI blade control also does not show the Angle blades.
Could you potentially share another sample DDF, code, or a more detailed explanation of the Syntax? This one is puzzling me greatly....
Thank you so much again! 
Hello Again Everyone!
Thanks for putting up with my madness every time I post 
I'm sure this is a topic that has been covered before, but through my search I have not been able to find.
With 3.3.0 RC5, is there currently a way to load the last saved project, or auto Load a project on launch?
Maybe a shortcut argument or something?
Thank you all!
Lol. Thank you all for your replies!
I will gladly make a ticket for this.
I will continue to keep you all updated on findings and questions
Hello again Everyone!
I was trying to experiment with the Electricity Parameters and Input Assignment Nodes.
I have a few questions, but to start, is there a way to change the Power-Source Voltage from 230 to 120 for American Standards?
Also, what is the "Send to Ammeter" option for? Is this a placeholder right now?
Also, in the electricity Input Assignment Nodes, What is "Ping" input?
Thank you in advance for any help or insight!
You know, The more i dig into this program the more impressed I am. Found a new way to do a thing Oh man are there easter eggs all through this app!
Will Update once complete!
Hmm..... Might there be another way to route DMX Loopback into the Input assignment?
The ability to take working Live DMX values and assign them to any parameter through Input Assignment is a very powerful feature I feel might be overlooked.
Unless there is a technical or system-resource reason that this is not a practical solution?
I really thought I remember in older versions that all DMX universes were available thru the input assignment.
Is it due to the application taking too much computing power to handle that kind of raw processing of data?
P.S. I mean not to be crass, but I have come across some concepts that could really be interesting if there is an efficient way DMXC can attach working DMX values to other Input Assignment Parameters. I will happily share the progress once the proof of concept is complete
I would Like to use channels of generic dimmers to light up midi buttons in relation to what is being output in the DMX matrix across all available universes.
This would be accomplished by the DMX Loopback feature within the Output Devices, and then mapped thru the input assignment with a little bit of logic.
Hopefully that makes sense. If not, I can try an upload some screenshots.
But what is the method you suggest?
So we can map MIDI Out to Active DMX Channels across multiple Universes
Thanks Stefan. I had an idea that was the case.
Is individual fixture control still possible thru input assignments?
Or would that better be implemented now thru Submasters/Executor?
Hello DMXC Friends.
Simple Question (Hopefully)
Is it possible to add more than 2 universes of Direct DMX In / Out in the Input Assignment?
Great Thanks
P.S. Happy Thanksgiving [Frohes Erntedankfest!]
I was testing some methods for your fixture the other night, and there may be a better workflow to manage this particular device.
Workflow #1
it is possible you will need to add 7 separate devices for each of these fixtures:
Namely:
1. DDF Containing the Master Dimmer (Ch.1) and Master Strobe (Ch. 26) ONLY
2. 6 Generic RGBW DDF's and add all those to a Device Group (For Organization Purposes)
It will be a little Strange, in terms of how DMXC will automatically auto-address fixtures added in a linear fashion.
You would need to overlap the DMX Address in the Device Manager in DMXC, But here is the Concept:
1 DDF (Device) Containing the Master Dimmer and Strobe Channel for the whole Fixture.
(Keep Master Dimmer always 100% in each cue you create, and never touch the strobe function)
This will take up DMX Channels 1-26
Then, add 6 Generic RGBW Devices Starting on channel 2, then channel 6, then channel 10, then channel 14, then channel 18, then channel 22. This will overlap the channels technically created with the First DDF using 26 channels, but that's Okay because the DDF would not have any control of those channels anyway.
Use the Dimmer and Strobe Function DMXC Will create within the software to control the dimming and strobing for each fixture individually, without using the actual Fixture's dimming and Strobe Channels (Channel 1 and Channel 26).
I hope this makes sense. If not, I can create this concept and upload a demo project.
In each Cue List, You can change the Fade Factor, and Speed Factor from 0% - 100% - 100%
Assigning a speed factor or fade factor to an Executor only allows for values from 0% - 100% Nothing more.
I am trying to find an efficient way to control the whole scale without creating an input assignment to every cue individually.
Hello. English User here. But I have viewed this thread translated.
In my personal experience, Sometimes there are some small and weird tricks you need to perform when creating the fixture profile to get it to function as the factory intended.
For example, say when the Strobe channel also functions as a devices Main Shutter channel.
I can't promise when I could take a quick look at the project and DDF, hopefully in the next few days, but, if you are able to post a link to the fixtures manufacturer page and manual that shows the channel descriptions, I would be happy to take a look and see If I can't try and make a profile that would fit this devices parameters.
I have had decent success when using the current version of DDF creator to make device profiles from scratch, with sometimes having to go and manually edit the XML.
But if you would like to post the Fixture and the Manual, as well as the current DDF XML you are currently using, I would be interested to see myself why this might be happening.
Is it possible for an executor Fader value to be Higher than 100%?
For instance, in a cue, you can set the "Fade Factor from 0 to 1000%"
Can an executor fader scale greater than 100%?
Yes! I'm really really happy that you were able to get it to work!
Funny enough, I have recently switched to sACN since making the original demonstration (due to a bug in the Art-Net firmware of DMX node I had gotten).
If you couldn't get the ArtNet to work, I was going to recommend trying with sACN, as it seems to use a more direct IP forward.
I am not quite sure how the developers changed the ArtNet Transmission in 3.3.0, but I am no longer sure how it 'Binds' to an IP anymore without using the 'optional' secondary IP Send parameter in DMX Interface Settings.
Perhaps 
LightningBrothers or JPK would know where to point for that updated information 3.3.0?
Either way, I would be interested to see what you do with it once you are able to create even a small demo! If you can render it out, totally share it here
Congratulations 🎉 🎉 🎉
To add additional universes in Pro DMX 2 (Up to 4) Follow these Steps.
1. Add another Art Net Device in DMX Control 3. Change the Settings Circled in Blue.
2. In Pro DMX 2, click 'Universe 2' and click on the 3 dots on channel 1 and enter the same settings as before, but just make sure to select universe 2.
3.Follow the same steps for Univers 3 and 4 respectively.
And it should be as 'Simple' as that!
Let me know if you are able to make this work!
It may take a couple tries to get everything to talk with each other, but this is how I was able to get it to work.
It's amazing your actually almost there. I am going to explain the 'Hidden Feature' Now to make it all work.
I have attached screenshots as detailed as possible:
1. First, Install Virtual Network Adapter As described in this tutorial (Click Link):
How to create virtual network adapter in windows 11 or windows 10
2. Once You Install the adapter, go to Start -> Type Control Panel -> In Control Panel type 'Network' -> Click on 'Network & Sharing Center'
3. In 'Network and Sharing Center' click 'Change Adapter Settings'
4. Find the new virtual network adapter 'Microsoft KM-Test Loopback' (I renamed mine to ArtNetLoop) -> Right Click -> Properties -> Double Click 'Internet Protocol Version (TCP/IPv4)'
5. Change Settings as Follows -> Click OK
6. Open DMX Control 3 (I am using v3.3.0)
Go to Settings -> DMX Interfaces -> Add Device - Artistic License -> Art-Net
[LEAVE ALL SETTINGS DEFAULT ('0')]
Change 'Additional Sent to IP' to the IP Address your Virtual Network Adapter is set to.
7. Open Pro DMX 2 -> Create a New Project AND SAVE AS! -> click Tools -> Options -> ArtNet -> Input -> Make Sure Network Adapter is set as your Virtual Loopback IP Address.
Also Make sure the On/Off Button is Turned ON [GREEN] Click It
8. Now for the Hidden Part. Click the Check Mark at the bottom and you will see this screen.
Make Sure you are in universe 1 (On the Right) -> CLICK THE 3 DOTS AT THE BOTTOM OF THE FIRST FADER
9. In this Window, Copy the Following settings exactly and hit Checkmark. [Only Adjust Setting Circled in Blue]
10. You should now be controlling ProDMX2 Faders from DMXC!
11. Now create your fixtures in ProDMX2 and Build your 3d show!
Wow, thank you for going out of your way to put that concept in a full testing environment.
I really hope that someday a 64 bit environment for DMXC can be possible. The workflow is just so fantastic, and I really support the project so much!
I look forward to keeping you up to date with any High-Scale concepts I can think of myself that may help in an efficient future development of the software and future features.
