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

Hellbender: Various Updates #213

Open
wants to merge 20 commits into
base: master
Choose a base branch
from

Conversation

HellDragon-HK
Copy link
Contributor

Well this engine sound is right but we've still got a bit of a pitch issue that I don't know how to solve, it does seem closer by adding in IdleRPM=2000 but not quite there yet, IdleRPM=4000 is about what we should hear for when actually moving I believe.

Well this engine sound is right but we've still got a bit of a pitch issue that I don't know how to solve, it does seem closer by adding in IdleRPM=2000 but not quite there yet, IdleRPM=4000 is about what we should hear for when actually moving I believe.
@HellDragon-HK HellDragon-HK changed the title Hellbender: Sound Update Hellbender: Sound Update WIP Mar 2, 2018
@HellDragon-HK HellDragon-HK changed the title Hellbender: Sound Update WIP Hellbender: Various Updates Mar 14, 2018
@HellDragon-HK
Copy link
Contributor Author

HellDragon-HK commented Mar 14, 2018

Sounds redone for UT3 style variance (non recorded now)
UT3 Bullet Impact sounds added
Didn't have Drawscale = 1.0 in my class so a few things needed to be redone like the headlights

@HellDragon-HK
Copy link
Contributor Author

Fixed combo self damage problem

@Unre-Alex
Copy link
Contributor

Thanks for fixing the combos! Like with the suspension, a small fix for a big issue.

This is duplicated in the class:

EntryPosition=(X=0,Y=0,Z=0)
EntryRadius=180.0  //300.000000

@HellDragon-HK
Copy link
Contributor Author

HellDragon-HK commented Mar 17, 2018

Thanks for pointing that out Alex, and in light of that and you said the ImpactDamageMult went missing, I've done what I've been wanting to do to everything and try to organize it more....would like to make it uniform format across all the other classes too if possible so we no longer need to look all over the place to avoid this from happening, any objections or opinions?

If unclear what I mean by this is all classes have the same order of info in defaults so for the main body of the vehicle it would be the looks/visuals related first, then sounds, damage, movement, entry & exit, and then camera, this way we have less issues with duplicate entries because we don't need to look at everything in the defaults area to try and make sure there are none and will only need to check a specific section.

I had a lot of duplicate issues with the Viper recently because it's defaults are all over the place for example.

@HellDragon-HK
Copy link
Contributor Author

HellDragon-HK commented Mar 17, 2018

Ok done with reorganizing...or at least attempting it, if it's a good idea and it came out well I'll slowly do it across other classes as well, if it is a good idea but needs some more thought we can do that here too before doing others.

EDIT - Oh and in a completely unrelated note but because I need to mention it somewhere, the CollisionHeight & CollisionRadius entries have nothing to do with physical impact that I can see, they appear to be the requirements for controlling if spawning has enough room which I've been trying to use on the Cicada but no luck fixing it on Urban with it.

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

Successfully merging this pull request may close these issues.

2 participants