cancel
Showing results for 
Search instead for 
Did you mean: 
EN
cancel
Showing results for 
Search instead for 
Did you mean: 
iggiv
Expert

Publisher reports "Saved" but no DWG or PDF files are created (Archicad 29)

Hello everyone,

I'm experiencing a strange Publisher issue in Archicad 29 INT (macOS) that only affects one specific PLN file.

When publishing a Layout Book:

  • Publisher completes successfully.
  • Every layout shows Status: Saved.
  • The destination folder is created.
  • The Xrefed ARCHICAD Views folder is created.
  • PNG reference images are exported.
  • However, no DWG or PDF files are actually created.

I've already tried the following:

  • Created a new Publisher Set.
  • Published only one layout.
  • Changed the output folder.
  • Used the standard Graphisoft DWG translator.
  • Opened the project with Repair.
  • Saved as PLA and reopened.
  • Verified macOS permissions.
  • Searched the entire computer for the exported files.

The important part is that:

  • File → Save As → DWG from the same layout works perfectly.
  • The same Publisher settings and translator work correctly in another project.

This makes me believe the problem is specific to this PLN file.

Has anyone experienced this before or knows how to repair the Publisher or project database without rebuilding the project?

Any suggestions would be greatly appreciated.


Screenshot 2026-07-03 at 7.36.34 PM.pngScreenshot 2026-07-03 at 7.37.41 PM.pngScreenshot 2026-07-03 at 7.37.02 PM.png
14 Replies 14
iggiv
Expert

Good morning Ryejuan:

Thank you for your help; I appreciate your response. I believe I did, but there was no result either. I am going to post a new theory that I need to test to confirm. I will explain my working procedure, but I have hope this could be the issue. Please bear with me as I explain in the next post.

iggiv
Expert

Update

First of all, thank you, Barry, Karl, RyeJuan, and everyone else for taking the time to help. I truly appreciate all of your suggestions.

After all the testing I've done, I no longer believe this is related to the output folder, file permissions, the DWG translator, or the Publisher Set itself. File → Save As works correctly for both PDF and DWG. The issue only occurs when using the Publisher, regardless of whether I publish to PDF or DWG.

I now have another theory that I would like to test, and I think it's worth explaining my project workflow because it may be related.

Originally, this project was developed as a single PLN. It included the complete site, both towers, and several DWG references while I was developing the model. As the project grew, the file became very large (over 6 GB), and performance slowed considerably.

To improve performance, I divided the project into three separate files:

  • A file for the apartment units.
  • A file for the North and South Towers.
  • A Site file, which became the main coordination project.

The Site file contains the terrain and both tower models as Hotlinked Modules. It also contains the complete Layout Book used to produce the final drawing set.

While working on the sloping site (approximately 3 meters of elevation difference), I encountered a display issue. The Hotlinked tower modules did not display correctly on the Site floor plans. As a workaround, I turned off the tower Hotlinks on the Site floor plans and instead overlaid the floor plan views imported from the Tower file. The Hotlinked tower models are still used for the elevations and sections so the terrain and building relationships are represented correctly.

Interestingly, I use the same workflow for my apartment unit modules, and their layouts publish without any problems. The issue only affects the tower layouts that are brought into the Site project.

At this point, I'm wondering whether this workflow could somehow be affecting the Publisher in the Site PLN.

Unfortunately, I don't have time to fully investigate this right now because I have an important project presentation deadline. For the moment, I am manually exporting the PDFs and DWGs using File → Save As, which works correctly.

As soon as I have time to test this theory, I will report back with the results. Hopefully, this information may also help someone else who encounters a similar issue in the future.

Thank you again to everyone for your time, suggestions, and willingness to help.

iggiv
Expert

Solved! 🎉

First of all, thank you to Barry, Karl, RyeJuan, and everyone who helped me troubleshoot this issue. I really appreciate all of your suggestions.

After hours of testing, the solution turned out to be surprisingly simple.

The problem was that my Publisher Subset did not have a Custom ID assigned (first image).

All I did was add "CRD" as the Custom ID (second image), and everything immediately started working. Publisher now exports both PDF and DWG files correctly.

What made this so confusing was that Publisher always reported "Saved", created the folders and Xref images, but never generated the final PDF or DWG files.

I honestly thought my project had become corrupted and was already planning to rebuild it. What a relief!

Hopefully this helps someone else in the future.

Thank you all again! 🍻

 
 

Screenshot 2026-07-06 at 9.32.33 AM.pngScreenshot 2026-07-06 at 9.32.46 AM.png
Barry Kelly
Moderator

So, as Karl said, any file beginning with a period will be invisible on a MAC system.

I am sure there will be a way to show hidden files, but I know nothing about MACs.

The files are there, just hidden.

 

By you adding the custom ID, the saved file name no longer starts with a period, so the files will not be invisible.

Still that is not the problem exactly.

 

You don't need the prefix if you don't want it.

Just turn off the "Add prefix for this subset" option or don't use the period as the prefix, use something else.

 

BarryKelly_0-1783384264505.png

 

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
iggiv
Expert

Thank you again, Barry:

Yes, I understand now and I’m glad to know it wasn’t a corrupted file. Rebuilding would have taken a lot of time and there’s still a chance they might make the same mistake. Thanks to everyone, this has been solved. It was a bit scary.

Still looking?

Browse more topics

Back to forum

See latest solutions

Accepted solutions

Start a new discussion!