HOME | DD
Wampa842 β [PMX Advanced] Merging different morph types
Published: 2014-10-12 09:34:41 +0000 UTC; Views: 4311; Favourites: 56; Downloads: 20
Redirect to original
Description
Download Notepad++: notepad-plus-plus.orgMessing around with exported CSV data can be rewarding. This will just add to the list of things I'll have to make tutorials about...
Anyways, this is a way to merge different morph types. PMX doesn't allow doing it the old fashioned Join way, so you have to make a morph that controls the other morphs, but that leaves the originals in the list. This is a way to hide them.
Related content
Comments: 11
π: 0 β©: 1
π: 0 β©: 0
This is great stuff I just had a model that had boots removal but then didn't have a foot adjustment. So i looked up how to do that but had two morphs I wanted to do in one. And i knew i'd seen a boot removal before so i came looking and found this. So awesome, thanks oh guru of PMX wisdomΒ Β
π: 0 β©: 0
Thank you so much for the tutorial!!
This literally saved my life!
π: 0 β©: 0
I'm sorry my ignorance but why would this be usefull? I mean what would we specifically use this for?Β
π: 0 β©: 1
For altering a model's shape and material properties with but one morph slider, for example. I'm only providing the means - use-cases are up to the user.
π: 0 β©: 1
Oh alright, this is usefull! Thank youΒ
π: 0 β©: 0
The old , vs . fight >.<
I am surprised to see that Japanese programmers adopted the "," when the US uses "."
But you will have the same problem with data which was processed by German speaking programmers since they also opted for the comma...
π: 0 β©: 1
It's more about programming and locale than national customs. There is an internal variable that contains the decimal character in the system. When a program stores a floating point value (i.e. real number) in the memory, it only stores the numeral data, not the decimal character. Within the program, it's not a problem. It will always handle float types the way it does. The real problem arises when you want to convert a string (input field) to float, or float to string (exported CSV). A function has to read the stored number and compile it into a humanly readable decimal number. In the process, the decimal character is inserted. If it's defined by your system as a dot, then no problem. But if it's a comma, it will conflict with the main use of commas in programming: value separation. This way, what used to be 0.3 becomes 0 and 3.
It is frustrating, and this is why I hate Japanese programmers.
π: 0 β©: 1
Oh my ... Now I understand your frustration.Β
Thx for taking the time to explain it.
π: 0 β©: 0