JRHockney* Posted September 17, 2006 Share Posted September 17, 2006 Both myself and vruki had this problem today at Jasks server. We both got "warning, failed assertion" windows pop up. it said it was at cg_players.c line 13938 for me, and vruki said his was at line 13440. Not sure what it is, but I was able to click ignore most of the time without it doing anything, but a few times it crashed me. Also, I noticed at that server that I couldnt block any kicks while in slowbounce with crouch or alt attack. Is the kick block gone in 0.0.9i? If so, its annoying me already and I want it back! LOL. If not has there been a button change? I dont think it was lag, because I started holding crouch (and when that didnt work, alt attack) even during the saberlock (which is another reason we need to make the locks escapable btw, lol). Link to comment Share on other sites More sharing options...
Tanqexe Posted September 17, 2006 Share Posted September 17, 2006 Maxstate said something about holding the back button in 0.0.9i? Something like that. I'm all for escapable locks btw...it'd be neat to have the option to either press the lock or disengage Link to comment Share on other sites More sharing options...
ensiform Posted September 17, 2006 Share Posted September 17, 2006 That is not exactly a bug, just a line (of the many) that raven left in for making sure something doesn't happen. These only show up when compiled via "Debug" and not "Final" or "Release" Link to comment Share on other sites More sharing options...
razorace Posted September 17, 2006 Share Posted September 17, 2006 But it normally indicates that something is wrong with the current state of the code. In this case, it means that someone is trying to use a blade on a lightsaber hilt that doesn't have an emitter point for said blade. IE, it doesn't have a *blade_ or *flash_ tag for that blade on the saber. It probably means that he's using a saber on the server that has more blades than the "default" hilts have. As such, if you don't have his blade, it freaks out. This is a basejka code check, so the problem is with one of Jask's moded sabers. I beleive I've already talked to him (or someone else) about this. I suppose we could improve the saber emitter detection stuff to prevent an issue like this but I'd need to know what the exact problem was. Link to comment Share on other sites More sharing options...
ensiform Posted September 17, 2006 Share Posted September 17, 2006 saber emitter u r? Link to comment Share on other sites More sharing options...
razorace Posted September 17, 2006 Share Posted September 17, 2006 Say wha Ensiform? Link to comment Share on other sites More sharing options...
ensiform Posted September 17, 2006 Share Posted September 17, 2006 what is this saber emitter you are refering too? Link to comment Share on other sites More sharing options...
razorace Posted September 17, 2006 Share Posted September 17, 2006 It's the surface tag from which the saber blade is rendered on the saber hilts. Link to comment Share on other sites More sharing options...
ensiform Posted September 17, 2006 Share Posted September 17, 2006 uhm......................................................... Link to comment Share on other sites More sharing options...
razorace Posted September 17, 2006 Share Posted September 17, 2006 IE, it's the point on the model where the saber beam comes out. If it's not actually defined on the model, the game doesn't know where the blade should stick out. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.