Chaos Corona Forum
General Category => Porting and API => Chaos Corona for Blender => Topic started by: kpulka on 2018-01-08, 20:12:34
-
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?
-
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?
-
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
-
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.
-
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.
-
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.
-
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">
-
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.
-
Same problem, maybe it's Corona Standalone problem, not exporter
-
Was this issue ever corrected?
-
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.
-
Hi,
we have part-time guy to work on this now (started this week). Lets hope he learns the codebase fast ;))
-
Hi,
we have part-time guy to work on this now (started this week). Lets hope he learns the codebase fast ;))
lets hope :)
-
Hi,
we have part-time guy to work on this now (started this week). Lets hope he learns the codebase fast ;))
Phew, thanks god
-
Is there any update on this fix?
-
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.