SU 9 Wishlist
-
That is something that I think all of us would like John. The more we make noise about it the more likely it will happen!!!
-
Bisection tracking!
-
-
@john2 said:
@rv1974 said:
Bisection tracking!
you mean angle bisection ?that would be awesome
You can do this already since v4?...
Make a guideline through one edge.
Select it and use Rotate+Ctrl to copy the guideline around the 'apex' by the full angle you'd like to subdivide...
Then immediately type /2
This will add a bisector guideline.Note: To divide the angle into 3 equal parts use /3 etc...
-
this is tedious workaround, not the tracking 'on the fly'
-
@rv1974 said:
this is tedious workaround, not the tracking 'on the fly'
Tell me how many clicks or key strokes your new "wonder-tool" would need - I suspect not many fewer than what I suggested...
You would somehow still need to define the apex, start angle, end angles and the subdivisions... -
very similar to square drawing in the present version.
(o.k. 0.5: just 2 keybord free hover moves over bisection forming edges)
BTW user defined angle snapping (with on\off mode) would be nice too. -
-
It you had a face with two edges at the vertex it could 'bisect' the angle [you'd still need keyboard input to say do 1/3's]... BUT if the vertex shares more than one face how is Sketchup to know which pair of edges it's to use and the associated face plane for the 'bisection' - you'd still need to pick to select the two edges in question [2 clicks], right-click for context-menu[?] and then enter the divisor numeral [e.g. '2'+enter] >>> 2+1+1+1=5 - whereas so using a guideline = shortcut-key + click/drag [2], then shortcut-key to Rotate +Ctrl to copy, click start, click end [4] plus the divisor numeral [e.g. '2'+enter] >>> 2+4+2=8 - so it could be done in less, but never 0 !
It is easy to code, but I'm not sure it's that useful
PS: It's a new context-menu tool available here http://forums.sketchucation.com/viewtopic.php?p=419335#p419335
-
-
I have more of a dream than a wish and only one:
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
What or which part of SU is responsible for not being able to handle such a big files?
Or could SU and vray do (in near future) something like thea render (instances in regards to tress, grass, flowers, hedges, etc.)
cheers
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
-
@cmoreink said:
Or could SU and vray do (in near future) something like thea render (instances in regards to tress, grass, flowers, hedges, etc.)
maxwell with mxs references (not instances, instances have to be stored in the scene)...
-
@cmoreink said:
I have more of a dream than a wish and only one:
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
What or which part of SU is responsible for not being able to handle such a big files?
Or could SU and vray do (in near future) something like thea render (instances in regards to tress, grass, flowers, hedges, etc.)
cheers
Not sure, a lot of people thought it was Sketchup not being 64 bit etc., but that balloon myth kind of got popped by a lot of members.
I think it is just the way Sketchup is coded at it's core....
It's my believe it will never be 'fixed' as I guess it would mean an overhaul and a little bit of a re-inventing the way Sketchup handles geometry?This has been a topic for years now...
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
-
@cmoreink said:
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
VfSU is being prepared for beta - it will get proxy support like VfRhino.
-
@thomthom said:
@cmoreink said:
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
VfSU is being prepared for beta - it will get proxy support like VfRhino.
Thomthom, can you flesh that out a bit more? Are you talking about something like Maxwell's references which live outside of a SU file, or would the high poly geometry have to live within the file being rendered?
-Brodie
-
@unknownuser said:
@thomthom said:
@cmoreink said:
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
VfSU is being prepared for beta - it will get proxy support like VfRhino.
Thomthom, can you flesh that out a bit more? Are you talking about something like Maxwell's references which live outside of a SU file, or would the high poly geometry have to live within the file being rendered?
-Brodie
Proxies - references to external files.
-
Like here (in Thea): http://forums.sketchucation.com/viewtopic.php?f=80&t=46858
...but I guess Brodie knows about it as he even mentioned it.
-
Octane Render now also has a beta version with 'instancing'.
You can export a single complex component/group as an OBJ file and import that into the renderer's OCS file as an OBJ 'node'; then in a SKP that has lots of objects placed [they don't need to be same object because simple placeholders for complex objects will work well].
You can then use a simple ruby script to export the transformations of these into a TXT file, it needs to make adjustments for the transformation-matrix differences between the two programs [!] and then you can paste the SSV text output into a new Transform node you add into the OCS; then you simply drag a link between the OBJ node and the Transform node - hey-presto! You have multiple copies of the complex object placed as desired inside the render, without the overhead of zillions of polys in the SKP or OCS files.
This way you can split up a SKP model into manageable parts and end up with a complex OCS file for rendering using placeholder data for the complex objects - like detailed 3d trees etc...
I have been working with smicha and others, on their forum, trying to sort out this 'translation' between the two transformation matrices... now it is working well.
It just needs 'wrapping-up' a bit nicer...
-
@thomthom said:
@unknownuser said:
@thomthom said:
@cmoreink said:
- import and handle large .obj files (trees, hedges, etc.), is this even possible for SU in next 12-24 months? or should I look into thea render, since I use SU+vray only.
VfSU is being prepared for beta - it will get proxy support like VfRhino.
Thomthom, can you flesh that out a bit more? Are you talking about something like Maxwell's references which live outside of a SU file, or would the high poly geometry have to live within the file being rendered?
-Brodie
Proxies - references to external files.
That's wonderful news. Do we have any idea of a timeline on this or how to get into the beta? I also wonder what sort of file you can reference. For example, I wonder if I can reference .max files.
-Brodie
-
@unknownuser said:
For example, I wonder if I can reference .max files.
.max format is propriety - not one for exchanging between applications. I'd expect either SketchUp files or some propriety V-Ray format. (Mental Ray for instance require you to export out proxies to an MR propriety format.)
@unknownuser said:
Do we have any idea of a timeline on this
When it's done. No one knows - not even them. But at least they've begun the work on it.
@unknownuser said:
how to get into the beta?
Ask Devin nicely.
And give good bug-reports.
Advertisement