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

Xbuf should not apply the wireframe modifier but set the material state #15

Open
MeFisto94 opened this issue May 28, 2018 · 2 comments
Open

Comments

@MeFisto94
Copy link
Contributor

This issue is rather subjective probably, so we might have to discuss pros and cons, at least people having the same problem might find this issue to understand what's going on.

A little context: My hitboxes are simple spheres placed in Blender and having a wireframe modifier (to not occlude the whole model). I was expecting xbuf to set the "AdditionalMaterialState" to Wireframe, but it applied the modifier and hence my collisions went wrong.

Now the question is: What is the desired behavior for that. I think in theory jme supports the wire thickness as well:

m2.getAdditionalRenderState().setWireframe(true);
m2.getAdditionalRenderState().setLineWidth(2f);

This might not be true for other engines and the results might be slightly different than in blender. However using the wireframe shader might be more performant than rendering the baked geometry.

@MeFisto94
Copy link
Contributor Author

Okay, this is solved in theory as I've found a "workaround":
If one does not want to have a certain modifier to be applied, just click the "camera" icon on the modifer, that way the modifier is not used during rendering (we use the xbuf render), but is still present in the scene view of blender.

@davidB
Copy link
Member

davidB commented May 28, 2018 via email

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

2 participants