I tried my best to create tooltip description similar to the standard ones
described in macros. For instance, I would like to have something like this
description, found in the standard 747:
I could set the tooltip title
(shown as “ROUTE PAGE” on this image) but I didn’t succeed in having the
bottom part, that is the descritption, the icon and the value. I tried to use
, and , even tried to make them dynamic, but nothing worked, no description
ever appeared. Here is a simple example of a push button where I tried to add
a description, but only the “CLIMB PAGE” title appeared:
You need to add this info to your localization / aircraft.loc file. Make sure
your aircraft.loc file is now located in a folder called localization. Once
MSFS creates your description they send you this file so add your info into
this file. I ended up making a program that writes it in the configuration for
me as this is a lot of work. Here is a sample of just the TITLE. Below is the
SET. I ended up doing all languages in English as this was easier.
Thanks for your answer. I understand the localization is useful when you want
to have the labels defined in several languages, but I don’t want this, I want
English only. In that case, I thought I could define a description with a
‘hard-coded’ label, without the need of a localization file. Do you know if
this is possible?
Hello @ericmarciano , This template is supposed to be used in association with
another (sub)templates (ASOBO_FMC_PushButton template). It may be missing the
associated input event, hence the lack of description / icon. You can check
for any warning error in the behavioer window
Otherwise you are right, for a
custom template and some other default template, the TT_DESCRIPTION_US_DYNAMIC
and TOOLTIP_TITLE_IS_DYNAMIC are the right tags to put to display a plain
text. I will ask the developer if there is a way to force the description (and
icon) to be displayed and get back to you. Regards, Boris
I have not defined any input event because I didn’t need to, maybe that’s why
it doesn’t work. This is why I have many errors like the one you mention
(interaction defined but no input event). Would it mean I MUST define an input
event for each interaction? I didn’t do it and my cockpit works fine, except
this tooltip question.
Not only did I forget about the new localization manager they added a feature
to use hard coding as you just asked that will only be in English. Example.
True
'Set AC Temp Setting'
True
'AIR CON PRIMARY MAIN CABIN'
What I can’t figure out is how to get
True
and have the tt_values with # work. @Boris Can this be done?
I was actually thinking later after I stopped testing and reading the SDK that
you needed to say True for the specific TT #. This could be added to the SDK.
Thanks I do appreciate the quick response.