Devin Johnston Posted October 16, 2014 Share Posted October 16, 2014 I purchased an Evermotion plant library Vol.126, I'm running Max 2014 SP5 and when I open certain models I get this warning: "The MassFX authored in this file was created with a newer version of the plugins. Forward compatibility is not supported, so things might not behave properly." I assume this means that these plants were made with Max 2015 and a newer version of MassFX than I have. Question is can I work around this, when I put these models in my scene and convert them to proxies they crash it. They don't do me much good if I can use them. Link to comment Share on other sites More sharing options...
Tommy L Posted October 16, 2014 Share Posted October 16, 2014 I dont think the incompatible MassFX is causing the crash. Link to comment Share on other sites More sharing options...
Devin Johnston Posted October 16, 2014 Author Share Posted October 16, 2014 I don't see what else it could be. Link to comment Share on other sites More sharing options...
Tommy L Posted October 16, 2014 Share Posted October 16, 2014 You should be able to get support from Evermotion, Im sure you wont have been the first to come across this problem. Are you collapsing to proxy prior to merging into a scene? Link to comment Share on other sites More sharing options...
RyderSK Posted October 16, 2014 Share Posted October 16, 2014 You should be able to get support from Evermotion, Im sure you wont have been the first to come across this problem. Are you collapsing to proxy prior to merging into a scene? It's probably this, some of the models are incredibly awkward prepared, with displacement modifier and whatnot. Collapse/Attach, xRef, check pivot point and then xRef. Link to comment Share on other sites More sharing options...
Devin Johnston Posted October 16, 2014 Author Share Posted October 16, 2014 Yes I turn the object into and editable mesh, collapse it down then export as a proxy which is my normal workflow. Link to comment Share on other sites More sharing options...
Zdravko Barisic Posted October 18, 2014 Share Posted October 18, 2014 Are you driving nVidia graphic card? If you still get that warning, you should update Physics plugin for nVidia driver. Link to comment Share on other sites More sharing options...
Chris MacDonald Posted October 18, 2014 Share Posted October 18, 2014 I've had the error before, but it's never caused any crashes for me. Link to comment Share on other sites More sharing options...
Josef Wienerroither Posted October 19, 2014 Share Posted October 19, 2014 The MassFX version warning is just caused by script which checks each Max file during load and looks for the MassFX properties in those files. If the version differs it triggers the warning. MassFX properties get saved with each file, even if you never used MassFX in them ... IMHO not a very cleverly coded solution, but as long as you are not using MassFX in your scenes you simply can ignore those warnings. As Max does'nt crash right at load time when the warning appears, the crash is 100% not related to MassFX. 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