Katarina Ollikainen

@TeeMuki, I have just checked in the newest (private) build, and there you will be able to use your 'way 1'. This is one of the residual issues that surfaced with the big rebuild. I can only ask you to be patient with this - we're putting it through a bit of a stress test and will release the fixes as soon as we know it won't create other problems down the road.

@Jonk, there are still a few issues outstanding, but we're just testing the last parts, and when this is done, we'll have all these question marks straightened out. This year's changes to the landscape area and the hardscape did unearth some old discrepancy combinations that weren't caught in the standard process, and that have created problems with the attributes. I'm hopeful that we've addressed them all now.

@Stefan B., thank you. Ok, I'll check out the file and see if I can find anything obvious. Please note that a few bugs in the Landscape area and hardscape affect the attributes. However, they are completely fixed for U4 and they shouldn't affect any other objects anyway (while we did a significant rework on these two tools for 2025, we found some discrepancies that had to be corrected. The engineers have now done this, and we're testing to ensure all is caught).

@Stefan B., What version did you create the original file, and what version are you working in? It seems like you have issues with all objects, not just the Landmark ones if you can't even create a rectangle with the correct colours. Please send over the file and I'll compare what results I get. Is it only this file that has the issue?

@Nedim, the existing site model can't deal with completely vertical surfaces (yet), so you must offset the bottom modifier slightly (1-2mm is enough). After that, you can add the two site modifiers you created the channel with to the site model data you're using to create the new site model. Take the modifiers and ungroup them to 3D polys (must be done in a 3D view) - then you can include them in the data and they will give you nice and crisp edges. We are working on some exciting changes to this workflow that will make it much smoother, but they depend on an overarching new feature that must be in place first, so today this is the best I can suggest. Let me know how it goes.

@zeno, I've contacted the engineers working on this and will leave an update as soon as I know more about the progress.

@TeeMuki, Hello, can you please send me some sample files where we can see this difference? The engineers are looking at this issue but couldn't reproduce it, so it would be great with the file you're showing here. Thanks.

@Felix_, honestly, I don't know. I'll add it to Jira - if it's already reported it will just be added to that bug.

You can get around it right now (if you're in a hurry to get a drawing out) by adding two 3D loci to the corner symbols to represent the joint. But, as I said, this should work...

@Jonk, you should get the same joint for the corner piece as you specified for all other joints. Can you please send over the file, and I'll file a bug if I can't find a reason for what you're showing here?

@kwik, unfortunately not - I have this on my wishlist. The only way to display this right now is to create two snapshots, one with the colour fill and one with contours and no fill, and place them on top of each other (or, of course, do the same with the site model and one snapshot below).

@kwik, Ok, I've looked at the file. The minimum elevation is at 0, so most of the colour range is below the site model surface. Go in and reset the min elevation and you'll see the range. Just notice that for some reason, when doing this, all data is temporarily invisible - just open the recreate from source data and exit again, and the geometry will be back (I've filed a bug on it). I can also see the snapshot issue in multi-pane view. There seems to be an issue in 2024 - in 2025 it works correctly.

Hi, @kwik, can you send me the file and I’ll have a look.

@Edgar RAMEL, I'm getting the same result in the extruded contour mode. The engineers are looking into it, so I hope we have a fix for it soon. I'll update the thread here when it's done.

@Jonk, I just had a chat with the engineers - the issue was rather deep, but the fix is now verified. From Update 3, everything will work correctly. We'll supply a help tool to batch-update all the resources in your user and workgroup libraries (and any files opened in earlier versions) to get them to conform to the fix. This will work similarly to the plant syle script but be more user-friendly via a menu command. As soon as the command is verified, I'll post it here in the forum with instructions on installing and using it. Thank you for being so patient.