[Plugin] VisMap - Layer/Scene Visibility Map
-
Martin,
I realize that the existing Layers Tool can be used to create scenes, but your tool is MUCH simpler to use. Why? Because I can look at all of the scenes at once. With the Layers Tool I have to open the scene, then go through and pick the layers I want, then save the scene. With your tool I can do several, if not all, layers at once. Much better.
Why do I press for this tool? We have a satellite processing facility and a launch facility at Vandenberg AFB, CA. I have built models of both of these facilities. When a new user comes I need to model their process through the facility. This requires the basic model, then certain layers of both their equipment and ours turned on/off for each stage of the process. Each stage of the process is a new scene with their and our equipment at different locations and attitudes (open/closed, up/down, etc.). I model their equipment and, for the pieces that will appear at different places in each scene, I make a new location-sensitive instance. Once all of this is done I can then, with your tool, turn on the applicable location-sensitive pieces of equipment at the appropriate location in the appropriate scene.
But to be useful it is (absolutely essential) to have the layers sorted.
It would also help a lot if:
-
Somehow the numbers representing the scenes need to stay fixed at the top when scrolling down. I can remember the scene number(s) I'm changing or, more likely, I can refer to a print out of the scene numbers/names.
-
The VisMap dialog stayed on top.
VisMap still does not capture the model data for a very large model/scene combination. If I copy the entire model (60 or 70 layers) and put it into a new instance of SU, VisMap can then read the data. But, of course, I've lost all the scenes.
Thank you very much for working on this Plugin.
-
-
@bob james said:
...
I model their equipment and, for the pieces that will appear at different places in each scene, I make a new location-sensitive instance. Once all of this is done I can then, with your tool, turn on the applicable location-sensitive pieces of equipment at the appropriate location in the appropriate scene. ...
That's very interesting. Am I right in thinking each layer configuration is saved in a client specific file? As VisMap is in a webdialog what would you think about saving configurations as JavaScript arrays, so that you need not open and close files and quickly move through the configurations, and, with further devices, compare selected parts/costs/status and suchlike in different configurations? If the Sketchup Viewer had plugin facilities, clients could access your configurations via the Net as a normal part of their business operation.
If the Sketchup Viewer had plugin facilities ... now that's definitely another topic ... sorry!
Chris
-
thanks mr. martin
-
@chrisglasier said:
Am I right in thinking each layer configuration is saved in a client specific file?
ChrisNot quite. Each scene in the process has its own layer configuration. The process (movement of their satellite through the facility) may take 10 or 15 scenes. This client-specific SU file is then saved. In most cases each scene is rendered using IDXRenditioner, the result saved, each picture touched up in Photoshop (if necessary), and the result put into a PowerPoint presentation. Sometimes the entire set of scenes is made into an SU animation.
During the development process I also use new version of Layer Manager to save the layer configurations (great plugin - use it and its associated Layer Tools all the time).
-
@chrisglasier said:
If the Sketchup Viewer had plugin facilities
<sketchup src='my_slick_model.skp'> If you had a better browser, you'd see My Slick Model here </sketchup>Right?
-
Like so?
Or should Layer0 always be at the top?
-
Super!!
Can I download this version? I'm just beginning a new project.
@martinrinehart said:
Or should Layer0 always be at the top?
My vote would be for Layer(0) to be at the top.
-
Like this:
-
I like Jim's layout better, but would still prefer Layer(0) at the beginning (but that's not a show stopper).
-
@bob james said:
I like Jim's layout better, but would still prefer Layer(0) at the beginning (but that's not a show stopper).
Forgive me if I have missed something but isn't layer0 always going to have to be the active layer and should not appear at all? If not it seems there will be lots of complications with reassignment/hiding.
Both seem to ignore the scene name problem!
Chris
-
'Layer0' is most often used as the current layer - you then put 'assembled' groups/components/etc on other layers to control visibility. However, you can set any layer as the 'active' one BUT it's not recommended without a good reason... An example would be you are puttings dimensions on the model and want them all to be on layer 'DIMS' - make that the active layer, add the dimensions [you can then switch them on and off separated from everything else] BUT remember to go back to active=Layer0 afterwards otherwise chaos will ensue...
-
@tig said:
'Layer0' is most often used as the current layer - you then put 'assembled' groups/components/etc on other layers to control visibility. However, you can set any layer as the 'active' one BUT it's not recommended without a good reason...
Ah yes I should have written ... "always going to have to be the active layer" when using VisMap
-
@chrisglasier said:
"always going to have to be the active layer" when using VisMap
Actually, Chris, I'd turn Layer0 off, if I could. In my tutorial I teach the common gospel re Layer0, but I don't believe it. I consider a model incomplete until Layer0 is empty.
-
@martinrinehart said:
@chrisglasier said:
"always going to have to be the active layer" when using VisMap
Actually, Chris, I'd turn Layer0 off, if I could. In my tutorial I teach the common gospel re Layer0, but I don't believe it. I consider a model incomplete until Layer0 is empty.
Yes I agree, empty, active and not an option in VisMap! Otherwise if you try and hide another layer that is active you will get an alert "You cannot hide an active layer" or something like that.
-
Sorted layer names.
These two are not in the .zip yet. Please rename "vismap.txt" to "vismap.js", try them in .../Plugins/Vismap and let me know.
Thanks.
-
@martinrinehart said:
Sorted layer names.
These two are not in the .zip yet. Please rename "vismap.txt" to "vismap.js", try them in .../Plugins/Vismap and let me know.
Thanks.
Just in case you want feedback here are two screenshots. Layer0 is empty, active and visible in all scenes. Some other layers also seem incorrectly checked - awkward to crosscheck though.
Perhaps the VIs strings did not get sorted (see top row, which was presumably previously level0).
And you really ought to address the awkwardness of the scene names and disappearing headers and unnecessary buttons (in my opinion,of course!).
Chris
-
Alphabetizing works great.
It still has a problem with pre-existing models with many layers and many scenes. I tried a new approach: I deleted all but one scene and re-saved the model with a different name. VisMap still would not load the layer names. (see attached)
Another request: Since you can have multiple models open at the same time, wouldn't it be a good idea to have the file name in the VisMap dialog box title?
![After clicking on "Get Data from Model"](/uploads/imported_attachments/M321_Screenshot2009-09-25at4.54.52PM.JPG "After clicking on "Get Data from Model"")
-
-
@chrisglasier said:
Perhaps the VIs strings did not get sorted (see top row, which was presumably previously level0).
Can you send me a model? Post here or MartinRinehart at gmail dot com.
@chrisglasier said:
And you really ought to address the awkwardness of the scene names and disappearing headers and unnecessary buttons (in my opinion,of course!).
Ground-up rebuild, but not anytime soon. Scene names should be in a separate window you can move/size to suit. Title should be in a frame you can fold away. Scene #s should be frozen. You should have Ctrl/+, Ctrl/- to adjust size....
-
Advertisement