Hello all,I enjoy flying Realair Simulations excellent Scout Package 2007 for FSX. Unfortunately, I am unable to get the Scout's engine started using all the steps clearly outlined in the user manual and POH that was supplied with the package. I've even contacted Rob at Realair and we can not seem to find a solution for this problem. His computer systems have no problem getting the engine started but he does concede that some customers are experiencing this problem also.As it is, I have to resort to using the "Engine Autostart" default key map within FSX (Ctrl-E), but that is not the same (or as authentic) as going through all the steps manually, as you would in a real-world Scout.Does anyone else out there have this similar issue? I'm hoping somebody out there will jot down a tried and true method for getting the Scout fired up using a "manual" procedure (that DOESN'T involve using Ctrl-E). I would just like to know what steps YOU take to make it work on your system and I will try and emulate - the process outlined in the manual simply are not working for me.Please jump in and share your thoughts and suggestions - I love this fine VFR plane, but really want to get this problem solved if possible.Thank you in advance for your help! - Rob

What plane is your default plane (so the one you see when you startup FSX)? If that is another addon plane (because you saved a flight with an addon plane as your default flight), that might be the cause of your problems: I had this happen to me one or two times (for instance the Quest Kodiak wouldn't start manually when I had a Carenado plane as default). See what happens when you make the FSX Ultralight default again (or rename your current fsx.cfg to make sure the default flight really is the default flight).EDIT:If the Scout is your default plane, you still might have problems if your previous default plane wasn't the Ultralight.

The cold and dark procedure is just a few steps. Since you've been in touch with Rob, I assume you're turning the fuel valve on by your left kneecap. If it's how you load the plane as JvE mentions, I load with the default Cessna, allow the flight to load, then click the aircraft tab and load the Scout. Never had an issue with the engines not firing. Good luck.

there is also a small patch for cold and dark start up, might resolve your problem

Hello all,I enjoy flying Realair Simulations excellent Scout Package 2007 for FSX. Unfortunately, I am unable to get the Scout's engine started using all the steps clearly outlined in the user manual and POH that was supplied with the package. I've even contacted Rob at Realair and we can not seem to find a solution for this problem. His computer systems have no problem getting the engine started but he does concede that some customers are experiencing this problem also.As it is, I have to resort to using the "Engine Autostart" default key map within FSX (Ctrl-E), but that is not the same (or as authentic) as going through all the steps manually, as you would in a real-world Scout.Does anyone else out there have this similar issue? I'm hoping somebody out there will jot down a tried and true method for getting the Scout fired up using a "manual" procedure (that DOESN'T involve using Ctrl-E). I would just like to know what steps YOU take to make it work on your system and I will try and emulate - the process outlined in the manual simply are not working for me.Please jump in and share your thoughts and suggestions - I love this fine VFR plane, but really want to get this problem solved if possible.Thank you in advance for your help! - Rob

Interesting. I also have no problem with the Scout, but ever since I updated the Duke I cannot start it manually any more, but could prior. I really dislike having to use the auto-start function with that bird. I've been meaning to contact Rob about this.

^^ realair duke startuphave you made sure that you turn on the fuel between the seats? i don't think it was mentioned in the manual and took me forever to figure out.

^^ realair duke startuphave you made sure that you turn on the fuel between the seats? i don't think it was mentioned in the manual and took me forever to figure out.

Hey, thanks for the tip, I'll check that out. I do not remember having to do that prior to the latest patch, but know you do have to open the fuel in the Scout.This could be a 'doh!' moment :(

there is also a small patch for cold and dark start up, might resolve your problem

Hello "level_7",Would you be able to provide a link to the patch for the C&D startup? I would like to give it a try.Thank you,Rob

Hello "level_7",Would you be able to provide a link to the patch for the C&D startup? I would like to give it a try.Thank you,Rob

Here on their homepage:http://dl.filekicker.com/send/file/228594-...dDark_Patch.exeOther goodies there too:http://realairsimulations.com/list_box.php?page=products

Here on their homepage:http://dl.filekicker.com/send/file/228594-...dDark_Patch.exeOther goodies there too:http://realairsimulations.com/list_box.php?page=products

Thank you very much, for the links... as it turns out I double-checked my installation and see that I did apply the "Cold and Dark" patch for the Scout. It's been so long since I installed it I honestly forgot all about the patch, but it was indeed there in my archives.I appreciate your help and the other members for sharing their thoughts and suggestions! :( Cheers,Rob

What plane is your default plane (so the one you see when you startup FSX)? If that is another addon plane (because you saved a flight with an addon plane as your default flight), that might be the cause of your problems: I had this happen to me one or two times (for instance the Quest Kodiak wouldn't start manually when I had a Carenado plane as default). See what happens when you make the FSX Ultralight default again (or rename your current fsx.cfg to make sure the default flight really is the default flight).EDIT:If the Scout is your default plane, you still might have problems if your previous default plane wasn't the Ultralight.

Hi J van E,IT WORKED!!!! Yes! I very much appreciate your suggestion to make the FSX (AirCreation) Trike Ultralight the default plane/flight again. Doing so, basically "reset" FSX (more likely one or more entries in the fsx.cfg file) and when I later selected RealAir's Scout plane and began a free flight, I was able to fire up the Scout's engine PERFECTLY using the manual method - I never had to press Ctrl-E. Also, after doing this "reset" with the trick you mentioned, I was able to save new default flights with the Scout selected and have had no problems manually starting the engines since. Your trick worked like a charm! Thank you so very much for your help! :( Cheers,Rob

Hi J van E,IT WORKED!!!! Yes! I very much appreciate your suggestion to make the FSX (AirCreation) Trike Ultralight the default plane/flight again. Doing so, basically "reset" FSX (more likely one or more entries in the fsx.cfg file) and when I later selected RealAir's Scout plane and began a free flight, I was able to fire up the Scout's engine PERFECTLY using the manual method - I never had to press Ctrl-E. Also, after doing this "reset" with the trick you mentioned, I was able to save new default flights with the Scout selected and have had no problems manually starting the engines since. Your trick worked like a charm! Thank you so very much for your help! :( Cheers,Rob

You are very welcome! :( And yes, once you have things working with a specific plane, you can indeed make a flight with that plane as default (I have the Carenado Bonanza as my default right now, cold and dark). Just remember that selecting another plane might result in some problems again! But I don't think you will forget that now. ;) BTW The problems you can encounter don't only have to do with starting up: I remember that switching between two Carenado planes, where one of them was my default, made the other specific plane bank a bit to the left all the time, as if my joystick wasn't calibrated well: simply switching to the ultralight (in flight) and back again helped getting rid of this! But (btw 2) simply switching to the Ultralight ('in flight') doesn't always help, because that Quest Kodiak I talked about wouldn't even start after switching planes while on the tarmac: I really had to make the Ultralight the default plane before I could get it working again. So if someone likes to fly in various planes a lot, the best thing to do is keep the Ultralight as default.