VirtualRender

 Like this app

VirtualRender is yet another LightWave renderer. The difference from other solutions is that it does not use physical memory for framebuffer allowing to render the biggest imaginable scenes without using virtual memory, which slow down rendering a lot, or which immediately...

VirtualRender screenshot 1

License model

Platforms

  • Windows
  • LightWave
  No rating
0 likes
0comments
0 news articles

Features

Suggest and vote on features
  1.  Rendering

VirtualRender News & Activities

Highlights All activities

Recent activities

No activities found.
Show all activities

VirtualRender information

  • Developed by

    TrueArt
  • Licensing

    Proprietary and Commercial product.
  • Alternatives

    46 alternatives listed
  • Supported Languages

    • English

Our users have written 0 comments and reviews about VirtualRender, and it has gotten 0 likes

VirtualRender was added to AlternativeTo by nbendala on Oct 7, 2011 and this page was last updated Nov 27, 2014.
No comments or reviews, maybe you want to be first?
Post comment/review

What is VirtualRender?

VirtualRender is yet another LightWave renderer. The difference from other solutions is that it does not use physical memory for framebuffer allowing to render the biggest imaginable scenes without using virtual memory, which slow down rendering a lot, or which immediately result in complete failure at initialization stage. That's why it's called "virtual" - rendered regions are saved immediately to hard disk without unnecessary taking memory during rendering rest of image.

VirtualRender is the first LightWave bucket renderer that splits framebuffer to small, user definable size regions. Each render node in your renderfarm now can work on the same frame of image telling other nodes which regions are in progress and which are rendered, and at the end there is done composition of all rendered regions into one with unlimited resolution, limitted only by available hard disk space. We were successfully rendering scenes with dual ScreamerNet setup on single machine which was taking 110 MB each node, 220 MB both, at resolution 16384x16384. LightWave renderer even failed to initialize. At 640x480 this scene was eating 800 MB of memory.