Exporters: Add support for 3dsMax 2020

[jarnoburger]

I know i could get into nothing when trying the plugin for 2019 in 2020..
But its not working.. Hehehe :).

[Drigax]

Thanks, sounds like we need another project to target 3dsMax 2020.

@kcoley do you have any insight as to what typically differs for the Max API assemblies for each version?
I'll most likely go off of your previous work for adding support for Maya2019 and looking at the differences between the other Max2Babylon projects.

I hope to get to this by the end of the month, as we should support the latest and greatest 3dsMax versions, but if anyone wants to take this on in the meantime, feel free.

[susares]

Hi,
there have been some changes in the .Net SDK wrapper resulting in the above error message.

@Drigax there are no real insights when it comes to changes in new versions of the SDK. Sometimes Autodesk documents it the rest is fixing compilor errors. Basicly how i did the 2019 port.

I started to work on a 2020 port but did not push anything yet.
This is due to a critical error in the current 2020 .Net SDK wrapper resulting in 3dsmax crashing without error messages, stack traces or exceptions.
We have filed a bug with Autodesk that is currently under investigation and escalated to their engineering team. As soon as this bug is fixed a 3dsmax 2020 port should be in sight in a timely manner.
I also mentioned BabylonJS during the communiction with Autodesk on how it affects development.

The bug seems to be stuck rather deep in the .Net SDK internally affecting basicly IGame interface related classes/methods. Once you call them 3dsmax trips over and crashes a view cpu cycles later.
According to Autodesk IMaterial seems to be another candidate that shows this behavior. So any plugin written with the .Net SDK and using IGame or IMaterial interface are doomed currently.

[sebavan]

@susares do you happen to have a public link to the issue ? or is it only kept internally on their side ?

[susares]

@sebavan sorry I don't have a public link. just the internal API support and a internal change request number that it resulted in. I will comment back here once I get more information from Autodesk.

[Drigax]

Hi @susares, is there any update from Autodesk with the bug report?

[susares]

@Drigax magical coincidence. We just got confirmation from Autodesk, that the issue is being sorted out and scheduled for the next Update.

[sebavan]

Amazing, can not wait to try it :-)

[Drigax]

@susares, do you know when we can expect Autodesk to ship the next update with the fix?

[susares]

@Drigax Nope sadly not. If it works like Max 2018/2019 should be around end of August to September.

[Drigax]

closing this issue until 2020.2 is released.

[CusthomeDev]

Hi @Drigax,

3DS Max 2020.2 have been released a week ago.
Is it possible to release your exporter to support it ?

Thank you in advance. You make a great work

[Drigax]

Hi @magelanOpenSource , I wanted to follow up to update that we finally have full support for Max 2020 thanks to @susares's great work via #623!