search

namazso / nSkinz

Skin changer for CS:GO
MIT License
219 stars 116 forks source link

Bug when updating skins #101

Closed JimmyBassy closed 5 years ago

JimmyBassy commented 6 years ago

screenshot_1

So as you can see the gloves are somehow glitched but this only happens if I change the skin, this happens with all the weapon models and knife models. As a temporary fix for me after tabbing out of the game and tabbing in again seems to fix it. Maybe is just my problem because everything was working fine before so if noone has this issue too I will try to fix it by myself. Thank you all!!!!

ghost commented 6 years ago

If you find a fix can you please share? I'm having the same issue

JimmyBassy commented 6 years ago

Sure, still nothing I just tab out and tab in to see them

ghost commented 6 years ago

With skins, if you drop them and pick them up it fixes as well, you don't need to Alt + Tab, but for knives and gloves you still need to

MagicTripz commented 6 years ago

Try to type "record x;stop" into the console whenever this bug happens. if it fixes it, then the problem is that cl_forceupdate isn't called

ghost commented 6 years ago

@MagicTripz could you explain this to me a bit further? I'm sorry, but I don't know much about the Source engine nor C++ coding and stuff. Is there any way to permanently fix it? Maybe I could figure it out by myself if someone explains to me the basics.

Here is my Discord: ward0#9736

namazso commented 6 years ago

If the suggested way works that means forceupdate is now sensitive of when its done. Currently setting is done in render thread because it hasn't caused problems so far. Commands are always queued and executed in game thread, so thay would explain why it fixes the problem.

MagicTripz commented 6 years ago

I compiled it yesterday and i realized the way forceupdate is called is really fucking up some parts of the game, atleast for me i'd go with the safe way (especially for most ac's) aka record x;stop. Pretty easy to implement just delete from the menu the forceupdate call, implement if not already there engine->Clientcmdunrestricted , and just on let your cheat type "record x;stop" every time the update button gets pressed. If you are really down to change things you could also implement instant kit updates(https://www.unknowncheats.me/forum/counterstrike-global-offensive/225472-instant-weapon-paintkit-update-fullupdate.html)

M1XT3NZ commented 5 years ago

as of #106 this is now fixed

fostersmiles commented 5 years ago

still not fixed mate, im running at the newest version and it is still doing the same thing, but alt+tab fixes it and the record x:stop too

M1XT3NZ commented 5 years ago

It’s actually weird I do not have this problem at all.

On Mon 11. Feb 2019 at 19:51, fostersmiles notifications@github.com wrote:

still not fixed mate, im running at the newest version and it is still doing the same thing, but alt+tab fixes it and the record x:stop too

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/namazso/nSkinz/issues/101#issuecomment-462447843, or mute the thread https://github.com/notifications/unsubscribe-auth/Ab_SZlqjPLNzQ8678r4Z5CWeVgVh_QMIks5vMbvEgaJpZM4WXZOZ .