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

"How to" improvements #18

Closed
Offlein opened this issue Dec 30, 2019 · 6 comments
Closed

"How to" improvements #18

Offlein opened this issue Dec 30, 2019 · 6 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@Offlein
Copy link

Offlein commented Dec 30, 2019

Hello,

As a newbie Unity dev, I found this tool very useful.

One quibble that was frustrating, however, was that the How-To guide is a PDF, which means that within GitHub (where I guess most people will read it) the text is not selectable or searchable (via Ctrl+F).

Is there a reason for this? And if not, would you be open to reworking it into standard markdown? I would be happy to help, if so. Additionally, I believe you are a non-native English speaker, and I think there are a number of things that could be phrased more clearly, if you would be open to letting me rejigger some things there, too?

The biggest downside is that I'm a really amateur Unity dev, so I think there are some fundamental concepts I may be misunderstanding in your explanation, and it may require you to answer some dumb questions on my side. :(

Thanks so much for the great lib.

@h8man
Copy link
Owner

h8man commented Jan 1, 2020

Hello,

Good points. Through, I don't want to put any resources (images etc.) into repository, as it is just a lib. I'm kind of annoyed when I want download 2 source files, but 10 images, 20 tests and 4 examples files.

We can make GitHub wiki page. I will create a draft from current PDF and enable modification for community.

What do you think?

@Offlein
Copy link
Author

Offlein commented Jan 2, 2020

@h8man Sounds good to me! And great thinking on the Wiki. However, if I click the Wiki top menu nav item, it just redirects to the repo homepage, so seemingly I may not have access to .. even view it? Yet?

In other news, I was curious how one gets images into a wiki. Apparently you commit to them like normal (but separate) Git repositories, and you can reference the images you commit. So I think I'll have to do that for screenshots, and then I guess commit to a fork and make a PR to get it back in? I'm not sure how PR's will work for wikis. Anyway we'll figure it out once I can at least access the wiki. :)

@h8man
Copy link
Owner

h8man commented Jan 5, 2020

@Offlein I've created wiki page and grant permission for edit.
I think you can edit text right form GH, or maybe even download as repository.

Check it out and tell me how it works for you.

@Offlein
Copy link
Author

Offlein commented Jan 17, 2020

Hello,

Well! You really did the hard work of getting the images in already!

I just did at least a first draft of fixes. I don't understand the hexagonal mesh stuff at all, however (and it's not part of my personal use case) so I think more can be said there.

Hope this helps!

@h8man
Copy link
Owner

h8man commented Jan 17, 2020

Nice,

I like highlights on terms.

As for hexagons, I was in search of easy workflow for non-square grid case. So you can build NavMesh from Boxes (override by grid enabled), Custom Shapes (override by grid enabled with a prefab) of use Sprite Mesh (override by grid disabled). It can improve perfomence if your navmesh is strict to grid. But to be honest, it just there because it was implemented.

@h8man
Copy link
Owner

h8man commented Jan 31, 2020

Added new paragraph ## USED GEOMETRY. It should explain how to bake PhysicsColliders instead of sprite's Meshes

@h8man h8man added the help wanted Extra attention is needed label Sep 5, 2020
@h8man h8man closed this as completed Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants