1st FVD Coaster- Woodie

I was thinking of making an 'El Toro' kind of ride, but using FVDs, and a better layout and more elements.

I just need some help with the FVDs themselves.

;;;;;;;;;;;;;;;;;
;; USER INPUT [1]: BANKING-TIMES
bTimA = 12
bTimB = 0

;;;;;;;;;;;;;;;;;
;; USER INPUT [2]: G-FORCE-TIMES
gTimA = 3
gTimB = 3.5
gTimC = 3
gTimD = 0
gTimE = 0

SWITCH[T]{
CASE[0.000,gTimA]{; < - - - - - - - - 'gTimA'
S=T/gTimA
tFunk = 6*pwr[S,5]-15*pwr[S,4]+10*pwr[S,3]
gPunk = 4.0
}
CASE[gTimA+0.000001,gTimB]{; < - - - - 'gTimB'
S=(T-gTimA)/(gTimB-gTimA)
tFunk = 6*pwr[S,5]-15*pwr[S,4]+10*pwr[S,3]
gPunk = -1.3
}
CASE[gTimB+0.000001,gTimC]{; < - - - - 'gTimC'
S=(T-gTimB)/(gTimC-gTimB)
tFunk = 6*pwr[S,5]-15*pwr[S,4]+10*pwr[S,3]
gPunk = 4.0*tFunk

------------

Can you tell me what I did wrong above? The g-forces are what I want them to be, and the g-force times are the only times that are correct so far (bTimA is not exact yet). I know, I am a newbie at this. I just need some help.

Can you feed me with a spoon?

^ Corn Pops okay (That's all I got)?

Read through the ReadMe, thats what it's there for.

I just need some help on what I did wrong.

Instead of having 4 in time a and -1.3 in tim b or something like that, have tim b say (4 - 5.3*tFunk) tFunk provides a smooth transition, and it needs to be used whenever you change the force or banking. The gtim's already have the tFunk set up, but most of the btim's need teh tFunk to be placed in.

gtimA = 4

gtimB = 4 - 5*tFunk

gtimC = -1

gtimD = -1 + 4*tFunk

gtimE = 3

Something along the lines of that

Well, that helps, but produces this odd loop or something. Is there a way to get rid of that?

Have g times of 1 and not like 3.

Also your g times and banking times must add up to be even.

Yashgh. You math junkies scare me.

Thanks Jake.

Originally posted by GerstlCrazy

Yashgh. You math junkies scare me.

I know huh.

Originally posted by GerstlCrazy

Yashgh. You math junkies scare me.

You are afraid of 3rd grade level (maybe 2nd grade??) addition and subtraction?

Your g force and banking times actually don't have to end up even. The shorter one is the limiting one.

Not a whole lot of math involved in making an FVD element GerstlCrazy.

Jake, the ejector hills (with your suggesstion of making the inputs like one second)end up starting flat instead of like 60 degrees up or something (which I want), but when I use like 3 seconds, it ends up fine. Got a suggesstion?

How about I send you the element file to show you what I mean?

2 pics posted

http://www.nolimitsdevcenter.net/p3923

Umm, if you're starting on a slope and want to start with the pull over, then your starting force need to be about 1.0 (middle of positive to negative g transition, aka "flat" track).

No, I start at the -80 degree angle. It's easier that way. (Sorry if I am taking the easy path).

It is also *barely* and partly H:SAKed (with some modifications, of course).

Put the formula "cos(theta*degrees)," with theta = slope in degrees, into google to find your initial force. If you do what Jake said you'll get some kind of bump or pump or something.

Well, it's pretty smooth nevertheless, even through the AHG.

I picked these stats from Wikipedia for El Toro:

Lift: 13.5 mph
15 sec to top of lift
Unnoticable slow down at top
70 mph, but sometimes 75 mph

For my coaster:

Lift: 15 mph
15 sec to top of lift
No slow down
76 mph

El Toro has a slower lift now.

Only at the top.

How come is it slower? Is it because to try to reduce the speed to 70 mph?

Probably maintenance issues.

How do you know it is slower?

DCs221 goes to SFGADV all the time and is kinda in the know...I believed they slowed it at the top becuase the train was too agressive on the drop and first hills, which caused the train to crap out near the end of the ride...with a slightly slower beginning the train keeps its pace throughout the entire layout.

Hopefully Dcs221 can explain in more detail.