|Marvelous Designer Performance|
So I just recently started learning and using Marvelous Designer 6 at work for character clothes creation.
I love it so far, it's great fun, a very stable application (Hasn't crashed even once in two weeks).
Easy to learn and it's basically like sewing in real life: It's reverse UV-mapping.
However, I do find that I get a lot of performance issues after running the program for a period of time. Especially when I have several pieces of clothing.
It doesn't seem to matter if I freeze/deactivate the clothes I'm not working on at the moment, performance still takes a hit. Even with a very high particle distance.
So I'm wondering if anyone of you guys who have used Marvelous before has any experience on what Marvelous needs to perform better?
Is it more CPU cores? Faster GPU? Faster RAM? SSD rather than HDD?
I've tried to google this but I get mixed messages about this particular thing.
Visit my Portfolio
read 488 times
3/24/2017 9:54:23 AM (last edit: 3/24/2017 9:54:23 AM)
Just be thankful it's stable. I used marvelous designer 2 back in the day (didn't realise it's up to 6) and it was constantly crashing or fucking out (you move a vert and it goes all spastic and you have to start again).
read 479 times
3/24/2017 11:03:39 AM (last edit: 3/24/2017 11:03:39 AM)
Just got done using it for the last week or so.
Very stable. Great performance. No issues like you are mentioning. I've only ever left a session open for no more than a couple of hours be fore switching.
2x E5-2687W v4 (12 cores each at 3.0ghz)
128gb ECC Ram
read 462 times
3/24/2017 5:04:06 PM (last edit: 3/24/2017 5:04:06 PM)
I always found it pretty stable too, but you can't sew in the 3D view-ports is a massive downer, I absolutely detest that 2D pattern thing.
read 457 times
3/24/2017 5:39:37 PM (last edit: 3/24/2017 5:39:37 PM)
"Just be thankful it's stable."
HAHA - Speaking from experience aren't we :) - haha u're definitely not alone on this one pal.
read 408 times
4/2/2017 12:10:23 AM (last edit: 4/2/2017 12:10:23 AM)
> However, I do find that I get a lot of performance issues after running the program for a period of time.
This sounds a lot like a memory leak.
read 404 times
4/2/2017 3:29:12 AM (last edit: 4/2/2017 3:29:12 AM)
Look for Marvelous Designer 6 in [Processes] tab and keep an eye on Memory usage.
If the memory usage increases gradually whilst using the program and drops to a much lower value when the softare is restarted just after it has ground to a halt or crashed, the program might be leaking memory i.e. not freeing up allocated memory as a result of poor internal housekeeping.
read 399 times
4/2/2017 5:56:10 AM (last edit: 4/2/2017 11:51:58 PM)