Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Yehat

Pages: [1] 2 3 ... 5
1
I have exactly the same problem. I regularly but non-systemically get the same message. Textures are stored on a network drive //server/project/bla-bla-bla. There are no third-party plugins in the scene. Max 2023.3, Corona 9 hotfix 1, Win10, Ryzen 3950х.
The message appears more often if you take material from an object in the material editor.

Then rendering stops, but the Stop button is not pressed.

2
As for other improvements (except bugfixing): It got even worse because since V6 we cannot switch on/off Dr during rendering any more - sacrificed to fix a bug I never met personally. I don't even know its ID or name - yet it stole me the most important load balancing feature!
Good Luck

Agree with you. I never know about this bug and never meet it. But every day I used on-the-fly rendernodes. The killing feature was killed in 7 version(((

3
Haha))
So, what about this feature?

5
Hello! In all previous versions, I could enable distributed rendering during rendering. It is really cool when you can connect the nodes on the fly. Especially when the department has its own render farm, this allows to exchange nodes between us without stopping the render. But in new 7 version I cant do this and got the message:

https://coronarenderer.freshdesk.com/support/solutions/articles/12000080850-distributed-rendering-cannot-be-enabled-during-rendering-please-enable-distributed-rendering-only-af

WHY? It is very VERY usefull feature! Turn it back, please )))

6
It's all unimportant.
The point is: this feature does not work in the new version, but it is very necessary.

Corona build date in renderstamp says that it is 31 aug 2020 build, that means HF2 according to information from site.

7
Hmmm, maybe. Just 6 version, non hotfix2

UPD

But, stop! It seems like hotfix2




8
It works even in version 6.

I don't think so :)


Good Luck
You dont think, but I know it and use it every day )

9
I use this function very actively, but I have never encountered any errors. It works even in version 6.

10
Hello! In all versions, I could enable distributed rendering during rendering. It is really cool when you can connect the nodes on the fly. Especially when the department has its own render farm, this allows to exchange nodes between us without stopping the render. But in new 7 version I cant do this and got the message:

https://coronarenderer.freshdesk.com/support/solutions/articles/12000080850-distributed-rendering-cannot-be-enabled-during-rendering-please-enable-distributed-rendering-only-af

WHY? It is very VERY usefull feature! Just turn it on, please )))

11
This is standart Windows10 firewall. No specific application.
In the firewall, the permission for DrServer.exe for TCP and UDP protocol is registered separately. I have asked my admins for details, because they did it and helped to me.
Yes, it works now without "Search lan" option.

Admin created these two new rules for input connection for DR server.
In the top-left corner automatically created rule by installer, I thought. We leaved it.

12
Solved!

Attentive firewall and policy setup for Drserver.exe and check/uncheck "Search lan during render" helped me.

13
No, it doesnt.

14
Thanks for the advices. I was sure that everything is set up correctly, because the renderfarm has been working for a long time on. I described the problem and asked my system administrator to check the network settings. As a result, after a while, one of the nodes began to work, but the second one is not yet available.
I do not know what exactly he did, but I ask him to do it again. :)

These are attached logs from problem node:

15
The log is it the 1st post.

Pages: [1] 2 3 ... 5