Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Hit location being confused with RHS clothing #2511

Closed
Khaosmatic opened this issue Sep 18, 2015 · 7 comments
Closed

[Bug] Hit location being confused with RHS clothing #2511

Khaosmatic opened this issue Sep 18, 2015 · 7 comments

Comments

@Khaosmatic
Copy link

Bear with me for this sudden shoddy bug report I will definitely update to proper bug report standards it after this group session I'm about to go into.

I just noticed that while wearing RHS USMC clothing when I shot an AI in either leg it would damage the corresponding side arm. If I shot the arms it would cause bleeding in the head and the torso also seems to cause head bleeding as well.

There are quite a lot of mods in use so I will try doing it with just RHS and ACE. I mainly made this now just in-case I forgot about reporting it.

@commy2
Copy link
Contributor

commy2 commented Sep 18, 2015

Is that uniform a retexture of the nato uniform from vanilla?

@gienkov
Copy link
Contributor

gienkov commented Sep 18, 2015

Lol we have the same issue here. They've made custom models for their uniforms so definitely not a retexture.

@Khaosmatic
Copy link
Author

Yeah it's their custom models, vanilla units worked absolutely fine. I'm surprised it still doesn't recognize the default skeleton of the model.

@commy2
Copy link
Contributor

commy2 commented Sep 19, 2015

Can someone mess around with vanilla + rhs and check with
cursorTarget getHit "hands" etc.
if the models are set up correctly?

@Armilio
Copy link

Armilio commented Sep 25, 2015

Same issue here with custom uniforms. I have problem with uniforms that have worked fine until my clan passed from AGM to ACE, at least. But probably it's a issue with the 3.3.1 patch.

@thojkooi thojkooi modified the milestone: 3.5.0 Nov 29, 2015
@bux
Copy link
Member

bux commented Feb 20, 2016

Closing due to no activity and no proper bug report. Even though it has been promised. 😢

@bux bux closed this as completed Feb 20, 2016
@thojkooi thojkooi removed this from the 3.5.0 milestone Feb 20, 2016
@Khaosmatic
Copy link
Author

Apologies I didn't realize this was still open, this issue was fixed a long time ago to my knowledge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants