Posts made by kirill2008

I think it is possible to use "face.classify_point(pt)" method to find/select entities, that "touch" some face.
For intersection I would recommend a method "intersect_line_plane" from Geom class. Face plane can be simply obtained like "face.plane", edge line like "edge.line", then it is possible to get intersection point like "Geom.intersect_line_plane". Finally it might be useful to make sure that intersection point lies inside of a face boundary using "face.classify_point".

I also can confirm that using of components as an external reference to represent some parts of a model stored in another file is a popular way to deal with big complex models. Seems to work fine and fairly easy to understand a logic of how it all works (i.e. fairly easy to explain to other team members if needed).
Obviously such approach helps a lot in case if an "assembly model" has some identical parts (for example identical building blocks on some site). After editing of a reference in a separate file update takes effect on all its instances inside a "host" model of course.

@medeek said:

I'm also curious as to how others have accomplished this with their own plugins.

Hello Nathaniel,
SketchUp Ruby API has a LanguageHandler class: http://ruby.sketchup.com/LanguageHandler.html
I think using of this class is a sort of an official way to implement localization to other languages. I've tried this way and looks like it works fine. However some extension developers prefer to use their own implementations of localization for some reasons. So it is not a some sort of a requirement, I think.

According to my observations there is still much work to be done to claim that "interoperability" between different BIM software is something real (not just a good intention). For now it seems like even big players in the field haven't yet figured out how to provide a way to interact (fully and safely) with objects transferred using IFC format between BIM software of each other.
However progress in this direction never stops, for example I've seen recently a new interesting innovation, which allows to insert a reference to an IFC file into a project, so it is possible to collaborate with engineers, detect clashes etc:

https://youtu.be/vUNxCW3weH4

Changes in a referenced IFC file can be observed in a project after refreshing (similar to a model inserted into LayOut) as far as I understood.

BTW big players may deliberately restrict interoperability between products of each other to protect their market position maybe (just an assumption though). Maybe it is the reason why progress in this direction is not that fast as we all would like.
I'm not sure how much time it may take to make possible to start working with some IFC file using one software package, then safely continue working with that same file using another software, then save to cloud and proceed editing using third software right in a browser window

On the other hand I have to admit that different software packages perceive even simple common objects like walls, slabs, openings sometime very differently (provide different ways to create/interact/edit) and such difference obviously affects how information about even basic elements is stored. Standardized data storing format even if it is excessive like IFC still may impose restrictions on certain functionality provided by certain software. So sometimes it feels like even smooth and lossless transfer between different BIM software products is something unachievable by definition not to mention real interoperability.

Hello All,
LSS Toolbar is an outdated plugin (as TIG correctly stated) and last version of SketchUp, which LSS Toolbar is compatible with is unfortunately SketchUp 2013.
The point is that I'm not able to continue developing of freeware projects like LSS Toolbar at the moment, so I highly recommend to look for some other alternatives to LSS Toolbar, which have similar functionality.

Hello Ray,
I decided to copy my answer in this thread as well. Here is LSS Arch Lite thread where I posted basically the same reply.
I agree about problems with UI in LSS Zone (lack of direction lock using Shift key while drawing and editing for example etc). I added recently a "Zone" tool to a full version of LSS Arch. It basically uses the same logic for zone object as free LSS Zone extension, but utilizes UI logic of LSS Arch (so zone tool behaves basically the same way as other LSS Arch tools, direction lock is available etc). I tested how zone tool works in LSS Arch during a project, which I'm currently involved in at work, and I'm mostly happy with results (I revealed a couple of minor problems in zone tool inside LSS Arch though so fixing is in progress right now and nearest minor update of LSS Arch will contain those fixes).
So now I have an idea to publish new commercial LSS Zone Pro extension, which would utilize UI logic of LSS Arch and drop support of a free LSS Zone extension, because I'm afraid I have no ability to continue developing of freeware projects (at least at the moment). Such new extension can be used in combination with LSS Arch Lite (such combination would provide ability to trace quickly closed spaces bounded by walls). I hope this plan will come true someday.

Sincerely,
Kirill

Hello Ray,
I agree about problems with UI in LSS Zone (lack of direction lock using Shift key while drawing and editing for example etc). I added recently a "Zone" tool to a full version of LSS Arch. It basically uses the same logic for zone object as free LSS Zone extension, but utilizes UI logic of LSS Arch (so zone tool behaves basically the same way as other LSS Arch tools, direction lock is available etc). I tested how zone tool works in LSS Arch during a project, which I'm currently involved in at work, and I'm mostly happy with results (I revealed a couple of minor problems in zone tool inside LSS Arch though so fixing is in progress right now and nearest minor update of LSS Arch will contain those fixes).
So now I have an idea to publish new commercial LSS Zone Pro extension, which would utilize UI logic of LSS Arch and drop support of a free LSS Zone extension, because I'm afraid I have no ability to continue developing of freeware projects (at least at the moment). Such new extension can be used in combination with LSS Arch Lite (such combination would provide ability to trace quickly closed spaces bounded by walls). I hope this plan will come true someday.

Sincerely,
Kirill

Hello Ray,

@facer said:

A. Can LSS Arch Lite be used with Skalp as for LSS Arch?

Yes ability to explode reveals of openings (which allows Skalp to detect empty openings inside walls) was also added to version 1.0.5 of LSS Arch Lite.

@facer said:

B. Could IFC naming be added?

I didn't think that this feature could be required in lite version. In fact I wasn't sure if users of full version will use it extensively. Note that IFC naming implemented in full version just applies corresponding names to selected objects, but it doesn't store implicit geometry of objects, so other software which is able to read IFC recognizes objects as walls, slabs, columns, beams etc, but unfortunately it will not allow to interact with imported objects the same way as if they were initially created in it.
The point is that storing of implicit geometry (for example coordinates of wall's or beam's axis line etc) requires a lot more coding (most likely it is necessary to use some third party IFC library for that purpose). And it requires some more experience in IFC specification itself, than I currently have. So I'm not sure if I'll be able to implement such functionality soon.

@unearthed said:

DOD3R - have you had a look at this http://sketchucation.com/forums/viewtopic.php?t=21077 - I haven't played with it yet but the images and discussion look very promising.

Yes I've seen this plugin. I think it might evolve into something really powerful. I didn't test it personally though.

Hello,

@dod3r said:

Hello Krill,
Can your plug in do this somehow ?

Unfortunately plug-in can not estimate daylight in Lux. It can only measure time of direct sunlight and sky view factor.

@dod3r said:

Any plans or info about any of your plug-ins.

I planned to update LSS Toolbar to make it compatible with Extension Warehouse requirements, but due to significant load at my official work I'm not sure when I'll finally complete this task.

@mitcorb said:

I like your latest innovation.

@unknownuser said:

Seems very useful for architecture!

Thank you guys!
I would like to mention that I personally use this extension heavily for my own practical purposes (architectural design) so chances are it may be useful for other architects as well. At least I hope so

Small announcement: automatic contour tracing implementation is in progress now. Here is a preview of room's contour tracing process:

http://youtu.be/_61w3bsJmf4

@srx said:

Besides automatic finding of areas, just one more thing - binding area geometry to structure. So if the structure was changed, areas are also changed

Sure why not
More seriously, I think that if automatic zone creation will be finally implemented somehow, then implementation of automatic refreshing of zones will be more or less easy to carry out.

@srx said:

This is one small step for a man, but the huge lip for SU BIM! Thank you Kiril.

Thank you!
Maybe I would rather say quite the opposite I mean, LSS Zone is not that big thing on the scale of Sketchupverse. This extension is a personal significant achievement (maybe), but it utilizes only one certain set of Sketchup's endless range of possibilities.
Dealing with SU API may give some insights into Sketchup's thrilling nature. But the amount of methods is not the point, the point is the core ideology. Something done right in it

@mitcorb said:

I just remembered about Voronoi cells. Maybe this has some application in defining/seeking areas? But I don't know, didn't look for how any Voronoi operation would treat a region with a hole in it.

The only solution I can imagine for now is to ask a user to define somehow what to treat as a hole. Still have no clear idea how to do the rest logic though...

@mitcorb said:

All you have to solve is how to differentiate between the entire floor plate component or group and that of the room.

Well that sounds challenging

But actually my dream is to solve even more challenging task. The point is that tracing zones' contours is not that time consuming after all in contrast with tracing of openings. In addition to that, there is no clear way in current version to generate a zone of a room with sloped walls and/or ceiling (for now it is only possible to edit zone's elements manually and recalculate zone's quantitative attributes). So the question, that hunts me, is how to differentiate between room's internal space and an entire space outside a room. Besides it would be nice to be able to "fill" automatically an internal space of any possible complex topology (sloped or curved walls, floor, ceiling). Of course it will be necessary to detect and take in account somehow holes (openings) in bounding surfaces as well.
I'm afraid it might take a while to implement such logic, but I don't say it's impossible as a matter of principle

Thanks to all for kind words!

@takesh h said:

"Not sure about the practical purposes of this graph?"
I thought that that was a question, to which you'll give us an ingenious use of the graph later in the video, but it was a statement!

That's right, this graph is only for aesthetic pleasure for now . There is no any practical utilization implemented for it in current version...

@takesh h said:

kirill2008, I use your LSS Chrono all the time.

@takesh h said:

The only issue I have with it so far is the way the plugin understands the floor area of rooms by tracing point by point. It's much easier if we can simply select the floor plane to designate the floor of rooms, don't you think?

The point is that the ability to pick a floor face is actually already present in the current version. This feature wasn't demonstrated in a video (as well as some other interesting features).

I would like also to inform everyone about some issues, which were found recently almost immediately after publication:

• error raises in case if creating zone of a zero height

• grouping of string fields just adds new strings without any separator (see attachment)

• 'List Template' dialog sometimes fail to refresh results of grouping/sorting properly
  

The mentioned issues will be fixed in the first minor update, which is scheduled in three nearest weeks.

@rich o brien said:

@kirill

Great plugin.

Thanks!

I won't be original, just want to say: it is a great plugin! Many thanks for it!

Small Announcement (29-Jan-2017)
Note that currently there are no plans to continue development of a free version of LSS Zone extension so it is recommended look for some other alternatives to this extension with a similar functionality.

ver. 1.2.1 beta

Brief
'LSS Zone' is an extension for Sketchup, which allows to create, store and manage information about rooms.

Features

• create geometric data carrier (so-called 'zone'), which stores identity, quantitative and descriptive information about a room

• reshape and/or re-adjust properties of created 'zone' interactively any time later

• manage entered information in a batch manner using 'Properties' dialog

• create and attach labels

• generate reports

Installation
Unzip archive contents to SketchUp 'Plugins' folder.

Basic Usage Steps
It is just a recommended workflow for entering and managing information about rooms in a SketchUp model using 'LSS Zone' extension:

• create some zones using main tool dialog

• copy geometrically identical zones using native SketchUp tools

• adjust identity attributes of copied zones

• attach labels

• generate reports

It is necessary to have more or less detailed model of a building before using 'LSS Zone'.

OS Support
WinXP, Win7

SketchUp Support
The extension was tested on SketchUp 2013.

http://youtu.be/LYsEQHlpKio

Extension's web-page.

Ver. 1.0.0 Known Issues

• error raises in case if creating zone of a zero height

• grouping of string fields just adds new strings without any separator (see attachment)

• 'List Template' dialog sometimes fail to refresh results of grouping/sorting properly

Version 1.1 Demo

http://youtu.be/c0t2zomTo4M

New Features

• 'Layers Toolbar' added

• 'Filter Zones' dialog added

• handling of three zone types added (room, box, flat)

• icon pack for backward compatibility with previous versions of Sketchup added
  Fixes

• 'List Template' dialog updates results after 'Query string' changes as expected

• report generator display properly grouped string values in a zones' list now

• proper handling of a zero height of a zone implemented

• picking a floor face in a model with multiple identical component instances works well now

Version 1.1.1
New Features

• floor, ceiling and walls cumulative area added to 'Properties' dialog

• suppressing units in an active model now affects zone labels, list and properties representation
  Fixes

• hang after applying new properties to a set of transformed zones removed

• an error fixed in 'Attach Labels' dialog if a label has a length value measured in feet and inches (appeared in a model with feet and inches)

Version 1.2.0

http://youtu.be/OGa_DDdBvpI

New Features

• automatic zone's contour tracing feature added

• 'Settings' dialog added (it contains settings only for automatic tracing for now)

• ability to list nested elements of zone group(s) added to zone's list generator

• suppressing of area units now affects 'LSS Zone' tool dialog as well

Fixes

• 'List Template' dialog restores caret position properly after refreshing of query results

• 'Floors count' property removed from 'LSS Zone' dialog, when 'room' zone type is active at an initial launch of a dialog (it is visible now only for 'box' zone type as intended)

• SU crash after deleting a nodal point while 'LSS Zone' tool is active is fixed

• custom attributes remain attached after zone's contour editing using 'LSS Zone' tool

Version 1.2.1
New Features

• ability to switch all dialogs to a smaller font size added
• layout of all web-dialogs is tableless now
• it is possible to fold/unfold groups of settings inside dialogs
• automatic adjustment of dialog's height added
• 'Trace Contour' settings added to 'Properties' dialog (it is possible to set contour tracing options individually for selected zone using 'Properties' dialog, options inside 'Settings' dialog affect new zone only)
• adjustment of an initial position of zone's label added
• persistence of zone's label position added (it is possible to move label manually after attaching and label will stay at the same position after rebuilding of a zone)
• eye-droppers of 'LSS Zone' main tool dialog now pick visible material of a face (tool checks if front surface or back surface of a face is under cursor and returns face.material or face.back_material depended on check result)
• 'LSS Zone' extension is made compatible with SketchUp 2014

Fixes

• pressing of an 'eye-dropper' button of 'Zone Tool' dialog now unpresses other 'eye-dropper' buttons in case if they were pressed
• label template now processes well all characters
• contour tracing now traces contours made of instances of the same component definition/group
• deleting of an attribute dictionary in 'Properties' dialog now handles the situation when there are not only zone objects in current selection set

First of all I have to agree that the plugin is poorly documented, far from intuitive and obsolete after all... I just have to say that initially my intentions were purely good. I wanted to make a tool that may help to model something more complicated than just a basic geometry. It was not intended to make anyone mad or frustrated. Vojo, please accept my apologies for having failed to meet expectations.

@vojo said:

I.e. since power not documented, a user may try 1.0 thinking he gets a 1:1 movement (or at least see that the movement is some linear relationship between the control points...

Speaking specifically about the term "power" I must say I really was not aware about the fact it might be misinterpreted such a way. "Power" means literally "power" here in a mathematical sense (not a linear coefficient or a factor). Actually I gave some more or less explicit explanations here in this thread about how it all works earlier (about three years ago):

@kirill2008 said:

The second method calculates offset vectors lengths of each vertex according to distances from it to all control points. The degree of influence of each control c-point depends on <1/(distance^power)>. Power is an adjustable value.

You may check the original comment here: http://sketchucation.com/forums/viewtopic.php?f=323&t=22709&start=60#p218438

In other words algorithm utilizes a type of deterministic method for multivariate interpolation with a known scattered set of points which is known as "inverse distance weighting" (IDW): http://en.wikipedia.org/wiki/Inverse_distance_weighting
Plugin interpolates offset value (support of rotation and scale transformations were also added later).

Anyway I highly recommend to stop discussion at this point, because discussion of an obsolete plugin is a kind of pointless to my mind.
Everyone else who was confused please also accept my apologies for not informing about the fact that this plugin has become obsolete at a time.

@vojo said:

pwr= 1/3 might get somebody a 1:1 ration).

Not sure I got you right, but actually ruby interprets the above code sequence such a way that "pwr=1/3" is literally the same as "pwr=0".
You may try that at ruby console by yourself.

In case if you need to enter somewhere a fractional value you should use floating point values.

And I must say that actually all plugins I made provide all 'advertised' functions. I never claim any feature unless it actually present (I have no idea why should I do it).