We value your input!
Please participate in Archicad 28 Home Screen and Tooltips/Quick Tutorials survey

Installation & update
About program installation and update, hardware, operating systems, setup, etc.

R19/6006 3D problems

Jeff Kogut
Booster
As soon as we updated we're having major problems in 3D on some projects, but not on others. 3D has become unusable as a tool.

Switching in to 3D causes several 3-4 second delays of the spinning circle. Then when switching to 3D Explore it lags 4-5 seconds and then runs as normal moving about the model. But then hitting ESC will trigger a few more 3-4 second delays. Selecting anything takes 3-5 seconds for it to happen and triggers more 3-4 second delays.

This is the same on 5 workstations with 2-4 year old i7, SSD, Win7 64 bit, 16gb RAM, and a mix of HD6670, GTX650Ti, and Quadro K620 video cars. The consistent item is particular files. Actual file size does not seem to matter as some larger (140mb) files work fine but our template (102mb) and other files (112-135mb) have the issue. We updated all video drivers and Java.

Our template has some furniture sets, cabinets, etc. set up already so they can be quickly moved in to a model. I've tried deleting some to all of the furniture and it appears there is some threshold where the model loses the lag issue. I have tried many deletion combos and can't isolate it to any one object. But some of our finished models also have the issue and this 'parts area' furniture has been eliminated (or moved in to the model).

Turning off Transparency has no effect, nor does turning the sliders all the way down in Advanced Redraw Options in the Work Environment.

Is anyone having similar issues?
Does anyone know what changed?
Suggestions for any other settings to try?

Edit: I posted here what our template looks like.
http://archicad-talk.graphisoft.com/viewtopic.php?t=51465
AC19-23 | Win10 Pro | i7-8700K | Quadro P600 | 500gb 960 EVO M2 | Dual 28" 4k Samsung U28E590
15 REPLIES 15
Anonymous
Not applicable
Scenario (everyone can try for themselves):

1) create a surface and assign a texture (jpg image).
Choose a large jpg file > 100Mb.

2) create a wall and assign this surface to the wall

3) save the file

I have opened the file in 3 different Archicad builds.

After opening the file open a 3D window.

Archicad 19 build 5005: smooth operation using zoom or orbit
Archicad 19 build 6006: terrible lagging/halt; spinning wheel of death all the time
ARCHICAD 20 build 3008: smooth operation using zoom or orbit

BUG in 19 build 6006 (using Windows 10 64-bit)?

-
Barry Kelly
Moderator
Gier Lund,
I have merged your post here as it seems others have found the same problem with build 6006.

Barry.
One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11
Laszlo Nagy
Community Admin
Community Admin
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...
Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac27
Anonymous
Not applicable
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...
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.
Laszlo Nagy
Community Admin
Community Admin
I am just guessing but I think the fact that it is summer (many people are on vacation) and that the localized ARCHICAD 20 versions are coming out probably means that at the moment there are less resources for an ARCHICAD 19 update or hotfix.
Again, I am just guessing.
Loving Archicad since 1995 - Find Archicad Tips at x.com/laszlonagy
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac27
Anonymous
Not applicable
Update:

Combing the file for surfaces with high resolution image files and decreasing their size/resolution fixed the problem. We did not have to do anything with the mirroring so that bullet was dodged.

We've put together a "best practices" document for the office so that we don't have large files decreasing the performance of the file. I'm wiping my brow that this wasn't a more difficult task (with large files everywhere) causing major delay to fix. At the end of the day, it was a good lesson to tighten up file management.
laszlonagy wrote:
I am just guessing but I think the fact that it is summer (many people are on vacation) and that the localized ARCHICAD 20 versions are coming out probably means that at the moment there are less resources for an ARCHICAD 19 update or hotfix.
Again, I am just guessing.