>G-Pack doesn't work on latest stable blenderaww
>>644221>Next-gen physically-based finite-element-analysis gravity-aware uv-unwrapping.Call me back when Max is able to do even a tenth of what Blender can already do.
>>644221lol good representation.I build things in intersecting segments just to avoid troublesome unwraps.
>>644221I don't understand?the UV Unwrapping Processes for me is were find all my hidden geometry to fix before exporting everything.
>>645074>purposely using uvs to find topology faultsyikesget better at topology pls
>>645102It's false-flagging. At least, that's what I chose to believe.
>>644221What am I looking at?
>>645111Blender's next-gen UV packing technology.
>>645111A gravity aware, physic based uv-packing solver. Unironically coded by a dev in two hours in Blender as a joke.The same feature has yet to be developed in the concurrence. Some say it is impossible as the data structures of 3ds Max are simply too inefficient for that kind of cutting edge algorithms. I think they are simply waiting to use this feature as a selling point for a new version.
>>645121is it truly superior to good old fashioned human controlled uv packing?
>>645121So it's a meme way of solving the knapsack problem? Pretty neat.
>>645149Jokes aside it's probably a step towards a better automated UV process
>>645122I have integrated it into my workflow. It has completely changed the way I do uv-packing. Tremendous change. Far more physically accurate way to do it.Unfortunately the finite element solver seems to use Newtonian physics: i.e when sending pieces at near-c velocities I saw no time dilation or space compression. This is a shame, and it poses a real problem when I try to use special relativity in order to have a tighter packing. It should be possible to compress space in such a way as to pack things even further.All in all it is a module that everyone should use and is order of magnitude more physically accurate than anything the concurrence propose.
>>645224so were you born retarded or just ended up that way due to some unforseen consequence from poor life choices?
>>645224>Unfortunately the finite element solver seems to use Newtonian physicsThe devs have their reasons. If they had implemented more accurate physics, concurrency would be very hard (or nearly impossible) to achieve between Blender's core process and the packing algorithm thread when moving UV cells at near-c speeds. Not to mention the RAM usage going through the roof as the UV data mass increases.Keeping it Newtonian is less accurate, sure, but more practical given the current state of computing technology.
>>644221cool
>>645074protip: select -> select faces by sides -> up to 5congrats, you now can see all your ngons
>>644221Well that's certainly one way to solve the bin packing problem
>>647955protip: activate mesh lintcongrats, you now can see all your ngons
>>647966protip: switch into wireframe modecongrats, you now can see all your ngons
>>647988You'd see your ngons but you'd also see everything else
>>648515Yes, that's what eyes do
