• 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.

Nav Com Screens

R

rarewings

Messages
23
Country
unitedstates
I have almost all the radio stack working on the AG4.
I am using most of the items from the DC3 as the AG4 didn't really have anything.
I have al the knobs and switches doing their thing.

But I can not get the
NavCom1_screens, NavCom2_screens and ADF_screen to show in MSFS
I am not sure what the Material type for MSFS should be. I have tried decal and Standard
I have Left the material for them as the same as the DC3
$ADF_Sreen
$NavCom2_Screens
$NavCom2_Screens

Any help?
navcam.png
 
I just recently got my radio displays working after almost a year of trying, so I think I know the feeling. There are a lot of factors that can prevent rendering aside from material type, I know this because I use 3ds Max and I am able to directly import fully functioning instruments from the SDK sample projects, which is how I finally figured it out, I used the exact material from the Cabri G2 MFD 650 and it still didn't work, but at least I knew it wasn't for improper material. It turns out, for example, you can have a fully working HTML display, but you have the display dimensions wrong so all the numbers are beyond the edge of the display.

So that's one thing to check, you want to set up your pixel dimensions such that there is as little empty space as possible, even it if means that portions of the display will fall outside the boundaries. The idea being that when the numbers finally become visible, you want to minimize the chances that happens outside your allocated screen territory. Another thing is that the display space should never render white. Active or idle, a properly configured HTML display will always be black or very dark. I briefly went through a white display phase while ChatGPT was coaching me to have excessive emissive. Yours do not look emissive, just plain white. Mine are always dark even in 3ds Max.

Finally, the Behaviors Debug is very useful for solving component issues, it will reveal states and conditions that are not visible or available without using the tool. It was probably more helpful than CGPT for getting my radios working.

You could share some more details, your panel.cfg, your xml components, even a material sample, it would probably be helpful.
 
Thanks for the help.

I always forget to check the panel.cfg.
I had a couple of mis-types in the .cfg

It is all working now, just need to work on getting the size a little better
 
You must log in or register to reply here.
Back
Top