x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Foliage scale affects Z Offset positioning

0

When applying scale to a mesh in the foliage tool, it applies the scale to the z-offset as well.

In the attached image I have the scale set from 1-10... I want to make clouds of different size.

I have min and max z-offset set to 2000..

The bigger clouds go up way higher than the small clouds even though they should be placed at the same height.alt text

Product Version: Not Selected
Tags:
capture.jpg (450.4 kB)
more ▼

asked Apr 14 '14 at 09:10 AM in Bug Reports

avatar image

Rasped
58 ● 9 ● 11 ● 13

avatar image Rasped Apr 14 '14 at 09:11 AM

But please... make this an option... even though it is the wrong behavior... it is actually useful... for placing clouds for example :) It looks very nice this way

avatar image fighter5347 Apr 14 '14 at 03:40 PM

Is this happening with every mesh that you use in the foliage tool and could you probably post your steps how you did it, because in my case it works as it should ^^

(comments are locked)
10|2000 characters needed characters left
▼ Viewable by all users
2 answers: sort voted first ▼
0

Hi,

The Z offset was intended to be used to move trees up and down to adjust their origin (pivot location) and to provide slight variation. For this usage case, the Z offset needs to scale with the tree's scale to ensure the tree's trunk remains in the ground.

I understand you want to use it for providing a fixed Z offset randomly scaled clouds, which is a great idea, but as it is the tool can't do that.

We intend to add support for foliage blueprints, which would be the best way to support this. I will also consider adding a checkbox next to the Z offset to toggle whether you want scaled or non-scaled Z offset behavior.

Cheers, Jack

more ▼

answered Apr 16 '14 at 05:44 AM

avatar image

JackP_oldaccount
1.3k ● 37 ● 11 ● 47

avatar image Rasped Apr 16 '14 at 01:52 PM

Ok, I understand the reasoning behind the descision. It does make sense... a little :)

Thank you for taking your time to come back to me and explain(again) why it behaves the way it does.

Props to you and your team.

(comments are locked)
10|2000 characters needed characters left
▼ Viewable by all users
0

Hi Rasped,

I was able to reproduce this effect, however, it is working as intended. Because foliage keeps the origin on the ground, not where the mesh lies via Z offset, as you scale you are effectively scaling the origin point itself, which affects the mesh you used. So the further you scale the origin, the larger the mesh gets but it is also pushed further away from the point of origin to maintain the Z offset ratio. This is why the scale also does not move the object upwards when z offset is 0. The object is directly on it's origin point, therefore it does not need to move upwards (or downwards) to compensate for any scaling changes. I hope this helps!

more ▼

answered Apr 14 '14 at 04:00 PM

avatar image Rasped Apr 14 '14 at 04:52 PM

Hi Adam.

When you speak of the "point of origin". You speak of the pivot point of the mesh? the point that get's placed on the landscape right? So my tree, which has a part under this point looks, as if it is coming up from the ground.

My logic tells me that if I place my entire mesh above this point... That air is also multiplied by the scale. However, my pivot point, (point of origin?) is inside the cloud, so no air is multiplied, if anything, the bottom of the cloud should be close to the ground since this point is 2000 units above the ground.

I have attached a screenshot of my cloud mesh and a screenshot showing 2 pillars and my cloud spread.

the lower pillar is 2000 units, the taller one is 20000.

So unless I misunderstand "point of origin". I believe something is wrong.

Because it says maximum offset... and I set that to 2000... but it ends up being offset by 20000 when the scale hits 10.

[1]: /storage/temp/4046-capture2.png

capture.png (106.7 kB)
capture2.png (166.2 kB)
avatar image Adam Davis STAFF Apr 14 '14 at 05:31 PM

This was where my confusion was as well. The point of origin in your mesh does not necessarily change. If you were to place it as a simple static mesh this would be true. However, foliage only works when attached directly to the landscape, so it forces the point of origin directly onto the landscape. With the z offset you are literally telling the mesh to appear a certain range away. In your case, you stated 2000 units, which means that the z offset is 2000 units away from wherever the original point of contact between the foliage and the ground was. So, continuing the example, the cloud now floats 2000 units above the actual point that the foliage is resting. When you scale that, the 2000 units must be multiplied by the value of the scale itself to maintain the scaled distance from the now larger origin point. So 2000x10 scale = 20000, which produces an equivalent distance from the point the foliage is actually resting to the amount offset on the Z axis. However if you leave the z offset at 0 the scale for z offset becomes 0x10 scale = 0, so it does not have to move upwards to compensate for the increased size of the origin.

avatar image Rasped Apr 14 '14 at 09:12 PM

Scaling the location or in this case the offset is not scaling... that is moving.

By following this logic all meshes placed in the world should be moved when it is scaled?

It is an issue. Either the text explaining the setting is wrong, or the functionality is wrong.

When I offset something with 2000 I expect 2000 to be the offset, not 2000*"the scale I choose"

Please reconsider this.

(comments are locked)
10|2000 characters needed characters left
▼ Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question

Related Questions

Using a rendertarget makes my graphic driver crash. But only in baked game not in editor.

[4.13] Forward render - Instanced (painted) foliage transparent?

My level is crashing.

4.8 Preview 1 - Landscape Grass Population Crash

Foliage not rendering correctly in split screen?

Foliage lasso & select crashes graphics card

4.5.1: Navmesh doesn't work with foliage rocks

Foliage culling seem broken

4.19p4 Foliage is black in editor

Incorrect foliage color in the editor preview when using PerInstanceRandom in foliage material