Matt McDonald Posted September 30, 2015 Share Posted September 30, 2015 Backburner 2014 has bug where it does not respect layer visibility of xrefs based on the scene file but rather the visibility of the layer in the xref file. http://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/Xref-scenes-not-rendered-properly-by-Backburner-if-they-contain-layers-states.html Do any of you know if this has been fixed in Backburner 2015 or 2016? Thanks for the help Matt Link to comment Share on other sites More sharing options...
Scott Schroeder Posted September 30, 2015 Share Posted September 30, 2015 2016 has had a major overhaul to xrefs and it now respects layer visibility in the scene, not the xref. State sets, xrefs, and layers (especially nested layers) are still a bit odd and it's best to avoid using state sets on complicated scenes. Link to comment Share on other sites More sharing options...
Matt McDonald Posted September 30, 2015 Author Share Posted September 30, 2015 Thanks Scott Link to comment Share on other sites More sharing options...
Tommy L Posted January 19, 2016 Share Posted January 19, 2016 2016 has had a major overhaul to xrefs and it now respects layer visibility in the scene, not the xref. State sets, xrefs, and layers (especially nested layers) are still a bit odd and it's best to avoid using state sets on complicated scenes. Hi Scott, seems youve been on 2016 for a while. How is the stability? Many bugs or is that all ironed out? We're on subscription and on the verge of upgrading, would welcome the feedback. Thanks, Tom. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now