Congratulations everyone! We've reached 1k members!

I know this post has nothing to do with Blender/Python. Thanks in advance to Victor Stepanov for understanding. 1. Regarding Artificial Intelligence - i'm afraid, there was a misunderstanding and i want to explain: The country where I live and work (at least for now...) is a member of the European Union (EU). When the EU enacts new laws (or regulations), these supersede national legislation. This means that national laws are irrelevant if there are specific EU laws for the respective area. The EU is known for viewing anything digital that doesn't originate within the EU itself as "evil," and AI is considered pure devil anyway. However, this is solely due to the fact that they themselves failed to set the appropriate course in education, trade, and industry in a timely manner. If I were to start acquiring the necessary knowledge in AI now, I would constantly have to reckon with the possibility that using AI would be prohibited by law the very next day. In today's Hangout, we talked a lot about AI, and I was surprised by how positively you all view it. I don't mean to belittle that, but from my perspective, it looks very different—if I have to expect that I might no longer be able to use AI at any time. Keeping this in mind, where is the sense for me to get the necessary knowledge about using AI? 2. To Robert McBride: I found your hints about physics (electrophysical?) very interesting. Since I'm new to this, could you perhaps explain the background/basics to me in a few short sentences? In a very general way? If so, thank you very much! 3. To Gregory Tada: Regarding your questions about solar energy, please send me one (or two) suggested times for a video call to markus@my-dwarf.com. I promise I'm not trying to sell you anything, just have a technical discussion. Finaly, again thanks to VIctor for understanding to use your platform for this issues.

I’ve yet to figure out how to go about turning my main Charge field atomic modeling project into a molecule maker, then into an Addon. In the meantime, here’s some proof of life, a quick and easy Blender project, with AI help of course. Circle and sphere Packing. Still, it took me a few hours to request and understand it, make notes and changes, then find and correct a bad initial y_offset value suggested in the sphere packing section. 1. A 2d hexagonal close packed array of overlapping circles, 7 circles; 2. A grid of circles with variable rows and columns; 3. 3d hexagonal close packed spheres consisting of two alternating layers. First un-comment (remove) the pair of triple ( ''' ) quotes at the top and bottom of the section you wish to mess with. Here’s the AI instructions for creating the Blender python SG grid. AI wrote. QUOTE How to use the script Open the Scripting Workspace: Open Blender and switch to the Scripting workspace via the tabs at the top. Create a New Script: In the text editor window, click the New button. Paste the Code: Copy the code above and paste it into the editor. Adjust Settings (Optional): Change the variables at the top of the script (circles_across, rows_down, circle_radius, overlap_factor) to get your desired grid. Run the Script: Click the Run Script button (the "play" icon) in the text editor header. How it works Variable Control: The top section provides a clear way to control the grid's dimensions and overlap. Clear Scene: The script first deletes any old circles from previous runs to ensure a clean slate. This is a best practice for re-running scripts. Hexagonal Spacing: The core of the hexagonal grid is in the x_spacing and y_spacing calculations. A hexagon's geometry dictates that the vertical distance between row centers is a multiple of $\sqrt{3}/2$. Row Offset: A hexagonal pattern requires every other row to be horizontally shifted. The if row % 2 == 1: statement handles this by adding x_offset to odd-numbered rows.

What I have: A mesh object in the form of a path. The indices of the individual vertices and edges correspond to the order of creation, but not to the direction of the path. What I want: The vertices and edges should be in the order of the path's direction. While playing around with KDTree(), I discovered that it doesn't take the path itself into account, but only considers the distances between the individual vertices. Unfortunately, that wasn't what I needed. So I put together my own script that proceeds as follows: 1. Create a list with (number of edges plus 1) entries. Each entry is 0, and the index corresponds to the index of the vertices of the unordered path. 2. Iterate over all edges and increment the value in the list corresponding to the index by 1. This gives me a list of all vertices, along with the value of how many edges are connected to each vertex. The two indices, each containing only the value 1, represent the starting and ending points. 3. Take the first index, which has the value 1, and determine the corresponding index of the edge. Since the index of one vertex is already known, the other vertex becomes the new starting point. 4. Iterate over all edges again, ignoring the first edge, and find the other vertex each time. Write the result in a new list. 5. Repeat step 4 for all remaining edges. 6. The new list contains the indices of the vertices in the direction of the path. From this, the coordinates can be read, and a new path can be created in the same order, with the vertices in the order of the path's direction. I'm sure there are much simpler and more elegant ways to do this. There may even be ready-made methods in Blender for this. This was my first attempt, and it actually works. But how can I do it more elegantly? What are things i should not do? (When I learned to program more than 40 years ago, spaghetti code was common—and that's exactly what my script looks like.)

I dont need to Register or make comments in loom right it is keep telling me I should and taking me to external website