Mixer 2020 Mesh import failed

Answered

February 28, 2020 09:22

Hi there,

i'm trying out new Mixer 2020 but i received a "Mesh import fail" message if i try a custom obj but even the internal Shaderball. Importing 3D assets from Megascans does the same.

I'm on Mac with 2 Geforce 1080ti, and i have the log if needed but i don't see here how to attach it, and it's too long to paste.

Hope you can help as i'm pretty excited about this new release.

cheers

Marco Iozzi

Comments

18 comments

Zunaira Elahi

February 28, 2020 10:07
marcoiozzi please submit a support request for this issue here:

https://help.quixel.com/hc/en-us/requests/new

and please follow these guidelines when filling the form: https://help.quixel.com/hc/en-us/articles/360006094198-How-can-I-reach-out-to-Quixel-Support-

Please do attach your Mixer log file in your request. You'll find it at the following locations based on your OS:

Windows

C:\Users\<username>\AppData\LocalLow\Quixel\Quixel Mixer\Player.log

Mac OSX

/Library/Logs/Unity/Player.log
0

Comment actions Permalink
Millennium Mike

March 02, 2020 08:07
I also have the exact problem.
No meshes will load apart from the plane.

Quixel - you should get this fixed ASAP! and not simply respond that we as customers have to submit a support request when the "hyped" product doesn't even work!
0

Comment actions Permalink
dnest

March 02, 2020 16:29
I have the same issue as well, no meshes will load.
0

Comment actions Permalink
Zunaira Elahi

March 02, 2020 17:03
We can only solve the issue if we're certain of what's causing it. In order to do that we need your respective log files. We do not encourage users to share their log files on the forum, hence the request to log a ticket via the support form. Thanks for your understanding.
1

Comment actions Permalink
Jonathan (Community Manager)

March 02, 2020 17:12
Millennium Mike I understand your frustration, but please note that demands to fix the software we're providing - free of charge - without cooperation on your end to assist us will be a fruitless exercise. Please be certain to follow Zunaira Elahi's directive and e-mail your log file to us so that we might be able to troubleshoot and resolve this problem.

Without log files there's very little we can do to help. Thank you in advance!
2

Comment actions Permalink
dnest

March 02, 2020 17:27
Hope this helps,

Log file uploaded, thank you!
0

Comment actions Permalink
marcoiozzi

March 02, 2020 17:30
my Log was previously submitted, hope this helps and hope we'll have a working version soon,

"glad" I was not alone with this problem, cheers

marco
0

Comment actions Permalink
Millennium Mike

March 02, 2020 21:44
I am not demanding anything. You have rolled out new functionality that doesn't work. Given you are presumably promoting your new release it makes sense to get a fix done quickly before frustrating more people.
-3

Comment actions Permalink
Jonathan (Community Manager)

March 02, 2020 21:46
Millennium Mike As I mentioned previously, please e-mail your log file to us so we can assist. Thank you for your understanding.
0

Comment actions Permalink
ahurig

March 04, 2020 09:26
What is really strange is that it works on a MacBook Pro Retina late 2012 and does not on an iMac Pro 2020 like x10 000 more powerful.

Could it be related to the graphic card? (I sent a log file too)

I'm waiting for the fix sooo bad. What I saw on my MacBook was bloody good.
0

Comment actions Permalink
ahurig

March 10, 2020 11:22
Hey guys, any news about the issue?

Can't wait to test it on my powerful setup 🤩
0

Comment actions Permalink
marcoiozzi

March 10, 2020 11:26
Hey Ahurig,

i was told we have to wait for a new release of the software, and they could not give me an ETA unfortunately.

You're not alone on this,

hope this helps,

cheers

marco
0

Comment actions Permalink
ahurig

March 10, 2020 15:50
Thx Marco for the feedback!

Can't wait for the fix as what I saw on a low power computer was amazing!
0

Comment actions Permalink
Bryan

March 22, 2020 16:35
They roll out a new update some days ago.. but the problem still remains with import mesh. :/
0

Comment actions Permalink
Lumes

March 26, 2020 15:19
I also had a problem with loading meshes. It stalled my system and then Quixel crashed. I lowered the working resolution, then I could load custom meshes.
0

Comment actions Permalink
Som

May 30, 2020 01:14
I have this issue on a late 2009 Mac Pro running High Sierra (10.13.6), 2xXeon 8-cores, Radeon RX Vega 64 (8GB), 64GB RAM.

I do not have this problem with my late 2013 Mac Pro running Mojave (10.14.6), 6-core Xeon, 2xAMD FirePro D700 (12GB), 128GB RAM.

I've only just today been able to get Mixer to open/login on the 2009 Mac Pro (after months of trying to get it to work), and discovered it will not load any meshes except the default plane. So maybe the issue has to do with the version of macOS? I believe the Vegas 64 is a more powerful card than the FirePros.
0

Comment actions Permalink
lumpy668

October 21, 2020 23:48
Any news? It's being 8 months and nothing has happened; I still have the same problem, any solution?
1

Comment actions Permalink
Jonathan (Community Manager)

October 21, 2020 23:55
Hi lumpy668 - there is no news on this front as we haven't released an update specifically to address it yet. We'll likely be resolving this in a future update to Mixer, but I can't speak to when it will happen. This thread has largely run its course so we'll be closing it for now. If you do continue running into issues, please e-mail support@quixel.com and we'll be happy to assist you however we can.
0

Comment actions Permalink

Post is closed for comments.

Comments

Windows

Mac OSX