[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Search] [Home]
Board
Settings Home
/3/ - 3DCG



Thread archived.
You cannot reply anymore.




File: Gpack.gif (3.12 MB, 381x466)
3.12 MB
3.12 MB GIF
>>
File: donut_steel.jpg (205 KB, 960x1280)
205 KB
205 KB JPG
>>
>G-Pack doesn't work on latest stable blender
aww
>>
>>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.
>>
>>644221
lol good representation.

I build things in intersecting segments just to avoid troublesome unwraps.
>>
File: Taking_The_Time.png (217 KB, 1920x1080)
217 KB
217 KB PNG
>>644221
I 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 faults
yikes
get better at topology pls
>>
>>645102
It's false-flagging. At least, that's what I chose to believe.
>>
>>644221
What am I looking at?
>>
File: 1538943059258.jpg (111 KB, 960x960)
111 KB
111 KB JPG
>>645111
Blender's next-gen UV packing technology.
>>
>>645111
A 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.
>>
>>645121
is it truly superior to good old fashioned human controlled uv packing?
>>
>>645121
So it's a meme way of solving the knapsack problem? Pretty neat.
>>
>>645149
Jokes aside it's probably a step towards a better automated UV process
>>
>>645122
I 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.
>>
>>645224
so 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 physics
The 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.
>>
>>644221
cool
>>
>>645074

protip: select -> select faces by sides -> up to 5

congrats, you now can see all your ngons
>>
>>644221
Well that's certainly one way to solve the bin packing problem
>>
>>647955
protip: activate mesh lint
congrats, you now can see all your ngons
>>
>>647966
protip: switch into wireframe mode
congrats, you now can see all your ngons
>>
>>647988
You'd see your ngons but you'd also see everything else
>>
>>648515
Yes, that's what eyes do





Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.