Starrfoxx

After the new U.K. update, REX Weather Force is now crashing the simulator just after it injects weather. Not sure if anyone else is having the same problem. I've seen this happen before when an update broke REX until they released a new update to Weather Force.

Has the latest MSFS patch broke WF again? I had recently reinstalled WF, and I'm getting no injection of weather - live or DCWS. Weather is set to clear.

TerraScene is another one that I'm looking for. I'm not able to find that one in the library, either.

Thanks, Colin. I sent you a message. I'm also hoping to find Terramodel 2.1, which I think works with the original "Fly!". I have the 2K special edition, and it's very good -- however not having the ability to add scenery is going to be a bit of a letdown.

Hello everyone! I've been playing "Fly! II" for the past week, downloading some scenery, and also creating some scenery with Terramodels. I'm looking for "Taxiway Editor" by Peter A Jacobson, which I see referenced in several files (mostly by Wayne Roberts). I have not been able to find that program anywhere in the library. Can anyone help me find it? Has anyone had any success in getting "Fly! II" to run in Windowed Mode? I see no option in the menus, nor the INI file. ALT + ENTER doesn't do anything, nor does adding "-w" or "-window" in the shortcut properties.

Shame. I was hoping to feature it in a world tour video series I'm working on with FS 2000.

I've tried reaching out to the author, but there hasn't been a response. I'm interested in Version 3 of Radar Contact, so that I can use it with FS 2000. I'm working on a series of retro flight-sim videos, and I wanted to have some ATC going with my flights. I would buy v4, but it isn't compatible with the older flight sims.

I have not seen this in my flights with VoxATC. I believe it says somewhere in the documentation that departure and arrival airports are the ones with generated traffic, so there wouldn't be anything in between. VoxATC is great for short flights, but for longer ones you might want to use something else such as PFE. I have both, and I like them each for different reasons.

That could be a "launcher" executable. Download it, start it, and then it downloads from that program. I've seen various other programs do that.

That is weird. Is this happening at all the airports with ATIS, or just one specific place? It could be a problem with the AFCAD file. Perhaps the ATIS wasn't programmed in, or it was programmed on the wrong frequency. It may not be the fault of Vox at all.

Are trying to use Com 2? If so, it doesn't work. All communication has to be done on Com 1; ATIS included.

I think I may have figured out a way for Tegwyn to give us traffic enroute. If traffic is generated at Departure and Arrival airports, then why not have an option where we can type in the ICAO airport codes for a list of airports along our flight plan? Then, Vox could generate traffic at those airports in the same manner as it does for departure and arrival. This would also give the user a little more control on what airports they want to see traffic at and which ones they don't.

I've only done one test, but I believe I was hearing AI traffic when I tuned into center. I may have contacted them, but I don't remember. Com 2 doesn't work for listening or broadcasting (just like Vox), unfortunately. PFE does have the "old style" canned ATC chatter. It wouldn't be based off any AI in the air, though. If you wanted to use canned chatter, then it's probably better to go to liveatc.net and have it play in the background with Vox. The only problem I found is that PFE is like the default ATC when it comes to 3 to 4 different frequencies for the same Center Controller. You will switch to different "Salt Lake City Centers" during your flight, for example. With Vox, I've noticed that I only had to worry about one Center. Once PFE and/or Vox allows us to use Com 2, then using both at the same time will actually work really well. I will admit that it sounded weird hearing the TTS voices from Vox mixed up with the "real-like" voices of PFE. At least I knew who was talking to me.

I've fooled around with this combo using PFE and VoxATC. PFE sounds better, because of all the voices. But you can run into a few snags combining the two. What I found difficult is that PFE and Vox only use Com1. And when PFE is wanting me to change to different frequencies for the same Center (like default ATC), I am unable to do so because Vox doesn't tell you to change to 4 different frequencies for the same Center. At least with default, you can use Com2.

You've got to create a flight plan, convert it through PF2000, and load it up into PFE. I look at it as if I had to really file a flight plan anyway. With PF2000, it acts like FSS while it's converting and tells you your flight plan is approved. I'm not sure how RC4 works, but I know with VoxATC you have to create a flight plan as well so that the program knows where you are flying from and to. It seemed cumbersome at first, but after a few times I got the hang of it and it's not much of a big deal now. The extra time is worth it for me.

Do you have any FS9 AI traffic, such as World of AI? If so, FSX will use it and ignore your FSX specific AI. To fix it, you'll want to convert your FS9 AI Traffic to FSX file format.

I haven't found a way to disable the ATC, but you can go into "sounds" and turn the Voice option off.

I haven't tried it, but I've had trouble with one of my custom CRJ-700 aircrafts with my virtual airline. I haven't figured the problem out in the .cfg file, so I had to remove it, so that the indexer would work properly. I've had to fix other planes by removing aliases and putting the actual folders/files in the particular aircraft folder for Vox to read it right.

I used Airport Design Editor (ADE) to look up the BGL's. Grand Canyon is KGCN. On both of the above examples, a name correction could be done so that it would read: Grand Canyon National Park instead of Grand Canyon Natl ParkDetroit Metro Wayne County instead of Detroit Metro Wayne Co That still doesn't help with the Vox controllers trumping the name to "Canyon" or "Metro", unless it's supposed to do that.

One thing that I really love about Vox (and default ATC) is being able to hear the name of the airport (even small ones). I've noticed a couple of airports where Vox does not read the entire name, though. For example:* Detroit Metro (KDTW) refers to itself as "metro"* Grand Canyon National Park Airport refers to itself as "canyon"So when calling ATC, I'll have to refer to them as "Metro Ground" or "Canyon Ground'.Is there a reason why this is happening, and can this be fixed so Vox reads it correctly?

Last night I had an enjoyable flight from Flagstaff to Grand Canyon, Arizona airport. I flew VFR and had no trouble with ATC or AI Traffic. Everything looked good. I had traffic set to 20% this time. I'll let you know if I have any other trouble. Hopefully turning down the traffic will be the trick.

I recently bought PFE 2.14 with the Voice Expansion and also the free Enhancement pack. I got it mainly for FS9 on my laptop, but I'll use it here and there on FSX on my desktop (where I use VoxATC mostly). All I have to say is .... awesome. There are TONS of voices, and it is just neat to hear something like that. I also flew from the US to Canada, and it was neat to hear controllers with French accents telling us Americans what to do and where to go. It's been a very enjoyable experience. It does take some patience to get set up, but I find it totally worth the investment.

I've got the latest PFE and Windows 7, and I didn't need to run it that way. I did have to install it as an administrator, though, and took some patience to get installed correctly. Works fine for me now.

VoxATC is also missing. I use both VoxATC and PFE, depending on the flight I'm doing.

This will happen to me also, especially if I start going through too many other windows that might have sound attached to them. It'll cut my VoxATC sound in half and will be harder to hear.