Thread Subject: virtual reality viewpoint immediate change, and rendering resolution improving

Subject: virtual reality viewpoint immediate change, and rendering resolution improving

From: Jose

Date: 26 Dec, 2011 23:59:09

Message: 1 of 2

Dear all,

Q1: I am using the Virtual Reality toolbox to move a viewpoint within a VRML world, but I observe there is some lag between setting a novel position/orientation and its effect on the rendered world image even when using the "vrdrawnow".
-- Is there a way to force the immediate reposition of a viewpoint?

Q2: The resolution of the images of the rendered virtual world is very coarse when objects come close to the camera/viewpoint.
-- Is there a way to improve the rendering resolution, even if it takes more computation time?

Thanking in advance for any help regarding these two issues,
Jose Gaspar

Subject: virtual reality viewpoint immediate change, and rendering resolution

From: Jan Houska

Date: 27 Dec, 2011 18:17:33

Message: 2 of 2

Hi Jose,

Jose wrote:
> Q1: I am using the Virtual Reality toolbox to move a viewpoint within a
> VRML world, but I observe there is some lag between setting a novel
> position/orientation and its effect on the rendered world image even
> when using the "vrdrawnow".
> -- Is there a way to force the immediate reposition of a viewpoint?

This is exactly what "vrdrawnow" is for. "vrdrawnow" should re-render
the world and not return until the world is re-rendered. There can be
still some delay caused by performance limits of the graphic hardware
and world complexity, but there should be no more delay than this. What
do you get if you change the viewpoint and do "vrdrawnow" repeatedly in
a loop? If one pass of such a loop takes approximately the same time as
the delay you see, then you have probably hit the limits of your graphic
card.

> Q2: The resolution of the images of the rendered virtual world is very
> coarse when objects come close to the camera/viewpoint.
> -- Is there a way to improve the rendering resolution, even if it takes
> more computation time?

I assume you are talking about image textures, aren't you? First, make
sure that the texture files (JPEG or whatever) have sufficiently high
resolution. Textures with dimensions that are powers of two (256, 512,
1024, etc.) render faster and give better results than those with
arbitrary dimensions. Then, there are properties of the "vrfigure"
object: MaxTextureSize (increase it) and Antialiasing (switch it on).
Both are settable from command line and from the Rendering menu.


Good Luck, Jan


--
Jan Houska HUMUSOFT s.r.o.
houska@humusoft.com Pobrezni 20
http://www.humusoft.com 186 00 Praha 8
tel: ++ 420 284 011 730 Czech Republic
fax: ++ 420 284 011 740

Tags for this Thread

Add a New Tag:

Separated by commas
Ex.: root locus, bode

What are tags?

A tag is like a keyword or category label associated with each thread. Tags make it easier for you to find threads of interest.

Anyone can tag a thread. Tags are public and visible to everyone.

rssFeed for this Thread

Contact us at files@mathworks.com