D
Deleted member 1281
Guest
Hello Doug and all!
I have just completed a "generic GCA" gauge based on 130 callouts for talking a plane down on final approach. You know, the kind of thing they had before ILS came along.
Here is my problem. How do I know a potential user hasn't already got Doug's sound gauge installed and running in the plane that is supposed to add the GCA module? I am assuming, and Doug has indicated as much, that having two sound gauges and hence two .ini files is likely to lead to a conflict. I can test this for my C-47, which has 380 assorted crew calls and sounds by default, and now is supposed to handle some 130 additional GCA calls. And as you can imagine, even though the sim doesn't crash outright, sounds are missing or erratic.
Now I could try to merge the ini files and run only one DSD sound gauge - but that is an error-prone and clumsy process, one which I can hardly expect the user to handle.
So I was wondering if another option presents itself, i.e., use two ini files, one defining Lvars 00 to 380, and the other Lvars 400-530. If this could be made to work without creating a conflict then distributing the GCA module would be much easier.
Thank you for any thoughts on that.
I have just completed a "generic GCA" gauge based on 130 callouts for talking a plane down on final approach. You know, the kind of thing they had before ILS came along.
Here is my problem. How do I know a potential user hasn't already got Doug's sound gauge installed and running in the plane that is supposed to add the GCA module? I am assuming, and Doug has indicated as much, that having two sound gauges and hence two .ini files is likely to lead to a conflict. I can test this for my C-47, which has 380 assorted crew calls and sounds by default, and now is supposed to handle some 130 additional GCA calls. And as you can imagine, even though the sim doesn't crash outright, sounds are missing or erratic.
Now I could try to merge the ini files and run only one DSD sound gauge - but that is an error-prone and clumsy process, one which I can hardly expect the user to handle.
So I was wondering if another option presents itself, i.e., use two ini files, one defining Lvars 00 to 380, and the other Lvars 400-530. If this could be made to work without creating a conflict then distributing the GCA module would be much easier.
Thank you for any thoughts on that.