Release Candidate 11x

Tech support and suggestions forum. If you only have a basic question on how to get started, please use the "newbies" forum in the community section.

Moderator: joepal

Re: Release Candidate 11x

Postby learning » Thu Mar 03, 2016 4:00 am

Can you just mark makehuman and makehuman-unstable as conflicting in your ppa?
learning
 
Posts: 317
Joined: Mon Feb 24, 2014 9:36 am

Re: Release Candidate 11x

Postby gaiha » Thu Mar 03, 2016 4:48 am

learning wrote:Can you just mark makehuman and makehuman-unstable as conflicting in your ppa?

Because this recent release candidate and the unstabe nightly build share the same files... this causes a conflict when installing the RC1. in order to resolve this (at this time) the unstable nightly build must be un-installed/removed prior to installing the Release Candidate. AS was noted by "joepal" - this can be updated in a second release candidate (if it is made) otherwise, it will wait until the final build.

smoochies
My Dev Box: Asus CrosshairV with an AMD FX-9370 4.4 Ghz 8 core Processor, 32 GB 1600hz DDR3,
GeForce GTX-760 Video card, 2TB Seagate Constellation Class HDD. 1 GB Ethernet Lan
Running Ubuntu 14.04.4 on the 4.2.0-30 Kernel, with the Gnome 3.8.4 Desktop.
User avatar
gaiha
 
Posts: 53
Joined: Tue Feb 09, 2016 7:45 pm
Location: Canada

Re: Release Candidate 11x

Postby joepal » Thu Mar 03, 2016 9:23 am

learning wrote:Can you just mark makehuman and makehuman-unstable as conflicting in your ppa?


Yes, the PPA owner can do this. And I have done so in the build source, but I haven't yet built an updated PPA, so the change hasn't propagated to launchpad yet.
Joel Palmius (LinkedIn)
MakeHuman Infrastructure Manager
http://www.palmius.com/joel
joepal
 
Posts: 4474
Joined: Wed Jun 04, 2008 11:20 am

Re: Release Candidate 11x

Postby learning » Thu Mar 03, 2016 5:40 pm

Aren't you the owner of the PPA?
learning
 
Posts: 317
Joined: Mon Feb 24, 2014 9:36 am

Re: Release Candidate 11x

Postby joepal » Thu Mar 03, 2016 8:19 pm

learning wrote:Aren't you the owner of the PPA?


Yes. But it isn't as if it's just of a push of a button and then it's done. There are quite a lot of manual steps in between. And I don't think this glitch is big enough to warrant the effort. So I'll wait with pushing a new version until there's something bigger to fix.
Joel Palmius (LinkedIn)
MakeHuman Infrastructure Manager
http://www.palmius.com/joel
joepal
 
Posts: 4474
Joined: Wed Jun 04, 2008 11:20 am

Re: Release Candidate 11x

Postby FairyTail » Thu Mar 17, 2016 8:40 am

On Ubuntu trusty, looking at the differences between 1.10~rc2 and an up-to-date install from mercurial, using the same config files, when starting the ppa build there is a warning
Code: Select all
Incompatible MakeHuman settings (version 1.2.0) detected (expected 1.1.0). Loading default settings.

Using the mercurial version
Code: Select all
makehuman -v
MakeHuman Copyright (C) 2001-2015 http://www.makehuman.org
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. For details use the option --license

NO VERSION file detected, retrieving revision info from HG
Detected HG revision: r2020 (c400adbeefe1)
1.2.0 (r2020 c400adbeefe1) [hg parents command]

So it looks like the mercurial version is incorrect.

The mercurial version also gives many more options under the Utilities tab than the ppa build; specifically it would be nice to have "Skeleton Debug", because there appears to be several issues with the weights for the default rig.

To see the weight differences, start makehuman, choose the default rig, go to Utilities, Debug Skeleton, and compare, for example, upperleg01.L and upperleg01.R, or foot.L and foot.R. I would assume that the weights ought to be mirrored. A quick and dirty comparison of vertex counts in ./makehuman/data/rigs/default_weights.mhw show several differences:
Code: Select all
 "breast.L":447
 "breast.R":434
 "clavicle.L":665
 "clavicle.R":635
 "finger3-1.L":247
 "finger3-1.R":241
 "foot.L":842
 "foot.R":716
 "levator05.L":436
 "levator05.R":437
 "levator06.L":319
 "levator06.R":271
 "lowerarm01.L":544
 "lowerarm01.R":548
 "lowerleg01.L":956
 "lowerleg01.R":959
 "lowerleg02.L":674
 "lowerleg02.R":600
 "metacarpal2.L":205
 "metacarpal2.R":198
 "oculi01.L":292
 "oculi01.R":273
 "orbicularis03.L":265
 "orbicularis03.R":259
 "orbicularis04.L":287
 "orbicularis04.R":286
 "pelvis.L":958
 "pelvis.R":964
 "risorius03.L":467
 "risorius03.R":466
 "shoulder01.L":615
 "shoulder01.R":588
 "tongue05.L":99
 "tongue05.R":86
 "tongue07.L":109
 "tongue07.R":100
 "upperarm01.L":936
 "upperarm01.R":910
 "upperarm02.L":703
 "upperarm02.R":696
 "upperleg01.L":1197
 "upperleg01.R":1222
 "upperleg02.L":1083
 "upperleg02.R":1076
 "wrist.L":251
 "wrist.R":254

Finally, purely to avoid the huge download, it would be nice if makehuman-clothes was a "suggested" package and not a dependency.
User avatar
FairyTail
 
Posts: 38
Joined: Wed Feb 18, 2015 6:22 pm

Re: Release Candidate 11x

Postby joepal » Thu Mar 17, 2016 9:05 am

Thanks for many helpful suggestions. I'll look at these for rc3.

For the first warning: Are you sure that's not because you had run 1.2.0 first and thus got a settings file in ~/makehuman with a 1.2.0 version stamp? If you temporarily rename ~/makehuman to ~/makehuman.bak and try the PPA again, do you get the same warning?
Joel Palmius (LinkedIn)
MakeHuman Infrastructure Manager
http://www.palmius.com/joel
joepal
 
Posts: 4474
Joined: Wed Jun 04, 2008 11:20 am

Re: Release Candidate 11x

Postby joepal » Thu Mar 17, 2016 9:21 am

Concerning the weights: that's most likely #954 http://bugtracker.makehumancommunity.org/issues/954

This is still scheduled for fix for 1.1.0, but I don't know what the status is.

If you have suggestions, maybe you could add them in that bug report?
Joel Palmius (LinkedIn)
MakeHuman Infrastructure Manager
http://www.palmius.com/joel
joepal
 
Posts: 4474
Joined: Wed Jun 04, 2008 11:20 am

Re: Release Candidate 11x

Postby FairyTail » Thu Mar 17, 2016 1:31 pm

joepal wrote:For the first warning: Are you sure that's not because you had run 1.2.0 first and thus got a settings file in ~/makehuman with a 1.2.0 version stamp? If you temporarily rename ~/makehuman to ~/makehuman.bak and try the PPA again, do you get the same warning?


Moving ~/makehuman out of the way, the mercurial makehuman -v returns 1.2.0 (r2020 c400adbeefe1) [hg parents command]

The ppa build makehuman -v returns data/VERSION file detected using value from version file: 2019:55f4570dc8ca 1.1.0

The ppa build is fine, but the difference in version numbers between the mercurial source and the ppa build means that there will be incompatibility issues with some saved files. IIRC, I had to edit some version numbers manually to open v1.1 files using makehuman from the mercurial source.
User avatar
FairyTail
 
Posts: 38
Joined: Wed Feb 18, 2015 6:22 pm

Re: Release Candidate 11x

Postby joepal » Thu Mar 17, 2016 5:18 pm

FairyTail wrote:
joepal wrote:For the first warning: Are you sure that's not because you had run 1.2.0 first and thus got a settings file in ~/makehuman with a 1.2.0 version stamp? If you temporarily rename ~/makehuman to ~/makehuman.bak and try the PPA again, do you get the same warning?


Moving ~/makehuman out of the way, the mercurial makehuman -v returns 1.2.0 (r2020 c400adbeefe1) [hg parents command]


Just checking... You *are* running stable branch here? I.e, you cloned and then did "hg update -C stable"? Cause 1.1 is now "stable" while "default" is 1.2.
Joel Palmius (LinkedIn)
MakeHuman Infrastructure Manager
http://www.palmius.com/joel
joepal
 
Posts: 4474
Joined: Wed Jun 04, 2008 11:20 am

PreviousNext

Return to Bugs, problems and feature requests

Who is online

Users browsing this forum: No registered users and 1 guest

cron