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.

The script is written with Blender 4.4.3. Please pardon my many working errors. Victor, Thanks again for the ‘collections and instances’ script you provided. I had no understanding or appreciation for that possible project alternative till you suggested it. Since then, I’ve been slowly learning the subject matter and changing my code to work with stack instances. For example, the build_all_stacks() function’s instance names can also work as 3D text. I believe all my basic modeling requirements: 1. assembling 4 proton collections (shown co-located at (0,0,0) in the image) to form 144 proton stack instances; 2. adding up to 19 properly oriented and positioned stacks to make 1-90 atoms; 3. properly orienting and positioning atoms to make 3D molecules; 4. and including 1 or 2 bonding site stack swap out modifications; can all be accomplished with collections and instances instead of objects. The more atoms the merrier, with little to no increase in processing demands. Nevertheless the group collections, instances and 3D text included in the image seems massive to me. The addon is gone, but I can rewrite an improved version later. My next main consideration is animation. For starters, each and every proton group instance should contain constantly spinning left or right protons, electrons, and charge intake vortices. The proton instances will cast particle emissions outward from its equatorial plane while the instance is also spinning and moving linearly in space. Please note that my initial, brief Linear_and_Angular_Motion() function that operates on a proton group instance contains instructions from two of your tutorials. Given all that, I hope I’m not asking for too much, might you be able to make any further suggestions or recommendations on how I might go about implementing such animations?

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.)

If you ever need to find the vertex nearest to a given point, Blender’s mathutils.kdtree makes it fast and easy. KDTree.find() returns the closest vertex position, its index, and the distance.

Hi there! Just wanna learn how to use Python to avoid a lot of repeating tasks in mockups for factory design, like handrails, stairs, and so on. I'm 57 years old, learned programming 40 years ago, and I'm struggling with Python syntax based on my admittedly outdated knowledge ...