DCForum Discussion Forum - Variable1 findings and relationship to speed variable

This applies to steam engines, maybe the others too. One problem with using variable1 has been that at speed, when you shut the throttle and things go quiet, then open the throttle, the engine will chug several times at the lowest speed wav file, then jump to the speed it should be at. The fix is simple! Add a quiet short wav file (x_power_cruiselow.wav or some such) and use it as the first speed. Give it a very short time like; Priority ( 6 )
Triggers ( 50 Variable_Trigger ( Variable1_Dec_Past 0.01 StartLoop ( 1 File ( "x_fs_power_cruiselow.wav" -1 ) SelectionMethod ( SequentialSelection ) ) )
Variable_Trigger (Variable1_Dec_Past 0.06 ReleaseLoopRelease () ) Variable_Trigger ( Variable1_Dec_Past -0.6 StartLoop ( 1 File ( "x_fs_power_cruise1.wav" -1 ) SelectionMethod ( SequentialSelection ) ) )
Variable_Trigger (Variable1_Dec_Past -1.6 ReleaseLoopRelease () ) This will access first now, and there will be no improper sound when you open the throttle.If you decide to convert from a speed variable set of chuffs, the speed range has a relationship. For instance, if the settings are; Variable_Trigger (Speed_Inc_Past 1 StartLoop ( 1 File ( "x_fs_power_cruise1_5.wav" -1 ) SelectionMethod ( SequentialSelection ) ) )
Variable_Trigger (Speed_Inc_Past 2 ReleaseLoopRelease () )1 to 2, in the variable 1 settings, to get the same chug rate, multiply by........PI, 3.14 ! So the new settings will be 3.14 to 6.28, It saves a lot of figuring!!!Steve

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Good work-around on the zero regulator bug Steve.Hmmm. PI you recon. How many engines have you tried that on Steve? Personally I have found I need to use different values for different engines.

Alert | IP