3DXChange Major Functionality Still Not Working


https://forum.reallusion.com/Topic482760.aspx 		Print Topic | Close Window

By Lord Ashes - 4 Years Ago
I have downloaded the latest version of 3DXChange and was disappointed to find that RL still has not fixed the Export OBJ issues which prevents a major portion of my content from being exported back into OBJ format. Due to this advertised feature in 3DXChange (which is available in PRO version license that I have purchased), I didn't keep the OBJ files for most of my content because I knew I would be able to export it from the Reallusion asset if I needed it.

However, the Export OBJ does not work for a lot of my content. A while back, I opened three issues related to this:

1. In some cases, the content exports but the material and UV mapping is not correct.
2. In many cases, parts of the content are missing.  
3. In a few cases the content won't export at all.

Export to OBJ is a significant function of the paid software (3DXChange) but it seems that RL is not addressing it in their patches.

I tried requesting a temporary Pipeline license so that, if the Export to FBX does not have the same issue, I could use that instead but RL has not provided me with such a license or even responded to my request. Up to this point I have been satisfied with Reallusion and their software but not providing any mitigation or resolution for such a large feature bug for a paid software is not good treatment of loyal customers and RL software users.
By vidi - 4 Years Ago
instead of opening the same content over and over again
let  help you 
By Peter (RL) - 4 Years Ago
Hi Lord Ashes

Have you reported these issues in the Feedback Tracker? If not, please do so and the issues will be looked at. If you are able to provide repeatable steps or supply example models that don't export properly then that will be even better. Thanks.
By Lord Ashes - 4 Years Ago
Yes I have opened these issues with Feedback Tracker. That is what I was referring to when I said that I open three different issues for the three different symptoms. This is also why I am a little frustrated because the issues were opened, sample content for each type of issue was provided, but apparently no resolution was done because even in the latest 3DXChange update, I am still seeing all 3 of the problems.

[Issue 7616] https://www.reallusion.com/FeedBackTracker/Issue/Export-OBJ-causes-part-of-the-content-mesh-to-be-removed-in-the-exported-file
[Issue 7617] https://www.reallusion.com/FeedBackTracker/Issue/Export-OBJ-sometimes-exports-Materials-Textures-incorrectly
[Issue 7618] https://www.reallusion.com/FeedBackTracker/Issue/Export-OBJ-sometimes-creates-a-corrupted-file

I have all my store content backed up locally but because of the Export OBJ feature in 3DXChange, I only have the RL files of my content as opposed to the OBJ files. I would like to have the OBJ files because I would like to mod some of the content but currently I cannot because I can't export by own content.

As I said, I even suggested that RL could issue me a temporary Pipeline license (I currently have Pro) so that I can try if the Export FBX has the same issues or not. I did not get any response to this suggest but I am guessing RL does not want to do that because it would be difficult to revoke such a license after the Export OBJ function has been fixed.

Edit: Added links to the Feedback Tracker issues
By Lord Ashes - 4 Years Ago
vidi (5/9/2021)
instead of opening the same content over and over again
let  help you 


Vidi, you may have misunderstood what wrote (or I may not have been clear). I initially posted in this forum to see if there was any trick that I was not aware of to make the Export OBJ work correctly. Getting no answer, I opened up 3 tickets in the Feedback Tracker for this problem. I opened up three individual tickets because, without knowing the code, I don't know if the issues have three individual causes or if they are all symptoms of the same root cause. RL responded to the tickets asking me to provide sample content that demonstrated each issue. I provided such content and, if I recall correctly, got a confirmation that it was received. I don't recall (without looking back) if they confirmed that they were able to reproduce the problem.

After the recent 3DXChange update, I re-tested the issues and the issues still don't seem to be addressed. So I returned back to the forum and opened this (one) post. 
By Peter (RL) - 4 Years Ago
Lord Ashes (5/11/2021)
Yes I have opened these issues with Feedback Tracker. That is what I was referring to when I said that I open three different issues for the three different symptoms. This is also why I am a little frustrated because the issues were opened, sample content for each type of issue was provided, but apparently no resolution was done because even in the latest 3DXChange update, I am still seeing all 3 of the problems.

[Issue 7616] https://www.reallusion.com/FeedBackTracker/Issue/Export-OBJ-causes-part-of-the-content-mesh-to-be-removed-in-the-exported-file
[Issue 7617] https://www.reallusion.com/FeedBackTracker/Issue/Export-OBJ-sometimes-exports-Materials-Textures-incorrectly
[Issue 7618] https://www.reallusion.com/FeedBackTracker/Issue/Export-OBJ-sometimes-creates-a-corrupted-file

I have all my store content backed up locally but because of the Export OBJ feature in 3DXChange, I only have the RL files of my content as opposed to the OBJ files. I would like to have the OBJ files because I would like to mod some of the content but currently I cannot because I can't export by own content.

As I said, I even suggested that RL could issue me a temporary Pipeline license (I currently have Pro) so that I can try if the Export FBX has the same issues or not. I did not get any response to this suggest but I am guessing RL does not want to do that because it would be difficult to revoke such a license after the Export OBJ function has been fixed.

Edit: Added links to the Feedback Tracker issues


Hi Lord Ashes

Just to give you an update;

After discussion with the development team they believe the issues reported in FT: 7616 and 7618 have now been fixed in the latest version 7.8.

The issue reported in 7617 is still under investigation and hopefully a fix for this will found soon.