• 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 Import Problems

tgibson

tgibson

Resource contributor
Messages
11,834
Country
us-california
Hi,

I've imported a COLLADA file called terminal.dae from Sketchup and get the problem displayed in the attachment. I click on the ... button of the Diffuse Texture line and this error message pops up. It appears that MCX lists the texture as being in terminal/xxx.bmp (or whatever extension), and this is not a valid path (or the path is being interpreted as a file name alone). Note the forward slash.

Thus there is no direct way to change the file name of this texture.

Also, my Spanish tile jpg file (from Sketchup) is not displayed in the 3D image (should be displaying on that gray roof).

The workaround I've found is to use the Mass Texture editor to remove the terminal/ part of the file name. When I convert the jpg file to a DXTBMP it also now displays on the roof.

Edit: Using latest development release, 12/12/2011

Hope this helps,
 

Attachments

  • mcx_error.jpg
    mcx_error.jpg
    69.8 KB · Views: 490
Last edited:
Hi Tom,

Can you send me the file for debugging?

I think it might be that the direction of the slash is wrong for Windows or so. But I did not change that recently, so I wonder why the problem suddenly appears. But having a model to test with will make solving easier.
 
I've sent a similar file, but it's not unique to that file - it happens to me with ALL DAE files I have created, new or old (if they include textures in the export). If you select a texture in in the Material Editor, when you click the ... button on the Diffuse texture line you get the error.

Thanks,
 
Hi Tom,

I got the file. I can't reproduce the problem directly, but I will do some more testing.
 
Hi,

I did some more testing, but I can't reproduce it yet.

What OS are you using?

And can I ask if other users have this issue as well?
 
I'm using Windows XP, on two different computers - same behavior.
 
I have seen this before,... off and on for quite awhile now,... though I haven't been around or using enough to remember when and how it occurred. But the work around is how I fixed before as well. I'm also using Windows XP.
 
Just to add from my previous reply.... the mass texture editor and the material editor are doing so,... including the last directory location that is.
 
Hi,

I can confirm what Doug and Tom said. I experience the same. Only, I am in a habit of changing the material in the editor straight away because I keep the originals I wanmt to use in another folder.
 
Hi,

Maybe it is a XP problem then, I am developing on Windows 7. Let me see if I can test on a XP machine.
 
Hi,

I got a virtual machine with XP running now and I can confirm that I see the message now as well. Tomorrow I am going to try to fix it.
 
Hi,

Got it fixed now. So in the next development release it will be working.
 
Works great for me now - the slash is now a backslash and it opens fine.

Thanks again,
 
Hi,

Found another little problem, probably related to the change made above.

In the Mass Texture Editor, the files are listed as (for example):

terminal\Roofing_Tile_Spanish.jpg

Which is fine - that's where the exported JPG file is found. But when I change the type to DXTBMP and press Update, the created BMP file is placed into the main folder (not into the terminal subfolder) and is now listed as:

Roofing_Tile_Spanish.bmp

which is correct, but not what I want - I want the converted BMP file to be in the terminal subfolder (as is was displayed originally in the Mass Texture Editor), not in the main folder.

I can force the converted BMP file to be placed into the terminal subfolder by removing the terminal\ from the name listed and changing the target folder to the terminal subfolder, but that's not what I would expect would be required from what is displayed originally.

Hope this helps,
 
Hi Tom,

That is sort of by design. In the mass texture editor you need to specify where you want the files to be placed. Any relative path information is removed in that process. When exporting to MDL files only the texture name is exported by default as well (there is an option to keep the path though).

I could probably change the behaviour so that the tool supports relative paths better, but many parts now work like FS, where only the filename and not the path is given.
 
Hi,

If you are not going to support relative paths in the Mass Texture Editor, then why do you display paths in the texture names? That's what caused my confusion. If only the file name was displayed, then I would understand your approach. As it is, it is just confusing... :confused:

Hope this helps,
 
Here's a picture of the problem. The terminal\ path in the file names makes me assume that any converted texture will go there. Removing that path display would make things clear.

Hope this helps,
 

Attachments

  • mcx_error.jpg
    mcx_error.jpg
    27.9 KB · Views: 499
Hi Tom,

It is supported because the COLLADA file uses the relative path, else your textures would not be found and displayed. But any operation currently works with only the filename. So if you update with the mass texture editor the textures are placed in the folder you indicate.

I'll put it on the todo list to see how this can be made more user friendly.
 
OK, I've added a warning in my Sketchup to FS Scenery tutorial to ignore the path information in the Mass Texture Editor.

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