Saw this recent vid on Geometry Maps which is now being integrated into OBD's F+P system.
Looking at the delivered patterns in C:\ProgramData\Bentley\connectsharedcontent\cell\GeometryMaps_Clean.cel, none of the patterns are localised for the UK market.
Started to look at how the Cells could be modified to match UK requirements... starting with S_BSUK_WallsExternal_Block which uses the Block (Tan) material which uses the block12_clean_g Cell.
Problems:
1. I updated the the units in the .cel which was in imperial to metric in the .cel. Hopefully, we will get this changed with U8 for the non-US datasets. It would be difficult to match masonry dims in metric for blockwork or paving for example... otherwise.
2. Added some text in the block12_clean_g.cel to show the horizontal and vertical dims of the blockwork module. On the first refresh, the text included was oversized in the Drawing Model. Never mind, I went back into the .cel and erased the text.
3. After more fiddling, the geometry map just kept refusing to update. I think that this is due to the fact that the block12_clean_g.cel is automatically converted into a Shared Cell. Tried using the Replace Cell> Update Global tool which did not seem to work either.
4. Used the Cell Library to delete the Shared Cell in the file. No update. Went back into the Material Editor via the F+P editor and changed the geometry map to block13_clean_g.cel. That worked. But when I changed it back to block12_clean_g.cel. I did not get any hatch. Looking at Cell Library / Project Explorer window, block12_clean_g.cel does not seem to be re-generated. Also tried clicking on the Material Attribute Update button in the Material Editor without success. Also tried turning the Material Editor>General>Geometry: off and then on again. Again no show.
Is there a force an update from the Material Editor or the F+P editor? After a change to the material / geometry map, the F+P does not seem to pick up the changes (Dataset commit changes etc remain grey'd out).
Really... really frustrating. Any tips, here? After spending the better part of a day on this, I still haven't got to the scaling and positioning bit. Hopefully, any loose-ends falling between the Viz and OBD teams can be sorted before U8 gets released.