Training mission 1
-
Well starting from the beginning! I have gone through the ramp start and check lists both as advised in the training manual and the video ramp start guide pt. 1 & 2. Always have problem at the same spot.
The engine won’t spool up beyond 25% so although sec caution light goes off. that’s as far as it goes; SEC light stays on.
Now using X52. Throttle moves 3D throttle and the X52 control shows it’s OK, so I don’t think it’s that.
I have not changed anything in the mission. I also haven’t tried a ramp start in any other mission/setup.
Suggestions?
-
After hitting JFS 2, and the engine spools up to 20%, Move the throttle to 50% or so, hit alt+i, then bring the throttle back to idle. This should get the engine starting up
-
What are you using for idle cutoff on your throttle? You hit Start 2 and wait for the engine to get to 20% more or less, and then advance the throttle past the cuttoff detent. Now, what you use as the detent it self may vary according to your hardware and Falcon config. I use Alt-i (the default) mapped to that function on the Warthog (because it has that detent). Can’t remember how you would do that on the X-52.
Also, for some reason I never bothered to check, I have to advance the throttle quite a bit before hitting Alt-i, otherwise it’s like the game doesn’t register the movement on the axis.
Edit: ninja’ed.
-
After hitting JFS 2, and the engine spools up to 20%, Move the throttle to 50% or so, hit alt+i, then, after the engine begins spooling (watch the RPM gauge), bring the throttle back to idle. This should get the engine starting up
Added my recommendation to your original advice.
There is also a recent thread on the same issue, here: https://www.benchmarksims.org/forum/showthread.php?24482-Ramp-start&p=348861
-
I will try that Alt i. Not sure about throttle setting about an X52 mapping of the throttle cutoff detent though ( on the throttle itself I suppose you mean). Anyway I’ll try and check that out.
-
Yeah, the TM Warthog has a physical detent that also triggers a joystick key when you pass it. That’s what I have setup to send Alt-i. No such thing in the X-52, thou.
-
Thanks guys. As it happens I have a spare button on the throttle so just set Alt i there for the time being, although probably just as easy to use the kb. Anyway got past that hiccup!
-
Further to above, I note one can make the X52 throttle into bands. Has anyone tried to use a band for Shift i and in which case what size. I note on the programme that the bands seem to work in reverse; i.e. 100% is at 0 throttle??
-
Further to above, I note one can make the X52 throttle into bands. Has anyone tried to use a band for Shift i and in which case what size. I note on the programme that the bands seem to work in reverse; i.e. 100% is at 0 throttle??
Why would you make bands when you can effectively do the same thing in the BMS UI?
set g_bUseAnalogIdleCutoff 1
The ‘problem’ with an X52/52 Pro is that there is no physical detent at the bottom end (the idle end). That means if you accidently cross that lower line (whether bands or BMS UI established) at ANY time after ramp start, you will stall the engine.
Not to mention that allocating any throttle movement distance to ‘above afterburner detent’ or ‘below idle detent’ reduces the resolution of the normal throttle range. That is, for example, you now have 80% of the range (10% below idle detent; 10% above AB Detent) for 100% of Mil power. At the tanker or in formation, that little bit of extra ‘sensitivity’ might be useful. And if you use dead zones (with bands), you’ll reduce that resolution even further.
What I’m saying so inelegantly is, “I want as much throttle movement as possible to be in the Mil power range.”
-
What I find is that I have to do an actual cockpit “wipe-out” prior to starting anything - upon entering the pit, move all of your controls - particularly the throttle - through full range and back to rest position(s). Then proceed with the start sequnce. No idea why this works for my set up (Cougar, Saitek pedals), but it does seem to solve some problems.
-
Ah! I didn’t know one could right click to set the detent! I’ll try that!
-
Ah! I didn’t know one could right click to set the detent! I’ll try that!
I think (pretty sure, but I don’t use it) that the option “set g_bUseAnalogIdleCutoff 1” has to be set in the file x:\Falcon BMS 4.33\User\Config\falcon bms.cfg before it’s available in the Setup screen. You can edit that file with a plain text editor like Notepad.
Edit:
Sorry. The ‘proper’ place to set this is in the Launcher Configurator: