Thanks for the E'mail Bill ref my problems 1. It is difficult to start the engines in the R4D and and impossible in the other DC3's. I have tried everything I can.2. In the other DC3's I have not been able to start them at all!I have read the forum info and that has not helped. I have loaded the service pack No.1 and that has not done the trick.System details are :-Mother board.- Asus P4P800. CPU-Intel Pentium 2.8Ghz FSB800. Hard disk. Seagate 120Gb Serial ATA. Graphics. G Force FX5950 256 Ultra. Memory. 1Gb DDR 400. Sound - on board. Hope this helps, but I still cannot start the thing!3. I am unable to get into the Virtual Cabins - cockpits are ok though.Can anybody plsese help methankJohn Aldridge

Hi John1. Engine start ... see another nearby thread on this started by tgabriel. The trick, given that you've tipped all the right switches in the right order, is to hit the VIB switch DURING the few seconds that the START switch is engaged, before it clicks back. That should do it.2. Virtual cabins ... you'll need ACTIVE CAMERA to go walkabout. With the standard FS install, all you can do is look back there or zoom in to it. With Active Camera, you can go back, turn around, sit down, and look out at the sunset. It doesn't serve drinks, though. It does, however, allow you to walk all around the outside of the aircraft too and has a number of other important features. Well worth the investment, for this and other aircraft.You can find out more at http://www.anticyclone.be/Mark "Dark Moment" Beaumonthttp://www.swiremariners.com/newlogo.jpg

Hi "Dark Moment" BeaumontThanks for the reply, unfortunatly it does not solve the problem (engines) that is. They don't start and I'm getting very frustrated by it! If anybody has any other ideas I would like to hear. They dont start on CTL. E either!The virtual cockpit, I will explore you suggestion this weekend but the main problem with it is, I dont get a VC cabin, just a blank.Thank all the sameJohn Aldridge

Sounds like ou may be trying to load the aircraft from a pre-saved flight, possibly involving a non-default aircraft? This can be the case if you have the sim loading directly into a saved flight situation, rather than allowing the saved flight menu selection first.Does the problem still occur if you load one of the supplied R4D/DC-3 flights? Allcott

Furhter to the above John, if you go to the forum of DC3 Airways you'll find the solution, which is close to what I suggested:http://www.dc3airways.com/Hope this helps Allcott

Hi You GuysI still cannot get the engines to start! 20 or 30 attempts on the right and the same on the left! If they start I quite often left with one engine going and cannot start the other one! I think the time has come for a radical rethink about the problem.Any suggestions would be welcome but a cure would be appreciated.John Aldridge (fedup)

I feel for you, John, if you'r still having problems. Nothing worse than such frustration ... been there, done that with other things in flightsim.You have to be missing a step somewhere. Or something is up with your install ... I am a bit concerned that you say you see no VC. No gauges, you mean?If you are set up on Roger Wilco or Teamspeak we could chat this through sometime if you like. Or even AOL AIM, MS Messenger, or whatever (anything but expensive phone calls, eh, LOL?)Mark "Dark Moment" BeaumontP.S. You have checked your fuel, right, and engaged fuel pumps?http://www.swiremariners.com/newlogo.jpg

>Hi You Guys>I still cannot get the engines to start! 20 or 30 attempts on>the right and the same on the left! If they start I quite>often left with one engine going and cannot start the other>one! I think the time has come for a radical rethink about the>problem.>Any suggestions would be welcome but a cure would be>appreciated.>>John Aldridge (fedup)>OK, let's remove the variables. Are you starting from one of the saved flight situations supplied with the package?Have you tried following the video of the startup procedure to the letter?Please describe how you are trying to start the engines, beginning with one of the three default MAAM flights. At least that way we can eliminate high altitude airports or dodgy aftermarket scenery from the equation and find out at what point things are going wrong. Did you try the system from the forum I linked to? The fact that the engines start sometimes suggest that you are either missing a key ingredient in the startup procedure, or possibly are trying to start the engines at an altiport, a cause of trouble in FS as the mixture setting have to be `just so` or else they don't start.Allcott

Hi Guys,All to no avail, The engines will not start, sometime thy do but it is not repeatable! If I start wit the R4D at Maam, the engines are stopped. I try to start them using Ctl E and the port engine will turn, speed up and look as thought it should start, but no smoke and no go! Using the correct method the same thing happens, and I think I will give up. I nolonger have any faith that it wll start and I'm wasting my time. I think I will fly the twotter that I downloaded from the net as it is more fun, it starts when required and it fly's well, but its no R4D.Very sad!John [email protected]

'twould be tragic to trade for a Twotter, John.You do have your mixture levers on full rich when starting, right? Check that by moving them. Sometimes, by default, they are at ICO even though visually they look to be at full rich.Mark "Dark Moment" Beaumonthttp://www.swiremariners.com/newlogo.jpg

>Hi Guys,>All to no avail, The engines will not start, sometime thy do>but it is not repeatable! If I start wit the R4D at Maam, the>engines are stopped. I try to start them using Ctl E and the>port engine will turn, speed up and look as thought it should>start, but no smoke and no go! Using the correct method the>same thing happens, and I think I will give up. I nolonger>have any faith that it wll start and I'm wasting my time. I>think I will fly the twotter that I downloaded from the net as>it is more fun, it starts when required and it fly's well, but>its no R4D.>Very sad!>John Aldridge>[email protected]>>As Mark says, this is a classic symptom of not having the mixture controls to full rich, or the master switch on. As you haven't replied to my previous post it's difficult to be more specific, but it sounds like you are loading DIRECTLY into a saved flight, then switching to the supplied MAAM scenario. This could be the cause as you have carried over settings from a previous flight into the new scenario. Not all MSFS settings are held in the saved flight file.Perhaps if you elect to start from the Choose Flight menu screen and then select the MAAM scenario you will have better luck, but it sounds like you need to work this through from your end. It isn't the package, it must be either your computer or your operating of it, but there are so many variables.Hope you get it sorted.Allcott

I was tearing my hair out having the same problem. I followed the checklists exactly, but I could only get the engines to start once in a while, sometimes only one engine, rarely both.Here's what I did. I deleted the fs9.cfg file, allowing the sim to regenerate it the next time fs9 was started. After that, no problems with R4D-6/DC-3 engine start. (You have to redo all your FS9 settings and assigments with the new fs9.cfg file, though).Hope this helps,Sandy

Hi, John and othersThere must be something to this problem with starting the engines. I was using the start-up scenario MAAM-BEA DC-3 Start up lfight for several trial flights. I was able to easily start the enignes manually without any problem Then last evening I fired up FS9 again and selected the same start up scenario - and I could not start the engines. Even Ctrl + E would not work. I switched to a different aircraft (R4D, etc) and they would not start either. Then I selected one of the other provided start up scenarios. NO PROBLEM. Started engines like a charm. Back to the first scenario. NO GO. The props would turn over as before but then would come to a stop. I looked at the FLT file for that scenario but could not see anything obvious (compared to the FLT file for one of the other startups.The previous post (by Sandy) suggested FS9.cfg may contain the problem. I will look at it. I hate to delete it and have it built from scratch. Too many tweaks & changes.Bill S.

This is a follow-up on my post above. I could not determine that fs9.cfg contains the problem. What I did to "restore" MAAM-SIM BEA DC-3 Startup flight is to move the non-starting BEA-DC3 to another location (I used CYYZ) and it started fine there. Then I simply returned the BEA DC-3 to its original location and saved that situation and then replaced the original FLT file with the new one I created. So I suspect the problem must be in the FLT file but have not spent any more time trying to find it.Bill S.