AccuRender nXt

Design with the lights on...
Welcome to AccuRender nXt Sign in
in Search

Manuals nXt for AutoCAD

Getting Started

This is a pretty early prototype of a new rendering engine that I've been experimenting with.  There should be enough here for people to at least take a look at. Please be in a friendly mood when trying this stuff, it is still early.  That being said, I do welcome any and all comments, and although I may not agree with everything said, I will listen carefully.  I am still not sure whether this stuff belongs in an AccuRender 5 type product or whether this is something entirely new.  It is very different and it may be time to nuke some of the old stuff.

Basics

To load the new engine for the first time in an AutoCAD version:

Appload the file "accurender nXt.arx " in 32-bit Operating system -OR-  "accurender nXt 64.arx " in 64-bit Operating system.  You can also drag and drop one of the files from explorer onto an open AutoCAD session.  You only need to do this once-it will demand load after that.

To run the new engine type: "ar5".

This brings up a very rudimentary control panel interface which is the working prototype.  It also displays an AccuRender palette which will contain the new interface-this is not working yet-you cannot render using this interface,  but you can still play with it and tell me what you think

On the right side of the control panel are four "Presets"-Industrial Design, Exterior, Interior Daylight, and Interior Artificial Light.  The easiest thing to do when you're first getting started is to choose the most appropriate one of these and let it handle the settings below.  An "Interior Daylight" rendering is probably the most adventurous of these settings-you may want to wait a few rounds and read the section below before trying one of these.

Start a rendering by selecting Render->Render from the pulldown.   Currently, only 640 x 480 resolution is available.  Renderings no longer stop automatically; the process will continue to refine the image (forever) until you tell it to stop.  Stop the rendering by hitting the Esc key or use Render->Stop.  You can let a rendering continue for seconds, minutes, hours, overnight, or for a week-it's up to you.  Some renderings won't change much after the first few seconds. Many images though, particularly those with things like soft-shadowing, blurry reflections, interior daylighting, will continue to improve.  Some rendering will require a long time to converge on an adequate solution.

I will, of course, be adding some automatic stopping criteria for batch type work like animations.  These will probably, at least initially, be simple criteria like time or number of passes.  I will also add some paranoid automatic saves for long renderings.

Renderings can be saved to .jpg format or .tif (tiff files have an alpha mask) using Render->Save Rendering.

Performance Notes

A. The basic engine should be at least 4-5 times faster than the old stuff under most conditions.  It's going to be very difficult to compare the render speed to AccuRender versions.  The closest you can get in terms of render settings is to use the Exterior preset and uncheck the box marked Sky Light.  This is similar to the old illumination algorithm.  A pass or two should yield similar or better anti-aliasing characteristics.

B. The status bar will display some important information during a rendering.  It should look something like this:

Pass 29(416) 00:01:59 1137611 104006

The pass count is incremented each time the renderer makes a pass over the entire rendering.  Each pass provides 4 samples per pixel.

I'm pretty sure the number in parentheses represents the last completed scanline of the pass.

The clock shows the elapsed time in hh:mm:ss.

The next number represents rays/second and the final figure is pixels/second.  These two are very important performance metrics.  The second, in particular, will tell us how long each pass will require. 

C. The performance of the engine should no longer be impacted as much by having a small detailed model on a large site (the teapot in the stadium phenomenon).  An exception to this is indirect lighting from sky and sunlight; it's better to have smaller models if you need this.

D. The performance of indirect lighting will not be impacted very much by having a lot of faces to render.  This is a large improvement over radiosity, which is sensitive to model complexity.

E. The thread scheduler has been redone and should be much more efficient on machines with 4 or more processors.

Notes on Interior Daylighting

Daylight sources are an option, not a requirement, for interior sky light.  Using daylight sources will make the images converge much faster.  Interior daylighting works pretty well without them for single rooms or small models on small sites with relatively large windows.  These models will still benefit from the faster convergence of daylight sources

If you attempt to render an interior daylight simulation of a small room in a large model without daylighting sources you will probably be disappointed.  Daylight sources should help a lot in this case-but try it if you've got the stomach for it and let me know how it goes.

If you model glass with a single sheet you'll get more realistic refraction if you tag the object as Thin using Ar4/3. 

Notes on Skylight (hdr)

Sky light is provided using either an analytical sky model or an hdr Image file.  Controls for this are under Sky Type.  You can select an hdr file using the button to the right of the Image checkbox.  I don't think there's any way at the moment to change the direction of (rotate) the hdr sky. I'll get to it soon.

Material Editor Prototype

Under the Test pulldown is a prototype of an interactive material editor using hdr lighting for the preview.  You can save/load materials to/from individual files. There is also a concept of template materials which present simplified versions of the material editor.  You cannot assign the new materials to objects in the drawing yet, this is coming soon.  Some of you may notice that there is an anisotropy setting-it doesn't work well yet.

Coming soon (partial list, I'm sure I've forgotten lots of stuff)

  • Saving the new settings (presets, etc.) to the drawing
  • Resolutions other than 640 x 480
  • Rotation of hdr sky light
  • Assigning the new materials
  • Infinite ground plane
  • Many plant settings
  • Bump mapping
  • Decals
  • Waves

Not sure if I'm going to implement yet

WalkAbout-may implement some navigation tools to supplement AutoCAD's-but it may be time to kill our own OpenGL viewer.

Unlikely to be implemented

Radiosity-too many problems, too many artifacts, too many restrictions, too much knowledge required by users-I think we can do better for most users.  Some people will definitely miss this.

 

Comments

 

Peter Milner said:

There are two problems I foresee with dropping the Walkabout view:

Very rarely does one render to the proportions of the screen. This means that the AutoCAD view does not show the final rendered view and therefore makes it very difficult to set up the right composition.

Secondly there would be no way of rendering a window which is very useful for testing certain aspects of an image before commiting to a final full render.

Could Radiosity and Raytrace be left in as an alternative rendering method separate from the new engine rather than incorporated into it?

September 28, 2007 3:47 AM
 

Ernesto said:

It looks very very promising!

You did a great job, and it is just starting!

Regarding the walkabout window, I agree with Peter.

Perhaps it is possible to implement a film gate or frame on the autocad view, so that the users will know the real limits of the rendered image, but such thing will not solve the whole problem.

The main obstacle here is the 2 points perspective, which is very important in architectural use. (I may look obsesive with this topic)

I still remember working with AR2 on Acad12 DOS, guessing the final composition in those cases, and cannot imagine someone going back there in 2007!

And regarding Radiosity: It was a GREAT revolutionary tool at the time it was implemented in AR, but now I am sad to say it is obsolete in my opinion, so it shouldn be missed.

The old Raytrace engine is still a great tool, if it is faster. There are cases where a more complex calculation has no sense, for instance big buildings exteriors, or far aereal images of huge urban complex.

Working with Maxwell Render, got surprised that I couldn´t get those great images we use to see in their forum.

Finally I realized that Maxwell makes the diference only under certain conditions: where the light is very indirect, or in very small models, where you could see the subtle effects of indirect lighting, or exteriors at backlight (which are very interesting but clients do not want them)

In case of exteriors under sunlight, there is almost no noticeable diference betwen an AR3 raytrace, and a Maxwell image, even in the rendering time.

Ernesto

September 28, 2007 8:54 PM
 

Jeff Waymack said:

I haven't been able to get any useful images using AR5 yet. This is probably because I'm not sure how to use it yet and there is no documentation (I'm a big manual reader).

I don't know if this is the area for problems & questions, but here are a few:

1) I seem to have gotten AR5 and AutoCAD v2007 a bit confused. When I load AutoCAD the AR5 interface comes up, but typing AR5 does not work. If I unload AR5 and then reload it then typing AR5 works.

2) Related to the comments above, I have not been able to get any usable images using the AutoCAD view as the basis for rendering. My problem is that while the perspective image completely fills the screen, the rendered image is tiny. I have tried all types of zooming in and changing camera positions, but nothing works.

3) While the brief getting started statement above suggests "At the moment the material and most of the lighting setup needs to happen using AccuRender 4 or 3" none of my materials show up in the rendering. Are there paths that need to be set and if so, where?

4) Using the materials editor is causing AutoCAD to bomb.

If I could generate something useful to look at, I might be able to comment on what I thought of AR5.

Jeff Waymack

ASPEN Computer Graphics

October 3, 2007 7:18 AM
 

Jeff Waymack said:

I'm another person in strongly in favor of keeping the walk around option from AR4. This has been the only tool I've used to generate the views I eventually render. Since it is designed by the Accurender team, it will work as expected with the rest of the Accurender program.

I feel the need to keep the interfaces in the same package and the logical, ease of use of the walk around view are critical for infrequent users or beginning users.

October 3, 2007 9:50 AM
 

Ernesto said:

Please take in mind that animations are a common tool. In the old times they were a professional creation made by specialists, but each day they are becoming more usual tools.

In case a desition is taken regarding the walkabout window, please think that a reat time shaded preview for animation is needed.

October 3, 2007 6:19 PM
 

GeneK said:

Walkabout, or something equivalent that navigates through views/cameras and saves them for rendering, is absolutely needed.  ACAD's View Manager does a lousy job of restoring saved views since 2005/2006 because it automatically alters the DVIEW parameters in the ACAD viewport unless the viewport is at the exact same proportions as when the view was saved, and ACAD2008 suffers from a serious (and as yet unresolved) bug that causes its view manager to randomly create and switch layer states when you save or restore saved views.  

October 12, 2007 11:42 AM
 

brianmacdonald said:

I have to agree with the walkabout window.  I ALWAYS set my view from the fine tuning availiable through this tool.  It is much easier than trying to fiddle with the autocad view, since you never really know what you are looking at if you have multiple layers of objects.  If you zoom in too far, you don't see something because it is now 'behind' the camera.  If you don't zoom in far enough, everything renders very small (in my limited experience).

All in all, I for one vote for keeping the walkabout view window.

October 12, 2007 12:14 PM
 

Yinka Gbotosho said:

The Walkabout view definitely plugs a hole in Acad view management lapse and is therefore a welcome addition from AR. Besides the views, it also offers a good medium to provide save-able shaded views for WIP. Need to keep it or provide equal or better alternative.

October 31, 2007 2:38 PM
 

joaohenriqueneto said:

You did a great job. The interface is very promising, with the presets of lightning and materials, but i dont like it of the drag and drop thing of the materials. I believe that a list, like in the others, is more simple. And i´m also in favor of the walkabout window. I hope to see the fully functional version soon.

November 1, 2007 1:03 PM
 

phoffmann said:

I've been using Accurender since the first beta and have never used the walkaround.  However i just moved to 2008 and the view controls seem to have been screwed up.

As for materials, yes a list would be nice for power users who know their libraries.  I still use the AR3 interface in AR4 for that reason.

November 12, 2007 7:17 AM
 

Manuals said:

To load the new engine for the first time : Appload the file "accurender nXt.arx ", or drag

January 21, 2008 4:22 PM
 

piranesi said:

I've been a fan of accurender for a long time. Mainly because of the walkabout. Please bring it back!

I can see the render quality improvements. But there is some work on other things.

- please enlarge the max. size of the render so I can zoom in on edges, etc.

- I use Maxwell Render a lot. This engine also keeps on rendering until I stop it or until some level is reached. In MR this level is time of the render or the (quality)level of the render. This is very useful.

- Emitter material. You really need this to get great interior scenes.

- I am glad radiosity is gone. I asume it is now part of the general render proces.

- Don't change to much of the old concept. It was easy and effective to use (maybe the interface could have been less chaotic). Especially for quick test of architectural models or quick presentations.

January 24, 2008 1:32 PM
 

neball9 said:

I have loaded ar5 & now ar3 &ar4 dont work???

January 25, 2008 1:18 AM
 

Andy Burton said:

I too have to put my vote in for keeping the walkabout tool. It is quick and easy to use and that's one of the main reasons I've stayed committed to Accurender for over 10 years. I'm also a big fan of the presets, as this is where programs like Vray drive me bananas trying to guess which settings will eventually get me a reasonable image. At least if you start with something reasonable and have access to the settings to tweak the variables you can save hours getting the image right. Keep up the good work, it's looking good

January 25, 2008 2:54 AM
 

Don Watts said:

I just loaded AR5, and have owned all versions until I switched over to Revit. I do not have the need for a rendering much, but when I do, I try to make the rendering  professional looking with poor results. It would be great if a Wizard or a "cookbook" were made part of the development of the program.I assume something will be available to help achieve a shorter learning curve.

Perhaps their is literature available (like AR for Dummies)...

So far, the program looks very promising.

January 26, 2008 9:30 AM
 

tdoremus said:

I was building my material library using texture maps that I use for the AutoCAD renderer materials, and ACAD crashed. When I re-opened the document, I had lost all of my AR5 materials and will have to start all over. Are you blocking the autosave? If the materials don't appear in the load list, does that mean they're not recorded in the .dwg, or do I have to purge it now?

By the way, the default ACAD renderer now does a pretty good job, so I'm wondering what you expect the added value of AR in AutoCAD to be.

February 8, 2008 5:55 AM
 

apspack said:

tdoremus-  ACAD renderer maxes out at 4000px wide.  Not anywhere near high res enough for large presentation renderings.  I often do 7200px wide.  Also I noticed the networking of the material library does not work as well (or at all) compared to accurender.

I like the new streamlined interface, ar4 seemed overly clunky and slow (even on quad core machine)  keep it up and get this software out so I can render in vista!  I have had problems with tech support and getting ar4 to read my mat libraries in vista, so I am eager to stop switching back and forth to XP.

February 11, 2008 10:56 AM
 

saeed said:

cool man its ok ill see onit

March 6, 2008 12:09 AM
 

trim6116 said:

Please keep the Walkabout function.  It is the best way to set views and fine tune the viewers position.  AutoCAD is lousy at setting views.  AR5 Interface is pretty clean so far......please keep it clean.  I feel the AR4 interface is too cluttered and sluggish - I loved the simplicity of the old AR3 menus.

March 27, 2008 4:41 PM
 

scothand said:

After playing with this in AutoCAD Architecture 2009 for a while this morning, I _can_ work without the walkabout controls, gradually getting used to Autocad's built-in steering wheel nonsense.  I thoroughly miss being able to use the arrow keys to move, but I understand that the new Autocad Walk can replace it.

I am running into the viewport size/orientation issue which was solved by having an internal walkabout view.

Easily, my biggest issue is the lack of material -> ACI.  All of our models are built in the ADT/Architecture modeling system, so the walls, doors, etc... all are based in Xrefs and pulled from Autocad's material designations (which I've set up to relate ACI to material).  I got used to this system using AR3 with Archtiectural Desktop 2006, and think it works beautifully.

April 15, 2008 8:58 AM
 

dollakid2002 said:

I have one major problem with ar5 it does not over ride the wall style in autocad its as if they are not in ssync i have to go into the autocad aec editor to tell the material to use ar5 material and that is very time consumeing for me i need to be able to apply the materials directly and they take imediate effect. I am using ACA 2008.

May 1, 2008 7:51 AM

This Blog

Syndication

Tags

No tags have been created or used yet.

Archives