Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-227762] Removal of Size from Land Impact calculation/Texture LOD/Adjustable LOD distance #5974

Open
sl-service-account opened this issue Oct 15, 2019 · 0 comments

Comments

@sl-service-account
Copy link

sl-service-account commented Oct 15, 2019

How would you like the feature to work?

First and foremost I would like Size to be removed/ separated from the LOD factor of the mesh, which easily inflates Land impact on bigger objects despite on how efficient they are additionally adding the adjustable settings (Distance from Camera) will allow for a more efficient way of controlling LODS. Additionally at a content creator meeting it was talked about that people are afraid of using anything less than 1k texture resolution, I believe there is another factor Laziness. The idea behind this is to give users the ability to lower the texture resolution that's being rendered for that object type, while the file remains unchanged so no pixelization occurs.

Why is this feature important to you? How would it benefit the community?

Size being removed from the land impact multiplier is incredibly important to me because it cultures bad behavior (Increasing vert count/uv) along with other things to get a lower land impact result. In his current form it cultures bad assets being created (Bigger objects become much more punished in land impact, rather than smaller objects) which means the reverse of what should be happening happens, smaller objects get more complexity in there geometry, while bigger objects little to none. Ultimately Size has 0 impact on what is being rendered, aside from Bigger objects being better due to Engine culling. For textures, the additional tool to adjust the resolution of an object/object face in real-time Is an incredible asset to have, in not only learning how to be more efficient with your texture space, but also receiving real time feedback on what your object would look like almost instantly.

Attachments

Original Jira Fields
Field Value
Issue BUG-227762
Summary Removal of Size from Land Impact calculation/Texture LOD/Adjustable LOD distance
Type New Feature Request
Priority Unset
Status Accepted
Resolution Accepted
Created at 2019-10-15T00:01:12Z
Updated at 2019-10-16T18:17:29Z
{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'How would you like the feature to work?': "First and foremost I would like Size to be removed/ separated from the LOD factor of the mesh, which easily inflates Land impact on bigger objects despite on how efficient they are additionally adding the adjustable settings (Distance from Camera) will allow for a more efficient way of controlling LODS. Additionally at a content creator meeting it was talked about that people are afraid of using anything less than 1k texture resolution, I believe there is another factor Laziness. The idea behind this is to give users the ability to lower the texture resolution that's being rendered for that object type, while the file remains unchanged so no pixelization occurs.",
  'Original Reporter': 'Creative Voxel (Creative.Voxel)',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'Target Viewer Version': 'viewer-development',
  'Why is this feature important to you? How would it benefit the community?': 'Size being removed from the land impact multiplier is incredibly important to me because it cultures bad behavior (Increasing vert count/uv) along with other things to get a lower land impact result. In his current form it cultures bad assets being created (Bigger objects become much more punished in land impact, rather than smaller objects) which means the reverse of what should be happening happens, smaller objects get more complexity in there geometry, while bigger objects little to none. Ultimately Size has 0 impact on what is being rendered, aside from Bigger objects being better due to Engine culling. For textures, the additional tool to adjust the resolution of an object/object face in real-time Is an incredible asset to have, in not only learning how to be more efficient with your texture space, but also receiving real time feedback on what your object would look like almost instantly.',
}
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant