• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Problem Importing "dae" files to MCX

falcon409

falcon409

Messages
687
Country
us-texas
Not sure what is causing this. I am trying to import a 3D model into MCX to convert to an object bgl. These are sketchup models so as each model is exported from Sketchup there is a corresponding texture folder. Normally importing the dae files to MCX is simple, MCX reads the 3D model along with the required textures and displays the finished model. However now when I try to import I get this:

8:51 AM AssimpReader Error, Error loading unmanaged library from path: Assimp64.dll, see inner exception for details. The specified module could not be found. (Exception from HRESULT: 0x8007007E)

I tried double clicking the 3D file (which displays the MCX Icon) and it does load MCX, but gives me this error message.

The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.

Any suggestions?
 
I suggest doing an online search for api-ms-win-crt-runtime-l1-1-0.dll.

It appears to be a matter of some missing Windows Updates, or a particular missing Visual C++ Redistributable.
 
Hi,

Is there a file assimp64.dll in your MCX folder?
 
Dave_W said:
I suggest doing an online search for api-ms-win-crt-runtime-l1-1-0.dll.
It appears to be a matter of some missing Windows Updates, or a particular missing Visual C++ Redistributable.
Click to expand...
I have had no luck trying to run a Windows Update. . .it simply hangs and never completes the task. I've even run Windows Safe Mode, deleted all the current cache for WinUpdates and restarted Windows to attempt another update with no success. (Using a method outlined by Microsoft).

Also, doing a search for the "api" dll was the first thing I did. I found it, downloaded and attempted to install, but it requires that it go through the Windows Update Process in order to install (which is obviously a problem right now), you can't just download and stick it in a folder somewhere.
 
Last edited:
Hello...

We're files deleted prior to this before this happen? Was the development release working prior to this happening? or was this the first time using this version?
 
Pyscen said:
Hello...
We're files deleted prior to this before this happen? Was the development release working prior to this happening? or was this the first time using this version?
Click to expand...
No files had been deleted and MCX worked fine last week. I also found that in updating to Sketchup Make 2017, it also gave me the error message about the "api" dll file. However SU 2016 does not. . .it works perfectly.
 
Let me double check, I thought the size was not exactly 5000 kB.
 
SU native format is also no longer compatible with versions prior to 2014, I believe, there was a banner in the warehouse site advising artists that models saved to earlier versions would be deleted. Perhaps this is a compatability issue with the current build.
 
Guys, can we stay on topic? The OP gets an error because MCX can't find a dll file. So that has nothing to do with SketchUp versions or anything else.
 
arno said:
Guys, can we stay on topic? The OP gets an error because MCX can't find a dll file. So that has nothing to do with SketchUp versions or anything else.
Click to expand...
Correct. . .SU Make 2016 is fine and works perfectly. Going to the updated SU Make 2017 is when the problem showed up (at least for Sketchup). I simply uninstalled 2017 and everything is fine as far as Sketchup goes.

The larger problem now is that at least some of the problem, specifically the above noted "api. . . ..dll file is one that is installed with a Microsoft Hotfix, however my Windows Update utility has decide it doesn't want to work any more. It consistently hangs during processing and never completes the update process, so I'm stuck until I can get the Updater to work again and that appears to be a real problem based on all the searches I've done and the information gleaned from those searches.
 
Hi,

I double checked but the 5000kB assimp64.dll is OK. I have downloaded the last build myself and it is working fine.

Since the file is in the right folder, it's weird you get an error that MCX can't find that DLL file. I have seen a few error reports like this before, but could never reproduce it.

What is your workflow? Just open MCX and load the DAE file gives that error? Or do you do something else first?
 
arno said:
Hi,
I double checked but the 5000kB assimp64.dll is OK. I have downloaded the last build myself and it is working fine.
Since the file is in the right folder, it's weird you get an error that MCX can't find that DLL file. I have seen a few error reports like this before, but could never reproduce it.
What is your workflow? Just open MCX and load the DAE file gives that error? Or do you do something else first?
Click to expand...
Arno, I open MCX (which by itself works fine)...but loading anything (dae, mdl, bgl) produces the error concerning the Assimp64.dll. If I double click the individual icons for those file types though I then get the error for the "api-ms-win-crt-runtime-l1-1-0.dll".
 
Hello,...

Double clicking on the icons? Which icons are you referring to? Are you referring to the dae file? Just to clarify what you mean
 
Pyscen said:
Hello,...
Double clicking on the icons? Which icons are you referring to? Are you referring to the dae file? Just to clarify what you mean
Click to expand...
Yes, if a file type is attached to a particular program, double clicking on that icon (dae, mdl, bgl) will start the utility (MCX) and load that file. Obviously that's not the way it's normally done, but given the current circumstances I was trying anything I could to get a positive result.
 
Hello,...

The information that I'm finding has to do with Visual C++ Redistributable for Visual Studio 2015 not installed properly or missing...

Have you uninstalled "any" programs or software in the past week? Try reinstalling Visual C++ Redistributable for Visual Studio 2015. Trying to locate a link for it now ...
 
The assimp dll was indeed build with visual studio 2015, so a good idea to make sure the redistributables are installed. I should maybe add check for that.
 
Pyscen said:
Hello,...
The information that I'm finding has to do with Visual C++ Redistributable for Visual Studio 2015 not installed properly or missing...
Have you uninstalled "any" programs or software in the past week? Try reinstalling Visual C++ Redistributable for Visual Studio 2015. Trying to locate a link for it now ...
Click to expand...
Yes, found that information as well. However when installing the 64 bit portion of the install it hangs a up and never completes the process. So while I know it needs that distributable, I'm finding it difficult going right now. I seem to be hitting brick walls no matter what I try. I may give a roll-back to an earlier restore a shot. . .just for grins.
 
arno said:
The assimp dll was indeed build with visual studio 2015, so a good idea to make sure the redistributables are installed. I should maybe add check for that.
Click to expand...

I think so as well;)
 
You must log in or register to reply here.
Back
Top