Settings
Most settings are preferences. A few change what the answers contain, and those are worth knowing about.
The ones that change answers
Units. The unit system the assistant works in and reports back. Set it once; a mismatch here is a source of results that look wrong by a factor of a thousand.
Preferred standard. Which code family answers should be based on when you do not say. A structure checked to the wrong national annex is checked to the wrong partial factors.
Personalization. What you tell Dlubal CALC about yourself and how you want answers written. It shapes wording and level of detail, not the engineering.
Example: you work in metric and set the preferred standard to the German national annex. From then on a prompt like "design a 6 m beam for 12 kN/m" is answered with the partial factors you actually use, without you writing the annex into every message.
If answers keep making an assumption you disagree with, the fix is usually here rather than in every prompt. Setting the standard once beats writing "use the German NA" fifty times.
Connection and access
Under MCP servers, RFEM is the only service with an on/off switch. The switch matters because CALC uses it to access a local application and can read or change your model. The row also shows the Dlubal-Connector status and the version details covered in RFEM troubleshooting.
Geo Zone Tool, File Conversion, Dlubal Account Info, Calc Account Info and the Dlubal Knowledge Base are operated by Dlubal. They are available whenever your sign-in and plan permit access, so they have no on/off switch. Available does not mean executed: Mia calls a tool only when your question needs it. A geo-data lookup, for example, costs credits only when it runs.
Control the Knowledge Base where the choice applies, in the message bar with Auto, On or Off. With Off, Mia is not given tools for that source.
API keys issues keys for the Developer API, on the plans that include it.
Conversation context and titles
Conversation history no longer has a fixed setting such as "10 turns". CALC automatically takes the most recent complete messages from the chat and drops the oldest ones first if the selected model's context window would otherwise be exceeded. The stored chat remains complete.
Chat titles are created automatically from the first message. If the short background call fails, CALC uses the first line of the message as a fallback, so the chat does not remain stuck at "New chat". You can rename it at any time.
Example: a long chat contains 30 earlier messages and several large tool results. For the next answer, CALC sends as many of the latest complete messages as fit the model. The older ones remain visible and searchable in the chat.
Language
The interface language, and the language the manual opens in when you follow a link from the app. Answers follow the language of your conversation rather than this setting: ask in German and you get German, whatever the interface says.
Appearance and shortcuts
Theme (light, dark or system) and the keyboard shortcuts list. Nothing here affects a result.
Where to go next
- Plans and credits for what your plan includes.
- Connecting RFEM for the connector and the API key.