bigseb
Alibre Super User
This. Would be great to select faces that are sparked/polished/etc in one part without massive workarounds.
2019- List of New Features or Fixes
- Thread starter ynnek
- Start date
Yes, that would be very convenient for me. No more Cut and Paste from the Drawing window!That's the one. I'm sold.
We'd need to be able to scale the image from its centre (As in Drawing Workspace). Also, it would be incredibly useful to be able to adjust the X and Y axis scaling separately.
STL import is not in 2019.0
Would you be able to open a drawing and then File > Package > Create Package and send it to me? That way I can benchmark it. Also, if your drawings have something that is particularly taxing on performance, we can use it for performance testing / debugging.
Max@alibre.com or if it's really big: https://www.dropbox.com/request/PjHmOBSg203xu0LN0Ks6
Based on your model, the following results were obtained:
File Open:
Old: 65 seconds
New: 54 seconds
Reproject everything:
Old: 230 seconds (3 min 50 seconds)
New: 228 seconds (3 min 48 seconds)
It does not appear that this drawing would be significantly affected by the new graphics pipeline. The primary culprit appears to be that there are 120 Views in this drawing. The biggest way we can approach improving this scenario is to perhaps multithread view creation. That is on our minds, but is not for this release. I will pass this drawing to our Dev team.
Thanks!
domcm
Senior Member
@Max
Thanks for the quick response. Yes, multithreading drawing view creation would be a significant improvement for those of us who create production drawings. My only other option is to re-structure my drawings and create multiple drawings per assembly to reduce the number of views per drawing which is not an ideal solution for me.
Thanks for the quick response. Yes, multithreading drawing view creation would be a significant improvement for those of us who create production drawings. My only other option is to re-structure my drawings and create multiple drawings per assembly to reduce the number of views per drawing which is not an ideal solution for me.
No worries. BTW, for access-heavy applications where you may read/write a lot, it's not a bad idea to invest in a NVMe M.2 SSD drive. If you don't know, all SSDs are not equal, NVMe being a newer standard and requiring a NVMe slot on your motherboard. But they are...ludicrously fast.
I use this one personally. It's not a silver bullet, but it really helps a lot.
That is functionality was single purpose to bring in mesh files and convert them to solids and used proprietary 3D Systems technology. Replacing it requires us to license some new stuff from other vendors who take a broader approach to engineering workflows.
As a result when we implement "mesh handling v2" we have to put a lot of thought into the extended workflows we want to enable and how to support them to take it from "toy" to real engineering flow. It's a big feature set and probably needs a release largely unto itself. Not something that can be slipped in.
Last edited:
GIOV
Alibre Super User
Hi Max,
I have an old AD 11 V13 and the latest one AD 2018.2. Right now I don't need a super Virtual Reality, only some features that are urgent to be implemented as the link below:
https://www.alibreforum.com/forum/index.php?threads/alibre-design-future-improvements.19151/
This is my sincere appraisement and I hope you will concentrate in this matter as soon as you can.
GIOV
I have an old AD 11 V13 and the latest one AD 2018.2. Right now I don't need a super Virtual Reality, only some features that are urgent to be implemented as the link below:
https://www.alibreforum.com/forum/index.php?threads/alibre-design-future-improvements.19151/
This is my sincere appraisement and I hope you will concentrate in this matter as soon as you can.
GIOV
Last edited:
MarcusWolschon
Senior Member
JST
Alibre Super User
Maybe I am unique, but I used mesh import/STL import a couple times, and in neither case did it actually work usefully for me. One left out things, and the others did not really give me anything I could work effectively with.
What I got was different from, but not much more useful than, the "data cloud" we got once from a CMM. Neither translated to anything that was very useful, probably because there was nothing available to allow extracting a sensible set of dimensions, or even tolerances.
I could not reduce it to a sensible part, and there were no useful tools to help.
If STL import never came back, I would not actually miss it, even though I have generated many STL files and had many 3D printed parts made.
What I got was different from, but not much more useful than, the "data cloud" we got once from a CMM. Neither translated to anything that was very useful, probably because there was nothing available to allow extracting a sensible set of dimensions, or even tolerances.
I could not reduce it to a sensible part, and there were no useful tools to help.
If STL import never came back, I would not actually miss it, even though I have generated many STL files and had many 3D printed parts made.
I've got a question about Section Views in the new graphics pipeline. Presently, the Section Plane only sections Part geometry which it intersects with. This shows up in cases such as, for example, a Circular Array. Here, unless one of the elements is intersected by the Section Plane, the whole Array remains visible. Will this change?
Last edited:
Another question..... As in my signature: "Wireframe with visible edges only display mode" Is this an easy implementation with the new graphics?