-
Notifications
You must be signed in to change notification settings - Fork 36
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
How to split mesh efficiently #35
Comments
The only way I know is to cut them manually and assigning materials. There is probably a better way to do it but I am doing it manually for each release. This project will soon be using OSSL baked texture function which will incorporate a more traditional transparency solution similar to the system avatar transparency. |
Hello Shin,
Does this mean the project will become Second Life incompatible?
Kind regards
Alvina
Le mar. 23 oct. 2018 à 18:33, Shin Ingen <notifications@github.com> a
écrit :
… The only way I know is to cut them manually and assigning materials. There
is probably a better way to do it but I am doing it manually for each
release.
This project will soon be using OSSL baked texture function which will
incorporate a more traditional transparency solution similar to the system
avatar transparency.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AjUtG0I68lX4aOuAmRBRm0cDvbsspO6bks5un0TrgaJpZM4Xyah2>
.
|
Our OpenSim implementation will be but the source will still be available for other types of implementation such as a Second Life specific release. |
I am sorry that i use the issue tracker for this question, but i am currently trying to create a HUD for Ruth and Roth that provides slightly more functionality like auto-hide and slots for saving the state and maybe more and i was wondering what your workflow is for splitting the mesh apart into the individual prims for the alphas.
Are you doing it manually on every release?
ty
The text was updated successfully, but these errors were encountered: