Community
3ds Max Forum
Welcome to Autodesk’s 3ds Max Forums. Share your knowledge, ask questions, and explore popular 3ds Max topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

send to max/send to maya not working

3 REPLIES 3
Reply
Message 1 of 4
Anonymous
1190 Views, 3 Replies

send to max/send to maya not working

I have searched for a long time and found some useful information, but still send to max/send to maya are always greyed out.

 

I know about the syncfg files, and that they must both point to current (or the same) versions of each application.

 

Here is my original max syncfg file -

 

"<?xml version="1.0" encoding="UTF-8"?>
<SynHubConfig SchemaVersion="1.0">
<Application Name="3ds Max" StringVersion="3ds Max 2019" NumericVersion="2019" ExecutablePath="C:\Program Files\Autodesk\3ds Max 2019\3dsmax.exe" Architecture="x86_64" />
</SynHubConfig>

 

And here is the edited Maya file that I created -

 

<?xml version="1.0" encoding="UTF-8"?>
<SynHubConfig SchemaVersion="1.0">
<Application Name="3ds Max" StringVersion="3ds Max 2019" NumericVersion="2019" ExecutablePath="C:\Program Files\Autodesk\Maya2019\bin\maya.exe" Architecture="x86_64" />
</SynHubConfig>

 

In Maya, the send to max option does not exist/show up. Only "send to unity" or "send to unreal"

 

In Max, the send to maya option is there, but the sub-menus are all still greyed out.

 

I cant think of anything else to try and was hoping someone here might be able to give me pointers to get it working.

 

BTW - Here is the original Maya syncfg file that I edited -

 

 

<?xml version="1.0" encoding="UTF-8"?>
<SynHubConfig SchemaVersion="1.0">
<!-- Schema version 1 description
The document must be contained in a "SynHubConfig" element, with the
SchemaVersion used.

The root element can contain an arbitrary number of "Application" elements,
each describing an appliaction that will be known to programes using SynHub.

The "Application" element is made of a few attributes:

Name [String]: Application name (e.g.: "Softimage"). Case is important.
The name can contain spaces (e.g.: "3ds Max" ).

StringVersion [String]: Describes the version in a user-readable way
(e.g.: "2011 extension 1 beta 3"). Will not be interpreted by the
application but may end up being displayed in an information panel.

NumericVersion [String]: Used for sorting, e.g. finding the latest
application. Must be an integer of the form a.b.c.d. The number of
levels has a limit of 4 but there can be fewer (the others are understood
to be zero).

Architecture [String]: x86_32 or x86_64. The executable's target
architecture.

StartWrapperPath [String]: Optional. Path for a wrapper script/executable
to use when starting the executable. This is to accomodate situations
where parts of the configuration are made in wrapper scripts to set
environment variables before launching the program per se.

ExecutablePath [String]: Path for the executable. Can be relative, in
which case the path is relative to the config file's location.

IconPath [String]: Optional. Path to an icon that can be used to
represent the application in a user interface.
-->
<Application
Name="Maya"
StringVersion="Autodesk Maya 2019"
NumericVersion="2019"
ExecutablePath="__EXECUTABLE_PATH__"
Architecture="x86_64"
/>
</SynHubConfig>

 

Since it had no path I did the edit and still got no result.

 

Thanks very much for taking a look.

 

Sam

 

3 REPLIES 3
Message 2 of 4
Anonymous
in reply to: Anonymous

Ugh - I posted the wrong edited file for the the Maya syncfg file.

 

This is the one I created (and that still does not work) -

 

<?xml version="1.0" encoding="UTF-8"?>
<SynHubConfig SchemaVersion="1.0">
<Application Name="Maya" StringVersion="Autodesk Maya 2019" NumericVersion="2019" ExecutablePath="C:\Program Files\Autodesk\Maya2019\bin\maya.exe" Architecture="x86_64" />
</SynHubConfig>

 

Thanks.

 

Sam

 

 

Message 3 of 4
dominique.bouthillette
in reply to: Anonymous

Hey @Anonymous, thanks for taking the time to help document this behavior.

 

Looks like this is a known issue that the development team is aware of and looking into. I will make a note in our internal database for the team with the useful information you've provided here.

 

As an alternative, you can export scene elements as an FBX:

  1. Navigate to File > Export 
  2. Select FBX (*.fbx) from the drop-down.
  3. Import the file into the desired software.

 

Thank you!

 

Please Accept as Solution if a reply has helped resolved the issue or answered your question, to help others in the community.

Kindest regards,


Dominique Bouthillette
Principal Specialist, Industry Support & Escalation
Entertainment & Media Solutions
Message 4 of 4
hagen.deloss
in reply to: Anonymous

@Anonymous 

 

Any thoughts on @dominique.bouthillette 's previous post? It would be helpful if you had time to give an update, that way other Community Members can benefit from your process 😄

 

Please select the Accept as Solution button if a post solves your issue or answers your question.

 

 



Hagen Deloss
Community Manager | Media & Entertainment
Installation & Licensing forums | Contact product support | Autodesk AREA


 

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report