Allow me to guess how the various AI contributers will react. There are a few options:* "That is a VERY good idea" - and then nothing happens* "We already have something similar and as the three of us in this group are going to cover all AI in the world with daily updates of all changes we do not need anything else".* "That is a VERY good idea - we do not like the way you have done it though, so we will improve the format for our models, then every one else can just follow our standards".The problem is that you need the momentum - meaning you need a working system WITH ENOUGH CONTENT so the AI creators can see that it makes sense going withyour solution as it is. If not I am afraid nothing will happen.Hence my idea to drive it from EditVoicepack. Evp is already having tousands of users - and more importantly it is used by virtually all AI packages/groups/whatever to support their need for callsigns. This means you have the install base needed to make it a viable distribution channel from the start - at least if you play it a bit smart, meaning first do AFCAD's. They are fairly simple, and no really good attempt to make a decent system for them exist. If you can get that going you would have callsigns and AFCADs comming though a single distibution channel, and adding the rest becomes doable as you now have the critical mass to get the channel going.When I was jong and stupid I would just have started doing it, but the fact is that I am already running way too many projects - and they are all suffering from it. So it would require a good C# programmer that can help me out (someone just learning C# lately won't do).

>The problem is that you need the momentum - meaning you need a>working system WITH ENOUGH CONTENT so the AI creators can see>that it makes sense going withyour solution as it is. If not I>am afraid nothing will happen.>>Hence my idea to drive it from EditVoicepack. E>>AFCAD's. They are fairly simple, and no really good attempt to>make a decent system for them exist. If you can get that going>you would have callsigns and AFCADs comming though a single>distibution channel, and adding the rest becomes doable as you>now have the critical mass to get the channel going.>I agree completely, that something like this needs some momentum to get started. I'm also pretty sure that nothing will happen any time soon, but it's still an interesting discussion. As you said, we'd need a good programmer (something I am definately not), and if we were to use EVP, then would need a lot of help from you in one way or the other.I also agree that AFCADs might be a good place to start. I'm the manager of the AFCAD dept. at PAI and I've already been thinking of ways to change the current distribution system for FSX AFCADs. The current system of having "official" and "Unoffical" files and a complicated testing process, has lots of problems. I'd prefer to open the whole design process up to the community at large and just come up with a way to better organize and distribute the work done by the community and help come up with some basic design standards. Not sure if that means a web-based distribution system of some sort, a stand alone application, or adding on to EVP. Probably depend on what kind of skills I can get to help more than anything. Without a programmer of some sort willing to commit to the project, we're probably not going to get anywhere.Matt

If you can use the PAI name you probably do not necessarely need Evp to get it moving. It just needs to be associated with one or another thing that will give the initial user base.

>If you can use the PAI name you probably do not necessarely>need Evp to get it moving. It just needs to be associated with>one or another thing that will give the initial user base.Or EVP and PAI joint venture, even better.I think what we really lack is a good programmer with time to dedicate to the project.Matt