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

Place dsd_xml_config.ini into panel folder ?

T

teson1

Messages
130
Country
france
Hello all (and Doug in particular ;) ),

-> Is it possible to specify relative paths (referring to the folder containing dsd_xml_config.gau) for the .ini file of dsd_xml_config ?

I want to place dsd_xml_config.gau and dsd_xml_config.ini into an aircraft's "panel" folder.

However, I want to avoid having to specify the path to the .ini file relative to the main FS folder, to make the gauges portable between aircraft.
Also, I prefer not to have the .ini in the gauges folder or another defined folder outside the panel folder either, as this would render maintaining the .ini files for different aircraft more complicated...

So I want the dsd_xml_config .ini file to be searched in the same folder as dsd_xml_config.gau.

This is possible with the sound gauge:
Code: 
gauge37=dsd_fsx_xml_sound!Sound,  2,2,2,2, [COLOR="Red"][B]\[/B][/COLOR]dsd_fsx_test_sound.ini
I've tried \dsd_xml_config.ini as path, but it didn't work for dsd_xml_config.

I know I'm hard to please :o
No problem if it's not possible, I'll place everything in the gauges folder.
But I've just come to expect such high level of excellence from Doug's gauges, that I thought I'd ask... :cool:

Many thanks in advance !

Gunter
 
I'm doing it this way

Code: 
gauge96=DSD\DSD_FSX_XML_Sound!Sound,      0,  0, 2, 2,    .\Aircraft\fsfsconv\panel.B727.RP_ENH\XMLDSD_Sounds\B727_XMLDSD_Sounds.ini
gauge97=DSD\DSD_XML_Save_Vars!config,     0,  0, 0, 0,    .\Aircraft\fsfsconv\panel.B727.RP_ENH\DSD\B727_XML_Save_Vars.ini


The DSD-gauges in a subdirectory of the panel directory.

Edi
 
Last edited:
Gunter,

The config gauge pre-dates the sound gauge by quite a bit. I hadn't got quite as creative with the configuration routine at that point. The answer is no.
That block of code in the sound gauge is fairly complex, as I allowed for just about anything being provided by way of a path.
I could certainly look at updating the config gauge, but it's not going to happen this week (probably not next week either... ;))

Doug
 
Doug, thanks for the reply !
Yes, I thought that it would be too much to expect to have every feature everywhere... :D

> I could certainly look at updating the config gauge, but it's not going to happen this week (probably not next week either... )

Even if it takes a year it would be awesome service !

Frankly, I believe for my current project I can come by with the existing gauge, placing the .ini files into the gauges folder, even if it may be elegant to have the same features as the sound gauge.

Knowing how much time implementing even trivial changes can take (at least for me :o), I don't want to push you to commit to such a project.

On the other hand, if you think you'd have fun implementing this feature, I'd welcome it with open arms. :D
And I believe it would be a nice incremental improvement to the config gauge.

But no pressure.

Thanks anyway, the config gauge is extremely useful as is !

Gunter

ddawson said:
Gunter,

The config gauge pre-dates the sound gauge by quite a bit. I hadn't got quite as creative with the configuration routine at that point. The answer is no.
That block of code in the sound gauge is fairly complex, as I allowed for just about anything being provided by way of a path.
I could certainly look at updating the config gauge, but it's not going to happen this week (probably not next week either... ;))

Doug
Click to expand...

Edi,
thanks for the advice, but I exactly want to avoid specifying a path relative to the main FS folder, as this would require to edit the path to the .ini file for every plane the gauge I'm working on is installed in.
But if no other solution is possible it's a working option of course. Just a little bit less convenient to configure. Thanks.
 
Last edited:
Why is having the ini files in the main Gauges folder more complicated? If you include the aircraft type in each ini file name, it makes it pretty simple. I even like them all in one place, since it makes mass edits much easier. :)
 
tgibson said:
Why is having the ini files in the main Gauges folder more complicated? If you include the aircraft type in each ini file name, it makes it pretty simple. I even like them all in one place, since it makes mass edits much easier. :)
Click to expand...
Only makes a (small !) difference if the gauges are supposed to be installed into several planes.

A. One small project I'm working on currently is to allow to keep popup panels in the VC open (only) when cycling the views.
I want to be able to add this so several of my planes, and which panel ID's are to be tracked is defined in an .ini file accessed by the config gauge.
Being able to place the gauge with the .ini file into the panel folder would allow to limit installation to 3 steps:
1. Place the gauges folder into the panel folder.
2. Open the generic .ini file and set which panel ID's to track.
3. Add generic entry to the VC section of the panel.cfg - No need of changing the link to the .ini file.

If the gauges and .ini file are in the gauges folder there are more steps:
1. Place the gauges into the gauges folder (only done once).
2. Open the generic .ini file and set which panel ID's to track.
3. Save .ini file under a unique name referencing the specific aircraft.
4. Add generic entry to the VC section of the panel.cfg - containing link to a generic .ini file.
5. Edit the link to .ini file in the panel.cfg to reference the aspecific file for the aircraft.

Just a tiny little bit more complex, requiring more steps, and switching between folders.

B. I prefer to place new gauges (in this case including the .ini files) into the aircraft's panel folder instead of into the gauges folder until I know that I like them and want to keep and use on several aircraft.

If the reference to .ini file is to the gauges folder, then that's not possible without editing the generic path to the .ini file in the panel.cfg, which kind of defeats the purpose...

But I completely agree that the config gauge works marvellously as is, and that the added functionality would be a really small incremental improvement. I don't want to push Doug at all to work on this.

However, I do have the impression that Doug derives pleasure out of polishing his work (well, I do :) ), so that's the only reason to mention it at all.

:)
 
Last edited:
teson
just for an update, have you manged to get the VC popups now open. Sorry I havent followed the progress on your issue to only keep certain popups open only in vc view or to manage them.
Regards
 
You must log in or register to reply here.
Back
Top