BrianG wrote on Mar 28^th, 2011 at 2:41pm:

Hi Brian.

Sorry that I missed your question there. I only know that the one I have in my C:\Windows\SysWOW64 seems to have been installed at the time that I upgrade my computer and did a clean reinstall of everything. I have never downloaded and installed msvcr71.dll, on any of my computer systems, since I started buying Captain Sim add-on aircraft. So it was either installed when I installed Windows 7 Professional 64bit, or I installed something else that installed it. Sorry I can't offer you more than that. If you want to email me, I'll send you a copy of the version I have.

Mark

When I bought the CS B727 I expected visuals and sound.  If I bought a nice looking car only to find out that the stereo did not work, I would expect it fixed in a reasonable amount of time.
And one other thing.......I do not understand this re-load BS.

The way I see it, this plane is SO good, I am willing to spend the extra 10 seconds to load a second time for the sounds to work right.  I would be willing to do it 10 times if that's what it took.  That's how much I love this plane.

I also had to buy FSX Acceleration to get the AP pitch control to work as it is supposed to.  I'd rather not have had to do that, but I still don't regret it.

Now we are talking:)

Good Day,
I'm one of those who lost their interior sounds in V2.4. In fact, it was that version that was available when I purchased the aircraft, so I've not had them from the start. I have tried to do the reload twice method of getting them back, with mixed success (more often than not it doesn't work), and a few other suggestions offered here. I've not yet found a reliable method. I also lose my Avionics after about 15 minutes or so of flying, as also has been noted here.

My question is, is there a patch on the way to fix these issues? I'm not flying the aircraft at the moment because it frankly, takes too much effort to get the machine up and running as it should be. I would LIKE to fly it, and would hope that since a patch disabled important features, a new patch should be issued to re-enable them again.

Thanks much - I look forward to your reply on this. I will admit, I've put my order for the 707 and 737-200 on hold pending a timely fix for the 727. Thanks again.

Thanks for your reply Tanya. I did check the link you posted prior to posting my message. It really just says that V2.4 was released in February, which I already knew. While it does state that updates are ongoing, I guess because V2.4 broke a key component of the aircraft, word would have come down by now regarding a fix for that part that was broken. These are complicated aircraft for sure and things can happen that are unexpected when a patch is issued, but I was hoping that anything broken by a patch would have priority and be fixed soonest, or we'd be given some assurance that a fix was being worked on. I've not seen that as of yet.

I'll continue to wait and monitor the situation for a "patch to fix the patch" before proceeding with further purchases.

Thanks again for your reply.

My workaround was to add electric_always_available=1 in the [electrical] section of the aircraft.cfg. Like this:

[electrical]
electric_always_available=1
max_battery_voltage = 24.0
generator_alternator_voltage = 30.0
max_generator_alternator_amps = 400.0

I don't use it now. I guess I must be doing everything "right" when starting the 727 because I no longer lose the avionics after 15 minutes or so.

Mark

CoolP wrote on Jul 30^th, 2011 at 7:34pm:
That's a handy feature of the registered version of FSUIPC, but the only aircraft that I find it necessary to use it on is the Flight1 Cessna Mustang. I hate to think of how many times the battery went flat while I was trying to set up my flight plan. I just have to remember to turn it on for that aircraft (which of often don't).

It also came in handy when I was having the 727 "losing avionics" problem.

Mark