-
Notifications
You must be signed in to change notification settings - Fork 151
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
VertexInstanceStream added on every meshes ! #12
Comments
It should only add it to ones with mesh renderers and only add it when On Thu, Oct 20, 2016 at 11:35 AM, apautrot notifications@github.com wrote:
|
Eh, yeah, it's being overly aggressive. Trying to rework it a bit to make I can either: a) Be aggressive with adding these components and attempt to clean them up b) Not be aggressive, and introduce a few more edge cases starting the Both have issues; with the first, you might save the scene, etc, with the With the second, you can't do things like preview the vertex data until you grr.. On Thu, Oct 20, 2016 at 11:39 AM, Jason Booth slipster216@gmail.com wrote:
|
Ok, I went with #2 and added some buttons to make it a bit easier to On Thu, Oct 20, 2016 at 2:00 PM, Jason Booth slipster216@gmail.com wrote:
|
Hi The component is added to any mesh (and full hierarchy under) at first Personally I would prefer the editor window to tell me "There is no Another issue : because you add the component but do not raise any Regards. 2016-10-20 17:39 GMT+02:00 Jason Booth notifications@github.com:
|
Did you get latest? I fixed both of these last week.. On Tue, Oct 25, 2016 at 2:26 PM, apautrot notifications@github.com wrote:
|
Hi Jason, I've seen that you did a fix. 2016-10-25 23:56 GMT+02:00 Jason Booth notifications@github.com:
|
While the tool window is opened, the tool is automatically adding component VertexInstanceStream to any selected GameObject and all its hierarchy !
In class VertexPainterWindow :
property public VertexInstanceStream stream { get {
...
_stream = meshFilter.gameObject.AddComponent();
...
} }
This is madness...
The text was updated successfully, but these errors were encountered: