Any chance we can get the Z (now Up) killzone value exposed from world settings? It seems to be overall restrictive to permit only up to -500 vertical units and not allow creators to override this value manually.
Iād recommend requesting that in a new issue thread so it gets picked up properly by our internal tracking so the right team can assess that request!
Regarding something rendering related then, is there any chance the Water plugin Material Function āGetWaveDataā can be exposed as well? This is a stock Unreal material function responsible for getting the Gersner wave data from a water body, without this function interacting with said system inside materials is not possible to my understanding, either this function or Custom material expressions would do the trick.
@Kev.EG sorry for being late, but I think this setting might not have been mentioned upthread and I always kept forgetting about it. I personally and other rely on it to achieve certain visual clarity or equality across different platforms. Additionally this setting allows to potentially boost FPS performance in certain situations.
On the post processing volume thereās a way to disable āLumenā.
bOverride_DynamicGlobalIlluminationMethodDynamicGlobalIlluminationMethod=None
External reference:
It would be great if these settings were also exposed.
We have a new wave displacement atlas system in the works that brings a lot of improvements over the current wave system so Iād have to check if it makes sense to expose that Mat Function at this stage or if weāre better off just holding out for the new thing.
1 Like
Thanks! Unfortunately weāve got 37.00 in lockdown now so I canāt make that change, but I will check in with the team on that one asap.
Just for clarification, even if it would error in v37.00, can it still be enabled in a future version?
In my case I can temporarily revert it, but I would like to enable it later again and disable global illumination.
Yes, exactly. Once 37.00 goes live, you will have errors in your project to resolve for properties that arenāt allowlisted (Iām checking to see if this will happen for already published projects or if it will only error if you try to re-publish in that version, Iāll get back with an answer on that later today).
If we later allowlist those properties, you can start using them again.
Iāll expose the DynamicGlobalIlluminationMethod property on the PPV for 37.10 so you can use it properly.
2 Likes
Ok so already published projects will keep working even if they use a disallowed property - this will only be a concern if you try to republish, then youāll have to fix all errors before publishing again.
2 Likes
Despite what the post is titled, Iām 99% sure it was JUST StaticMeshComponent related properties that were disallowed like this, if this is now being applied to everything, notably PostProcessVolumes, once 37.00 goes live, I imagine there will be a lot more properties being listed off here by people to be added properly to the UI.
Can we expect to continue receiving responses and such here once that happens? Many creators projects will still likely break and people will want to have properties validated if it applies to things outside of just StaticMeshComponents.
Sounds promising, the Gerstner wave system did frequently give me trouble. In the meantime though GetWaveData would be nice.
One other thing, whatās the status on RuntimeVirtualTexturing in UEFN? Is there a reason it is not fully allowed to be used? Itās something Iāve wondered for a while, and wanted to use in my maps as well. I know many creators have wanted it for a very long time.
1 Like
Iām pretty sure it was a global change when it was enabled last time. Either way, youāre right - weāll likely get more requests after 37.00. We are constantly working towards exposing more things and with SceneGraph getting built out more, things will come through there as well (my team is picking up PPV for SceneGraph shortly, so weāll see some movement on that soon). Iāll be keeping an eye on rendering related things here.
RVT is currently not on the roadmap at this time, so not part of the short term plans. What use case would it solve for you?
This will have to land in a later version as we currently donāt have a good way of exposing partial dropdowns. Currently that option contains things like Screen Space GI (Beta) and Plugin entries - this will have to be sanitized before exposing. Can hopefully hit 37.20.
@Kev.EG just checked v37.00. It looks like bDisallowNanite is only a mesh component setting. While great for finally having it, itās a bit unfortunate as the Nanite mesh is still included and probably cooking for potentially every custom mesh asset.
Can we get the checkbox and itās functionality exposed inside the mesh asset settings?
Nanite Settings / Enable Nanite Support
I would like to untick this setting for certain low poly meshes as I donāt need any additional Nanite geometry or generally want a target mesh to be non-Nanite. This should hopefully also reduce the final project cook size.
2 Likes
RVT is an incredible tool for blending things together, such as objects with the terrain itself, like grass, rocks, terrain mesh inserts, and so much more. Itās used on every single one of Epicās official BR type maps to my knowledge.
RVT also serves as a MASSIVE optimization to complicated landscape materials, due to how it effectively stores the result of instructions to be computed once rather than every frame. Even if you arenāt using it for blending things, merely adding it to a landscape material of your own has a good few benefits. The fact it hasnāt been added to UEFN is another one of the main things that puts me off from serious environment tech art design, I really donāt see a good reason its not in or at least planned.
3 Likes
To follow up on my lost post, we got āBounds Scaleā exposed on the mesh component, however the mesh asset setting still does not expose the setting for adjusting the bounds. In order to do that, you have to edit it in regular UE and migrate the asset. This workflow is not very convenient, therefore I propose the exposure of the related mesh asset setting(s).
We can visualize the bounds, but the settings for adjusting it are still hidden.
3 Likes
This is what i need so the thing doesnt vanish when its semi off screen i think ?
Opting out of cooking in the Nanite data is a larger discussion to be had as opposed to what I exposed as a component override. It does make sense, but it means weād have to include all the Nanite data in the future when we go āNanite everythingā - meaning a lot of projects would suddenly have Nanite data cooked for the first time in one go.
Iāll have to look into this.
Thanks! Iāll bring this feedback back to the team.
1 Like