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

Add direction noise fluctuation post-process #51

Open
wants to merge 2 commits into
base: development
Choose a base branch
from

Conversation

sinbad
Copy link
Collaborator

@sinbad sinbad commented Dec 19, 2016

This is just like the speed fluctuation component but gives a little extra variance to final result which helps it look more natural.

BTW: hope you don't mind all these PRs, it's just my principle to contribute back changes I find useful even on MIT projects. There's no urgency to merge these from my perspective, I'm just sending them as I make them.

@ricardojmendez
Copy link
Owner

BTW: hope you don't mind all these PRs, it's just my principle to contribute back changes I find useful even on MIT projects. There's no urgency to merge these from my perspective, I'm just sending them as I make them.

Not at all! I'm glad you not only find it useful but contribute.

I hope you don't mind my delays in getting them reviewed and merged. This end of year is providing to be a bit overloading, so I've had to table anything non-fundamental for now.

I hope to get around to them before the end of the year, but in fact, let me just add you as a contributor.

Cheers!

@ricardojmendez
Copy link
Owner

There you go. Couple of requests:

  • I'm using git-flow. Please make your changes on develop, we'll eventually do a release on master.
  • Keep a changelog.
  • When adding a feature, please provide an example using it on UnitySteerExamples (where I've also added you as a collaborator).

Cheers!

@sinbad
Copy link
Collaborator Author

sinbad commented Dec 19, 2016

Thanks!

I'm using git-flow. Please make your changes on develop, we'll eventually do a release on master.

I only see a development branch rather than develop, I pointed all my PRs at that assuming that was the target, that OK? Since I'm still pretty new to this I'm happier submitting PRs rather than merging directly to development myself.

Keep a changelog.

Cool, I didn't know what your procedure was here, assumed Changelog.md got updated at release time since updating it for every PR tends to cause merge conflicts. Happy to update it for each PR though if you prefer.

When adding a feature, please provide an example using it on UnitySteerExamples

👍 given most of these are small refinements is it OK to tweak an existing sample to include it where appropriate?

I hope you don't mind my delays in getting them reviewed and merged.

Not at all, I'm not waiting on anything, I'm just submitting these as I go so I don't forget. I'm happy if I can add something back (and equally relaxed if you say something doesn't fit being upstream) but there's absolutely no rush since I'm using my modified copy. I'm very grateful for your work on this project and don't wish to give you more work to do! :) I won't be at all offended if these PRs sit in the queue until you have some free time, be that day, weeks, months, more or even never 😉

Thanks again!

@ricardojmendez
Copy link
Owner

I only see a development branch rather than develop, I pointed all my PRs at that assuming that was the target, that OK? Since I'm still pretty new to this I'm happier submitting PRs rather than merging directly to development myself.

You are right. I forgot that I named the one on UnitySteer before I switched naming to the more succinct develop :-)

Cool, I didn't know what your procedure was here, assumed Changelog.md got updated at release time since updating it for every PR tends to cause merge conflicts. Happy to update it for each PR though if you prefer.

Thanks! I usually just add to the changelog under a SNAPSHOT or WIP version. Such conflicts are easy enough to fix if we keep them to one line, one change.

given most of these are small refinements is it OK to tweak an existing sample to include it where appropriate?

Definitely!

Cheers!

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