I'm sorry, but I have to butt in here and throw down some truth. I am only being honest here and in no way intend to harm you. Jakizle, as I'm sure you know from only two days of design, this is not good work. The shaping is like, not even close. The transitions are unbearably fast and frankly not even smooth; they're almost rct-like. These are definitely the most prominent, outstanding flaws. The hill shaping is mediocre, not horrible though. I would just say you need to look at a lot of pictures and much more importantly, ride POVs of the gigas and get the feel. This didn't ride like a B&M should and I know you that know how it should ride, so I feel that this is just a result of quick, prototype-esque work. Additionally I am very, very against the inverting turnarounds I have seen on some mega/giga uploads. I look forward to your uploads on NL2 in which you take more time to perfect the design and technique. Thanks for the ride!
T: excellent smooth, and flows really nicely, although towards the end the transition thru the elements wasn't as fast as the first half, but that's normal for a B&M. A: Great hands down, lots to keep the blood flowing, those quick turns and transitions helped this score the most, great pacing! U: That transition back, made this score, it was unexpected, and when I first rode, I said wow out loud! The speed thru it was constant, and would have some "Full Throttle" type hang time. It does seems like a possible element, thats how well it was executed. R: Lots of B&M inspiration, Fury 325 turns, and general B&M techniques were used. RV: Lots to enjoy, surprise, and excite! Could of used some more scenery, but I don't believe it should affect any score.
P.S. Upload more screenshots, its a great ride, advertise this great coaster!
As usual your trackwork and supports were really really good. I don't have much to complain about, but I will say that the area between the tall turnaround and the low turn before it could have been done a little bit less rigidly in the banking, and when you make supports that end up close together, have each pole go into its own footer and cluster them around each other, don't have all of the poles merging into one solitary footer. If you look at really B&M's they end up right next to each other, not within each other like what you have.
The ride feels right in the front and back seats, and you really nailed that sideways air thing that Fury 325 has. The ride is presented in a nice but subtle environment, and feels and looks like a real B&M. I like that your layout is a nice realistic "controlled sprawl" instead of just being meandering and pointless. The trim and the Shambala hill were a nice touch too. I hated your final brakes just like I hate the final brakes on Leviathan. Do you think it's cheaper in the long run part-wise to stop a slower train high up and then let it gradually work its way down than to go through all of the brakepads you'd need for a ground level much faster stop? I can never figure those brakes out.
As a final nitpick, you may want to have catwalks on both side of the track when you have sections of track that have brakes on them. Mantis has only one catwalk on the turn after the final brakes but it switches to two catwalks again in the final brakes so the mechanics can get to the other side of the brakes.
Again I don't have much to complain about as usual and I'm really reaching here. Thanks for making this.
"Did it in like 2 days". Oh how I wish I could do that in two days lol
I'm really busy with some things but I really wanted to say this. If there is one thing I miss about NL1.x is the feel for having a ride not 100 slammed with realism focus but is just meant to be fun. I really miss that feeling and now NL has turned into a park creating thing with some roller coasters. That said I LOVE what you're doing with these rides! They bring that old feel back and I really enjoy that. Keep it up
Home
Contact Us
Login
Register
Store
Exchange
Browse The Scrapyard
Forum
Donate
The speed thru it was constant, and would have some "Full Throttle" type hang time. It does seems like a possible element, thats how well it was executed.
