tshuff

I have a dual SSD setup with FSX on my second drive, but it looks like it is located on my C drive. This is accomplished using Symlinks (or Junctions in the windows world). I believe this only works in Vista and above. * Move all of your FSX files to the "new" location (in my case F:\apps\Microsoft Flight Simulator X) * If there is still an FSX folder on your source location, make sure it's empty then delete it * Open up a command prompt as administrator * Create the symlink with the junction syntax (mklink /J "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X" "F:\apps\Microsoft Flight Simulator X") * If done correctly, you should have an FSX folder at your source location that, when opened, has the contents of the FSX folder in the target location. For all intents and purposes the OS, game, addons, and everything else will think the program is still installed on the source location. http://www.howtogeek.com/howto/windows-vista/using-symlinks-in-windows-vista/ Edit- I should note that if you don't plan on keeping the source drive, this won't work, as it relies on the system thinking things are sitting where they used to sit.

First time poster, long time lurker. I've been experiencing the same problem. It's been a fairly random period of time before it happens for me. Sometimes sound will cut when I'm taxiing, other taking off, climbing, cruising, and everything in between. I've used the ARCDU with doors open, closed, and left it off completely (just going with the bare minimum); the only thing I have been able to determine is that it's definitely the addon. What I've noticed is that if I change my camera to an AI aircraft I can hear their sounds just fine... ATC works just fine... everything internal to FSX works great, but everything to do with the Q400 is completely muted. I reached out to support and have had some back and forth with them. The only tangible information that they've been able to provide is that this is an issue that they have seen before. It could be related to soundcard drivers (updated those), speaker configuration (tried the 7.1 as they suggested), and possible DirectX (that's up to date). It also sounds like they believe the problem may be specific to Windows 8. I'm pretty much expecting to have to pack it in and go for a refund at this point as I've spent the better portion of the last 6 hours working on figuring this bug out. Will be interested in seeing who else has experienced the same problem. Edit- Just got what is probably the nail in the coffin for this one. The support person I'm working with doesn't believe there is anything I can do to actually make this work. Guess it's refund time :(. Bummer.