It turned out that fully supporting shininess in combination with BSDF Shaders is more complicated on the Importer side. Therefore i have removed import of shininess for Blender 2.80 and i will take care of this for Blender 2.81 the today's quickfix still needs approval though.

this are actually 2 bugs and one missing feature.

@Gaia Clary (gaiaclary) any more to do here?

For the record, if matrix and the others are present, then both should be applied by the COLLADA software. It's not a multi-representational option in other words. Second, regarding:

@Mike Lima (lunarbase) Hi, there. If you still are interested in this issue, could you please try with the next Blender 2.80 daily build (28-may-2019) if the issue is fixed? I am not entirely sure if the camera behaves as expected now. It is unclear to me what you mean by this:

@Daniel Balster (dbalster) The Blender 2.80 exporter now has 2 options for exporting transforms either as "Matrix" or as "Decomposed". The restrictions from older Blender releases no longer apply.

In T63692#666017, @Gaia Clary (gaiaclary) wrote:

@Francesco Sorrentino (zeirus) : Can you provide a demo blend file so that i can be sure i am inspecting what you actually mean and not what i think that you mean ? Thanks!

@Francesco Sorrentino (zeirus) : Can you provide a demo blend file so that i can be sure i am inspecting what you actually mean and not what i think that you mean ? Thanks!

sorry. Easter holidays stepped in between :)

Ops... i completely forgot about this one :( I guess we can get this to work in 2.80 :)

@Gaia Clary (gaiaclary), seems this slipped through the cracks. Is it still relevant for the 2.80 with the new instancing based on collections?

already fixed properly by Brecht

Yes true no problem

I have talked with Kent online and he clarified that the issue has already been resolved. So i close this ticket now.

@Gaia Clary (gaiaclary) yes thanks.
@Philipp Oeser (lichtwerk) I did inspect deeply and they already fixed. Make sure daily build is today March 19, 2019 not use previous of January 2019 on old Blender 2.80 beta. Please make sure daily build is today (March 19, 2019) https://builder.blender.org/download/
For Macintosh Mojave MacOS 10.14.3
May I have your document .blend please also .dae too.

@Kent Davis (mac4kent) Wasn't this issue already solved in https://developer.blender.org/T61122 ?

@Gaia Clary (gaiaclary) : could you check on this? Not sure what changed here in 2.8...

This patch now has been replaced with a more complete fix for blender 2.80.
Thanks again for reporting this issue! This was truly a good find!

thanks for the patch. I took a look at this and i found that actually the shader value is not a color but a factor, so the function returns completely wrong data. So actually Collada should not export a specular color but a specular factor. I will add a fix for this.

This issue has already been fixed in the master branch (for Blender 2.80). I also believe that this particular issue has been there since ever. Maybe back porting the fix to 2.79 might not be too important?

I also have this same issue.

(Messed up these comments forms default to Change Status: Resolved!)

YesI show you example of a collada file with multiply materials/textures that actually displays correctly in Mac, Yes.
Blender 2.79b is fine no error.

@Kent Davis (mac4kent): thx for checking

@Philipp Kant (philipp) Allright I see you say "Only selected UV Map" I click make uncheck then export. Still same problem.

Just one more thing: Have you tried unchecking "Only selected UV Map" under Export Collada Texture Options?

We talk about Materials:
One can be show (Original).
Two and Three doesn't show

@williams (williams) I already put date (January 21, 2018) I show you youtube https://youtu.be/wntTiNXQCgM
@Philipp Kant (philipp) I did not say import. I say Export.

subscribing @Gaia Clary (gaiaclary) here to comment on this (not sure for example if something like T33744 still applies....)

Have you checked importing that .dae back to blender?
(Since you seem to be judging this by inspecting in the MAC filebrowser)

@Kent Davis (mac4kent): Blender uses the same codebase on the Mac as other platforms. There may be sligt differences caused by differences in GPU's and other things, but Blender is basically the same on Mac, Windows and Linux. For this reason, the platform (Mac) is very unlikely to be the cause of most bugs.

I show you youtube. https://youtu.be/wntTiNXQCgM
Please do it use Macintosh not use Windows.

Did you use Macintosh?

@Gaia Clary (gaiaclary) Sure, but the thrust of this (COLLADA) ticket IS losing primitives. The materials are lost because the primitives are discarded @Trevor Glauz (TSGlauz) says this defect is something core to Blender.

Blender should not loose vertices, edges or faces on import, at least not with Collada.

In D4187#94721, @Trevor Glauz (TSGlauz) wrote:

Removing duplicate edges/faces is just how blender works since it is considered invalid data. You can have duplicate vertices, though. And with duplicate vertices, you can overlap faces that use entirely different vertices that sit in the exact same positions. You can also duplicate triangles into separate meshes and overlap them that way.

Removing duplicate edges/faces is just how blender works since it is considered invalid data. You can have duplicate vertices, though. And with duplicate vertices, you can overlap faces that use entirely different vertices that sit in the exact same positions. You can also duplicate triangles into separate meshes and overlap them that way.