xx Next release , xlights will have a props directory

[DMJPixel]

Where would you like us to post new models we create?  I'm sure one specific place would be easier than several different threads/forums/Facebook.

I really don't like sharing models.  I like to create my own.  The first time I used a shared model it had a mistake that caused me to cut and splice a pixel up on the roof and wasted my time.

I can see both sides here - I do like shared models as they have helped me to get snowflakes setup much quicker than I could have on my own. 

To Gil's point - I had put up my new snowflakes and the next night my wife told me I had a "light" out.  I went out and sure enough one pixel not working at all - I thought I would just replace it once I brought props back in.  The next day I added a candy cane and the bad pixel moved about 12 pixels!  Wait a minute...went and looked in the model and a someone had mistyped a node number (28 instead of 38).  I fixed that and pixel is not dead anymore.  Were it not for me putting out that other prop I would have cut out 2 pixels and then had the exact same problem.  So I would say shared is good but buyer beware...

[Gilrock]

I have no problem if someone wants to setup a way to share models.  We already share stuff on Facebook so that's where I go when I look.  But it appeared someone was wanting ME to determine how we centralize this so I'm just saying I'm not your guy to do that because I'm not motivated since it's not a key feature for me.  I'm not saying its a bad thing for the rest of you to do I just don't want to champion it.

[jnealand]

I think of a MODEL as something like a tree.  In reality I have 23 tree MODELS.  Each of them are PROPS that have unique properties and channel assignments.  So there is a difference.

[sean]

Sean, please call them MODELS.  All references in the application and the documentation is for MODELS.

I think i will call them custom_models.
This requests tarted with james from boscoyo studios. the directory structure is probabvly going to be something like

../custom_models/boscoyo/chromastar1.xmodel
../custom_models/boscoyo/chromamesh1.xmodel
../custom_models/holidaycoro/singing_tree1.xmodel

or maybe xls files with background images?

I could use peoples help in mining all the current places these files have been stored.
problems i see is how do you know what purchased prop the xmodel applies to?
what about peoples home grown props?

[Gilrock]

Yes another issue is the exact same display element can be modeled more than one way.  I know on FB another user and I both modeled the Matt Johnson 34 pixel snowflake but we used different sub-models and I'm pretty sure mine is rotated 180 degrees for where my first pixel starts.

[flyinverted]

The custom models will get the shapes correct. It will be up to the users to plug in the pixels in that exact order, or renumber them to match how they want to plug them in.

Sent from my SAMSUNG-SM-N910A using Tapatalk

[keithsw1111]

Sean, please call them MODELS.  All references in the application and the documentation is for MODELS.

I think i will call them custom_models.
This requests tarted with james from boscoyo studios. the directory structure is probabvly going to be something like

../custom_models/boscoyo/chromastar1.xmodel
../custom_models/boscoyo/chromamesh1.xmodel
../custom_models/holidaycoro/singing_tree1.xmodel

or maybe xls files with background images?

I could use peoples help in mining all the current places these files have been stored.
problems i see is how do you know what purchased prop the xmodel applies to?
what about peoples home grown props?

I don't want this sean. I want James to set us up something we can call on his webpage and pull them down for the user. Yes it will require an Internet link to work but it means he can update it whenever he wants and we don't need to fuss. I just want one xml file from him defining where we can find the inventory online.

[flyinverted]

This is not much different than the included song timing marks that come with every install. Just a helper to get started. This application should be standalone with no Internet connection needed IMHO.

There are MANY vendors for models, not just James. Granted the profits may increase by us including models, this is not to help the vendors, but to help the users.

[sean]

Keith; i would like vendors to provide xml files (boscoyo,holidaycoro) .etc. but they have not done so to daye. what about multiple models for the same prop? Some users create models and sub models. Some custom models are 20x30, others 40x40. Resolution. When vendors start providing *.xmodel files for what they sell we should include links. Providing them with the install just gives one place to look. Wr have user submitted xmodel and xls files in at least 3-4 places now.
I would rather be the recipient of files and i just need to package them.


Sent from my iPhone using Tapatalk

[keithsw1111]

The problem sean is you get a hundred different versions of the same model. Who decides what the right one is and if you push multiple how does the user decide which to use. I prefer the vendors own this accountability.