T-37 Engine Start

falcon409

falcon409

Moderator
Staff member
Has anyone ever successfully started the engines on the payware T-37Sim? That has to be the most frustrating exercise ever. The engine start switches don't work (they remain in the off position and aren't clickable (in 2D)), the ground start switches also don't really work. The instructions say to click and hold the switch to ground until the engine has spooled to 10%, then increase the throttle. . . however the ground switch isn't animated to stay on. . .if you click it, it pops up and right back down again, it won't stay on.

Also, I have yet to get the one engine that seems to want to start to actually run. . . it won't spool up until it's gone beyond 35 to 40% and even then it just clicks and smokes and never really kicks over. If I try to start the right engine, the left engine quits. . . .grrrrrrrrrrr.

Any help from someone who either still flies this airplane, or at least has gone through numerous successful starts, will be appreciated. . . .I don't need suggestions I need instructions only from someone who flies the T-37Sim. . .thanks.:salute:
 
Thunderbolt said:
Which config do you use to start the FS9. The original FS9 oder LaunchT37 ?
Click to expand...
Going strictly by the book, using the T-37 Launch Icon on the desktop.:salute:
My only thought here is that because they came out with an updated version to work with Vista before they closed up shop, that it is now not compatible with Win7.
 
What a bummer. I just tried buying this beauty and its been discontiniued :( Another awesome fs9 airplane bites the dust!!!
 
T-37 Engine Start.

Falcon,

I feel your pain. Have the same problem with the Dragonfly (VNAF AT-37C call sign) on my old XP setup and same on my Win 7/64.

Thanks for bringing this to light. Hoping someone comes up with an answer.

sbp
USAF, Ret.........:salute:
 
sctybdy said:
What a bummer. I just tried buying this beauty and its been discontiniued :( Another awesome fs9 airplane bites the dust!!!
Click to expand...
Yea, I know it used to be available as an item from Flight1, but it no longer shows up in the list of FS9 aircraft. If you bought it while it was still available, you can download the wrapper, but not as a new purchase. . .too bad.
 
Hi,

Time ago I saved this (don't remember from where ..)

I fly this aircraft, like all well-modeled trainers, by the 'book.' I've never had an engine conk out, unless I didn't turn on my INDEFINITE BATTERY (=0) in the FSUIPC module configuration) or, for truer realism, I turn on Failures in the sim or use a Failure generating utility.

First load the default cessna172. Turn on battery, generator, fuel pump from there. Then load the T37. Now just press on the left engine starter switch. If you hear "starting engine one", it's OK. When I load the aircraft from other aircrafts like realair sf260, it says "engine started" instead, and I can't start the engine whatever.

Now wait until 10% N1, then advance your throttle to max then bring it back to idle. Once engine 1 started, stablize it at 60% N1 and start engine 2.

A other trick:

To make this addon work first,go to your FS9 root folder and look for the aircraft folder then look up the folder T-37v20 then open the panel folder and delete everything out of it you wont have a 2d cockpit no more but the virtual cockpit is framerate friendly and i like it better anyways but this will stop the nagging startup procedure that fails and you will have a flyable aircraft.
Click to expand...
 
I don't use the launch icon, I launch the sim normally and select the T-37. I start it by the book all the time, but sometimes it's a little quirky and you have to scroll through the 2D cockpit and back to the VC to reset it. Yes, the ground start switch won't stay up after you click on it, but that doesn't seem to inhibit the start sequence...at least for me. I'm running it on my Vista machine, haven't yet tried it on my Windows 7 machine.
 
falcon409 said:
Has anyone ever successfully started the engines on the payware T-37Sim? That has to be the most frustrating exercise ever. The engine start switches don't work (they remain in the off position and aren't clickable (in 2D)), the ground start switches also don't really work. The instructions say to click and hold the switch to ground until the engine has spooled to 10%, then increase the throttle. . . however the ground switch isn't animated to stay on. . .if you click it, it pops up and right back down again, it won't stay on.

Also, I have yet to get the one engine that seems to want to start to actually run. . . it won't spool up until it's gone beyond 35 to 40% and even then it just clicks and smokes and never really kicks over. If I try to start the right engine, the left engine quits. . . .grrrrrrrrrrr.

Any help from someone who either still flies this airplane, or at least has gone through numerous successful starts, will be appreciated. . . .I don't need suggestions I need instructions only from someone who flies the T-37Sim. . .thanks.:salute:
Click to expand...
Okay, here goes...

I've had the Tweety for some time. I just did a quick cold start to make sure I remember the process. I should mention that I have version 1.2 and use the co-pilot voice narrates the engine start process.

I started in the 2D and open up the engine panel with Shift-4. Turn on the battery and generators. Activate the GND switch for the left engine. The copilot will tell you if its started and when you have ignition. The engine sounds are really faint so you don't hear them until you have power. As the engine starts you'll see the start switch activate and return to neutral, then eventually hear the engine.

For the right engine you repeat the process. But make sure you have at least 60% power on the left engine. Again your copilot will narrate all the steps.

No, I didn't have to hold down any switches. Just one click got things going. And I didn't activate the boost pump, but then again I was in a hurry cause dinner was on the table. :jump:

--WH
 
WarHorse47 said:
Okay, here goes...

I've had the Tweety for some time. I just did a quick cold start to make sure I remember the process. I should mention that I have version 1.2 and use the co-pilot voice narrates the engine start process.

I started in the 2D and open up the engine panel with Shift-4. Turn on the battery and generators. Activate the GND switch for the left engine. The copilot will tell you if its started and when you have ignition. The engine sounds are really faint so you don't hear them until you have power. As the engine starts you'll see the start switch activate and return to neutral, then eventually hear the engine.

For the right engine you repeat the process. But make sure you have at least 60% power on the left engine. Again your copilot will narrate all the steps.

No, I didn't have to hold down any switches. Just one click got things going. And I didn't activate the boost pump, but then again I was in a hurry cause dinner was on the table. :jump:

--WH
Click to expand...
Thanks, none of that works for me and it matters not whether I load it using the T-37 Icon or normally, through FS9 startup.

With all switches active (battery, generator, inverter, fuel pump) when I click on the Ground start switch the RPM needle jumps, the co-pilot states that the engine has started and the needle settles right back to "0". . .the ignition switch never moves. I have the auto engine start shortcut mapped to one of the buttons on the joystick. If I use that, and hold the button down until the RPM's are above 40% and then advance the throttle, the engine will spool but never ignite. If I hit the autostart to try to light the right engine, the left engine shuts down.

I am quickly reaching the threshold of "This isn't worth the trouble". Unless someone actually has it running in Win7_64bit (so far it looks like most are using Vista), then I have to assume that Win7 is the culprit. None of the switches react as anyone here has related. The ground start switch has no effect, the left engine never get's above about 5% before dropping to "0" and even bypassing all switches and using autostart has no effect.:salute:

Oh, also. . . .starting in the Cessna, all switches turned on and the engine started and then switching to the Tweet, "nada". . .once loaded, the tweets engines slowly shut down.
 
Falcon, I got a couple of questions for ya'

1. Is this a new install of the T-37?
2. Are you trying to start from a custom default flight??

--WH
 
Okay, lets try this.. here's your ride and what it looks like from the cold cockpit with the panel switch activated.

View attachment 31563 View attachment 31564

This next shot is after all switches are activated and the left engine is running. Notice that the engine gauge shows 60 percent, and I'm now starting the right engine (start switch animates to the up position during start). And that is all it takes (for me).

View attachment 31565 View attachment 31566

One more comment. The engines do take a few seconds to spool up. I assume since you can hear the copilot, you know this already.

--WH
 
Ok, are you using Vista, or Win7? None of my switches animate like yours. If I click the GRD switch, it only jumps up and right back down and has no effect on engine start. The ignition switches never move at all.:salute:
 
falcon409 said:
Ok, are you using Vista, or Win7? None of my switches animate like yours. If I click the GRD switch, it only jumps up and right back down and has no effect on engine start. The ignition switches never move at all.:salute:
Click to expand...
I'm still with XP. (trying to save enough to retire!!)

Looks like there's a whole page on Vista issues. Couldn't see any language related to your setup however.

http://www.flight1.com/view.asp?page=vista

--WH
 
Yea, thanks for the assist, but I'm uninstalling the T-37. It would appear that under Win7, it is incompatible. I've already spent more time just trying to start the engines than I would on any addon. This was one of my favorites, but it hasn't kept up with current OS's and I can't be bothered messing with it any more.

Thanks again!:salute:
 
Sorry to hear. Sounds like Win7 is a mixed bag. We've been having some software compatibility issues at work where some 32-bit apps will not play nice with the 64-bit apps which is forcing us to go another direction on some programs. I might have a steep learning curve and some software transitions if and when I upgrade my home box and OS.

--WH
 
Hi,

It's refreshing to know that it's not a aircraft problem .. but a OS problem ....
At least all work as in the book under the OS for what this plane was intended to run (WinXP) :)
 
You must log in or register to reply here.
Back
Top