Just testing our airports in 2024, it appears projected mesh now no longer displays the default a detailed normal maps.
Nor will render projected mesh normal maps render.
Here you can see an apron material loading the details map however the surrounding projected mesh doesn’t load the detailed map. This obviously looks quite bad.
I believe this is the expected behavior now due to the new displacement maps for aprons. Have you tried adding a detail map to the materials of your projected mesh?
+1 on this. Terrain detail maps do not appear to apply on top of projected mesh texture. Changing type of surface had no effect, other than ‘allow grass’ or not.
To avoid a duplicate im going to attached another bug report here.
Version:1.0.84.0
Frequency: Consistently
Severity: High
Context: Custom Scenery Package
Bug Report:
Build 84 fixed asphalt detail maps showing on Projected Mesh’s in 2020 and loaded in legacy mode, see screenshot 1. However 2024 built packages Projected Mesh’s DO NOT have thier assosiated detail map, see screenshot 2.
Screenshot 1 [Built in 2020 running in 2024 as legacy package]
Version 1.0.84.0 introduced a fix to reinstate the behavior of 2020 packages.
However, detail maps on 2024 package projected meshes are no longer supported.
There has been a significant increase in terrain LOD depth, such that the resolution of textures can be increased and details baked directly into them.
Documentation is still lagging on this so I can understand the confusion.
I have logged a separate issue for this to make sure this is something we clarify.
Thank you for the clarification and fix for 2020 legacy mode.
Just a question on the 2024 projected mesh standard.
Our airports use large albedo (over a big distance) with roughness (comp) and normals maps.
With the new standard are we expected to now have albedo, comp and diffusion on the same UV or can displacement be loaded on to the secondary UV space so that the smaller diffusion map can loop on a smaller tile loop than the albedo?
EG Im hoping that a model can support UV1 (albedo 4k, comp 4k) and UV2 (displacement 512px or whatever size is then tiled to keep efficiency) or we have a default asphalt or concrete etc displacement map we can apply to the projected mesh in the SDK.
Without this it will cause quite a problem if the displacement map needs to be looped and then baked into a larger image and then loaded onto the same UV as the albedo. This method is going to increase the size of the Projected meshes over all texture sizes significantly doing it this way…
Here are the current problems still with projected mesh for 2020 legacy mode content in 2024.
Normals are still not working on projected mesh objects. EG when you add normals to the PM model in blender, these arent rendering in 2024 at all.
The default SDK detail maps work for asphalt only, but not any other default material types. Other material types dont work EG the grass type or the ability to set a PM to paint type etc.
Adding detailed maps to blender custom PM models doesn’t render in game and has never worked.
Debug tools in 2024 devmode for normals dont seem to work either anymore
You can use NZA Simulations - NZCH - Christchurch (on the market place) to check and hang the sun low on the horizon to see the normals working in 2020. Which are the in the original screenshots I’ve provided above.
For grass you can use NZA Simulations - NZMF - Milford Sound Region (on the market place) and check the side of the run way for the PM grass not working example (you need World Update New Zealand installed and remove the WU NZMF as well for it function correctly)
I don’t have an example for custom detail maps being added to PM model and exported from blender as its never worked.
My issue is with 2024 SDK compiled Projected Meshes. They are no longer blended with stock detail maps (for example surface=Aspahlt etc). This is fine, but It would be nice if we could insert out own detail maps.
As soon as I add a texture to the detail color/oclusion/normal slots, export and compile (2024 sdk), the projected mesh material in question no longer renders at all ingame.
As HybridNZ said, this never worked in 2020 either, but since we lost the surface=Aspahlt and other stock detail maps, it would be nice to allow custom detail maps.
I briefly got a detail map to work on a projected mesh… somehow… but then it got bugged and had to remove it. The projected mesh does not load with a detail map. We also can’t apply any sort of normal map. We also can’t add the game’s default detail map, eg asphalt, to the PM. So I’m a bit confused why the topic says “fixed”.
Is there an ETA on this? This is fairly critical for airports. We can’t use detail maps on our aprons, this is quite serious, is it not?
Has anyone supplied you with a sample? If not I will do so today, please let me know as soon as possible.
Our team has been away on summer (in our location in the world) holidays … were starting to get back to it now but we haven’t had a chance to make up a sample.
Would be great if you could.