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 - newke

Pages: [1]
1
Yes problem seems to come from busy network  for me. I add that the two computers with corona are stuck, not only mine.
One has a gtx760 graphic cards and the other a gtx1050ti.
About the proxies, i have to make more tests (like saturating the network and removing them to see if this resolve the problem). I will update asap. thanks.

2
Thanks for your answer Maru,

All my bitmaps are in Corona, so i'll try to convert to standard max bitmaps to see if it's better.
But i noticed something : If i'm transfering massive amount of files on my network (ie from my PC to my server), it's impossible for me to work with Corona. So here's my question :  Is Corona needs full netwok bandwith to be able to work at full speed ?

Thanks

3
After more research, problem seems to come from coronaproxy.No proxy in the scene, no viewport slowdowns.
Looks like proxies are constantly updated, maybe saturating the network ?

4
Hello,

i'm part of a team of 2 people who are working on max 2014 and corona 1.6, textures and assets are shared on a network. Until yesterday i was working alone and all was fine. But now, when my teammate is using his 3dsmax to navigate in a corona scene, my viewport is affected by short slowdowns (and his viewport too). Strangely, there is no problem when he is rendering his scene. There is no problem on my computer when my teammate is working on a vray scene too.
First i find this : https://coronarenderer.freshdesk.com/support/solutions/articles/12000011479 . This is exactly the behavior explained here.
I stopped every process that could cause the problem on the 2 computers (Windows defender / Firewall / Avira Antivirus) and checked with windows resources monitor (resmon), but i found nothing special.
So we can't work together at the same time without having big hicups. Last precisions : we are not working on the same scenes and this problem was inexistant in corona 1.5.2hf

Thanks in advance for your help.


Pages: [1]