I have two SW assemblies. One is a pack and go of the other with some minor changes done to it. When importing the second one into the first one's scene; even though I have "From Previous Import" checked, it is still coming in at a different scale. Why can't we have absolute units in KeyShot?
I can't reproduce that. Make sure that you are on the latest version. Also if you can share the files with us, then we can take a look.
Ok, I'm running some tests with simpler assemblies and I can't seem to recreate the issue we were having the other day. What I do notice is that as you're importing parts or variations of the assembly; if they're model envelope sizes are different, they still come in at different scales even when you have "from Previous" selected. You must go to the scale boxes and match the scales of the objects. Why don't new imports come in at the same scales? Why are there now scale boxes and size box dialouges in the Scene tab? I'm certain I don't understand why Keyshot does not consider the original assemblies and part's xyz origins when importing either. It always seems to be placing the model according to the center of it's bounding box and not the origin of the model or assembly. It would make life sooo much easier when working on iterations of assemblies to be able to import parts consistently to the same places without having to constantly rescale and move them within Keyshot.
I've reopened one of the bib files I've been testing and now, though all the objects are still the same size relative to each other, the scale numbers showing up in the Scene tab are all over the place for the different objects in the scene. Please see the attached bip to see what I mean.
Those scale values look whacky. Can you share the SW model?
If you turn off "center geometry" and "snap to ground" upon import, parts will come in relative to their original position in the CAD file.
Parts will maintain the scale when imported separately and have "from previous" checked. It may help to check this by default.
Thanks for looking at that Thomas. I'm finding Keyshot to be behaving very erratically. Today I've been starting a new bip file and importing some of the same parts. They are behaving like you have described they should. While they do import to where they should be respective to their origins, the Translation values for each import are all different and appear to be based on their model envelope centers. This makes moving them relative to the assemblies difficult. All imports with no snap to ground and center options chosen should have all zeros showing in the positions and rotations tabs, but they have translation values as if the part;s origins were centered on their model envelopes. Also, on reopening the bip file the objects scale values change (this time in unison anyway).
A seemingly unrelated issue I'm having is that Keyshot really bogs down if I'm opening new files. By the time I've opened the fourth file in succession (not in separate sessions) Keyshot becomes unusable and must be killed.
We are working on an update that will address the scale issue. I have not heard of the open issue before, but we will investigate and see if we can reproduce it.
-- Henrik
We had the discussion about whether it should show the transformation values as 0, 0,0 or not. We decided not to do it as 0, 0, 0 describes the scene center.
But it sounds like everything is working, but some of the scale values are out of whack. Can you please provide your SW files so we can take a look at the scale values based on the original data, not just what's written in the bip file.
Here are the SW files I used for the tests. They are a mix of 2010 and 2011 files.
This is a huge issues for me importing Rhino files too. Exact same issue!
Doesn't matter which box I check the parts come in different sizes. Also, y-up or Z-up doesn't seem to make a difference either, my files always come in face down no matter which x,y,z box I check.
same problem here with SW2010
only way to get objects same scale relative to each other is by preparing an assembly in Solidworks.
Quote from: Robb63 on March 08, 2011, 10:04:48 AM
This is a huge issues for me importing Rhino files too. Exact same issue!
Doesn't matter which box I check the parts come in different sizes. Also, y-up or Z-up doesn't seem to make a difference either, my files always come in face down no matter which x,y,z box I check.
The orientation works just fine - make sure you are using 2.2.45. If you use the Rhino plugin and then import a second model, then the scale is off.
Quote from: Thomas Teger on March 08, 2011, 12:55:30 PM
If you use the Rhino plugin and then import a second model, then the scale is off.
This is exactly why Keyshot needs to use real units; or at least the option to. If it's a matter of trying to be simple because you don't know if someone is bringing in a car or jewelry, then scale the environment automatically, NOT the geometry.
I'm not using the Rhino Plug-in. I'm just importing data, when the "use previous" is checked the new data comes in tiny (unless the data in there is gigantic and the new data is correct?).
At least if I look at the data in the scene now I can scale it using those numbers. A day or so ago those numbers were all over the place so I couldn't rely on them, now they seem to work.
I am using 2.2.45 since it came out. I'm working in Rhino 5, but there is no difference if I save as Rhino 4 version either.
Thanks for sending the files m2tts. When importing individual pieces, make sure you do the following:
Turn off Snap to Ground.
Turn off Center Geometry.
Then import the first piece.
When importing the subsequent pieces, makes sure to check Add to Scene, and From Previous (we will check them by default in the next update".
Snap to Ground and Center Geometry are still turned off - LEAVE IT THAT WAY.
Now everything comes in correctly. I noticed that the object can sometimes be very big. If this is the case, bring all objects in as described above. Then go to the scene tree, select all objects in the tree, and right click on the selection (still in the scene tree).
Select Scale from the menu. Scale all object using the widget, then click Snap to Ground.
Done.
Hope this helps.
Yes Thomas, I have been doing this.
Do you see the scale of the objects changing when you reopen the files? Mine were importing to a scale of "40" (in the x,y,z, boxes). When opening the files later, the scale had changed to "1600" for those same objects.
I just opened Scale Test 4.bip and see this. I have just imported Scale A.sldasm into this doing just as you said and it comes in at scale "1600" and is 40 times bigger than the previous objects. Changing it's scale to "40" gets it back to being the same size.
And it's making keyshot crawl again and is unusable. Maybe these issues are related?
Interestingly enough it brings it in correctly when I leave the scale at "Automatic" ...
Crawl? Don't see that. What is slow?
I just recreated scene Scale Test 4 from scratch, and I didn't see the scale changing - stays at 40. I am using 2.2.45. Your are "opening" the bip file, not importing it, correct?
I then added Scale A to it after saving the scene, closing and opening KeyShot again. All came in fine.
Are you running 2.2.45 for sure?
Yes I am running the latest version. I don't really know what is making Keyshot crawl, but I suspect my video card drivers have something to do with it. I know Keyshot does not use the video card for rendering the scene, but the video card is responsible for displaying windows the program runs in, and ultimately for what shows up on the display, right?
Try opening the Scale 4 scene today and see what you get for scaling.
The graphics card has nothing to do with it. What are the FPS numbers you are getting?
I will take a look at the scene in a bit.
Opened up the file from yesterday - scale is still at 40. I imported scale A, and it all works fine.
My FPS will go to 2. The interface stops responding. I have to kill it, and then the cpu will continue to fluctuate between 12 and 20 percent usage. This is why I suspect my graphics card is not giving up some resources, though Keyshot is the instigator as no other application is behaving this way.
Very strange - never heard that before.
On a different note - I was finally able to reproduce the scaling issue you were seeing. You will be happy to know that we fixed for the next update.
Thanks for your patience.
That's good to hear. When is that new release coming? I've begun to notice numbers changing in the rotation dialogs too if you have applied any rotations to the objects.
Within the next couple of days - going through the final testing now.
Yes - the rotation issue is also fixed.
Hi Thomas;
[quoteWithin the next couple of days - going through the final testing now.
][/quote]
May be too late to ask, but it would be great if "Saving Camera" saved absolutely everything related to the camera and model, including scale and model position.
Bill G
Would also like to take the time to ask a question regarding this issue. What IS the appropriate workflow for bringing in "life size" objects? I'm working on large industrial plants, buildings, equipment.
Should I be letting KeyShot scale down my models and work with that, or changing the scale to 1 and adjusting the environment height, size, and ground size?
Let KeyShot do the scaling. If you want to place the object relative to an environment, I suggest you use a backplate. Hope this helps.