Author:Justin Merkovich
Posted: Fri Aug 19, 2016 3:50 pm (GMT+1)
Sorry, just trying to understand what is happening here. This issue has been identified by Graphisoft since June 25 and we are still waiting for an update that fixes this issue?
We have a junior person in the office going through every custom surface and checking the pixel dimensions and mirroring options for textures. We are going to decrease any large file size that we find to the 1024 x 1024 range and start there. We'll test the 3d navigating performance and only then will we alter mirroring options - we have used the mirroring options deliberately to get textures to look the way we want so to simply accept the default as shown on the help page in the link isn't really a "solution" so much as a workaround that increases navigation functionality but creates visualization problems.
I can accept that maybe we have used large file sizes for image files and that is on us but if the mirroring is broken, that is a major hindrance to our work and unacceptable. This update was suggested to us by several 3rd parties and now I'm regretting this update in a major way as it is impacting our most important file/client. Two months after this problem was identified by Graphisoft and we are still waiting for an update is not a great situation.
Posted: Fri Aug 19, 2016 3:50 pm (GMT+1)
| laszlonagy wrote: |
| There is info about this issue on the Help Center. It seems it has something to do with large textures and it occurs in 6006 only because texture handling has been changed in this latest update: http://helpcenter.graphisoft.com/troubleshooting/performance/archicad-19-performance-troubleshooting-guide/#Selection_and_Navigation_in_3D_becomes_slow_and_can_even_freeze_in_casetextures_with_huge_resolution_are_displayed_inARCHICAD_19_Update_6006 |
Sorry, just trying to understand what is happening here. This issue has been identified by Graphisoft since June 25 and we are still waiting for an update that fixes this issue?
We have a junior person in the office going through every custom surface and checking the pixel dimensions and mirroring options for textures. We are going to decrease any large file size that we find to the 1024 x 1024 range and start there. We'll test the 3d navigating performance and only then will we alter mirroring options - we have used the mirroring options deliberately to get textures to look the way we want so to simply accept the default as shown on the help page in the link isn't really a "solution" so much as a workaround that increases navigation functionality but creates visualization problems.
I can accept that maybe we have used large file sizes for image files and that is on us but if the mirroring is broken, that is a major hindrance to our work and unacceptable. This update was suggested to us by several 3rd parties and now I'm regretting this update in a major way as it is impacting our most important file/client. Two months after this problem was identified by Graphisoft and we are still waiting for an update is not a great situation.
