HebHeb

Thank you very much for these detailed insights. I will find a way to make my library/workflow work with that, I guess. 🙂 I think that I will use my data class as the main bed class but give each style an individual bed color. It might be a bummer for my colleagues using the class structure without using Hardscape or Landscape Area and using polys instead, but it's a good reason to encourage more people to use the dedicated tools ;D

I remember a coffee break where new features on the roadmap for this tool were discussed. One really interesting feature was the ability to end curbs at angles other than 90 degrees. Does anyone have any hints on when this discussed feature might be implemented?

Any idea when the fix will come (Update 4.1 or 5)? Some of our projects seem to be kind of buggy (especially with projectsharing) since opening them with U4, coming from U3 and then rolling back to U3.1. I kind of thought that this whole Hardscape/Landscape Area dysfunction might be seen as a "bigger bug" and would be addressed sooner.

Only working with styled LA and Hardscapes (initially created from versions pre-2020 and ongoing). I still don't fully understand if it will be possible to have separate classes for the "bed" and "General" after the fix. If not, I made a huge mistake chaining a complete workflow and large library to work exactly like that! Because this is what v2025 until U4 would assume is possible. 3 classes: object-class: class-based data mapping and datasets (used by many: bigger group than "specific" styles) bed-class a class with solid attributes only (used only for specific styles) hatch-class: a class with hatches to disable if not wanted (used only for specific styles)

Same Issues. I guess the bug is somehow that (at least for me in the German Update 4 Version), the Base Fill Class and the Class under General where the Object is placed should be different classes but are interpreted as the same. When I change an Attribute Class (Base), it changes the class in General and vice versa. Our Hardscape styles use 3 different classes (object, base, hatch) (which was a really game-changing nice new feature, and I changed the whole library based on that). It's a shame that this is broken now. I hope it wasn't a misunderstanding by myself and this will still be like this, even with the possibility to change color via the attribute palette (which for me isn't that important...)

I am dealing with the same bugs? What helped me: Having just one document open at a time after a restart, so I could access the records correctly again. If not, I had records and record fields from other files (even ones I had open several days ago shown up), the ones i was searching whre missing 🙂 It seems buggy, but after a clean restart, at least for me, it works. (I guess we are talking about the German local Verison and "Datenbank abgleichen")

Actually, I did know this, but speaking about databases (Datenbanken) every day... sometimes you forget just because it sounds too logical. And then the research is almost impossible; neither Google nor any LLM knows what I mean, that i meant "records" instead od datbases... Sorry for the confusion. I would literally die for a UI where you can switch between languages... It's so bad that the local version differs, and in our case, we even have modules/plugins we couldn't live without...

Hope this helps... When the data is inside the database field, there are plenty of options on how to proceed further. Here is just an example example.vwx

Unfortunately, I don't know the English terms... The German translation is sometimes quite... let's say "special." "Datenbank ändert Objektstildarstellung..." But my understanding is: You have an existing site model with "wrong locus points." Go into the site model. You could add a database for all locus points there, writing the existing height inside a field (for example a class based mapping inside data manager mapping). Afterwards, you could change the Z height of each point with the "database changes object appearance" (Datenbank ändert Objektdarstellung). There, you can choose the database field and set it to Z height (you might put them to value 0 first, otherwise it might stack on top...). This operator also has a scale option (in your case, 1000). If you are talking about site modifiers, there might be other workarounds... (My guess was you are talking about locus, survey points, or 3D polys to create an existing model.)

Yes, unfortunately, I’m having exactly the same experiences in this regard. I read in the German forum that it is very important to keep all documents synchronized with regard to the user origin and the blue Vectorworks origin in order to avoid exactly this kind of issue. Maybe this helps as an idea?

Apparently, my memory was incorrect, and the thread doesn't contain the information you were looking for. To get the name as a handle, you need the name... ;D Sorry!

vielleicht hier ein paar Infos die weiter helfen? Marionette - get values/strings or formulas from a existing worksheet

I was testing the German release today and encountered similar issues. It seems like a bug to me, so I stopped further investigations. What works: reassigning the hatch at “joint pattern overlay.” There is something off with the 2D-display settings above (especially when using 2024 styles?)

finally!

i came to the conclusion that it is faster to redraw the whole modifier when "big" changes are needed. wich is a real pity... could be the best and most useable modifier ever for me, but for now I stick with the "old" modifiers (and my Marionette Objects that do kind of similar things...) just because of the poor changeability options. But I am curious to read how other people work with this tool!