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

P3D v4 trusted modules entries

Vitus

Resource contributor
Messages
1,480
Country
newzealand
Hey guys!

FSX saves the "trusted" modules in the FSX.cfg file. I'm trying to find out how Prepar3d saves these entries, since they're not in the prepar3d.cfg file. Any ideas?
 
P3D doesn't do that. Recall that it doesn't ask you for permission to run third party modules or gauges.

Doug
 
Yep, that "trusted feature" of FSX was not very well thought out, as the only way to circumvent that was to purchase a Certificate of Trust and compile that into your module(s). It was a major PITA and eventually most of us simply quite bothering. It was just an additional expense and major bother.
 
If you think implementing trusted modules was poorly considered, you may be overlooking the clear similarity to trusted websites, for which a webmaster must purchase and renew a certificate of trust from Microsoft and the practice is so ubiquitous, most people don't realize it occurs. You see, the effect on traffic for being presented with the "potentially unsafe" page, because these people chose to not tithe to M$, is so extreme that almost no one refuses. The former owner of my ISP was one, apparently they are relatively expensive, because he finally sold out altogether. I used to actually enjoy the perverse attempt to assert M$ dominance as I would have to click through the warning about the security of my own mailbox.
 
Back
Top