Hi all, have a really strange issue with Wilco's Tilt Rotor, in that try as I might, I cannot get the right side motor to start.
This applies to version 1.4 clean, v1.4 with the patch to 1.5 , and both with or without the upgraded freeware VTOL gauge by Rob B available in the file library here.
Just for preemptive confirmation: Yes, SimConnect is present and fully working, as is the newest (Feb 4, 2013) version of Pete's FSUIPC4. All other add-ons utilizing these modules work like a charm without issue. And this Wilco aircraft is installed on a Win7 x64 machine, with all the usual permissions issues taken care of ages ago.
So, what is happening is this: Jump into the aircraft in cold and dark conditions, follow the checklist and the left engine fires right up with no problem at all. The right one, however, only gives me the whine noise of the starter spooling up, and this increase in rpm does show on the EIS display. But that's as far as it goes. The prop never spins up. Same thing happens if I load another aircraft first, get the motors running and drop the flaps then jump back into the Tilit Rotor... Once the scene rebuilds, the engines on the tilt are off, the props are horizontal, and I can't get the right one to start.
Interestingly, I noticed that when the left motor is starting, the Master Caution panel lights up showing "Ignition On" and "Starter" are activated. But these lights never come on for the right motor. Also, there's a fuel warning light that comes on as well (can't recall its tag at the moment.)
Now, I can force the issue and get the engine running, but only by slewing vertically up a thousand feet or so. Set the throttle to about 90%, come off of slew, and the engine is forced to be in running mode. When I do this, then all appears to be runnning perfectly ... no Caution lights about fuel, even and equal EIS numbers between engine 1 and 2, full functionality across all power settings, etc. So, it works (and flies remarkably well, I might add; lots of fun!)... but is not really ideal, of course! AND, if I land and shut down the motors but don't leave the sim, then I'm back to square one, with a no-go on the right engine.
If anyone else has encountered this, please let me know what the devil is going on! I've checked, and double-checked, and triple-checked just about everything in my fsx install that I can think of, but can't fathom any solution. If you have an idea, lay it on me.
Thanks in advance.
Jason
Bookmarks