Our team would like to be transparent about the known issues found in this release, while investigation is going on and fixes are being implemented. If you encountered similar issues, please provide all necessary details to us for investigation (synchrosupport@bentley.com) In the meantime, please try out the provided workaround to see if the issues still persist. Not enough memory error or crash on startup of SYNCHRO 4D Pro (November 16, 2022) The most probable cause is that user installed MSVS 2015-2022 redistributable (version 14.34.31931) update by Microsoft. Microsoft has been contacted and their product team is now investigating the issue. It is also confirmed by Microsoft that SYNCHRO 4D Pro is not the only product impacted by this issue. Track this issue logged by Microsoft here: Legacy applications may crash with latest vc_redist 14.34.31931.0 - Visual Studio Feedback Impacted versions: 6.5.1.5 and potentially all versions. Workaround: If possible, do NOT install the MSVS 2015-2022 redistributable (version 14.34.31931) update until Microsoft provides a resolution to this issue. If this issue is experienced, manually add msvcp140.dll to SYNCHRO 4D Pro installation directory: C:\Program Files\Bentley\SYNCHRO\4D Pro should help solve the issue. The dll can be requested by contacting synchrosupport@bentley.com . To be safer, request a copy of dlls from synchrosupport@bentley.com and add them to SYNCHRO 4D Pro installation directory: C:\Program Files\Bentley\SYNCHRO\4D Pro. On some geometry imported to 4D Pro from .spx through Revit plugin, Edit as Assigned does not show manipulator, 3D Resources do not move along the assigned 3D Path, and 3D Subdivision has issues (such as it cannot detect subdivided parts). This issue only occur on some geometry imported to SYNCHRO 4D Pro from .spx exported via Revit plugin; it does not happen to all geometry exported from Revit plugin. For the geometry or models that have this issue, the workaround is to separate those models and geometry then import into 4D Pro using another format such as dwfx , skp, or fbx instead of spx through the Revit plugin. Unfortunately some rework is required after the those geometry and models are imported into 4D Pro in a different format, if previously Edit as Assigned, 3D Path, and 3D Subdivision were used. If you have a copy of .sp file saved in 6.4, and if the above workaround does not work for you, please continue your work in 6.4 until a fix is available. The development has identified the root cause and has started working on a fix. We will make an announcement as soon as the fix is available to users. Learn how to report issues with full details for faster resolution. NOTE that the the suggested fixes and workarounds are not universal and may be suitable only for some particular cases.
↧
