keithsw1111 wrote:And now in the 2019 releases.Sent from my iPhone using Tapatalk
I'm new to this since 2019.1, and am now running 2019.2 on Mac, how do you go about importing the .obj?
Click the obj button. Last model type.
Sent from my iPhone using Tapatalk
keithsw1111 wrote:Click the obj button. Last model type.Sent from my iPhone using Tapatalk
Hi Keith,
Thanks for pointing me in the right direction. I had tried that myself as well, after searching and searching, but figured I was still doing something wrong as the only options that come up when I click that button are "Image", "Gridlines", and "Mesh". I've tried each of them however the only one that takes an .obj was mesh - it did seem to import the .obj, however nothing appeared in the preview area. I then played around with sizing and position, and finally got something to appear but only if "Mesh Only" check box was enabled in the properties pane. It seems to fairly accurately show a wireframe of the house in the .obj, however nothing shows up when the 'Mesh Only' checkbox is disabled. I've also tried 'painting' the house in sketch-up with different colours, etc. and reimporting into xLights, with no changes.
Thanks,
You need the texture files etc that were created with the obj file.
Sent from my iPhone using Tapatalk
keithsw1111 wrote:You need the texture files etc that were created with the obj file.Sent from my iPhone using Tapatalk
Ah yes I see, I moved the .obj file to another directory for xlights after sketch created it, I hadn't noticed it created a .mtl at the same time.
What is the scale relationship between the grid units in xLights and the units in Sketchup? When I import an actual dimensioned model out of sketchup, the representation of same in xlights is visually very very small compared to the default 'gridlines' object
Also when importing, the Z and Y axes seems to be translated as well. what was +Z in sketchup becomes +Y in xlights. +Y becomes -Z, and thankfully +X stays +X.
Also, two suggestions would be:
1. zoom in and zoom out (using mouse wheel) currently zooms in xLights based on the centre of the screen(window), in sketchup zoom in/out re-centres based on cursor position.
2. it would also would be nice to be able to change from orbit to pan. in sketchup this is done by changing to the 'hand' tool. or using the control key with a mouse click to present a context menu that allows selection of orbit or pan (among others).
I hope these images will illustrate the axes translation issue:
In SketchUp (typical Blue is Z, green is Y, and X is Red.) . the bottom left corner of the monopoly house is 0,0,0
In xLights (the colours of the axes certainly match, and so do the size/location coordinates), however the imported .obj has been rotated 90 degrees around (away from viewer) the x axis. ie +Z > +Y, +Y > -Z, and +X > +X
Also the Y and X dimensions of the monopoly house in SketchUp were set to 40'. In xLights, I've reduced the grid size to Width=40 and Height=40, and Line Spacing = 1. You'll notice that the axis handles (the cones) are extremely large relative to the house, and the orange cube (origin) is equally large.
Hope that helps some. Let me know if you need anymore info, or if you want to jump on a GTM to see all this in action.
Xlights has no dimensions. It seems to me most of your problems are simple to resolve by just moving the model once imported.
Sent from my iPhone using Tapatalk
keithsw1111 wrote:Xlights has no dimensions. It seems to me most of your problems are simple to resolve by just moving the model once imported.Sent from my iPhone using Tapatalk
I'm not sure I follow your statement that "xLights has no dimensions". xLights seems to be based on a three dimensional space cartesian coordinate system, which means it does have dimensions in X, Y, and Z. Even certain objects have properties labeled as 'Width', and 'Height', which are certainly dimensions.
Regarding your suggestion of 'just moving the model once imported', yes that is a band-aid fix that I had come up with as well, however that isn't a particularly well thought of long term solution to the larger issue.
If we just start willy nilly re-sizing things, just to make it work, then it becomes nearly impossible to place objects using any sort of real world unit of measure. If there is no relationship between the units of measure in sketchup (or any other CAD/CAM 3D modeling software) and the units in xLights, how is one to know, for example, where to place one's mega tree in software, so that it accurately represents the real world. Or are we just to give it a best guess?
Further testing of 2019.3 yields other concerns, perhaps you can shed some light on the design decision around the translated Y and Z axis for us. It seems to be the case that not only 'imported' objects get translated, but all objects placed are rotated 90 degrees around the X axis. I'm sure there is a good use case for this, otherwise why would xLights behave in this manor, but I'm just not seeing it - do please advise. My tiny brain can't fathom why xLights would treat Y as if it were Z and vice-versa. Typically in 3D modeling and CAM software, the XY plane would represent the 'ground', and houses (mega trees, arches, etc.) would be built up in the Z axis on the XY plane. Instead, xLights seems to be treating the XZ plane as 'ground' and all things are being built up on the Y axis.
Also, carrying forward my previous two suggestions, modifying one and adding another couple:
1. zoom in and zoom out (using mouse wheel) currently zooms in xLights based on the centre of the screen(window), in sketchup zoom in/out re-centres based on cursor position.
2. it would also would be nice to be able to change from orbit to pan. in sketchup this is done by changing to the 'hand' tool, using the control key with a mouse click, or right clicking to present a context menu that allows selection of orbit or pan (among others).
3. the size of the axis handles, and origin should be fixed regardless of the zoom extent, to avoid those controls from blocking a properly sized object. See photo attached of a reasonable sized house that is 40'x40' square - once you zoom in enough to see the house, the axes controls are inappropriately sized.
4. add something similar to the 'standard views' of sketchup with Top (Z), Bottom (Z), Front (Y), Back (Y), Left (X), Right (X), Iso.
Here is the photo for my #4 above
Thanks!
The xLights numbers for model position and size dont mean anything at all. They are not mm or inches or any other dimension.
Your obj file may well have some dimensions but everyone's model is potentially different. So xlights just scales the obj file to the size of the bounding box you import. If you want 1.0 = 1 foot then size your obj accordingly.
As I said xLights doesn't and shouldn't care.
X/Y is deeply entrenched in the software as the dimensions from the 2D view ... so Z has to be depth. That is the way things are.
As for the remainder of your suggestions.
Inherent in these comments is the assumption that because software x/y/z works that way it is how xlights must do it. At the end of the day there are lots of ways to do 3d navigation and we could almost certainly find other software that does it different ways. Some things will change over time as Gil feels they need to ... other things are the way they are and you always have the choice of moving to another sequencer that does 3d more to your liking.
That being said there are some valid observations here and over time i expect some will get addressed ... just not necessarily aligning to your 3d software of choice.
keithsw1111 wrote:The xLights numbers for model position and size dont mean anything at all. They are not mm or inches or any other dimension.Your obj file may well have some dimensions but everyone's model is potentially different. So xlights just scales the obj file to the size of the bounding box you import. If you want 1.0 = 1 foot then size your obj accordingly.
As I said xLights doesn't and shouldn't care.
X/Y is deeply entrenched in the software as the dimensions from the 2D view ... so Z has to be depth. That is the way things are.
As for the remainder of your suggestions.
Inherent in these comments is the assumption that because software x/y/z works that way it is how xlights must do it. At the end of the day there are lots of ways to do 3d navigation and we could almost certainly find other software that does it different ways. Some things will change over time as Gil feels they need to ... other things are the way they are and you always have the choice of moving to another sequencer that does 3d more to your liking.
That being said there are some valid observations here and over time i expect some will get addressed ... just not necessarily aligning to your 3d software of choice.
I think when you say 'dimension' you mean 'units'. But that's ok, I get you now.
I did size my obj accordingly, and my issue #3 still stands - perhaps more so because it is accurately sized to real world.
You are correct, my assumption is that new software entrants would carefully consider the design patterns of other more established players and industry leaders; design patterns that are a) intuitive, and b) tried, tested and true. Rather than arrogantly thinking that re-inventing the wheel is a good thing. That's not to say that doing it differently shouldn't be explored, however it ought to be based on a pretty compelling reason. The reason of "it is this way because it's always been this way", isn't particularly compelling to me as a seasoned Enterprise and Solutions Architect. Given that with v2019.x you undertake to 'rebuild' legacy dimensions of objects into a 3 dimensional coordinates - this seems like it would be a perfect time to correct prior decisions to use the XZ plane as the 'ground' and move to a more intuitive, industry standard of an XY ground.
You are also correct that I can move to other software that does things better, and I am currently in the evaluation phase of different software - so that may be the end result. TBD. However one of the most important things I look at when evaluating software (either open source, or commercial), is how the vendor (or development team) is able to take constructive feedback from users in an effort to improve the product. I look for software teams that strive for excellence, continually work to improving the product and thoughtfully and cordially listen and respond to User concerns. I find little room for arrogance, attitude, and ego.
With that all said, I do think that you and your team have certainly done a good job at xLights, and I hope that you continue to take my (any others) feedback constructively, with an eye to excellence. Should I conclude my evaluation and determine that xLights is the way to go, you can count on my support.
Keep up the good work!




