Your post is missing information about the DAE file, the settings for the texture path, whether you have the textures in the required folder, etc…
but how can i import the dae file with texture in sketch up?
SKP file tire.skp (4.9 MB)
Use this model until I do some more tests with your DAE file for direct import with textures into SketchUp for Web.
Hi @Colin,
please tell me if you know if there are (still?) problems with UVmap when importing DAE, 3ds files into SketchUp for Web (Free, Go)?
Same DAE file imported in SketchUp for Web (I added the texture after import in Material)
and
SU2022 (no editing of the material was necessary)
OH I am with the go version, so if i want my metarial, i just apply the whole texture (uv mapping ver)to the model in sketch up?
//edit
Thanks to Daniel, the solution is - How can I import dae model with texture in web sketch up - #13 by daniel_pidcock
No, it doesn’t work like that because in SketchUp for Web (Free, Go) once imported, the model loses its UVmap.
In Go, you can add the texture in Material, but it doesn’t know the original coordinates and will only apply it by repeating it.
That’s why I asked Colin if he knew about the problem with importing DAE files and their UVmap.
Importing into the web version seemed not to bring in the material. Filling the faces with a material looked ok.
I couldn’t figure out what name to give the material, to try the original DAE.
Thanks, Colin!
texture . png
at line 99 in the DAE file
It didn’t import the texture and the UVunwrap info, so there’s no point in adding the texture to the material slot.
I had searched for .png and .jpg, not sure why I didn’t find that line.
Exporting the posted JPEG as PNG, and naming it right, then imported the DAE looking ok.
If you create a zip file containing the .DAE file and texture.png together, then import that into SketchUp for Web, it brings the texture in:
Thank you, Daniel!
And I hadn’t even uploaded dozens of models to Sketchfab before by archiving the model and PBR textures in a ZIP file.
Does SketchUp use or honor the ".zae"
file type?
Not currently as far as I can see. However according to https://www.khronos.org/files/collada_spec_1_5.pdf it is a zip file, so renaming it to .zip should work, as long as there is only one .dae in the archive. Adding full support for .zae files containing multiple .dae files would need some code changes, is it a common requirement?
I would guess not common. And how would the separate DAEs be imported? as components?
I was just wondering if the import dialog could filter by “*.zae” and the importer allow the import (knowing it was a zip archive.)
I mean is ZAE support at all a common requirement?
Because if all is wanted is the hack of pulling in the first .dae in a .zae, the file can be renamed to .zip and that will happen today.

I mean is ZAE support at all a common requirement?
I know what the question was and could only offer a guess based on what I’ve seen described by users in the forum talking about Collada import and export. (Meaning, I haven’t done much DAE import myself except for cursory tests.)
My question about .zae
was prompted by the Copilot AI telling me there was such an archive, which I did not previously know.

My question about
.zae
was prompted by the Copilot AI telling me there was such an archive, which I did not previously know.
Got it, thanks.
My impression from web search is that zae is not in use much, in which case adding partly working support to sketchup is a bad idea IMO when we have a decent workaround (rename to zip). I’ll definitely keep an open mind on this though if we discover more demand.

… we have a decent workaround (rename to zip).
Acknowledged. But I do notice that zip is not listed as an import filetype in the Import file open dialog.