Doing a LDBIM Export on a Sheet Frame with custom car, counterweight or ghost positions would crash.

PropertyGrid generates hundreds of GDI objects for TemplateUITypeEditor

In the wrong contect, this would crash the Liftdesigner UI after about a hundred user interactions.

There was also a smaller leak in the drawing core.

..when opening the result in AutoCAD

For some variations of gear on top, single deflection sheaf, the angle of wrap for the rope was 180 degrees minus the true value.

It accidentally had an emissive component and was bright white.

Giving a sheet a border frame from a DWG via the sheet's property grid has been fixed.

In some situations, mostly after some Undo operations, the property grid would send a change intended for one grid element to another.

There was no individual index and no name, they all were just '-1'.

Roof faces would sometimes subtract from the gable length as if they were active, when in fact they were not

In a previous version, we replaced function calls in rules with variables. We did not consider a quirk in VB.NET that affected string concatenation there. This caused rule compilation failures and performance problems, observed first on the "Develop this BIM Component" sheet.

It is now possible, via settings or the prototype DWG for dimensions, to define a background fill color for text fields. This can be used for highlighting or to make dimension texts on dense backgrounds more readable.

Liftdesigner now supports loading up to SolidWorks 2023, Revit and Inventor 2024 and Creo 10.
CAD parameter updates are possible for the most recent SolidWorks and Inventor versions.

In the component exchange dialog, there are now several ways to filter the components on offer. In the Table View, one can set filters at the top of columns. And at the top of the Tree View, there is a new filter icon where one can define filters that are applied to the whole tree.

Shafts and machinery rooms can now have a range of roof shapes other than just flat.

Sheet frames and sheet frame texts now have an URI property; they are exported to SVG and PDF and turn the elements into clickable links.
They are also exported to DWG as plain URI properties.

Doing a LDBIM Export on a Sheet Frame with custom car, counterweight or ghost positions would crash.

It accidentally had an emissive component and was bright white.

PropertyGrid generates hundreds of GDI objects for TemplateUITypeEditor

In the wrong contect, this would crash the Liftdesigner UI after about a hundred user interactions.

There was also a smaller leak in the drawing core.

..when opening the result in AutoCAD

For example, 294.5 mm was rounded down to 294 mm for display in drawings, instead of up to 295 mm as in previous versions (up to Liftdesigner 2020)

When copying components in the data manager between manufacturers, node files (for UserComps and CAD Files) were not copied along.

They previously required an automation license by mistake.

Deleting one manually would actually delete the other after a recalc.

When exporting a DWG with the default metric prototype DWG, the print settings when viewed in AutoCAD 2024 were not properly initialized.

Also affected: X3D, POV, SAT and STEP.

There was a premature conversion to the signed short data type.

UserComp and Sheet Frame loading code would open files with the harshest lock possible, meaning no other LiftDesigner instance could access the files at the same time. This resulted in wrong drawings and models on LDAWP servers under heavy load.

In some usage scenarios, the special sheet frames for the sheet border and title had data deleted, but then used. At the very least, this caused a small memory leak, but also crashes.

Due to an internal bug, LdBIM exports with non-ASCII names were not in a format that the ElevatorArchitect importer could read.

The UserComp's name was used as is to determine the filename to save under, which did not work if the name contained slashes or other special characters.

Previously, text containing right-to-left sequences would disable the automatic line break calculation.

Previously, text annotations set to underlined would use an underlined font. Now, they use the regular font with a line drawn under the text, just as AutoCAD does, and just as the \L and \l escape sequences would use. Export of underline to PDF and DWG was broken, too. Especially bad: even without underline, we would export a made up font modifier to the DWG, which did confuse the Revit importer.

Change a component, select "Document View", select a component with a document (indicated by the green selector; an example would be the Guide Shoe with GS_RID 2.) A licence error would pop up.

Some checks were added that prevent input infinities to propagate to our internal geometry representation and exports.

Give a dimension an ID >= 32768 and some conversion to SHORT will have it interpreted as something small and have the dimension sorted in wrong in drawings.

If all extension points for a dimension endpoint lie outside of the visible box in the same direction, that is now respected and the selected point is not clamped to the visible box.

When image view frames were introduced, it was overlooked that a bit of code would automatically set the v4 compatibility flag. When discovered, it was left alone to avoid sudden incompatibilities, but now it has been disabled as the titular bad side effect of that flag was discovered.

Most dynamic dimensions were destroyed and recreated in CalculateModel. In some reproducible cases, trying to select them caught them in the destroyed state and selection failed.

This was a sorting bug, the description flag unintentionally entered the sorting key

In the floor level material dialog, having the box unticked still triggered a lengthy CalculateModel call on every change.

Building Storeys are now sorted by level
Project, Site and Building names are now customizable in the document's component BIM Properties
Nonstandard door type enum values are now stored in UserDefinedOperationType

Previously, at least three were required, for no good reason.

API Bug only

Have a freshly created anchor rail
Set the concrete beam to active
Set CONCRETE_BEAM_DZ
Call CalculateModel
Only then, the concrete beam will be activated and the activation will reset DZ to the default of 200 mm.

Workaround: Do a local CalculateModel on the anchor rail after setting the concrete beam flag.

Dimensions set to be visible if one or both end points lie outside of the frame's visible box are usually drawn at full length. Now a new option "Cut at geometric limits" is available for them in the property grid, shortening their display to the part that matches the geometry.

Block references, even though they are just in 2D space, can be flipped in 3D space. This build fixes export of the most common unusual case.

For rail brackets set to custom fixing options, you can now individually position the separator beam using the RB_SEPB_Y value in the local data table

A new context menu item allows you to quickly save the current view frame under its stored filename.

If you activate a separator beam for rail brackets on the rear wall (for the counterweight), Y2 was modified so the rail brackets would extend all the way to the back of the car. It now is left untouched.
Separator beams on the right and left wall with an L-shaped car frame had the same effect.

after edits, the Overwrites docking window would jump back to the top after edits. It now remembers and restores its previous position.

Previosuly, CAD files could only be added from network shares mapped to a drive letter, now the network path (\\Server\...) also is accepted and does not lead to a cryptic error

Some CAD files natively have rounded parts, we need to have them tesselated to triangles for processing. The new option "Tesselation Detail" in the property grid of CAD files controls how many triangles are used.

An overeager fix for an infinite loop subtly changed what gets displayed of the ghost components

The PSET selection now is filtered according to the actually exported IFC class set via DigiPara.IfcExportAs

Builtin parameters and user defined parameters are now exported the same way, all should be editable and visible like parameters added in Revit itself.

Sad exception: The OmniClass number refuses to let itself be set via the API available to us.

In an effort to make usage easier, BANK_2_START_SX was reset to -1 if it was greater than the number of shafts. This turned out to break existing code that relied on there being no meddling with temporarily nonsensical states, for example by first setting BANK_2_START_SX in a new project, then adding shafts.

Bug was introduced in LD 21.0.11 and also fixed in 21.0.217.

Still a work in progress, we need to test more samples.

Under very rare, but reproducible, circumstances, the last sheet in a PDF export in the LDAWP environment would get incorrect sheet frame sizes from DWG frames and dimension the page wrong

In a postprocessing step for 3D exports (3DDWG, IFC,...), an array was sometimes accessed out of bounds

Sheet/Frame save/load operations now support full unicode filenames. Previously, only characters in the configured system locale were supported.

The shfrm2V4Compatible-Flag in LDXSheet.Mode2 was set for all DWG frames on dynamic sheets while it should be off. This affects the position of those frames if they contain non-line drawing elements.
In the rare cases this causes wrong placements, a manual recalc after the load was a workaround.

Access to dccSettings.xml files has been made more robust

If set up in the document BIM settings before the document's objects are created

It was simply completely broken since early builds of Liftdesigner 2022.

Rights to change system wide XML configuration files are now granted to everyone.

If activated, various exports of BIM Properties to PSETs threw errors.

When cutting some CAD geometry with a section plane, be it a detail section or the ghost car section, the process producing the polygons on the section plane would sometimes get stuck.

The BIM Properties defining IFC export properties have been simplified:
- it is no longer required to have leading and trailing dot for enum values
- instead of a plain IFC type, which was limited to PSets, you can write IFCTYPE=... in BP_DESC for all properties.
- Adapt our standard BIM Properties to make use of both above
- we no longer write descriptions (BP_DESC, BPS_DESC) into the IFC export

are now copied from the source if you develop a UserComp and save it to a new UserComp in LiftDesigner.

Is now saved when you save a profile group to the database in LiftDesigner

In previously disregarded corner cases, we no longer compile the dynamic rules DLL in hopeless cases, but we do recompile it when required.

Due to erroneous small object culling, some geometry would sometimes be missing from rendered central projection view frames. Traditional line mode was unaffected.

Dynamic dimensions from force symbols did not work in early LD 20.0. They do work now, so to avoid sleeper dimensions popping up when loading old projects, the sleepers are removed.

However, there was a workaround that made the dimensions appear even on 20.0; the removal code now detects that workaround and leaves those dynamic dimensions alone.

The raw loading of pre-2022 files worked, but component exchange was no longer possible.

It was broken and the result was the same as if the anchor rail was selected to have arbitrary length.

We were marking doors as filling shaft openings even if said shaft openings were not supposed to be in the export. That confused the Revit Importer.

Leave 3D views empty if no driver works.

Default data was fixed, duplicate BP_IDs were removed
The code now handles the duplicate BP_ID case better; features that rely on BP_ID lookup will still have trouble, obviouslz.

Duct Delta points now visible on selection.

Fixes failing updates when importing to SolidWorks

Previosuly, CAD files could only be added from network shares mapped to a drive letter, now the network path (\\Server\...) also is accepted and does not lead to a cryptic error

Using LD/EA as multiple users on the same PC sometimes caused file access rights trouble.

Copying the length from one element of the guide rail list to all others was accidentally introduced with the new fish plate component.

When adding a CAD file in "Develop this Product", it would automatically be selected afterwards, which caused a crash in the coordinate system display code.

New database rows in L_DoorDimTab:
DD_DH_MIN
DD_DH_MAX
DD_DH_STEP_WIDTH
If set, the UI defaults to only allow door sizes from _MIN to _MAX in _STEP_WIDTH intervals.
The LDX core only checks for the _MIN and _MAX limits.
Checks and restrictions can be disabled by setting the DD_MODE_DH_USERDEFINED bit (value 16) in DD_MODE.

Various ways in which undo/redo would in some cases not do what it is supposed to were fixed.

In the developer view frames, profile points defining paths now appear on the profile itself in the position they affect the profile.
The PropertyGrid edit functions related to paths have been improved.

Prerequists installation order has been adapted:
----------------------------------------------------------------
1. Microsoft Visual C++ 2015 Redistributable Package (x64)
2.Microsoft SQL Server Express 2017 RTM (x64)

Reboot behavior of Microsoft Visual C++ 2015 Redistributable Package (x64):
-------------------------------------------------------------------------------------------------------------------
- Has been changed to "Reboot the machine and resume on reboot" -> will immediately reboot the machine, if required, after the prerequisite has been installed.

Registry lookup of Microsoft Visual C++ 2015 Redistributable Package (x64):
-----------------------------------------------------------------------------------------------------------------
- Redistributable installer now explicitely looks up the 64bit section of the Windows Registry,
to check whether the prerequisite has already been intalled on the target machine or not.

In the main project data window, the property subwindow stayed empty. It is supposed to show the same properties as the docking window property grid.

A new, optionally installeed, performance profiler docking window shows which components are taking up the most time, so future optimization efforts have a solid source of data to base decisions on.

For ribbons and docking window titles.

Compeletey redone from scratch.

Floor levels marked as sloppy and their associated entries, guides, rail brackets and lamps are omitted from drawings in Sloppy Mode.

Implemented as LDXSheetFrame.GetVisibleObjectsByFilter and the simpler GetVisibleObjectsByObjectId.

Difficult cases:
CGrDoorComp, has both DoorType and DoorDim
CGrGear, has Art and Performance

Below the text edit field, you now get a preview with resolved External$ references.

if it does not contain enough bolts to satisfy the bolt count from the selected length record

The Z axis was sometimes pointing upwards, sometimes downwards. There was no visible difference because all anchor rails were symmetric.

Now it always points upwards. While this was the minority rule, it makes more sense.

They were grouped into the 160...169 range (left wall).

when created between successive elements; that even makes their internal representation shorter.

The number of available LampLists, TravelingCables and RefugeSpaces can now be increased (or decreased) by changing LAMP_LIST_COUNT, TRAVELING_CABLE_COUNT and REFUGE_SPACE_COUNT.

Furthermore, extra machine rooms can be added by increasing EXTRA_MACHINEROOM_COUNT.

Many list elements, such as Guide Rails, Rail Brackets and Floor Levels, have functions to manage list elements. They are reachable via the context menu in the Tree View as "Insert Duplicate" and "Remove" and over the COM interfaces as LDXObject.RemoveMe and LDXObject.CloneMe.

Make raw IDispatch ** accepting functions (DpGetInterface) private.

In the compatibility test sample 17_0_0_E, the gear flips orientation from one calculate run to the next.

LiftDesigner product catalog archives are now downloaded and updated over the network in the new Liftdesigner Cloud Manager.

Fish Plates link two Guide Rails together.

Also happens with separator beams

The VisibleBox can now be driven by .NET rules and be relative to any component in the data model.

A context menu entries now allows you to inspect the source of External$ substitutions in imported DWG frames.

A SaveUndo should be performed, though.

Do not persist activation bit, only the individual option bits

When loading \src\LDNET\ManagedTests\ManagedTestData\FileCompatibility\20_0_266_B.ld3,

Shaft0.Car.Frame.YokeGuide0.GuideList0.Guide-1.WorldMatrix.R.Z
takes an extra CalculateModel button press to find its final value.
After load, it is at 5020, after the extra calculate at 5170.

to allow making dynamic dimensions from one floor level to the next.

The idea is that Shaft.Entries1.E0.Next. would yield E1.

Before this flag was introduced, it was effectively always on, so this is what the entry level default constructor now does.

The shaft wizard, on completion, disables it.

Add a new entry on an already populated side, and the flag gets copied from a previous entry, so it defaults to off then.

BUT, if you add a new entry on an entirely unused side, it will default to on.

Change suggestion: on adding the first entry on a side, find any other entry as sync soure.

Trigger: A serialization error due to missing AFX_MANAGE_STATE in the code path
Crash reason: Poor error handling

always go to one specific corner. This leads to problems for views with a VisibleBox that excludes those points, the dimensions then vanish.

Solutions: Put the extension endpoints to a visible shaft, or set multiple extension points.

Followup to TR-06270

The windows system was already preventing most of the invisible work.

just like in view.cpp.

Also, please rename executable to LiftdesignerCloud.exe

Should be automatically numbered with the build processes.

Hatch not correct shown between machine room and shaft

CalculateModel should be split into two functions:
One to call when modifications have been made that require certain updates,
and one to call when the updates would actually be needed.

The first function should just set some flags and not do any work so it can be called often on any change.

The second function can then be called by anyone who needs current data without needing to know what has changed.

The current CalculateModel would then call both those functions.

making default visibility checks return wrong results for it.
Related to TR-06260, the full fix should not happen in LD 2020 because of possible side effects.

We currently handle all bounding planes of the convex cut object in order of definition. Reordering them so that subsequent planes are as orthogonal to each other as possible would make the resulting body lists easier to manage, with less large objects with sharp angles.

Under specific circumstances. The observed case was a sheet with two frames, the second having a custom car position. Deleting the second frame with "DEL" on the keyboard caused the crash.

It takes up most of the body list building time in complex situations, is only used as a pre-check and does far too much work for that purpose.

For example:
Shaft0.RopeCompensationUnit1.Buffer0.

ChangePartRID is never called on that component, so it stays at its initial RID 0 and default activity state 'active'. Later RID changes can not reproduce that state.

Attempt 1: Test in the 21_0 branch whether generally disabling components that start out with RID 0 is a suitable fix.
Turns out that is a bad idea due to too many objects with RID 0 that still need to be active by default.

Attempt 2: Just fix the specific observed situation.

Regular exports from BIM frames show them as very transparent on import, the way it should be.

They were solid blocks back in LD 2015 or 2016, we fixed that, but the fix now only applies to BIM exports done the regular way.

A proper solution would be to turn all dashed/dottet objects transparent on 3D exports. This would also change the look of doors, the ghost door postions would turn transparent.

No action if module extis in export directory

Create a WPF app for LDCloud (download / manage ldcloud libraries)

The data communication is complete with salesforce soap api.

Create a view based on the design specification from tfs\Documents\Development\LD Cloud\Design\cloud-finish-grün-final.jpg

Enable / Disable Modules by Contract

Please save which level 1 & level 2 items were expanded and which were collapsed. Save this to the settings file for the next session.

Non existing metafile instructions

Show uninstall library reason
- library not longer available
- library not licensed

Internal -> use a returncode for further improvements.

Sort ldcloud libraries from cloud group, contract and library name

Like:
- Similar
| - Common Libraries
| | - Some Libary 00055.ldm12

Use database caches to locate properties in their standards.

Lazily sort properties and standards by their BP_ID and do a binary search.

Exploit that most message lookups will hit the cache, requiring neither a database connection nor a default value. Passing those along has considerable marshalling costs, and they need to be generated and processed.

A new lookup BMessageCached was added, accepting only the message ID and LCID.

If possible. Selection change can also mean switching sheets; view frames with custom car positions need a recalc, then.

Instead, it uses only the bit LandingDoorModes.ldmNoSil in LDXLandingDoor.SD_MODE.

It should use both bits, while old projects should have the bit in DT_DRAW_TYPE cleared on serialization.

At application level.

In sloppy mode, all normally triggered CalculateModels should be with reduced iteration count.

Only the active view frame should really get updated; other dirty view frames should be visibly marked as outdated (grey/pink/soft).

Only the dedicated recalc button should do a real full recalc and rebuild all frames.

Also supported now:
5[2] -> 5*[2]
3*[2]*5 = 3*5*[2] -> 15*[2]

If the primary dimension is Inch with a configured rounding of 1/16 and the secondary dimension is mm, there was no way to have the secondary dimension rounded to whole mm.

Previously, all geometry from one occurrence (part file) was merged into one body and exported as one mesh. That causes problems with some importers. Instead, use representation items (features) as the largest unit to combine geometry for.

See also: https://dev.azure.com/digipara/DigiPara%20Developments/_workitems/edit/1796

See AZ-1702 for details. Especially, correct the odd
1' - 0'' 1/4'' format back to the 1' - 0 1/4'' it was in 18.0.

If the parent COMPONENT of a CGrComp has a different SX than the child, CGrComp::DoCalculateModel tries to switch the child's SX to that of the parent. However, even after checking that it found another CGrComp ancestor, it used a hard cast of the direct parent to CGrComp, which the direct parent sometimes isn't. That, of course, is always illegal and sometimes caused crashes (in many more other cases, one would imagine, wrong values for SX).

when dealing with relative CAD file paths that would go higher than the root of the file system.

When copying dynamic dimension overwrites without doing replacements, the standard move overwrite of the copy source got deleted.

When having only the dimension overwrite or the dynamic dimension overwrite selected and naively editing the replacment (so it still contains DynDims.DynDimX), the dynamic dimension did not get the replacement applied.

Workaround: From a LD 2018 installation pool, copy over DWG\tables2000.dwg into the LD 2020 pool. (Attached for convenience)

In the attached project, the value 1000.4 is displayed as 1001 because it is rounded twice; first up to 1000.5 by the deliberate rounding code and then up to 1001 by the string fromat code.
The format rounding comes from the prototype DWG, dimstyle LIFT.

Solution: Ignore the decimal digits setting from the prototyle DWG if it is insufficient for displaying the selected rounding accuracy.

This gets precise mm dimensions displayed as 1000.0 with a forced fractional part; optionally, changing the prototype dwg to allow trailing zero omission removes those.

An IFC export stalls trying to process huge amounts of polygon edge visibility data that the system erroneously generated during simplification steps.

Affected files are in M:\TMP\Moos\2020\TR-Archive\TR-06559.

if the work area is deleted (then recreated at the end of the sheet list), the project is saved and loaded with a different Language setting.

UserComps with this flag take their product group from the parent; the result should never be shfpUnknown.

Skip setting the product group then.

making it essentially unusable.

on a view frame that has shaft 0 visibility disabled, even though machine rooms are joined.

Analogous to the points on LDXCar. Component is already there, just not COM accessible.

If a representation item contains a triangle strip with an odd number of points, the following one was rendered incorrectly (and all following ones, until the next odd numbered one flips the switch again).

So adding rules and profile points (let alone profiles) to cylinders over the DataManager had no effect when loading the component.

Then eliminate lines like
factory.TolerateWarning() ' IFC export warnings are OK for now TODO

and is disabled if dimensions for shaft0 are disabled

If user comps are on manual position mode, activate the x and y rotation buttons to directly rotate them over the matrix.

Also, make X/Y/Z position editing in the property grid do something.

Criterion: Type parameters should have the same value for all elements of a clone group (all front shaft doors), even if you customize that value.
Instance parameters may have different values and can be customized individually.

Examples:
Correctly set to type parameter:
the IFC export type properties
The elements of Pset_BuildingStoreyCommon not mentioned below.

Correctly set to instance parameter:
COBie.Component.TagNumber, I think.

Incorrectly set to type parameter:
Pset_BuildingStoreyCommon.AboveGround; each floor level has a different value here. Same for .EntranceLevel.

Questionable:
DigiPara.IfcParent is currently a type parameter. The rules we do have all evaluate to a constant, so it seems fine. But maybe we want it customized per instance so that the user can set a specific rail bracket to a specific floor?

It can happen that there is a property value that has lost or not yet received its BIM property, maybe even does not have a corresponding property in the database. Make sure those cases are handled well and recover once the property (re)appears.

Only affected orthogonal 3D views. The car section plane clipping interfered.

Immediate reason: the check
if (sbt.Checked)
in LD.UI.Operations.DetailLevelFunctions.SetDetailLevelProperties()
fails and the delete is not executed.

Only the second delete attempt works.

The legacy FLL dialog supports decimals, the recent (new green colored) one does not.
In particular Imperial project dimensions require decimal inputs.
Please consider decimal inputs for all fields marked in the image attached.

Bug-Fixing: Now FLL dialog supports decimals, and displaying Imperial String Value is now right, if the Project-Unit is metric and Display-Unit is Imperial.

It did nothing useful. It should be doing the same as the _BOTTOM_ setting: Extent the maximum range of movement of the cylinder without changing the maximum range actually used by the elevator.

BIM Properties mit fehlerhaften Rules oder, wichtiger, fehlerhaft vom Benutzer eingegebenen Werten sollten irgendwie in den ObjectBIMProperties-Listen klar markiert werden. Z.B. mit rotem Text oder einem Blitzsymbol.
Erkennbar sind sie daran, dass RuleEvaluationSucceeded bei ihnen false ist.

Beispieldatei mit vielen fehlerhaften Rules ist angehaengt.

For example: Property c0065fb7-4899-4753-9b1f-d08a15a7fdf4
(Revit Standard Parameter/Description)
on Shaft0.Entries1.E0.ShaftDoor.

Only over the old ShaftWizard (LD Favicon -> New), after a new project is created, the selection is empty.

As a result, the component BIM settings window stays empty (this is fine! and expected), and if you enter the Project BIM settings over it (instead of over the Ribbon), it will not fetch the full list of BIM Properties from the database, only the retained ones (see ProjectSettings.png)

Opening the project BIM settings calls LDXDocumentBIMSettings.UpdateFromDatabase and LDXDocument.SaveUndo in the wrong order; SaveUndo would need to come first.
UpdateFromDatabase is called in DigiPara.LD.UI.Operations.WpfBIMSettings.lduiVmBIMPropertiesMain.ShowBIMSettingsWindow(),
SaveUndo comes later from DigiPara.LD.UI.Operations.WpfBIMSettings.lduiVwBimSettingsMainWindow.SaveBackup().
The result is that if you do trigger an undo afterwards, the state of the document is wrong; the datatree below DocumentBIMSettings. is all full and if there have been changes to the database that were not yet in the project before, they are now.

The component buttons should work similar to dimension buttons (inverse function).
This will remove the current feature of "Switch on everything / switch off everything)

SingleRuleEditor can be not scrolled. If resize to minimum, no scroll showed.
added minimum size to SingleRuleEditor Form. Added minimum size to docking windows. Added AutoScroll to SingleRuleEditor user control.

Changeable via data tree for Excel Project Integration

it only looks at the GBody lists.

A new flag SheetFrameVisibleClassesModes.sfvcmIncludeLines (hidden in 20_0, not ready for general use in COM clients, interface may change) triggers inclusion of objects that only have lines in drawings.

if doors are set to individual has undesired behavior

To make sure the edited value stays and is not overwritten, the jmWohManual flag in the corresponding jamb mode is set. All changes are synchronized to all floor levels; this leads to identical values on all floor levels, which is wrong because the door heights and jamb parameters may be different.

The synchronization must not occur for floor levels with individual jambs OR individual doors OR if the source floor level has individual jamb or door.

require an additional OnChange event on the rail bracket list to be updated.

Does not affect RID changes over the UI, they send the change event. Does affect RID changes done internally to initialize a project from DutyTables.

Das CoordinateSystem.rfa wird noch von version 2019 auf 2020 upgegraded obwohl ich im LD Revit 2020 eingestellt habe.
Das gleiche gilt offensichtlich auch noch für ein paar andere rfa files im LDBIM file.

or a component below in the tree. On the sync targets, the world roots of the source is still set.

Also fixed in 18.0.237.
A subsequent CalculateModel call would put things right.

This was introduced when car doors got their fixing points for version 2017.

Exception for TR-06038: If LD decides itself that the door should be invisible (for example, because it is on a wall that is not being displayed), the door machine should be invisible as well.

In the attached file, the car DM is automatically invisible in 18_0, but visible in 20_0.

See attached file; the hole is visible in 18.0, but invisible in 20.0 since TR-06158.

There used to be a visibility check by component group in DoCreate3DModell, but it was removed; because of TR-06259, that caused visibility checks to return 'visible' when they should not have.

In the attached LD 2018 file, this leads to extended dimensions (enabled by overwrites) of forces popping up, for example Shaft0.CW.Weight.GuideList0.Force0.Y0.

as if they were identical. They may not be. Combining objects should be based on the clone state, not the DWG filename.

You need to activate BIM properties for LDXBuffer for this to happen.

has weird results. The shaft hole still gets exported as individual object (compatibility with old EAs? Recheck the history of that, we went back and forth a bit.) and with wrong TargetRevitName (that of the next highest object with BIM properties enabled, it seems)

The export TargetRevitName has been fixed.
The main shaft hole indeed needs to be exported as its own DWG for backwards compatibility with the old BIM importer. The old importer always generates its own main shaft opening based on the datatree XML dump, so including it in the shaft or document DWG would have it appear twice in the old importer. Separating it out allows for it to be omitted from the file list for the old importer.
And since holes are only supposed to be visible as their special parametrized families if individual export is enabled, the main hole still needs to be exported as a raw 3DDWG in this case.

If the target revit version is 2020 or later, we can get rid of this legacy behavior.

so the UI has a chance to generate a proper tree

Addtional types are required:

AREA
LENGTH
CURRENCY
URL
Das folgende File muss mit LD synchron sein:

C:\Program Files (x86)\Autodesk\BIT\2020\COBie\Resources\COBie Extension Shared Parameters.txt

If you go to the project BIM properties dialog with an old LD3 file, and standards have been deleted in the meantime, you get a hard crash.

Test: Works.

Test: Works.

Fix shelved at FIX-TR-06207, delay deployment until after vacation for fear of side effects. The bug resides in an often used core geometry function.

Bug probably dates back to 2014.

will be displayed with the same ghost size.

Fixed for 2021 in cs 41612 and 2020 in cs41706.

Since default values are just stored as rules that evaluate to the given value, quotation marks need escaping.

See sample file from TR-06180.

Frame contents vanish on export.

Attached project reproduces all kinds of errors on load.
A recalc should no longer produce new errors.
Just loading the project tests the DocumentRules code paths, to test the RulesCompiler5 code paths, one needs to import LD-Developer*.ldm12 from M:\TMP\Moos\TR-Archive\TR-06180 .

Should allow to trace to the rule that failed, callstack is probably less relevant.

What happens if the passed string cannot be converted to the true value type?

Let the reported value be the entered string value, but set the error flag (resp. clear the EvaluationSucceeded flag).

in CloneGroupMember() if the parent rail bracket is set to individual (but AR still on by group)

so if "Display As" is not "BIM Exports", the whole shaft geometry should be exported

Value can be omitted, though.

Replacement logic:
- BIMExportModes CGrIndividualBIMSettings::m_BIMExportMode should never be synced in memcopy
- Only type parameter BIM property values are synced, not instance parameters.

Rail Bracket instance parameters affected as well.

Payload
Speed
ShaftCount

No, but they were not logged.

Procedure:
Set evaluation of property to disabled
set custom value
set evaluation back to enabled
value is still the customized one, not the one from the rule

Attached file: Block cut by sheet frame secion is hatched in LD2018, but not in LD2020.

so that on export, class names are not reported as empty strings.

Example: LDXID *0033 in escalators.

The overwrite search pattern is malformed, of course, so it should not match anything by that reason alone.

The system was growing and shrinking the list every CalculateModel pass.

Even an annotation is added, it does not become visible in view

It only happens if the window is exactly the same

Was the trigger for TR-06111.

May also affect other features like sheet overlay editing.

With the sample files from TR-06102, selecting anything in the 3d view, LD crashes while doing the grow/shrink thing from TR-06108.

LD 2018 is unaffected, the change to shared DLL MFC for LD 2020 was one of the triggers.

LD 2020 - 199 : different result after loading ld3 again after generation over xml

Attached file has them displayed in 18_0, but they are missing in 20_0.

LD 2020 Annotation shown in LD2020 which is not visible in LiftDesigner 2018

(Title was: DXF Annotations do not show)

Fallout from TR-05984 ?
No, from TR-05961.
The frame in question is marked as V4 compatible, which means, among other things, that annotations should be visible independently of the objects they annotate. This was not on my radar when TR-05961 unified the annotation visibility checks.

Probably harmless.
Yes, it was just a shared pointer that should borrow its target instead of taking ownership; the code already detected it and did the right thing, with the assertion as warning.

and its member BPs with special functions

See attached sample, front car line is visible in 2018, but not in 2020.0.197.

default setting from the Prototype-Drawing?

No, that would be equally wrong in the reported case, the prototype DWG has long extension lines as the default, going all the way to the dimension endpoint.

Instead, the default (configurable via LDXSheets::DefaultDimMode) should go back to what it was in LD2018: short extension line stubs.

The legacy loading code first renames one to the other and produces conflicts.

Reproduce: Test code in shelfset TEST_TR-06080, just call LDXComp.UserChildren.Add() in VB, but with the LDXComp first cast to generic Object.

DelayedActivator is used to show document frames as soon as it makes sense, but no sooner; however, in the case create/destroy/recreate document, it would try to show an already disposed form.

Seems to be another side effect of TR-05333.

leading to crashes when they get released

Changes:
- Please improve layout ( positioning, default dialog size)
- "On IFC4": Enable AND check "Include BIM Properties"
- "On IFC 2x3": Disable AND uncheck "BIM Properties"
- "On LDBIM": Enable AND check "Include BIM Properties"

"Cancel"
"Export" -> "Export & Close"

broke around cs 39471 for TR-05869

Wir unterstuetzen jetzt das AutoCAD2018-Ausgabeformat, das sollten wir dann auch in der UI zum Export anbieten. Neues DocumentCreateFileType siehe Titel.

Suche cfDwg2013, dann findest Du die relevanten stellen.

Results:
Solibri Model Viewer, Tekla BIMSight: No support for IFC4
Revit 2019, FZKViewer, BIMVision, Trimble Connect Desktop: work, BIM properties are visibible somewhere in each.

The new unique_ptr based operations left large and ever growing nullptr holes in the body list that, on repeat calls without cleanup (such as happening in GBodyList::ExecuteHatch) would accumulate and slow subsequent calls down.

verschiedene Einträge zum Thema "BIMProperties" erscheinen rot.

Diese sollten als Default auf "EIN" gestellt sein.

Derzeit sind sie ausgeschaltet und man muss 2 x clicken um sie einzuschalten:

- erster Klick auf "Export as Individual BIM object":
root/"BIMProperties." Node wird erzeugt

- zweiter Klick auf "Export as Individual BIM object":
Jetzt werden dieBIm Properties angezeigt

BIM Properties are only synced from the database to the LDX Project when they are first created or when that function is called.

.LDXType already does something similar, but always returns the most specific interface. No good if you want an ILDXBIMProperties5 and not ILDXObjectBIMProperties5 or ILDXDocumentBIMProperties5.

L_UnitTab mit
U_RID : int64
U_MF_RID : int64 (wie üblich)
U_TYPE: int32 (um die Werte kümmere ich mich dann)
U_NAME: string (kann kurz sein, 64 sollte dicke reichen)
U_DERIVED_FACTOR: double
U_DESC: string
U_COMMENT: string

L_UnitComponentTab mit
UC_RID
UC_MF_RID
UC_U_RID: int64 (referenziert U_RID in L_UnitTab, zu dem der Eintrag gehört)
UC_U_RID_REF_MET: int64 (referenziert auch U_RID in L_UnitTab)
UC_U_RID_REF_IMP: int64 (referenziert auch U_RID in L_UnitTab)
UC_EXPONENT: int8 (signed)

Dann neu in L_BimPropertyTab:
BP_U_RID (referenziert auch U_RID in L_UnitTab, hier brauchen wir jedenfalls im DM einen Browser)

http://www.buildingsmart-tech.org/ifc/IFC2x3/TC1/html/ifcmeasureresource/lexical/ifclogical.htm

IFC Export class/hierarchy changes

Bug where switching sheets TO one with a masqueraded view frame causes wrong geometry to appear on that frame (like TR-05920, same cause)

Core issue: Consistent usage of CGrLdvFrame::IsBehind in CreateModel and Annotations
Also: IsBehindSectionalCut

A couple of components (almost all if you count commented out sections...) do a check for CGrLdvFrame::IsBehind and bail out of displaying geometry if they are on the wall that is not visible in the given view frame.

These tests, if done, should go into a separate function and annotations should use that as an additional visibility check.

On the attached project "Annotation.ld3", rotate the view frame twice around the z axis; in old versions, the annotation will stay visible, while in new versions, it will vanish along with the ladder.

"AnnotationMultiple.ld3" has multiple annotations on other affected components.

sollten mit try{}finally{} abgesichert werden.

Sonst vergisst man leicht einen Pfad, der eigentlich BLogTabDec() aufrufen sollte, aber es nicht tut, so geschehen in RulesCompiler5.Evaluate.

Currently, the DM mode edit can only deal with mods where single bits have significance.

That's not true for all modes. Many have bits that have significance in groups, for example for PG_P_MODE, 1024, 2096, 8192 and 3072 = 1024 | 2096 have different meanings.

Insert a CheckBox with "Include BIM Properites" to include or exclude BIM Properties in / from Export

Fixed for MR hole alongside TR-05634; for the other holes, the error report came from the LD MAX view frame which had no shaft geometry enabled, hence no holes.

Temporarily, until we figure units out.

if Sheets.CLASS_FILTERS is used.

Replace Buttons and Images

Such as guide shoes.

New extension in Dialog, Add LDX Groups and LDX Types to Enable/Disable BIM Properties

Check License for BIM Properties and enable or disable all UI with editing the Properties

So far, they all are evaluated as strings, it would be better to evaluate them as bool/doble rule if that is the property type.

leading to all sort of poltergeist bugs.

- Create a new object with "Add New"
- the green dialog shows up
- i select any user comp

the object appears in the drawing and in the data tree
The object does NOT appear in the additional child form

If a mapping is initially created on a sub-part that is below the main assembly in the list, the first update does not do the right thing (this is fine!) and subsequent updates after the part has been moved to the top also do nothing.

even if there are pending changes in it. We can be reasonably sure those are fine and caused by the opening itself.

See attached project; Annotation looks fine in 2018, lookups fail in 2020

Wird nicht angezeigt

Rules containing literals of string, double and boolean type are now normally just parsed from C++.

The same could be done for plain LD("...") and LDS("...") calls, but the speed gains are not that big. Plus, LD and LDS can be weird and implementing the simple cases in C++ could lead to surprising behavior changes on trivial changes that switch the used implementation from C++ to .NET.

Add new Column BPS_GRP_DESC

In LD 2018, CAD file occurrences that were used as profile point coordinate sources were automatically turned invisible.

Since it is now possilbe (and has been for a while) to control occurrence visibility explicitly, this automatism was retired; if you do not wish to see profile point sources in any drawings, use their the LOD settings to disable them explicitly.

(Extracted from checkpoint item in TR-05984 for better visibility)

In LD 2018 and earlier, if a door was invisible for any reason, its door machine was invisible, too. This is at odds with other visibility behavior where parent component visibility settings have no impact on their subcomponents' visibilities and caused problems (TR-05637).

To disable display of an unwanted Door Machine, try disabling Electrical Components in the view frame; if that is too coarse, either use an LOD overwrite or add "-LDXDoorMachine" to the view frame's CLASS_FILTERS list (a new feature in LD 2020).

Most our COM interfaces have rigid lifetimes. The implementation lifetime is managed by C++, the COM interface just references the C++ implementation, and when the C++ implementation vanishes, COM gets notified and at least doesn't crash if the interface gets used.

See if we can make that more flexible to allow lifetime management to go exclusively to the COM client or be shared between COM client and C++ implementation.

Complicated case. Requires rethinking of the whole Get(Sub)Object(ByTreeName) architecture.

Also: CGrOverwriteNode::FindNodeWithErase

Create new Windows Build Server
Install InstallShield (Check License for InstallShield)
Install DotFuscator (Check License for Dotfuscator)
Install everything necessary for installation

siehe
C:\_tfs\Docs\Development\LD\BIMProperties\Revit Template Table Structures.xlsx

suggest the user should restart CREO.

Im Moment, wenn man in das BPR_RULE-Feld Quatsch eingibt, kommt die Rule-Compiler-Hilfe fuer Condition/Boolean Rules hoch, und bei der sieht man nicht, wo die Rule in den Code eingebaut wird.


Leider Unsere Condition Dialog zeigt nur das was er kennt. Das sind die Funktionen "LD()", "LDS()", und "gv()", wenn sie nicht in Rule-String vorhanden sind, zeigt Dialog gar nicht.

RFA is obsolete in 2019 and main

Also:
Profiles, profile points

Done in CGrComp::BIMExportMode

Should apply the delete operation after you have clicked "OK"

I mean all doors of the same group.
I assume the change notification is missing.

Please also verify that it also works for the e.g.
Shaft0.Entries1.E0.Opening.Hole0.

Customized BIM properties are not returned back to group defaults.

New Dialog for Export BIM and IFC Files

See attached file, when switching TO Sheet 301, the floor markers appear there; when switching back, they are missing from the LDBIM sheet. Recalc fixes things.