ArchiCAD 18 Update 4020 - OS X Yosemite - Missing Fields

[Eduardo Rolon]

Most text on palettes is screwed up but I have missing/hidden text on all the setting windows.

For example all of the data fields have information but I only can see it if I click on them.

[Anonymous]

yes...i upgraded to yosemite, and now when i perform command T on objects like doors, windows, and stairs, i don't get their parameters....but other objects like chairs, bqs etc...open...any glues?
i am using AC15-16, any ideas anyone...im on a deadline.
much thanks in advance

[Laszlo Nagy]

You can read AC 15-16 related info on Yosemite here:

http://helpcenter.graphisoft.com/technotes/operating-systems/mac-os-x-10-10-yosemite/

Not supported versions:
ArchiCAD 13-16 version can run on Yosemite, though these were designed to work well with older versions of the operating system. As a result there is no technical support for operating system specific problems, like the ones explained in this article.

[Eduardo Rolon]

Getting the post back on track.
• I disabled the font and AC behaves correctly but now I just keep finding all the other documents were I use Aptifer
• Any way to fix this bug?

[NCornia]

Rick wrote:
Nicholas, if you see this would you recommend the same action... Repair and run the update again?

Rick, I have responded to your email you sent to tech support. We can handle it from there.

ejrolon wrote:
• I disabled the font and AC behaves correctly but now I just keep finding all the other documents were I use Aptifer
• Any way to fix this bug?

Eduardo,

Yes I believe you can fix this using methods described in an old ArchiCADWiki article about Font Handling. The old article needs to be updated and posted to HelpCenter. For now, see the PDF below for a slightly cleaned up version of that article.

I hope this helps.

Best regards,

[Eduardo Rolon]

Will do that. Is there a more permanent solution or will I be forced to always edit this file? or recreate my template again?

[NCornia]

Eduardo,

It should be permanent as long as you are using your current installation of version 18. The file you edit is global for ArchiCAD 18 and will map the font as you set it for each file that you open which calls for the Aptifier font. In the future, if you open files calling for the Aptifier font then you will potentially need to update the "Xread.Cfg.txt" file for installations of 19, 20 etc. A once-a-year process.

The issue is that the font is being called from your project files. So the permanent solution is to open your project files and change your text elements from calling the Aptifier font. OR conversely, if the Aptifier font has an update and starts to work well on OS X Yosemite with AC18 then you can reverse the edit in the "Xread.Cfg.txt" file and return to using that font. I can submit a report about your situation and see if there would be any fix in an update for AC18. I will mention that these fixes are usually weighted on the number of users with the same problem and it may not be an ArchiCAD-caused issue in the end.

Best regards,

[Eduardo Rolon]

Ok.
Though you should know that I don't use Aptifier on any of my projects and the problem persist even doing a Reset of AC and using a default template.

• AC 11 fails to launch in Yosemite
• AC 12 fails to detect the Codemeter Key but launches without problems
• AC 13 launches without problems
• AC 14 has the error substituting the program font for Aptifier and it is when I started using my base template but all menus behave correctly and the console does not log any errors
• AC 15 same as 14 except it logs "DEFAULTFONT"(11) and all other missing fonts with Aptifier
• AC 16 same as 15. Doing a "New and Reset" and using the regular Template does not fix anything.

-----
I think that the basic problem is "DEFAULTFONT"(11) and that in AC18 the Field Height is too small for Aptifier.
Can you verify at the screenshot to confirm that the "gibberish" for Arial is correct

[Eduardo Rolon]

AC 17 behaves as all priors, opening the base AC template still substitutes the Font

[Eduardo Rolon]

Editing the XReadCfg.txt file does nothing. Have found most of the other font substitutions and fixed them. There were not that many.