Wed, Dec 25, 2:03 PM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)



Subject: Main Camera View versus Render


Airmarshal ( ) posted Tue, 22 February 2011 at 6:21 PM · edited Thu, 05 December 2024 at 3:00 PM

Hi All,

Bit of a noob question I know but this puzzles me a bit.

I was working on a comp earlier today and really liked the view (material appearence, etc) in the main camera window. However, when I actually rendered the comp on superior settings, the materials didn't look nearly as good as when I just looked at it through the main camera window. It just seemed like textures and materials really broke up and pixalated upon rendering. Is there a way to render exactly how a model can look in the main camera window?

Thanks in advance for the assist.

-Marshal

 


ddaydreams ( ) posted Tue, 22 February 2011 at 7:17 PM
Airmarshal ( ) posted Tue, 22 February 2011 at 7:33 PM

file_465921.JPG

Good point... uploading a screen shot...

Thanks!


Airmarshal ( ) posted Tue, 22 February 2011 at 7:34 PM

The metal material looks so much cleaner in the main camera window then any render I was able to do. Not sure why. Ideas?


ddaydreams ( ) posted Tue, 22 February 2011 at 7:46 PM

Hi

Actually I meant if you like the way it looks expand it to fill the main screen then screen shot it and use that screen shot in place of a render.

other than that since your main camera view is in open gl and you like that look.You can set your render quality to open gl at least in newer vue versions.

Maybe someone else can help with a better idea

Frank Hawkins/Owner/DigitalDaydreams

Frank_Hawkins_Design

Frank Lee Hawkins Eastern Sierra Gallery Store

 

My U.S.A eBay Graphics Software Store~~ My International eBay Graphics Software Store

 


Airmarshal ( ) posted Tue, 22 February 2011 at 7:56 PM

Thank you so much for the open gl idea. Makes a huge difference.

The materials are much more crisp in this case.

I appreciate the assist.

-Marshal


ddaydreams ( ) posted Tue, 22 February 2011 at 8:14 PM
Airmarshal ( ) posted Tue, 22 February 2011 at 8:47 PM

It doesn't appear you can do the whole render though including clouds, etc. It seems open GL is good for object detail but not for atmosphere, background etc. Again, not sure why.


tsquare ( ) posted Wed, 23 February 2011 at 3:23 AM

If the materials look pixelated, you may have to scale them down to get better results in your render........if they are procedural.  Check over your render settings and experiment a bit, elsewise.


bruno021 ( ) posted Wed, 23 February 2011 at 3:56 AM

Maybe you should show use the rendered material. OpenGL is fine but has limits in terms of what it can render: no reflections/refractions, no bump (in Vue anyway), no blur, and no indirect lighting.



impish ( ) posted Wed, 23 February 2011 at 6:19 AM

I can sympathise - I spent hours at the weekend getting some bought imported models to look good.  Saddly "standard" model formats are not as "standard" or transferable as we might like and materials are the usual suspects when it comes to finding a fix.  There are all sorts of things in textures that may need tweeking for renders that look fine in OpenGL.  The ones causing me problems at the weekend were:

  • Reflection maps that need inverting
  • Reflections set to 100% on materials that shouldn't be reflective
  • Bump maps / Displacement maps that are extreme, inverted or missaligned
  • Highlight colours that are either black or white

I ususally start by turning Reflections, Bumps and Displacements down to almost off for the materials then add them in a bit at a time.

impworks | vue news blog | twitter | pinterest


Airmarshal ( ) posted Wed, 23 February 2011 at 10:01 AM · edited Wed, 23 February 2011 at 10:05 AM

file_465951.JPG

Thanks for all of the replies. Listed are two samples. The first is a superior render at 1280x720 (below). The second is an Open GL Render at 1280x720 (above). Once importing I did not resize the mech at all but simply moved the camera close to the object. The Open GL mech textures look a lot crisper and sharp but the background is virtually non existant where as the opposite is true with the superior render.

Is there a way to have the best of both worlds so to speak or do I simply need a massive tutorial on rendering?

Thanks for the assist.

-Marshal


Airmarshal ( ) posted Wed, 23 February 2011 at 10:03 AM

file_465950.JPG

Here is the suuperior render picture...


bruno021 ( ) posted Wed, 23 February 2011 at 11:30 AM

Just turn down the bump amount in the material editor, and it will look good.



vintorix ( ) posted Sun, 27 February 2011 at 3:53 AM · edited Sun, 27 February 2011 at 3:57 AM

Thank you Airmarshal for illustrating a point I have asked before without anyone being interested. The main window often looks better, especially with high resolution handpainted photographs as texture. The problem with taking a screen dump is that it can't be any larger than your screen size. Why not render like it looks on the screen? "What you see is what you get" is a philosophy I approve of.

As far as I am concerned, the render destroy my work.


bigbraader ( ) posted Sun, 27 February 2011 at 6:35 AM

@ vintorix: Try making the photograpic texture not-anitaliased, see if that makes a difference. Often it has already been anitaliased once, in the editing proces.


vintorix ( ) posted Sun, 27 February 2011 at 7:11 AM

I have no doubt that Vue without I have been asking it, apply antialiasing both two or three times or maybe more. I suppose I have to bite the stick and do some research. Its only that it feels so unnessecary.. I always do several renders including multipass, to have as many options as possible in the composite session. One of the renders should be the crisp and clear main window without I have to do anything. Is is already there! Madre Mia ;)


Airmarshal ( ) posted Sun, 27 February 2011 at 11:08 AM

Good info here gents... let's all do a little testing and report results.

Thanks for the support!


impish ( ) posted Sun, 27 February 2011 at 1:07 PM

Vintorix - if your using one of the preset render settings they all have anti-aliasing set. If you want to control them you need to use User Settings.

Maybe your seeing the effect of Interpolation Type on a projected texture map (you can find this in the function editor for a texture on the Projected Texture node) - if you don't want any just set it to None.  That has been discussed here before and I wrote some Python scripts to make switching between the different modes quick when an object has a complex set of materials.  You can find the scripts on my website on the page the page Switch Mapping of Images in Vue Materials.

Hope those help you get the settings you prefer.

impworks | vue news blog | twitter | pinterest


vintorix ( ) posted Sun, 27 February 2011 at 1:21 PM

impish, oh thank you I certainly will look into your scripts carefully I am sure they are useful. Still, let us not loose sight of th main thing, namly that we want to save out the main camera picture in whatever resolution we want. Atmoshere and clouds can be rendered seperatly most people use HDRI for light anyway.

It is not easy for a render to improve on high resolution photographic elements taken by a first class camera, tone mapped and handpainted by an artist. The universal concept of erudition comes to mind. Whatever you do, the original is going to suffer.


bruno021 ( ) posted Sun, 27 February 2011 at 1:44 PM

Render options: choose OpenGL as your render quality.. And since Vue 8.5, clouds can be rendered in OpenGl. The fact they don't show in the first post, is either because the option is not activated in the display options, or because they are not spectral clouds. Fog is also rendered in OpenGL, as well as direct sun shadows.



Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.