1. #1

    Depth Disturbance (Underwater Riding)

    I've run into a bit of a problem as regards getting my rider to work underwater, a track give me some inspiration to make a fully pledged underwater track but ran into some issues.

    1. My rider only worked underwater due to changing my waters default setting to no contact response, whenever I came to changing my bike, it made my rider crash for no reason, even though I hadn't changed any of the settings in the water after that, I would have to go into the water setting, alter it to default and switch it back to no contact response and it would work again...

    2. Once getting to this I could work on my track with no other problems... until I came to sharing my track it asks what bike you want then I selected the Roach and it started killing my rider at the beginning. I tried looking into Depth Disturbance and saw that invulnerability wasn't active else it would leave a horrid splash effect that only happens when you leave this active underwater.

    3. I thought if manually setting it to default then setting it back to no contact response works, maybe I could generate it to work by the code.

    So I set my water source to default and went into the water where my rider was at the start checkpoint. I placed and area trigger down and 2 set value events down also, with 2 variable data sources and a delay trigger.

    I placed the area effector over the rider and set the rider to checked on invulnerability then put the set event to the variable data source to change the default setting to no contact response on the water effect, then delayed the action so I could get my rider to work without this horrid splash effect and keep the mobility of the rider and set the invulnerability off after the delay so I knew the data source of the water had already done its duty by going into no contact response, but my rider still dies.

    I would of thought this would've worked considering if you can do it manually to get it to work this should also... so this must be a bug, surely.

    Thanks for having the patience reading this.

    Shout out to my boys at the OTHG, *fist bump*
    Share this post

  2. #2
    All sorted now. Got a solution and Vimes X helped me test it, cheers bro.
    Share this post