• 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.

DAE textures not importing

G

gww53

Messages
172
Country
us-newyork
I know I've seen this problem addressed in an old thread, but can't find it.

I've been away from sketchup to fsx conversion for a month or two, and I'm sure I'm doing something wrong, but I can't figure it out.

My sketchup model is exported as DAE, but when I import to MCX, I get only checkerboard faces rather than textures, and an error message that says the jpg textures are not loading...but they are in the folder with the DAE. If I export the checkerboard "failed to load" DAE project to a mdl file, the "missing files" appear, and the mdl is fine,and the textures are present!!!

I've tried loading dozens of older dae exports, all with the same checkerboard result. But I can load the mdl from any of those projects with no problem. Somehow, I've screwed up the DAE import function/process.

What do you suppose I'm doing wrong (this time....).
I have the problem with a 2 week old download of MCX and yesterday's version of MCX.

I"ve attached images of the dae import, the error file, and the image after conversion of the checkerboard image to mdl by mcx

I've tried check/uncheck "texture faces render mode". If I check "faces render mode", the surfaces are all white rather than checkered, but still no textures.

Sorry to be so dense, somehow I've set a path wrong somewhere, I guess.

Thanks in advance, for this help, a terrific set of tools, and for all of you who share your knowledge with "lurkers" like me

Gary
 

Attachments

  • mdl import.jpg
    mdl import.jpg
    98.6 KB · Views: 570
  • message and files.jpg
    message and files.jpg
    104 KB · Views: 553
  • dae import.JPG
    dae import.JPG
    71.9 KB · Views: 529
Hi Gary,

By default SketchUp will put your textures in a folder with the name of the DAE file, not in the same folder as the DAE file. Inside the DAE file that folder is given as part of the texture name.

A while ago ModelConverterX has been improved to use this information correctly. So I think that is why your textures don't load now.

But when exporting to MDL the files names will still be stored in the MDL, so if you place the texture in the right FS texture folder they will indeed work fine in FS.
 
Thanks for the quick reply.

Yes, in the past I had to move the DAE file into the "subfolder" with the textures to display the textures in MCX. But now, whether i put the DAE in the texture folder or the "parent" (or even the root above that) I have no textures displayed in MCX.

What seems so odd is that if I export that project (with no textures) to a mdl file, MCX now finds the textures and creates a perfect model!!!

Until I figure this out, I guess I'll just convert to the mdl file then change to DDS, rename textures, etc.

I have over 350 Sketchup buildings that I've converted to mdl and used in FSX happily over the past few years, and after exploring about 50 of the old ones, none of them can display texture files on the DAE models.

Time to start exploring what else I've done on this computer recently!
Thanks, Gary
 
Hi Gary,

I see in your screenshot of the event log that the path looks a bit weird. It seems the space is converted as %20, maybe that is the problem. I'll take a look at that.
 
Hi,

I can confirm that this is a bug when you use a space in the model name. I never use spaces in filenames myself, that's why I didn't notice it earlier. I am going to try to fix this bug soon.
 
Hi,

I have now fixed the bug. So if you download the development release again in about 1 hour, it should work.
 
Hi,

You probably didn't encounter this bug before because the export process from GMAX (for example) doesn't allow spaces in the MDL filename, as I remember.
 
I guess it is my habit as a programmer that I never use spaces in my filenames, I always use an underscore.

But maybe I should more often. It is often a great way to break a tool :)
 
Same here, Arno! I seldom use filenames or paths that contain spaces. This is undoubtedly a holdover from my decades of DOS experience... :D
 
Well, the new version does fix the error. But, I've looked and nearly all of my projects have spaces in them (item 873,452 that I've learned from you all) and they were working. I found a few items with no space--they didn't work either.

My experience is that it's usually something I did....But the new version/installation seems to fix it an I very much appreciate your help.

Gary
 
Recommend Updating the Version # of MCX

I just spent several hours trying to figure out why my MCX wasn't working as before.

I had updated to 1.3.0, the version before the bug fix. I had no idea there was a problem until I started using it again recently, and had the same problem as the original poster.

I though I had the most recent version, but found out after downloading tonight that the version 1.3.0 was actually updated and yet held the same version number as my earlier version.

After d/l and installing the newer version everything is working fine again. I would recommend that the most recent sable version be renumbered 1.3.1 or something to show it was since updated from 1.3.0.

Bryan
 
Hi Bryan,

I guess you had a development release before and these are labeled as so in the about box. There is only one version of a stable 1.3. The development release is now 1.4.
 
OK thanks arno...I guess I got confused as mine said 1.3 and the version I d/l'ed as the most recent was 1.3.

Anyway, more to the point, I used the newest version over the past few days and everything it working well.

thanks.
 
You must log in or register to reply here.
Back
Top