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

VoiceEditPak help

Messages
4
Country
us-wisconsin
I am new to sdk and i have a problem that i have run into lately with installed aircraft. I have changed the atc_id tag in my addon aircraft to reflect the ICAO identifier. Several of the aircraft atc will correctly speak, but, Flagship, the identifier for Pinnacle airlines(Norhtwest AirlinK) does not work.. I found VoiceEdit Pak in another forum but no version for FSX. I am running Windows Vista with Flight Simulator X and would like to add this callsign.

any help or ideas?????????????
 
Hi there,

If you go to Lars website it clearly says...

"A Flight Simulator X compatible version is currently being developed, and a community technology preview is available for download. Please visit the development wiki page for details. "

If You click on the Wiki page link, you can download the beta which works well.

I'm also running FSX on Vist x64 and have had no problems with this beta.

Cheers
 
xr 219, thanks for the reply. I had tried the first release and could not get it to work. I will download the second release and give that a try. Since you are using this is the 3.1 version tutorial still applicable???


i just tried the second release and it crashed and i still do not have the availability to create new items. XR I am starting to have second thoughts about this::::::: I did go back to Lars wiki page and see that this is a CTP release. Were did you find a functioning beta????
 
Last edited:
There is no functioning beta, there is a functioning CTP (at least I do not recall hearing of any crashes once people had actually installed .NET 3.0). It is unfortunately not possible to develop a user interface for the Windows system as it is right now, so it has to wait.

It might come as a surprise to some people - more precisely, the people who do not understand WPF is a 20 years advance in how we build user interfaces for Windows.

Once the WPF development environment is finally released I'll return to EditVoicepack development as my schedule allow - meaning I will NOT interrupt another project I am working on at the time just to make a new version of EditVoicepack.
 
Hi Lars,

Beta was the wrong word to use, sorry. I was just pointing out that the basic fuctionality of EVP seems to work well, on my system anyway. I'm just happy to take what comes, when it comes. :)

ATB.

Ben.
 
Lars, thank you for explaining this. Since I am new to this I am sure I did something wrong to get the CTP to crash. I will keep on checking your WIKI page and hopefully i can get the voices I need. In the CTP I did find a nicely sounding rendition of Flagship. Keep up the good work

mark
 
Very long time since this topic was started, but is there any update on the schedule?

Version 4.0 for FSX looks fantastic - but not being able to update FSX correctly is a pita. :(

I'd like to give users the ability to add my current aircraft project to their callsigns. There even is an entry in the "community" section, but FSX doesn't want to call it.
 
Sorry, no progress. I simply have too many other projects running, and unfortunately I keep getting dragged into more and more. :(
 
Sorry to hear that but absolutely understandable. I just wonder if there's no option at all to change callsigns in fsx? FS9-version of editvoicepack can't be run under Vista.
 
Keep an XP machine around. That is what I do.

I run EVP v3.1 and with that version, you can import and export voicepack mods all day long...and it works with FSX.

After I'm done modding, I transfer the new voice pack over to the Vista machine and go.
 
Mace

Are there a different number of airports in FSX than in FS9? Maybe I don't know fully how to use 3.1, but doesn't it modify the entire voice pack. Not like FSX traffic files where you can add individual files. Wouldn't some airports be left out if you use the FS9 voicepack? Or would there be some kind of generic ATC at those airports? BTW, I run both 3.1 and 4 on my Vista machine.

Bob
 
But what to do with the vcpmod-File? With EditVoicepack4 you cannot import those files.

And then, how do I get them to customers?

Funny thing is that somebody already did a Bushhawk callsign, but I cannot get ATC to call me Bushhawk.
See attached screenshot.

In FSX I call ATC with "this is N8372 type , 5 miles north of..."
So, there's only a gap where "Bushhawk" should be.

aircraft.cfg looks like this:

[General]
atc_type=Bush Hawk
atc_model=Bush Hawk
editable=0
...
 

Attachments

  • VoicePack1.jpg
    VoicePack1.jpg
    87 KB · Views: 589
Oh, come on, FSX is case sensitive?! :eek: :banghead:

Actually it was allright, just BUSH HAWK instead of Bush Hawk. Well...

Thanks anyway!
 
Sorry to hear that but absolutely understandable. I just wonder if there's no option at all to change callsigns in fsx? FS9-version of editvoicepack can't be run under Vista.

EditVoicepack 3.1 runs fine under Vista (32 or 64 bit). If you have UAC enabled you do need to start it by right clicking and selecting Run as administrator as it needs to access FS files in the Program Files folder.
 
Problem is it demands an older version of net...-work, erm, frameNet, erm, you know what I mean.
I have a higher version installed, seems the VoicepackInstaller doesn't want that.
 
Problem is it demands an older version of net...-work, erm, frameNet, erm, you know what I mean.
I have a higher version installed, seems the VoicepackInstaller doesn't want that.

Then install the one it wants. :)

From the EditVoicepack readme http://www.editvoicepack.com/readme.html#ToC1
Please notice that newer versions of the .NET Framework might not be able to run EditVoicepack (it will then allow you to install both version 1.1 and the newer version).

First google hit when searching for ".net framework 1.1":
http://www.microsoft.com/Downloads/...E3-F589-4842-8157-034D1E7CF3A3&displaylang=en
Supported Operating Systems: Windows 2000; Windows Server 2003 Service Pack 1 for Itanium-based Systems; Windows Server 2003 x64 editions; Windows Server 2008 Datacenter; Windows Server 2008 Enterprise; Windows Server 2008 for Itanium-based Systems; Windows Server 2008 Standard; Windows Vista Business; Windows Vista Enterprise; Windows Vista Home Basic; Windows Vista Home Premium; Windows Vista Starter; Windows Vista Ultimate; Windows XP; Windows XP Professional x64 Edition
 
Thanks for the help, Lars. Actually I'm not sure which applications want newer versions of net framework, so I'm a bit anxious to install the older one.

But as I do not want to use it anyway, I just skip it.

Users will have to use editvoicepack anyway, and the Bushhawk does work with the community update, I just had to fix the typo.
 
Thanks for the help, Lars. Actually I'm not sure which applications want newer versions of net framework, so I'm a bit anxious to install the older one.

But as I do not want to use it anyway, I just skip it.

Users will have to use editvoicepack anyway, and the Bushhawk does work with the community update, I just had to fix the typo.

The various versions of NET Framework co-exist. I have
at least three installed. No need to worry about uninstalling
any of them to make way for a newer version.

Paul
 
Back
Top