[GRASSLIST:399] Re: d.3d

[Paul Kelly]

Hello
Yes, I can confirm that is correct; the inter and cmd versions of d.3d really
don't share very much code between them and are implemented differently. E.g.
as far as I can remember the cmd-line version doesn't do near plane clipping
properly so some objects behind the observer are drawn towards the top of
the screen, and the inter version has problems if you are looking close to
directly east or west, when only half the scene is drawn.

A while ago I thought of extending the cmd version so it could load 3dview
files from the GRASS database from the command line. This would solve most
of the scripting problems as the 3dview file could be written from the
script and then loaded automatically. But I found the code was in such a
mess that I never really got started.

But you can also do scripting with SG3d or NVIZ; NVIZ has fairly good
support for loading 3dview files now although you can't yet do it from the
command-line. SG3d is great if you have access to a Silicon Graphics
workstation.

Paul Kelly


On Mon, 16 Jun 2003, Peter Slizik wrote:

>
>   Hi,
>
> I have a strange problem with d.3d. I'm using it both interactively and from the
> script. It seems to me it behaves differently in both modes. I checked twice I
> gave it exactly the same parameters. And, after reading manuals, I realized the
> non-interactive version lacks some functionality - e.g., there's no "resolution"
> parameter, which is present in the interactive version. Is there any way, how to
> overcome this problem? Or am I just missing something?
>
> Thanks in advance,
>
> -- Peter
>
>