AccuRender nXt

advanced rendering for AutoCAD

I've rendered about 40 images for product presentation over the past few days via 'batch' rendering directly in nXt and with the nXt Farm with all out put as .nXtImage files so that I could further manipulate the images as need before inserting into various documents.  As I'm performing post production on the images, I realize there is a hard line gradient in all of the images displayed in the Image Editor. All images saved as JPG from the Image Editor also have these hard line shadows.

I've attached screen captures of the output. The first image is a capture of the render window and represents how JPG output from nXt appears as well, smooth gradient on the floor. The second image is a capture of the Image Editor screen and also represents how the JPG out put looks when saved from the Image Editor.

I got the same results with both builds 283 and 284 Image Editor.

Tags: ImageViewer

Views: 217

Attachments:

Reply to This

Replies to This Discussion

When you get a chance-- try saving from the Image Editor to png.  This will help me determine if this is a jpg compression problem or some other Image Editor problem.

Thanks for looking Roy. Same result -see attached

Attachments:

I just read your message a little more carefully-- it does sound like the nXtImage is bad.  

This isn't happening here-- until I can make it happen I wouldn't even know where to start.  See if you can come up with a simple procedure to reproduce the problem.  If you can, stop and upload all of the necessary files and explain the procedure.

you can grab the file here: https://secure.logmein.com/f?00_lPUwd1h8H9TcNMi9Vza.3drWgZ4yaxNwgrR...

It's about a 7MB download. This is the DWG with related files in an ACAD eTransmit folder.

The unorthodox approach I took to lighting this model is most likely the source of the problem when it hits the Image Editor, and the reason you'll need to see the original file. I tried to replicate this with a smaller model, but was unable to get the same lighting effect. It's an old school quasi light dome set-up that I've been using for years and often resort back to when I do not have an HDR providing the needed effect.

So... render the model "VIEW 1" (I did at 3300x3300, but resolution doesn't seem to matter. I tried it at lessor resolutions and got the same result)

The number of passes don't seem matter either. My original was a 20 passes. I've tested this at 40+ and as few as 6 and have gotten the same result.

save the output as a JPG or PNG and you will see the image background is smooth, colors on the model are correct, wood grain represented properly.

save the output as an nXtImage.

open in the Image Editor - you will see the "stepped" shadowing in the background. The colors of the wood grain will appear over saturated. The image actually looks like it is being processed with 256 colors as opposed to 16 million.

Thanks again for looking Roy.

Ah-- if you've got an nXtImage file hand I can take a look at that and may be able to tell right away-- without running your model.  It's possible that the actual luminance values using your method are either very low or very high.  The nXtImage file does compress the original floating point data using a similar method to .exr files.  This is normally not a problem if the lighting in the drawing is in a "normal" range.  However, very low values can result in a precision loss and very high values are clipped.

Never mind-- it was obvious once I ran the model.  As suspected-- the lighting values are way too low.  You'll need to use a lighting scheme that brings that up to something reasonable if you want to use the .nXtImage format.  If you move your cursor around the image and see a lot of zeros for values in non-black parts of the image, you're in trouble.

That did it, I increased the light source to 900,000 lumens. It was at just 12,000. Even at 900k, the values were at .001. I increased the lighting to 2 million lumens and get a reading of .012 on the floor. Even so, at 900K, the image made a trip through the Image Editor just fine.

I know this has been asked and answered before, but what is a good average to shoot for? and can you give to me, again, the formula for deciphering the lighting values at the bottom of the screen.

Thanks again, for your help. Glad it was my bad, and not your code.

BW

The Luminance units are in cd/m^2 and have a huge range.

An average gray surface in direct sunlight will measure something like 15,000.

The same surface on a cloudy day might be 1000.

Indoors, in a bright, daylit interior (out of direct light) and you might get a value like 500-- under artificial light at night, perhaps 50.

Moonlight on a forest floor might be 0.001.

You can find typical values if you poke around online-- there are some here.

RSS

Search

Translate

Latest Activity

Roy Hirshkowitz replied to roberto sacchetti's discussion memory problem
"Yeah-- something has clearly gone wrong.  It's just not running out of memory, though-- not in the old sense (which it could easily do on 32 bit systems.)"
4 hours ago
Roy Hirshkowitz replied to roberto sacchetti's discussion memory problem
"The user mode virtual address space limit on 64 bit windows (the statistic we probably care most about here) is actually 8TB or 8192GB.  All of that must be backed by swap file space which would likely be the limiting factor here.  That…"
4 hours ago
Jorge Javier Lara Domínguez posted a discussion

Hola amigos...

Hola amigos, les dejo un link con mis ultimos trabajos. Felices fiestas, bendiciones para todos!!!https://www.facebook.com/N3dArquitecturaDigitalSee More
6 hours ago
roberto sacchetti replied to roberto sacchetti's discussion memory problem
"good morningI did a bit of evidence:1- I increased the page file windows to 25000 mb and kept giving me error2-I split between layers in the parking lot (front, center back), and also render individually gave me error3-I started to delete objects…"
10 hours ago
mike makki replied to roberto sacchetti's discussion memory problem
" hi george i did a render 3 years a ago for harvester restaurant where i needed to show rpc people eating ,walking in ,standing etc....i could only put about 13 of them.....then i tried 15...i got the message roberto got....i took it down to 13…"
19 hours ago
George Ioannidis replied to roberto sacchetti's discussion memory problem
"According to Micro$oft the memory limit of Windows 7 pro 64 bit is 192GB on physical memory. I doubt anyone could ever produce model that big. I remember one of my "heaviest" model I ever did with particle grass translated into mesh…"
19 hours ago
mike makki replied to roberto sacchetti's discussion memory problem
"i dont hink so roy....the more objects the more memory...."
19 hours ago
roberto sacchetti replied to roberto sacchetti's discussion memory problem
"I have a 1tb hdd, so I can increase the swap file size. How do I know which object is damaged rpc ???? are many: plants, people, cars ..... or I have to go to attempts?"
yesterday

© 2014   Header image courtesy Peter Milner   Powered by

Badges  |  Report an Issue  |  Terms of Service