#380110
This is what I have now at work and I am having some really weird texture issues.

Fire usually works, but when I export to render, some textures go to grey.
These are textures within sketchup, not linked MXM.

Also, clip maps don't seem to be work, the image in the clip just goes to green.
#380111
Yes, it (2.7.25 is the actual plugin version) is compatible with SU2013. Regarding the issues you mention, what do you find if you export to Studio and look at the materials & textures that are being written?
#380113
It sounds like a case where SketchUp is either failing to write the image, or is writing a corrupted one. You will find the written images (the ones contained inside the SKP file) in the /textures folder, next to the output MXS.
#380116
I couldn't say, but I've seen it quite a few times (most often with geo-location maps from Google, it seems) before -- it may help to use the "Edit texture image in external editor" button in SketchUp, save the image somewhere, possibly using a different format, and then re-assign the newly-saved image.
#380117
It is a geo-location image. and I did use the edit button, and saved it to an actual location. I also exploded the image and pulled it down to make a volume.
It's weird. I didn't try with a different file type or name. I'll try that tomorrow.

Thanks
#380203
I really have no way of guessing about that. The plugin asks SketchUp to write the image to disk, and if it fails, it fails (I more commonly see that on OSX than Windows, incidentally, though I'm not sure why it should be so). When you say you're saving it with different formats & names, you do mean that after doing so, you replace the texture in the SketchUp material, correct? And that you then save the SKP file, and then re-open it? Just to be sure the new image is actually being put into the SKP. Another idea, if a long shot: have you tried resizing the image before reassigning it? Have you tried using a completely different image, to confirm that it's related to the image, and not somehow to the material itself? You could always try creating a new material from scratch. But I'm just shooting in the dark here, since like I say, it's something that lies outside the plugin's domain.
#380204
I've tried pretty much all of the above. I think maybe the size of the image is too big to export?
I opened a new model and made a small square and applied the same image to it, import image as texture. and it renders.
#380209
i had this problem too recently. A sketchup texture was not exported no matter how i saved it in PS. I only got the constant colour in the render.
I solved it by creating an MXM.

(SU 8/ Plugin 3.0.5)
#380217
creating a basic MXM with the google earth image worked. But now, the trees i use, that have clipmap branches/leaves, don't work.

Does this have something to do with the new "Material Assistant"

Will I need to make MXM of each of the branches/trees to be able to use them in maxwell?
#380221
Thanks, but unfortunately, I have not yet been able to observe any failure with these files. It will not be anything related to material assistants, as the materials being used are all still just using default settings. Whatever the cause for the failure, it is always an option, short of actually creating & linking an MXM, to assign the desired texture directly in the plugin's material editor, by setting Texture > Source to Use Specific Texture, and browsing to the file:
  • Image
Sketchup 2025 Released

Thank you Fernando!!!!!!!!!!!!!!!!!!!!!!!!!!! hwol[…]

I've noticed that "export all" creates l[…]

hmmm can you elaborate a bit about the the use of […]

render engines and Maxwell

Funny, I think, that when I check CG sites they ar[…]