Meshmixer won't launch on VMs

[Anonymous]

I can install and launch on physical PCs, but when trying to launch on a VM of Windows 10 64-bit Meshmixer generates 'A software problem has caused Meshmixer to close unexpectedly'. Has anyone got this launching on a virtual machine at all????

[Mark.Lancaster]

@Anonymous

Welcome to the Autodesk User's Community..

Most times this points to a Microsoft C++ issue on your machine.  However please review the Windows Event logs for errors and warnings around the time this happened.

[Anonymous]

It's not C++, I've ran through that fix uninstalling and reinstalling. The key point is that the same build is used for physical and virtual machines with the same runtimes. The app works on physical, but not virtual. Same launch problem/pattern occurs with release 3.3 too.

Paul

[Mark.Lancaster]

@Anonymous

Well computers are not the same..  Just because it works on a physical machine doesn't mean it works on another physical or VM.   Did you review the event log like I stated earlier?

[natasha.l]

Hello @Anonymous, 

This may not function on a virtual machine if it is not listed as being supported >here<. Then this means it has not been tested by Autodesk's development & cannot be formally supported with this setup. 

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Anonymous]

Zero events generated to the event log. The minidump log states 'Error accessing UPI repository in the 64-bits registry'.

[natasha.l]

Hello @Anonymous, 

I will move this post over to the Meshmixer forum to see we find members that have set this up on a Virtual Machine before. 

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Anonymous]

Hmm, seems to me that it's relevant to know something about your VM installation attempt:

What's your host host system?

What's your VM?

Which version of MM do you try to install?

Different VMs on different hosts provide different virtual resources. The only versions of MM available atm are 3.3 and 3.5.

3.3 needs less resources (except the Autodesk ViewCube same functionality as 3.5.)so you might try this version as a first step...

[Anonymous]

I get same results with 3.3 and 3.5.
It's a Hyper-V Hypervisor on Citrix VDI running Windows Server 2016.
Hope that helps.

[Anonymous]

Sorry, I 'm not experienced on Win Server installs...

Might be some virtual GPU drivers issue:

Here I have a host macOSX system (HighSierra (10.13.6)) and a guest (WIN 7 64) via VMFusion 7.1.3. 

VMFusion isn't supporting HighSierra completely (I'd need to update VMFusion).

Installing MM 3.5 on this outdated handshake:

As there's no support for latest (GPU-) drivers I need to set MM to BasicRendeering.

To do this you might try this:

- If MM's splash screen launches without a crash, go to menu: File/Preferences. In its General tab and its View section enable EnableBasicRendering. Shut down MM and launch it again.

- If MM crashes before the the splash screen, call C:\Users\User Name\AppData\Roaming\Autodesk\meshmixer.ini (you need to replace User Name of course) via CommandPrompt, search for "EnableBasicRenderingV3", set this line from "=false" to "=true" and save. Now try to launch MM.

BasicRendering limits rendering and previews of certain tools as there's no transparency any more. But if it works it  points to to some limited graphics support of your VM.

[Anonymous]

Thanks for the suggestion but it's made no difference editing that ini file and it crashes before the splashscreen

[Anonymous]

Do graphics support Qt5?