Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roth RC#2 Preparation #26

Open
aiaustin opened this issue Apr 24, 2019 · 9 comments
Open

Roth RC#2 Preparation #26

aiaustin opened this issue Apr 24, 2019 · 9 comments

Comments

@aiaustin
Copy link
Member

Starting this issue to act as a place to discuss the update for Roth.

My first comment is that we should include a new default shape. The current one has ludicrously long arms (80). I have changed my version to arm length 45 and toned down the muscles a bit! I suggest a new default and maybe leave the current shape in labelled as RC#1 Shape for those wanting to look like a gorilla.

@AdaRadius
Copy link
Member

This is what I think, after the last disaster with Ruth. The mismatches in Ruth are in the hands as well as the neck. With Roth, the mesh is breaking altogether, but I'll do something like freeze it and start over with the weights.

While we're doing the work in Blender, we should stick to what Avastar calls the OS default shape. It's not a good shape, aesthetically, but it's Gaia's and therefore our best shot at matching from Blender to inworld. Ya, 80% arms, what were they thinking?
Anyway, once we have a match between Blender export and the armature after importing inworld, we can offer shapes that are more pleasing inworld, as a few people have done with Ruth.

@aiaustin
Copy link
Member Author

Good plan to use the default shape for the core build and the offer decent shapes as bases for people in the Extras package.

I think for the base package its worth including the basic underwear as well, like Shin's Boxer shorts. So people can equip a base avatar, save that and take it from there for their own customization.

@AdaRadius
Copy link
Member

I'm nearly ready to upload the first of the RothRC#2 files - I redrew the UV maps - new seams etc. But first I'll take it inworld to test that armature-neck problem and find out if I have to do more remodeling. Question: I'm going to want to do the same with RuthRC#4 - would it be possible to remove all of my *.blend and *.dae files from my contrib folder? Or better to replace them? I can do better with file labeling the second time.

@aiaustin
Copy link
Member Author

aiaustin commented Apr 30, 2019

Serie or myself can delete anything you want Ada. Do you want me to do that now? All *.blend and *.dae that are there now? Leave all .png and .txt files, and the various directories?

@aiaustin
Copy link
Member Author

aiaustin commented Apr 30, 2019

I moved all the files relating to the previous preparation of Ruth 2.0 RC#4 for Ada into Contrib/Ada Radius/ Ruth2.0_RC4_Previous .. including the various text files and .png. We can move any still needed back if that is wanted, and when Ada is sure she has all she needs to place on GitHub we can delete Ruth2.0_RC4_Previous.

I was getting an odd GitHub desktop thing when I updated the Ruth repository locally... this ONE file changes its filename (capitalisation only) in my Windows setup versus the name it appears to have in the repository. I am not doing anything at my end.. it just shows as a changed file. Odd.

Ruth2.0_RC4.2UV_lower+feetflat.png turns into Ruth2.0_RC4.2UV_LOWER+FEETflat.png

I bet this is something to do with the underlying original file name, later renamed. Windows seems to do odd things with the file name in these circumstances. I did a remove and replaced to fix that (I hope). The .png file contents itself is unchanged.

@AdaRadius
Copy link
Member

Sounds perfect, thank you! Ah, maybe it was the + in the file name. I knew spaces were bad, but hadn't seen the name change to caps before. Or maybe Win is weird, but we already knew that.
:)

@aiaustin
Copy link
Member Author

If you are naming, best to stay clear of + & ( ) : / ; ? etc. Underscore _ is also good to avoid space which will be %20 URLs

@seriesumei
Copy link
Member

Windows NTFS filesystems are "case retentive" meaning they save whatever case you give filenames but ignore case on matching so README.txt and readme.txt are the same there. The default HFS filesystems on Macs are similar, you have to explicitly re-format disks to enable case sensitivity. My MAcBook Air is not case sensitive and that bit me when I was doing the renames for the Robin Wood skins more than once...

@aiaustin
Copy link
Member Author

aiaustin commented May 3, 2019

Good to know its NTFS only, I had assumed it was for all Windows filenames. To change the underlying capitalisation you must change the filename to a different one with case ignored and then change back to the case specific original filename.

@aiaustin aiaustin reopened this May 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants