Results 1 to 7 of 7

Thread: Custom player skin bug

  1. #1

    Default Custom player skin bug

    So, since the beginning of MOHAA, there has been a bug with custom player skins on a server.
    For one (which makes sense), you can ONLY see the player skin of the other person if YOU, the SERVER and the OTHER PLAYER have that skin in their main.
    So you'd think, that people not having those skins in their main, wouldn't experience any difference..

    However, when the SERVER and the OTHER PLAYER are using certain custom skins (not all custom skins!), and you don't have those.. you can see their weapon pointed towards the sky. So the weapon is not visually located on the body where it should be. This also gives a huge disadvantage to players who don't have those custom skins in their main folder, as you can't see where the opponent is aiming at and they can clip even better without being seen.

    This is one of the main reasons we don't see people using custom skins all the time and having fun (like in Quake 3, which was amazing in using custom skins).

    Click image for larger version. 

Name:	shot4692.jpg 
Views:	12 
Size:	69.0 KB 
ID:	1865
    Click image for larger version. 

Name:	shot4695.jpg 
Views:	13 
Size:	59.8 KB 
ID:	1866
    Click image for larger version. 

Name:	shot4687.jpg 
Views:	10 
Size:	73.2 KB 
ID:	1863
    Click image for larger version. 

Name:	shot4685.jpg 
Views:	11 
Size:	159.1 KB 
ID:	1864

    After loads of testing, all the custom skins with these issues are based on the following stock models:
    • german_winter_2
    • german_worker
    • allied_manon


    You can see which stock skins they are based on by opening up the pk3s and going to the models\players folder and accessing the skin's tik file.
    You can see which skin they're based on next to 'skelmodel' & 'path model' (and sometimes there are more indicators).
    Example:
    Code:
    	path models/human/German_worker
    	skelmodel german_worker.skd
    Now I always advice admins to either remove custom skin packs or remove only specific skins.. but might there be an actual way to solve this problem?
    I have never seen anyone trying to solve this (that I'm aware of ofc.).. so.. can this issue be solved, so that every custom skin can be used on servers without any issues/bugs?
    (My first thought was if it was possible to change the stock model the skin was assigned too, but no idea if that'd work.)

    Any help is much appreciated!
    Last edited by Shadow; February 24th, 2018 at 07:25 AM.

  2. #2

    Default

    Someone told be a long tie back, think I was in NUF clan at the time that was caused by a "bad" weapons on back mod which don't really make any sense because what I know now I didn't know then is you don't need a mod for that just remove the // from the holster weapons part of tik files. Wonder if something could be added to the skins checker script to "glue" or "tag" it to the model path on custom skins ?

  3. #3

    Default

    I see this bug happening in some of the skins of the BA skin pack.

    Theres something on that skins cause that bug.

    We only need to see the difference between a skin working good and the other not to fix this.

  4. #4

    Default

    i think that bug is normal to happen, as you are missing files, so the error is from the client side

    can you post a link for a skin that doesn't have that bug?

  5. #5

    Default

    Yeah it definitely doesn't have to do with any other mod.. and it happens with loads of different skin packs and also individual skin pk3s.
    Including the BA skin pack yeah, but again.. always and only the custom skins that are based on: german_winter_2, german_worker and allied_manon, in literally every case.

    To take the BA skin pack as an example:
    BA_skin_pack1.pk3

    The bug does NOT occur on all skins in that pack like:
    • allied_Airborne_101E_Col_Sink
    • allied_capt_recon
    • german_Brandenburg_Commando
    • german_Elite_NCO
    • german_Gestapo
    • german_afrika_grenadier


    (and more, but I won't list them all)

    The bug DOES occur on the following skins in the pack:
    • german_SS_Elite_Guard
    • german_luftwaffe_field
    • Allied_British_1_snow_RADIO
    • Allied_British_1_snow_helmet1


    3 of those 4 are based on German_Winter_2 and the other one is based on allied_manon.
    I tested other skins and skin packs to find out that it also occurs on custom skins based on german_worker, however none of the skins in the BA skin pack are based on that one.
    Last edited by Shadow; February 24th, 2018 at 07:43 AM.

  6. #6

    Default

    Click image for larger version. 

Name:	shot0000.png 
Views:	14 
Size:	400.3 KB 
ID:	1868

    Here's a screenshot using r_showtris 3 (shows the origin point of each model). using the Allied_British_1_snow_helmet1 model.
    it shows the player origin at the bottom, the origin of the main weapon (tag_weapon_right bone) and the origin of an attached model to the tag_weapon_left bone

    and for some reason, both tag_weapon_right and tag_weapon_left bones are shown on the back of the player when they should be near to the hands.

    so i think probably the problem is some models where made using different skeletons/bones, and that makes the tag_weapon_ bones to get misplaced when you don't have the model. (just my theory)

    and this also happen when using the skin i made, the ugandan knuckles
    it uses a custom .skd with this skeleton mohaa_player_skeleton.RAY.zip
    i don't remember what animation file i imported it from, but probably from a skeleton made for single player bots because it has a "helmet bone" and the helper bones are missing
    i wonder if this also happens to TheRipppa's models

    but still, i have no idea if this is fixable or not
    Last edited by Zappa; February 24th, 2018 at 05:05 PM.

  7. #7
    Administrator James's Avatar
    Join Date
    May 2010
    Location
    on the intraweb
    Posts
    3,180

    Default

    It probably has something to do with the model of the player. Try replacing the skelmodel with that of another player that doesn't have this issue and see if that works.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •