Frequently asked questions about LightWorks

by GRAPHISOFT, Katalin Götz and Emőke Csikós · updated: 12.30.2011

Note: ARCHICAD 18 introduced a new rendering engine: CineRender.


LightWorks rendering engine is incorporated into ARCHICAD from version 9. LightWorks rendering engine is developed by LightWork Design

Q: Does LightWorks in ARCHICAD supports radiosity?

A: No, currently Ray-tracing is supported

Q: Does LightWorks in ARCHICAD support multi-threading?

A: Yes, although not all of the rendering modes in LightWorks are multithreaded. Therefore some settings cause the rendering process to use one processor only.

Q: What settings are limiting the multi-thread functionality?

A: There are two settings:

  • If Antialiasing is set to “best”, then the projection will use scanline rendering which is a single-thread rendering mode in LightWorks
  • If Realistic Sun is used, then the rendering will break down to separate threads, but only one of these threads will be active most of the time, while the others will be idle, therefore there will be no performance benefit over a single-processor computer .

Q: When do I need to set Antialising to best?

A: You will probably only need this option when you have very thin (1-pixel) elements (e.g. wires) that run at a steep angle in your composition.

Q: When do I need to turn Realistic Sun on?

A: Realistic Sun has the benefit of most accurate shading, because it uses ray tracing algorithm. The rays of the Realistic Sun will penetrate transparent materials, while the simple Sun will not penetrate such materials, creating a less realistic shadow casting. Since the use of Realistic Sun puts a heavy burden on performance, use it only when you do the final renderings. You can improve rendering speed by setting the Number of Samples value lower.

Q: Can LightWorks take advantage of more than 2 processors?

A: LightWorks will use as many processors as many you have. However, do not expect rendering times to be divided by the number of processors compared to a single processor. Photo rendering has 3 stages: creating 3D model, converting model to LightWorks format, then rendering. Only the 3rd stage is multi-threaded.

Q: Rendering an image fails due to lack of memory. How do I fix that?

A: Read this article: LightWorks memory usage

Q: Is ARCHICAD LWA-Enabled ?

A: This feature is not yet implemented in ARCHICAD.

Q: Where can I learn more about LightWorks rendering in ARCHICAD?

A: Dwight Atkinson’s ‘LightWorks in ARCHICAD book is a highly recommended read if you are interested in learning more about this topic


alt text

Is rendering with LightWorks twice as fast on a dual-core processor?

Creating a rendered image involves separate steps. When you start a “Photorender projection”, first the 3D model of your project is generated in the 3D window, then the model is converted into LightWorks data format, and only the last step is the so-called “rendering”, when the lines of the image are starting to appear on screen. In the latest version of ARCHICAD, most of these steps are multithreaded. Only the last phase is multi-threaded prior to ARCHICAD 12.

I never use LightWorks. Does it make any sense at all to buy a dual-core, quad-core, or more, computer?

Absolutely, because of the tremendous performance gains achieved in ARCHICAD due to multithreading. Even though earlier versions of ARCHICAD will typically use only 50% percent of the CPU resources, you are always running other tasks as well – invisible (or not so invisible) operating systems tasks, or user tasks such as another copy of ARCHICAD, for example. During processor-heavy activities (e.g. 3D model or section generating, publishing, updating layouts) when ARCHICAD’s CPU usage maxes out, your system will still be responsive when you try to use other applications. For example, when you are updating drawings that are linked into another ARCHICAD project, the Background ARCHICAD – which is another copy of ARCHICAD – will not keep you from working on in the open project. Dual-core will benefit everyone. Quad, Oct-core, or higher will benefit users with reasonably complex models as well as those doing a lot of multitasking. Visit archicad-talk and search for discussion threads concerning purchasing new machines.

I am rendering with LightWorks, but it still seems that both processors stop at 50%

There are areas in LightWorks that are not multi-threaded. Depending on the antialiasing level and other settings, it is normal that LightWorks renders with only one thread. See more in the LightWorks article

Can LightWorks use 4 processors?

Yes. Theoretically, LightWorks can use as many processors as you have.

 

 

 

  • Was this Helpful ?
  • 0   ​1

Related content

Multiprocessing and ARCHICAD

  Multiprocessing means the use of two or more Central Processing Units (CPU) at the same time. Most of new computers have dual-core processors, or feature two or more processors, therefore they are called multiprocessor computers .   What is…

Interior LightWorks Example

This example uses a Japanese house. A SkyObject and SunObject are both placed on the Floor Plan for exterior lighting. The way their parameters are set is very similar to the Exterior example. Also, surface shader definitions are done the same way. Since…

Exterior LightWorks Example

After building your model in ArchiCAD, you need to create good camera positions, apply shaders to your surfaces, place light objects, set rendering parameters and create a test rendering. From the test result, you can identify any needed adjustments to…

Expert LightWorks Options

The LightWorks Library contains some unique light objects that can enhance your renderings: although they are lamps, they simulate ambient lighting. These objects are placed using ArchiCAD’s Lamp tool: to find them, open the Lamp Settings dialog box and…

Basic LightWorks Options

The LightWorks Rendering Engine, built into the ArchiCAD PhotoRendering interface, gives you the power to create high-quality photorealistic images that can be published as ArchiCAD views. LightWorks offers ray-tracing, soft-shadow and reflection features…