• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Hello World

Messages
84
Hi
simply add Hello World to the DA62 SDK example doesn't work. What am I doing wrong?
Many thanks


// Panel Configuration File
// DA62

[VCockpit01]
size_mm=1024,768
pixel_size=1024,768
texture=$SCREEN_1
background_color=42,42,40
htmlgauge00=NavSystems/WTG1000/MFD/WTG1000_MFD.html, 0,0,1024,768

[VCockpit02]
size_mm=1024,768
pixel_size=1024,768
texture=$SCREEN_2
background_color=42,42,40
htmlgauge00=NavSystems/WTG1000/PFD/WTG1000_PFD.html, 0,0,1024,768

[VCockpit03]
size_mm=400,512
pixel_size=400,512
texture=$SCREEN_3
background_color=42,42,40
htmlgauge00=NavSystems/AS1000_BackupDisplay/Attitude/AS1000_AttitudeBackup.html, 0,0,400,512

[VCockpit04]
size_mm=400,512
pixel_size=400,512
texture=$SCREEN_4
background_color=42,42,40
htmlgauge00=NavSystems/AS1000_BackupDisplay/Speed/AS1000_SpeedBackup.html, 0,0,400,512

[VCockpit05]
size_mm=1024,768
pixel_size=1024,768
texture=$SCREEN_5
background_color=255,0,0
gauge00=AircraftInterior!SimpleGauge, 0,0,1024,768


AircraftInterior.xml in the same directory:

<Gauge Name="SimpleGauge" Version="1.0">
<Element>
<Position X="0" Y="0"/>
<Size X="1024" Y="768"/>
</Element>

<SimGauge.Gauge Version="1.0" Name="SimpleGauge">
<!-- Define a simple text element -->
<Element ID="SimpleText" Type="Text" X="100" Y="100" Font="Arial" FontSize="24" TextColor="white" Text="Hello, World!" />
</SimGauge.Gauge>
</Gauge>
 
Does the plane's model have a polygon mapped to a texture called $SCREEN_5? Those are built into the model itself, you cannot just add it to the panel config file.
 
The "Hello World" tutorial is incorrectly written. I think they even say in the instructions that it is intentional to teach us how to troubleshoot. I could not figure it out so I hacked the lesson example into the default DA-62.

// Panel Configuration File
// DA62

[VCockpit01]
size_mm=1024,768
pixel_size=1024,768
texture=$AS1000_PFD_2
background_color=42,42,40
htmlgauge00=NavSystems/WTG1000/MFD/WTG1000_MFD.html, 0,0,1024,768

[VCockpit02]
size_mm=1024,768
pixel_size=1024,768
texture=$AS1000_PFD_1
background_color=42,42,40
htmlgauge00=NavSystems/WTG1000/PFD/WTG1000_PFD.html, 0,0,1024,768

[VCockpit03]
size_mm=400,512
pixel_size=400,512
texture=AttitudeDisplay
background_color=42,42,40
htmlgauge00=NavSystems/AS1000_BackupDisplay/Attitude/AS1000_AttitudeBackup.html, 0,0,400,512

[VCockpit04]
size_mm=400,512
pixel_size=400,512
texture=SpeedDisplay
background_color=42,42,40
htmlgauge00=HelloWorldDisplay/helloworld.html, 0,0,400,512


[VIEWS]
VIEW_FORWARD_DIR=2.000, 0.000, 0.000

[Color]
Day=255,255,255
Night=255,255,255
Luminous=201,64,64

[VPainting01]
size_mm = 2048,512
texture = RegistrationNumber
location = exterior
painting00=Registration/Registration.html?font_color=black, 0, 0, 2048, 512

[VPainting02]
size_mm = 512,128
texture = RegistrationNumber
location = interior
painting00=Registration/Registration.html?font_color=white, 0, 0, 512, 128
 
No log and it's been so long I can't walk you through it. I posted that mainly to prove it is possible and it's also not that hard. What worked for me was to look at what I had to work with and then compare that to the developer version of DA-62 and how that package builds into the flying DA-62, then make my hello world project look just like the similar part of the DA-62 sample project. If you compare them side by side, you should be able to spot the issue, I think it is bad path assignments, but I forget, it's been too long.
 
To the best of my memory only panel.cfg was edited. Bear in mind the test instrument already exists, is registered and functions. We change only it's display.
 
Last edited:
As I'd commented, it's been a while, but currently my radios refuse to display and that part of the instrument is the same as the Hello World sample instrument. I might have to redo the entire thing anyway, if you're still trying to figure it out. If not, maybe I can show you my files and let you tell me what I did wrong.
 
Back
Top