[0.9.002-BACKER#2105] Sela "Ride Cock" Crash

[Rumpumcels]

Attempting Sela's Ride Cock scene causes a crash.

``` Version: 0.9.002-BACKER#2105 Message: Unexpected pregnancy slot 0 used to call tryKnockUp. Stack:
TiTSException: Unexpected pregnancy slot 0 used to call tryKnockUp.
at r (https://www.fenoxo.com/play/TiTS/backer/main.21e9a28c.js:1:9528152)
at o.value (https://www.fenoxo.com/play/TiTS/backer/main.21e9a28c.js:1:1800477)
at o.value (https://www.fenoxo.com/play/TiTS/backer/main.21e9a28c.js:1:2197499)
at md (https://www.fenoxo.com/play/TiTS/backer/content_zhengshi.864f4c46.js:1:4401068)
at Jw (https://www.fenoxo.com/play/TiTS/backer/main.21e9a28c.js:1:16180342)
at Kw (https://www.fenoxo.com/play/TiTS/backer/main.21e9a28c.js:1:16179602)
at Object. (https://www.fenoxo.com/play/TiTS/backer/content_zhengshi.864f4c46.js:1:4389304)
at https://www.fenoxo.com/play/TiTS/backer/main.21e9a28c.js:1:11851818
at s (https://www.fenoxo.com/play/TiTS/backer/main.21e9a28c.js:1:10165183)
at o (https://www.fenoxo.com/play/TiTS/backer/vendors.c5a896e9.js:1:48980)

 

[DrunkZombie]

Ok, I expect this is the same issue I've seen elsewhere where the vagina router is returning -1 for single vagina Steeles.

 

[DrunkZombie]

When I get a chance I'll put in a change in sela sex scenes to deal with it. Then I can invistigate what was changed in the vagina router to cause the issue in the first place. It is supposed to return 0 for single vagina Steeles.

 

[Rumpumcels]

My Steele doesn't have a vagina though.

 

[DrunkZombie]

hmm, interesting. Will look when I can.

 

[DrunkZombie]

Scene was coded to cum in vagina even for anal, so fixed that issue. I does point to a possible related issue I am curious about, did this character used to have a vagina at some point and it got removed?

 

[Rumpumcels]

I don't think so. Definitely not in the Java version. And even if I added one through save editing, at some point, I didn't save afterwards. I'd just load a previous save to revert it.

 

[DrunkZombie]

Ok, just curious. It might have explained why you hit the bug you did that normally shouldn't happen even without the change I just did. Need to look for another cause but at least this issue is fixed now. Thanks.