Archicad 28 Direct3D Runtime Error

[ETSaum]

Archicad 28 is constantly freezing or crashing, diving a Direct3D / graphics card error.

Archicad 27 and Archicad 26 do not have the same problem.

I've updated graphics drivers, and uninstalled / reinstalled Archicad to no avail.

I get the same error every time; sometimes, it's within seconds of opening the program. Other times, it can take several minutes. But it happens multiple times a day.

'Direct3D Runtime received a Device Removed Message  DXGI_ERROR_DEVICE_HUNG'

That's typically an issue with either the graphics card itself or the graphics card's connection the rest of the machine. However, this is the *only* program experiencing the problem, which is usually indicative of a glitch in the program or an incompatibility between the program and the graphics drivers.

These are two of the smallest projects I've ever done in Archicad, and the only two on 28 so far. Archicad 28 appears to be sending conflicting instructions to the GPU, which causes it to hang. No other programs are effected when it happens; in some instances, when it happens in one Archicad 28 file, it doesn't even impact the *other* Archicad 28 file I've got open.

Dell XPS 15 9530 with NVIDIA GeForce RTX 4060 Laptop GPU.

Archicad 28.0.2 (3110)

Operating system used: Windows

[dyer]

Hello!

We have the same problem in two of our projects.

Project A:

for this project it's somehow related to a specific design option, fade environment and a building materials cut fill (solid+dot-dashed fill). So the problem only occurs if we turn on fade environment and if the element (in this case a simple wall with the previously mentioned fill) is on a specific design option and we start zooming in & out.

If we put the element on another DO or we don't turn on fade enviromnet or change the cut fill for the building material (or any of these combined) then no error message.

We are able the recreate the error as many times as we want to.

Project B:

It just happened on a different WS while I was writing this comment. For this project it was much simpler, my collegue was moving the AC window from one display to another.

We not tested this one yet, just a wierd coincidence, that it came out on a different PC, on a different project while we were investigating the problem.

[Paul King]

---

@Botonis wrote:

Have you checked you motherboard 's BIOS settings concerning the GPU. 

4G decoding enabled- PCI speed- Default GPU, performance settings (Sometimes for OS to handle the performance you have to enable it in BIOS otherwise 

the motherboard has the control) etc.

Are you using any overclocking utility?

Good suggestions, but in my case BIOS settings unchanged from AC27, which did not trigger this particular issue, but yes, 4G enabled, PCI speed = default (no bios or utility based over-clocking)

[Botonis]

I am really curious because we are using the same windows version and GPU (I have a 3080Ti)

Never had a  problem with Archicad and Direct3D errors.....

Is there any chance that something from you hardware is not working properly.

What about your PSU? Any possible software conflict, (Antivirus, Antimalware)

Are your memory dimms OK....

Just throwing some questions here.....!!!!

Have you tried to fix any possible windows installation problem (scannow/sfc)?

To be honest I don't feel this is related to Archicad. Something else is triggering this. 

[ETSaum]

It often happened to me in situations similar to your Project A instance, especially when zooming in on a specific design option wall.

Since I turned off background 2D regeneration, I've only gotten the error once.

[Paul King]

---

@Botonis wrote:

Is there any chance that something from you hardware is not working properly.

What about your PSU? Any possible software conflict, (Antivirus, Antimalware)

Are your memory dimms OK....

....

To be honest I don't feel this is related to Archicad. Something else is triggering this. 

---

I also suspected that it might be a system thing - except for the fact that only ArchiCAD 28 triggers it, and in my case, weirdly,  only while ArchiCAD is running but  not in active use.  Other graphical apps are fine if left running overnight.   I am wondering if there may be an issue with background updating of views, and whether this uses Direct3D.

[Botonis]

Any chance the efficiency mode is enabled for Archicad?

GPU Scheduling for windows disabled?

[Paul King]

---

@Botonis wrote:

Any chance the efficiency mode is enabled for Archicad?

GPU Scheduling for windows disabled?

---

Good suggestions.

ArchiCAD 28 is set to 'High Performance' mode.

GPU scheduling for windows is off (this was required to address some other issue as I recall, possibly in a 3D game or other application, though vague on the details now).

[Frank Schlenke]

Sadly, I have lost hope at this point. If I had to guess, it could be a bug within the design options, since it was added in ArchiCAD 28 and we never had any issues like this in ArchiCAD 26 & 27 or Twinmotion. Also it is affecting all our machines with different setups. Some more some less though. But I don't think its a hardware thing.

[Sefa Yakut]

Hello,

I don't think problem caused by design options. Design options added to Archicad 27 first.

[victorbaboi]

Hello,

I encountered this error today in a client's project, and I managed to reproduce it myself on a new, clean, file with INT template (windows, INT version).
It only happens in 28, not in 27. Both on current build (5000) and previous one (4001). I only had NVIDIA cards to test (4070 laptop, 572.83 on mine, not sure on the other one, studio version and 4070 if I remember correctly, desktop.). One AMD, one Intel on the processor side.

To reproduce it:

- open a new file

- create a new design option

- create a slab (or a single fill), with a cover fill "Block - Stack bond"

- move the slab to said design option

- with the Fade Environment active, zoom out (or in) until the detail level of the element changes from vectorial to solid.
At the exact moment the fill switches from vectorial hatch to solid (basically the old optimisation for hatches), the DXGI_ERROR_DEVICE_HUNG appears.
The window seems to become unresponsive (it isn't, it just stops rendering), and you can still select elements, change them, quit & save.

So this leads me to believe that that bug was introduced in ArchiCAD 28, as the process of switching from vectorial hatch to solid seems to be a bit different: in 27 it switches from vectorial to solid, while in 28 it seems to switch from vectorial to solid and then to empty when the element becomes too small altogether.

I tested other scenarios:

- moving the slider all the way to the right doesn't fix the issue

- solid fills - no error

- trace & reference (expecting similar behaviour from colour & fade) - no error (so it's certainly related to DO & Fade Environment, as it's a per element override in the graphics card, not the entire viewport).

- different fills seem to have different behaviours - some work and some don't ("Brick - Soldier Bond", "Long Brick - Stack Bond" gives the same error) [and Alt+Click on a fill to select it in settings doesn't work anymore :(( ]

- it appears that only vector fills are the problem, symbol fills, solid and gradient seem to work just fine.

- changing the Work Environment >  Advanced Redraw Options > Model Display in 2D Navigation to Simplified model doesn't exactly work, as at the end of a zoom operation it still triggers the bug, when redrawing the fills. Same for Structural Contours Only, but it triggers after a few zooms, not immediately.

My guess it's something to do with the way the overwritten (vectorial) fills are being streamed to the graphics card and not the colour filter by itself.

Workaround:

As a work-around a graphic override to change the fill type works... or probably any other way to avoid the problematic vectorial fills (if you have the patience to replace them with symbol fills, kudos to you - it's probably the safest way for now, and you can replace them back later).

Also, if you are unlucky enough to save the file just at the right level of zoom and get the error on file open, you can just zoom-in the window after the error, close & save and reopen (the window is still active and you can interact with the model).

And in the end, if any of you know of a way to disable the fade environment being active by default, please do tell! I'd be happy even with a registry edit to do it!

PS:: updating driver to 576.52 (both game ready and studio, clean install) had no impact. And I'm not going to reinstall windows since the issue is clearly in ArchiCAD 28.

Thanks,

Victor