Vivian Meazza wrote: > You certainly are! The Boost Control works by adjusting the > _throttle_ (in accordance with reality and your earlier suggestion).
Why not just use a solution setting that doesn't involve the boost control cutout? I'd think that a "flat out" solution would be most likely wrong anyway -- that's where engines are going to vary the most between installations. Choosing anything at the edge of a performance envelope and expecting the conditions to hold in the middle is always problematic. What's wrong with using a cruise value for the cruise solution? > The patch in my previous email, combined with your recent cvs input > does all that is required, both now and in preparation for the > supercharger/turbo charger thing. If you can suggest a way of doing > it using the existing code, then I'm listening. As I read it, though, your patch is currently a noop. All it does is add a new configuration option and adjust the handling of the wastegate in a way that will never make a difference in practice (skipping the wastegate handling for superchargers is irrelevant -- supercharged engines already have a very high wastegate setting that cannot be reached by an engine, running or not). I'm not arguing against it in principle. I'm just saying that I'm going to wait until we have a real issue that needs to be solved; using the _running boolean (which just indicates whether fuel is being burned) is not the right mechanism long-term. Can you explain again, really carefully, exactly what behavior this patch gives you that you need right now? Andy _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
