AccuRender nXt

advanced rendering for AutoCAD

Hey everyone,

  New to this forum, but I had a couple of questions regarding the nXtRender Farm that I haven't really seen answered on the forums.

  • To start I have a file that has been active in the farm for around 16 hours now and it's size is minimal the base dwg is only 25.4 MB and the complexity is rather limited, I'm unfamiliar with the potential cons of online render farms this is the first time in my career I've not had access to an in-house render farm.
    • Is this a queue time thing? A failure or error in my drawing? or is it a fairly standard speed I will have to grow accustom to?
  • Since sending the drawing to farm a NXTMODEL File of a total size of 1.45 GB has populated with the title of 0.nXtModell what is this file? It seems rather large compared to the base file used even if I incorporated a massive amount of complexity with shadows and reflective surfaces this seems to be a bit much. 

Any help or advice would be much appreciated. I've been running the renderings I do at 2000 passes and 1 task.

Views: 73

Reply to This

Replies to This Discussion

The nXt Render farm is a simple, in house, render farm-- NOT an online one.  If you haven't set up any machines to access the files it will remain there forever.

The nXtModel is a binary dump of what the file looks like in memory.  Lots of things can make it grow relative to file sizes.  Trees, bitmaps, hdr files, tesselation of curved objects-- etc.

Thank you for your fast response Roy. My co-workers and I all have nXt Render farm on our systems; correct me if I am wrong but if render farm as a program works as an in-house render farm it is acting as conduit if you will for our systems to work as a distributive or collaborative farm? 

Yep, that's about it.  The individual "farmers" need to be running on each participating machine.  They all watch a common "Farm Folder" which needs to be read/write accessible to everyone.  They'll latch on to any available task and run with it.  Beware of slow networks and slow machines-- this all tends to work best with uniform systems.

That was very helpful and I was better able to communicate with my fellow co-workers and management how things are operating. We are currently in a transition to fiber optic and with this information I have additional information for my proposal of investing in further tech capital like the beginning of a dedicated render farm.

RSS

Search

Translate

Latest Activity

Rich Hart replied to John Prentice's discussion AUTOCAD 2018 XREFS
"Great! Thanks for the update, Rich"
Monday
John Prentice replied to John Prentice's discussion AUTOCAD 2018 XREFS
"Rich, The new version seems to be working well. Thanks - super job. JP"
Monday
Rich Hart replied to John Prentice's discussion AUTOCAD 2018 XREFS
"I posted a new version, 0358-QF23, with a fix for this. The Material by Layer was not being recognized correctly in XREFs in AutoCAD 2018.  Please try the latest version from the downloads page and see if this new version works correctly…"
Friday
George Ioannidis commented on Bryan's photo
Thumbnail

D1

"Path is OK. Peter Milner has done some stunning results using hybrid engine, though it requires really long rendering times for noise clear images. For his job he has got super powered rendering cluster with n² cores and lots of GB of RAM. The…"
Jun 22
Bryan commented on Bryan's photo
Thumbnail

D1

"George, this is the path tracer engine. Do you have another recommendation? I am still figuring out materials. I will note that for future renders."
Jun 22
mike makki posted a discussion
Jun 22
George Ioannidis commented on Bryan's photo
Thumbnail

D1

"Is this done with hybrid render engine or the basic one?Comment not about rendering: Stone material is visibly repeating and I thing also out of scale (too big). Looks more like wallpaper, as there are windows and the wall is too thin to be made of…"
Jun 21
Bryan posted photos
Jun 21

© 2017   Header image courtesy Peter Milner   Powered by

Badges  |  Report an Issue  |  Terms of Service