Jump to content
  • 0
herbieherb

Maximum of grasses with the grass shader? VB-125221

Question

Is there a maximum in the number of drawn grasses in the grass shader? From a certain area, I have to subdivide the areas in order to render the grass. With a certain amount of grass, that doesn't help anymore. Then some areas are no longer filled with grass.

Share this post


Link to post

17 answers to this question

Recommended Posts

  • 0

Typically there is, when you work with such kind of "Replicators"

 

My experience is from Modo but it will fill a given Area with the amount of

"Particle" geometry and stop after that randomly.

This means you have to either increase the amount of Particles or decrease

the density to fill the missing surface parts.

 

No experience with C4D's Systems but I would assume it is working alike.

And pretty sure that there is no setting for it in Shader or CineEngine.

 

So you can try to decrease the density to check if it will fill the whole Area

that way.

Second option is to use real Grass only where visible and necessary and

normal Bump Textured Materials for areas far away.

Share this post


Link to post
  • 0
45 minutes ago, zoomer said:

So you can try to decrease the density to check if it will fill the whole Area

that way.

Second option is to use real Grass only where visible and necessary and

normal Bump Textured Materials for areas far away.

This is how i work around this. Unfortunately the amount of grass seems very limited even though my hardware coul'd easily handle much more. Something like a renderstyle quality setting for the maximum amount of grass woul'd be very welcomed. Or something like a lod so that grass at a certain distance isn't replicated.

Share this post


Link to post
  • 0

Which version of Vectorworks are you working with, 2016 still? I know some of the older versions erroneously spread the grass across larger objects at the incorrect density, i thought that had since been resolved. However, I still only recommend using grass shaders really close to the camera to save render time, since you often cant see the detail in the distance to make the geometry calc delay worth it.

Share this post


Link to post
  • 0

2018. I also tested it with 2019. Both seemed to work similar.

Edited by herbieherb

Share this post


Link to post
  • 0

Can you send me the object in a test file please? I can confirm if its buggy or a configuration issue.

Share this post


Link to post
  • 0

Here you have a sample. Funny thing is, when you cut the grass polygons in smaller pieces (still same area of grass) all works fine.

grass.vwx

I got this same issue in several different files.

Edited by herbieherb

Share this post


Link to post
  • 0

For me, in the Viewport Rendering, there is grass everywhere (?)

 

But I had the mirrored Rendering on top for the first time that was mentioned

be someone else. It disappeared now anyway.

Share this post


Link to post
  • 0

In the file it only happens on the left side of the viewport. You coul'd also fly around and render without viewport. It still doesn't work in one polygon. Whats a mirrored rendering?

Share this post


Link to post
  • 0
2 minutes ago, herbieherb said:

Whats a mirrored rendering?

 

I don't find the thread again, I think it was @Grethe Connerth

 

The Grass content below the horizon was mirrored to the top of the VP

as if there would be a Mirror or Lake in the Sky.

Share this post


Link to post
  • 0

No, it really seems missing at all. I also had the issue at site models. Thought of, maybe the polygons are flipped in the model, but also found no grass on the inside of my terrain. 🙃

Share this post


Link to post
  • 0

I now tested it with some other workstations (all Windows10, VW2018 with latest updates & drivers). Seems to only affect this threadripper built:

 

    AMD Threadripper 1950X
    MSI GeForce GTX 1080 Ti GAMING X TRIO (latest drivers)
    AsRock X399 Taichi (latest bios)

 

I didn't expect different results with a cpu renderer. Can someone else with a threadripper (or maybe another AMD CPU) reproduce the issue?

Deleting the library folder (sets all settings back) didn't work.

Share this post


Link to post
  • 0

Des kann ich mir jezd ned vorstellen.

Liegt sicher an dei'm Speicher mit ohne ECC 😉

 

Also hab ich's schon richtig gesehen,

vorne links kurzes Gras, vorne rechts hohes Gras und im Hintergrund auch.

Dazwischen ist nix oder ein Weg.

Diese 3 Felder im VP sind bei mir alle voll Gras.

Share this post


Link to post
  • 0

Yes, three of the four areas shoul'd render with the grass shader, one is empty. If it's the ecc i'll officially join your religion 😉

Here is a file where it's easier to test. It has only two polygons. Both shoul'd render with grass on it.

grass.vwx

Share this post


Link to post
  • 0

Well, as said I am on Mojave, VW 2019,

and like with your first example I have problems to render your VP in general.

it needs several attempts and switching between DL and SL before it renders anything.

The first time it looks like it does render but not show anything,

further update attempts seem to start render but abort quickly.

 

EDIT :

It is an issuewith new VP acceleration and max performance settings.

As soon as I switch down to good performance and compatibility the 2019 VP looks fine

 

Rendering DL works fine, Grass on whole Rectangles.

 

In VW 2018 the VP at least shows some initial Lines content and renders and displays

fine. And I DO have grass over the whole Areas in VP or DL.

Share this post


Link to post
  • 0
On 10/1/2018 at 3:34 PM, zoomer said:

EDIT :

It is an issuewith new VP acceleration and max performance settings.

As soon as I switch down to good performance and compatibility the 2019 VP looks fine

 

Strange,

I have to switch down OpenGL Performance ONLY in your (both) Files !

 

I have no problems with Viewports on SLs with my own files so far.

Although these were migrated from VW 2018 or even earlier.

But I had no RW Render VPs so far ....

Edited by zoomer

Share this post


Link to post
  • 0

Any news on this? Is it a bug? Is it related to the threadripper processor? Is there a plan to fix it?

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×