I find bugs extremely fun to drive so I felt great. But it was extremely frusturating to do clip at 2nd apple and end, got internal errors every 0.01 and many bounces and attempts wasted because impossible.Zweq wrote:I cant imagine how b0ne felt. I let him do al the imposible clip stuf while I spent time optimizing easy parts)).
Final rec in lab pro
http://www.recsource.tv/r/byvzjdwqgu
Quick-just-finish rec that was made cause fuk all with lab pro end.
http://www.recsource.tv/r/uzrefcmogh
I recommend you watch the two big bounces at 2nd and 3rd apple in slow motion, actually all bug recs are amazing to watch in slow motion because you can really see what goes on with the head/wheels.
My first rec managing clip after 2nd apple was http://www.recsource.tv/r/mbojldqknf, now we had to investigate if it would be poss fast to skip third apple and use a clip like this. Because the time spent driving from 2nd apple to third is quite long.
After Zanpe fooled around with 35firstbigclip he told me it still faster to grab third apple propably, even though it requires normal vromage from 2nd to 3rd apple. Remember we were still sure it is impossible to survive clipping at second apple and land at third apple norm. And we cant do some mega bounce and continue clipping to flower because this route requires apple bugs.
Saddened by zanpes news about not using my cliprec that I spent quite some time driving I went and tried and tried until I got clip and survived to third apple. Zweq drove the very last part of the bug (15,70-15,90s) where you get big speed towards the apple. He has an amazing ability to turn my close enuf attempts into something fast.
I can't really explain this clip in any norm explainable way, what I did was just vrom and see what happens, if I ended up with too much speed or too little I redrove the entire bounce with another start speed. I spent like 7 hours total or something just playing this 2 second long part of the level.
Third apple bounce-clip I will try to explain because here I had a norm idea that I managed to convert and twist to my advantage.
1. Zweq drives part after bigclip, gets third apple, does bounce that pops wheel into wall. He sends me http://www.recsource.tv/r/ctwudvmxlk and says "Here enough stretch for bugging".
How Zanpe even can imagine that clipping with just a stretch of wheel is something I still don't understand. Thinking about it now it really feels like something that is impossible.
2. I fool around making shitty attempts for a while until I realize that there is a really simple physics property that you probably can abuse. http://www.recsource.tv/r/fdpvtjhagk. Rec is driven with 999 fps to illustrate property. Doing this at lower fps will (theoretically) be stronger and able to build up enuf speed.
3. I manage to drive the same thing with low fps, since wheel just clips bike doesn't slow down and it sends it flying to the top left. A rec like http://www.recsource.tv/r/vkyiubnzhd is made. Clip is done, now to fall down instead of up left.
4. Alternate low/high fps to "insert bugged frames" causing the wheel to alternate between inside/outside the wall at third apple. This makes it so the wall can be used as a hang to swing down http://www.recsource.tv/r/hrtvcyuqmi. The bugged frames also help change direction of the bug. You can do max fps and just hang but that is slow compared to bug frames.
5. Now bike is falling down, problem is that there is no stretch left so bike just falls without any bugs happening. So what is made, and shown in final rec is more weird frames to keep stretch.
6. Lazy driving while falling, alternate 100/999 fps every now and then. Reason is that only 999 fps will cause wheels to unstretch and "kill the bug" and only low fps will cause international error. This can be done anywhere while falling in a big area to keep bug alive.
7. Now bike is above flower. Why is end so hard? Because it is a big stretch that is very likely to cause a crash while you have head in a tight space. If you don't crash you most likely die.
Also the finished rec has the most butiful end frame of any bugrec. Likely the check for finish level is made before the check for crash because if you cut this rec to remove the last frame eol will crash when watching the rec.
So in theory you could make a program to bruteforce instantfinish of no apple levels?