Author Topic: MultiTexture problem with DR in Alpha 6  (Read 6342 times)

2014-03-26, 11:16:58

crowinhand

  • Active Users
  • **
  • Posts: 43
    • View Profile
Hi, I've run in to a problem with MultiTexture.
Yesterday I sent to render a simple interior scene with wooden floor material, in the morning when i saw the result, floor was all black :(
It apears that DR does not work with multitexture, or does it?
Tis the wind and nothing more!

2014-03-27, 13:52:42
Reply #1

mvc

  • Active Users
  • **
  • Posts: 16
    • View Profile
I'm experiencing similar issues with DR, vut rather than MultiTexture, i'm finding that DR is not reading any textures on DR slave nodes.

Am currently testing to see if this an issue with mapped network drives.
UPDATE - yes, looks like UNC pathing on the assets fixed the dropped textures.

UPDATE 2 - nevermind, i've just found this... http://forum.corona-renderer.com/index.php/topic,3148.0.html , but i notice that the fix was just to UNC everything.  can we have mapped network drive support?


« Last Edit: 2014-03-27, 14:09:52 by mvc »

2014-06-22, 21:30:58
Reply #2

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
Do you have the paths set up correctly on both computers? I tried a simple scene with multitexture, but it works correctly
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2014-06-23, 01:19:42
Reply #3

cecofuli

  • Active Users
  • **
  • Posts: 1578
    • View Profile
    • www.francescolegrenzi.com
Ondra, I have the same problem. And my renderfarm settings are perfect.
The solution? I open the scene on the rendernode, I open the Material editor, pick with the color picker the shader with multitexture and click "reload".
Or, save the main scene (on the worksation) with this shader in the material editor. When you ope the scene and the material editor in the node, everything is ok.
I think there is some issue with the "reload" option in the multitexture map. I'm not sure if it's a Corona problem.

2014-07-02, 20:04:51
Reply #4

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
I can confirm that this bug exist.
Alpha7 installed. This is not a DR problem I suppose.

1 - Create scene with one object which have material with MultiTexture inside
2 - Save it and close Max
3 - Open scene and click render straight away. Object will render completely black

Solutions for one PC:
1) If you enable "Show Shaded Material in Viewport" (just show map in viewport) and save the scene, then when you open it - max will load textures. But this doesn't work for DR
2) Open and close Material Editor. Even if there is no MultiTexture material it will load all textures.
3) ATSOps.Refresh() also can load textures, as well as many ATSOP commands. I tried to write a StartUp script which execute this command by ScenePostOpen callback but it didn't work that way :(

Solution for node?
Still no solution... Because node doesn't load max's interface or somewhat else, it can't load textures.

Update.
VP Crossmap load textures fine, but...
Image distribution:
- Per Element - Crashes max
- Per Object - Renders black
« Last Edit: 2014-07-05, 16:31:14 by nik684 »

2014-07-10, 12:04:06
Reply #5

moadr

  • Active Users
  • **
  • Posts: 58
    • View Profile
    • Vermeer by Stableworks
Hello dear Corona friends! Haven't been around for a while, but I just wanted to chime in to this topic, that I have experienced the same thing happening to me.

I have an interior scene with multitexture map applied to the floor and when I want to send it out to the renderblades to render, it renders the whole floor black. What the solution is, that I open the scene on the blade itself, pick the material of the floor and after that it works just fine.
But there is another thing, that I have experienced: I have the same problem (not all the times but from time-to-time it happens), when I open a scene on a different PC, not the one that I was working on with previously sometimes my multitexture floor material also renders in black (the sollution is the same, have to open the material editor, pick the material, and after that it's fine).

So I'm not sure what can cause this problem, but I have experienced it not just when I try to send out a job to the renderblades, but also when I just simply open it on a different computer.

(I have to add, that all the PCs and the network is setup correctly, because I haven't had this problem with other materials in the same Corona scene, nor I had that with any of the Vray scenes before. So I guess it should be something with the Corona-Multitexture combination)

I hope my additional information could help you guys with the solution, or at least it gave a bit of a guidance to you to the right direction :)

Thanks and keep up the amazing work!
Adrian Moorsel

Vermeer by Stableworks   |   https://stableworks.tech

2014-07-16, 01:13:18
Reply #6

SaY

  • Active Users
  • **
  • Posts: 72
    • View Profile
Has anyone found a solution to Miltitexture problem?

2014-08-05, 19:24:06
Reply #7

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
Multitexture 2.01 has no such problems!

2015-01-12, 16:13:18
Reply #8

Nik

  • Active Users
  • **
  • Posts: 167
    • View Profile
    • HQ Details
VP Crossmap - Per Element - Crashes max
Could this bug be corrected?
It seems this plugin is the only one who can randomize map per poly elements with same matID.