Luis M Ruiz

Also, a good idea is to check out the mtexture library. More and more I find cool goodies here. Available in v2019

This video tells me there are no symbols called "metal mesh". I learned the hard way to always set the type of resource I need, then type what I am looking for.

I typically keep a project folder dedicated for renderings, just to keep a record. Typically a screenshot is enough. Here is a sample of the before, during and after.

@John Erren Hi John. Creating renderings is always a balance between viewport size, sheet resolution and settings. For example, if you have a sheet 36"x24", 300dpi and viewport at best quality, including displacement mapping, it'll take a long, long time to process. If you are just in the process of previewing your renderings, trade size and quality for speed. Perhaps reducing those renderings to 17"x11" at 72dpi and make use of Custom Renderworks, most of them at low quality including 1 reflection. Once you are super happy with the quality, go high on Custom Renderworks and increase your sheet res to 300dpi. Some settings are different in case of interiors. Post a pict of what you are trying to create and I may have a similar file you can take a look at in terms of settings.

@jamie innes If you can post a sample file, I think we can take a look at it and give you a better report.

I am going to take a guess here. Are you using Image Effects on top of that viewport? (v2019) is that box checked when you hit update?

Here is a black and white rendering as I am testing all glow textures included in a working file. Recipe: -At least one light object included in the file and switched off -No ambient light -Four bounces -Ambient occlusion on -Custom Renderworks

@Zeno I wonder if you have some screen or plane objects not helping this viewport?

With the latest release of Service Pack 3, awesome new updates got included. One that we all requested, was a path to create linked panoramas. I had the opportunity to test it and I'd like to share my results. Click here to view the presentation

I tested the output and for this single sheet with all those views at 300dpi res. PDF jumped to 6mb, 18mb if increased at 600dpi. Then again, That same high res pdf got exported again as a jpg for the client to see and it went down to 4.2mb and the quality was excellent (but included no vector lines) I think it is always a balance of the final intent vs quality vs size.

@Charlie Winter Thank you for sharing the file. I did some tests and I found a few things that can help the rendering: Sheet resolution was set to default 72dpi. Ok for preview but for finals go up to 300dpi min. That takes away the graininess and makes the carpet and walls look sharper. There was no light source (sun object for example) always create one even if this one is off. That light source can be set to smooth shadows or sharp depending on the effect you are going after. I think for the look you were going after there was no need for hdri background Increase the resolution of some of those light settings, Once you are done with previewing the viewport, uncheck full screen, that'll make the rendering go faster. For quick testing of textures, try artistic cartoon other than OpenGL Add some ambient occlusion, helps to create some volume. I hope these tips may help.

@Alex71 Recommendation. Don't be afraid of bringing those sheets with OpenGL viewports at 600dpi.

@Kevin Allen I almost forgot about this test. Here is in grass, thick blades but the tips are always sharp. Funny.

let me get on it....