So in my track I am currently working on, I have a spot in the map where when I place down a checkpoint, that checkpoint doesn't seem to work, when I press "b" on the controller the rider is frozen as if the frozen selection was bolded in, so from what I heard was that heetsauce had the same problem and didn't want to upload his track to show you guys the glitch in the sake of his work , I am willing to upload the track only if as soon as you receive it you take the track down immediately! For I want this glitch to be solved so I and others don't have to deal with this anymore
So what do you as the developers want me to do?
Do you have anything attatched to the rider at all?Originally Posted by snipen108
how many check points you got
maybe you all ready know about the 20 check point limit in which case i have know idea
could be over loaded with effects or bright lights in that area
you could post a vid of the track allso show some of the production side. i make tracks but i don't have the power to take tracks down, that would be a cool power
This happens on Synapsis' Dead Pool also, 3rd or 4thcheck point, if you press b the rider and bike are frozen as if the physics bubble didn't reset to the checkpoint. It really needs to get fixed.
Originally Posted by Barrybarfly
Not a single impulse, data source, etc
Just so some people don't disbelieve this and think I'm stupid, there isn't a blue, a red, or a green arrow that goes into the rider
5-7Originally Posted by look3y
is it on paine island or does this occur else whereOriginally Posted by snipen108
i allso never encountered that problem so im sort of interested in case i ever do
No, I just wondered if you had soemthing attatched via a physics joint. I've seen it happen when a CP reset causes a physics joint to "drop" and the attatched object makes it act as if the rider is frozen. It was caused by too much happening at that CP. So I just wondered if that might have been a cause as that would be fixable.![]()
actually i was playing custom last night and it did happen
didn't happen every time
does it happen if you have faulted earlier it happend to me on a no fault run
Anytime to meOriginally Posted by look3y