Author Topic: Error mtl-XML file; texture not found/not accessible problem  (Read 2724 times)

2018-01-08, 20:12:34

kpulka

  • Users
  • *
  • Posts: 2
    • View Profile
Hey
I'm receiving such error after trying to render my file. No issue if I don't have any texture though. Any idea what is the problem about?

2018-01-08, 22:27:18
Reply #1

blanchg

  • Moderator
  • Active Users
  • ***
  • Posts: 373
    • View Profile
    • Blender exporter for Corona
Not sure without some more info, but the message says concrete2 but the files seem to be called concrete1.

Does the texture file exist at the path you are showing?

2018-02-08, 19:14:11
Reply #2

kpulka

  • Users
  • *
  • Posts: 2
    • View Profile
Sorry for late responding. The issue is still unsolved.
I've created new scene where I use corona since begging (previous one was too complex).
Now I use just one texture which I selected from bitmap tab so I'm sure the path is right.
But same message is still on.
Blender 2.79
Corona exporter 7.5.2

2018-04-19, 11:28:13
Reply #3

spenrobert

  • Active Users
  • **
  • Posts: 21
    • View Profile
I have this same error. I have it on the very first image texture I tried to upload. I can't use Corona I guess.

2018-04-19, 11:51:04
Reply #4

blanchg

  • Moderator
  • Active Users
  • ***
  • Posts: 373
    • View Profile
    • Blender exporter for Corona
If you can provide the log for this, confirm in the material output files that the path is correct etc as this is something that works.

2018-04-19, 16:24:28
Reply #5

rigveda

  • Active Users
  • **
  • Posts: 13
    • View Profile
Hey
I'm receiving such error after trying to render my file. No issue if I don't have any texture though. Any idea what is the problem about?

simply del the mat and create new.
Or The best way to work(I use this all the time) use node material and apply texture files again. hope this helps.

Oh make sure have set output path in render-panel. Almost forgot try running blender "run as admin" sometime it helps.
« Last Edit: 2018-04-19, 16:34:06 by rigveda »

2018-04-20, 13:15:24
Reply #6

Zorian

  • Active Users
  • **
  • Posts: 49
    • View Profile
Hey
I'm receiving such error after trying to render my file. No issue if I don't have any texture though. Any idea what is the problem about?

I've got the same issue when I'm using Corona 1.7.3. for some way the exporter is writing the path like:

E:/CGstuff/textures_concrete/concrete2.normal.jpg

the previous version writes the path with reversed flash:

<image>D:\Dysk_google\azrstudio\Projecten\Parijsch Culemborg\Glowne_pliki\EXTERIOR\textures\Am_Blender_V1_008_trunk_color.png</image>
      <bumpStrength>1.000000</bumpStrength>
    </map>
  </mapDefinition>
  <mapDefinition name="Image_Texture.001_2279793449496_1524197680">


« Last Edit: 2018-04-20, 13:24:21 by Zorian »

2018-05-10, 06:41:24
Reply #7

lacilaci

  • Active Users
  • **
  • Posts: 757
    • View Profile
I have the same problem. If I put any texture on material or any type of hdri, it will give me this fatal error file not found/accessible.
I tried 2.79 2.79a 2.79b and 2.79.4.
Different corona exporter versions and different types of textures and tried to relocate those textures to different places/drives it still won't render.

2018-05-10, 07:38:13
Reply #8

Sanekum

  • Active Users
  • **
  • Posts: 42
    • View Profile
Same problem, maybe it's Corona Standalone problem, not exporter

2018-07-23, 14:36:17
Reply #9

aleksandera

  • Users
  • *
  • Posts: 1
    • View Profile

2018-07-23, 22:28:32
Reply #10

blanchg

  • Moderator
  • Active Users
  • ***
  • Posts: 373
    • View Profile
    • Blender exporter for Corona
The paths either way produce the same error on all platforms so there is nothing to be fixed yet.  Waiting on a bug fix from the Corona team.

2018-07-26, 10:40:14
Reply #11

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 8860
  • Turning coffee to features since 2009
    • View Profile
Hi,
we have part-time guy to work on this now (started this week). Lets hope he learns the codebase fast ;))
Rendering is magic.
Private scene uploader | How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2018-07-27, 10:23:51
Reply #12

andreimd87

  • Active Users
  • **
  • Posts: 11
    • View Profile
Hi,
we have part-time guy to work on this now (started this week). Lets hope he learns the codebase fast ;))

lets hope :)

2018-08-04, 00:22:36
Reply #13

Owin

  • Users
  • *
  • Posts: 1
    • View Profile
Hi,
we have part-time guy to work on this now (started this week). Lets hope he learns the codebase fast ;))

Phew, thanks god

2018-09-02, 02:00:24
Reply #14

StefanVisser

  • Users
  • *
  • Posts: 3
    • View Profile

2018-09-03, 09:43:58
Reply #15

Zorian

  • Active Users
  • **
  • Posts: 49
    • View Profile
not really. but there is a solution to use new builds of corona with the exporter. You need to keep Corona 1.6 for creating materials and after creation switch in settings to use Corona 1.7 or above for render.

In this way you can make renders on new build which are faster. Also Blanchg is working with improving export time of particlesettings - and first test was really promising. To export genereted water with foam, exporting time decreased from 48+h to 5 minutes but causes problems with linked objects.