Leaderboard

Want to learn some nodes? Dive into this unique training which covers all the novelties in the nodes system for R25. Nodes? Capsules? Assets? Parser? Tessellation? If these terms are confusing and sound odd, then this volume will get you up to speed. Understand the concepts and techniques needed to use node sytem efficiently and to your advantage. Lesson outline 1. Intro_and_requirements 2. Capsules 03_Geometry_Caching 04_Database_parser 05_New_Nodes_And_Assets 06_Spline_Primitives 07_Spline_Assembler 08_Spline_Length 09_Spline_Property_Interpolate 10_Spline_Type 11_Evaluate_Spline 12_Tessellation 13_Spline_Primitive_Group 14_Line_To_Mesh 15_Formula_Spline 16_Data_Visualizer 17_Delete_Segment 18_Multitrace 19_Curl_Spline 20_Typewritter Duration 135 mins https://www.core4d.com/ipb/store/product/45-introduction-to-r25-nodes/ Note: Link will work only for registered members

Oh, well done - that certainly wins my award for most awful tesselation of the year 🙂 I'm sure Rhino can do better than that if it tries ! Even the almighty Z-ReMesher is going to struggle with that. I haven't looked at HP's plan for rescuing it, but mine begins with deleting the thickness polys leaving a flat layer, doing UQ to select the outline of that, and extracting a spline (edge to spline) from it, which is then going under an Extrude, where, TBH I am probably going to stick with the ngon option - the surface is entirely flat, so as long as it produces a renderable surface - the triangulation going on behind the scenes is still likely to be moderately better than what Rhino did (let's face it - it couldn't be worse!) and if we don't have to look at ngon lines, then they need not worry us ! However if we do care about nice(r) topology, then the delaunay options in the extrude caps can work for us if we set the source spline to be uniform and a low point value such as 1, and choose Quad-dominant and suitable density... CBR

I cleaned it as much as possible. The steps I took are hidden. The order is in reverse (from bottom-to-top). If you have any questions don't hesitate asking. grass-front-03 happy polygon.c4d You should test some extra parameters from the export menu of Rhino. Here there is an option about exporting Ngons. It might help for future cleaner geometries. I assume the file was obj. @Fritz please take a look of a buggy behavior I found. At the final reconstruction step, in the Extrude Attributes, any value above 29.98 at the Grid Spacing results in an unimaginable dense grid. For some reason instead of getting bigger polygons it looks like it reverts to 0.1. Could be just R23, or a perpetuating bug.

more RS confusion... so doing the update to 2023.1 it killed some of the icons for RS which I had to manually add back to the UI. It also defaulted back to "Standard" as the Default Material, but it's the old c4d Standard material and not the new RS Standard Material: If I change the dropdown for Default Material to RS Shader Graph, it's the RS Standard Material and called "Mat" versus RS Shader Material or RS STandard in the material node editor itself? However if I chose the top level RS menu, drill down and select Standard, it creates a "RS Standard" and then calls it "RS Standard" and not "Mat"? Finally, if I pick from the Redshift top menu > Materials > Materials > Material (yes. triple), it creates a RS Material, using the newer Node Editor too but it used to use the old node editor? So are we still supposed to use the RS Standard, which is the new NEW standard material? If so shouldn't the Default Material dropdown in Preferences be labeled "RS Standard", with the name it creates in the Material Manager labeled as such "RS Standard" versus "Mat" or "RS Shader Graph" (which is implied in the Default Material in Preferences)? Maybe the dropdown in the Preferences for Default Material should be changed to reflect these: RS Standard Standard (C4D native - legacy) RS Material (Redshift native - legacy) Also, regardless of how you create a material, the name shows up the same in the Material Manager.