While using this circle, the default wiring/lights will not work for my spinner prop, as it has individual arms and space on outer most part is about 8 inches between holes, I need to wire up and down each arm. This is a 3D spinner prop. Is there a way to modify the wiring of the prop I created with the circle, without creating a custom model? I know there will be some rework, but trying to stay away from custom model if possible.
First, your vids are always informative and entertaining, thanks Ron!! Alas, this nifty trick for creating 'native' spinners does not work, as what xLights creates does not even come close to matching the actual node layout and wiring. In order to deal with 3 or 4 inch spaced bullet nodes, they are wired up one spoke and down the next. And the around the edges they go to every other node then double back. Whereas xLights generates a bunch of concentric circles. While it would seem more logical to wire them that way, on the outermost rings (except for THE outermost) the holes are too far apart, and that would require a lot of splicing to extend lengths between the pixels. And I doubt most people wanna pull the pixels out and re-push them differently. Just pull up the wiring view on your native model and then on a custom model for a typical spinner from a coro vendor, and you will see what I mean. And I tried to edit the node layout or remap them, but no dice. Cool concept tho!
Have you considered exporting as a custom model and wiring any way you choose? That would be the fastest way to have complete control of the model's wiring.
@@xTremeSequences Tried that. But that seems to defeat your stated advantages of creating it as a native model to start with. Might as well create as a custom model to begin with. In fact, the custom one I had already created is more symmetrical than the one that started out native and got exported/re-imported-as-custom. Plus I had to go thru the re-imported one and fix all the node numbers to match the real world wiring. All I accomplished was to waste some time. But I still applaud your thinking-outside-the-box!
@@Doctor_Wizard This isn't really thinking ouside the box. It's just something new added to xlights to allow for more creative native spinner models and the dreaded center hole that I have hated for years. LOL.
Great work! I don't follow you exactly when you refer to the layers of the spinner, is a layer a circle that starts at the center and goes out x numbers of times?
This explains lots. I have bigda style fan arches but I built them using the native arch model. Many of the sequences I use have spinarchy or EFL fan models and even after confirming the submodels node order is the same, the effects never look right without modifying the render style. Ron in this case would you adjust the render style or would you build a custom xmodel in place of the native?
That's a great question. I think the answer lays in what requires the most work when mapping sequences. If most of the sequences require altering duo the the native model behaving in such a manner than maybe the custom model is the best solution.
@@xTremeSequences Well it was a good idea. I exported the native model as a custom xmodel, then imported it as a new custom model prop. I then tried mapping a sequence to that model and it still has the render issues. Maybe I missed something in the submodels but I'm pretty sure they are the same order / pattern as the EFL fan (which is what's in the original sequence). Ah the mysterious joys of xLights! :)
In this case I would have created a custom model. Converting a native spinner to a custom spinner is not suggested. The only value I have seen from converting a native model to custom is on matrices for wiring issues that need more control due to some strange wiring ideas/mistakes.
Who knew I could right-click and divide up a submodel. Wow!
How about that, right?
While using this circle, the default wiring/lights will not work for my spinner prop, as it has individual arms and space on outer most part is about 8 inches between holes, I need to wire up and down each arm. This is a 3D spinner prop. Is there a way to modify the wiring of the prop I created with the circle, without creating a custom model? I know there will be some rework, but trying to stay away from custom model if possible.
First, your vids are always informative and entertaining, thanks Ron!!
Alas, this nifty trick for creating 'native' spinners does not work, as what xLights creates does not even come close to matching the actual node layout and wiring. In order to deal with 3 or 4 inch spaced bullet nodes, they are wired up one spoke and down the next. And the around the edges they go to every other node then double back. Whereas xLights generates a bunch of concentric circles. While it would seem more logical to wire them that way, on the outermost rings (except for THE outermost) the holes are too far apart, and that would require a lot of splicing to extend lengths between the pixels. And I doubt most people wanna pull the pixels out and re-push them differently. Just pull up the wiring view on your native model and then on a custom model for a typical spinner from a coro vendor, and you will see what I mean. And I tried to edit the node layout or remap them, but no dice.
Cool concept tho!
Have you considered exporting as a custom model and wiring any way you choose? That would be the fastest way to have complete control of the model's wiring.
@@xTremeSequences Tried that. But that seems to defeat your stated advantages of creating it as a native model to start with. Might as well create as a custom model to begin with. In fact, the custom one I had already created is more symmetrical than the one that started out native and got exported/re-imported-as-custom. Plus I had to go thru the re-imported one and fix all the node numbers to match the real world wiring. All I accomplished was to waste some time.
But I still applaud your thinking-outside-the-box!
@@Doctor_Wizard This isn't really thinking ouside the box. It's just something new added to xlights to allow for more creative native spinner models and the dreaded center hole that I have hated for years. LOL.
Great work! I don't follow you exactly when you refer to the layers of the spinner, is a layer a circle that starts at the center and goes out x numbers of times?
This explains lots. I have bigda style fan arches but I built them using the native arch model. Many of the sequences I use have spinarchy or EFL fan models and even after confirming the submodels node order is the same, the effects never look right without modifying the render style. Ron in this case would you adjust the render style or would you build a custom xmodel in place of the native?
That's a great question. I think the answer lays in what requires the most work when mapping sequences. If most of the sequences require altering duo the the native model behaving in such a manner than maybe the custom model is the best solution.
@@xTremeSequences Well it was a good idea. I exported the native model as a custom xmodel, then imported it as a new custom model prop. I then tried mapping a sequence to that model and it still has the render issues. Maybe I missed something in the submodels but I'm pretty sure they are the same order / pattern as the EFL fan (which is what's in the original sequence). Ah the mysterious joys of xLights! :)
In this case I would have created a custom model. Converting a native spinner to a custom spinner is not suggested. The only value I have seen from converting a native model to custom is on matrices for wiring issues that need more control due to some strange wiring ideas/mistakes.
Are there any good Discord Servers for this hobby?