![]() I think the difference is in detail and/or animation complexity, i.e. ![]() I'm not saying the new model looks bigger or is unfair, it actually looks the same size to me. Looks like it, because the first iteration of the new player model was a certain size, and this last iteration is a new size that is too large for what ezq is expecting. I won´t stop nagging until it is (Pokes Empezar, dimman etc)īesides, is it really necessary to edit something on the client to make the model work? ![]() One day in the not-so-distant future this player model will be plug-and-play and standard in nQuake. It´s great that more people start taking this implementation more seriously, for me, it´s a nobrainer with all to gain and nothing to lose. The 24-bit textured skins looked very nice on it aswell (maybe not perfectionist-perfect though). * Make the client load the old player model when playing a demo that has the value: new_player_model: 0 (arbitrary line and value, I know jack shit about coding and just wanted to make my point come across)īesides, is it really necessary to edit something on the client to make the model work? The first iteration of the model that was posted further up in this thread was pretty much plug and play. ![]() * Make the client check for this specific player model (or the old one, if people still prefer it) when doing a ruleset check. * Make skins (most people use fullbright one or two-colored skins, so this isn´t really a big deal) Great work BlooD_DoG, didn´t know you were such a haxxor! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |