Hi @timtryz,
I appreciate you updating the documentation and setting up a dedicated forum. The unity boards are nice and an OKish first step, but having all the questions and answers in one long thread makes it hard to find the information one is looking for.
I am not sure which in direction you want to take this forum, but having a place where users can show off their current projects which utilize the ootii suite would be cool. Maybe even adding an entire sub-forum for that reason 😉
Anyway, I hope this site will thrive and this forum will get more usage!
Hey @tzirrit, ask and ye shall receive!
https://ootii.com/forum/forum-showcase/
I can't say I have a well laid out plan for the knowledge-base and forums, but I do want to help the community more. Any suggestions are super appreciated. 😀
@timtryz Cool, thanks!
Not that my own project is in any state yet to show off, but I would really like to see what others are doing. And I also think this might help get more attention for the MC, motion packs and co.
Moving from static PDF documentation to a more flexible and maintainable knowledge base is a great idea (which of course takes its time). In the meantime, I would still keep the old PDFs alive, in case people (like me) are searching for them.
The original links no longer worked, but I assumed, you moved them to the same place as the vault, and voila - it works, e.g.: https://ootii-home.azureedge.net/Unity/MotionControllerPacks/SwordShield/SwordShieldUsersGuide.pdf Maybe you want to put that link in the knowledge base, as well?
Another suggestion is a aroadmap for each of the assets, or a list of planned features and things you currently are working on.
Not to put you under pressure, just because it is interesting to know what is planned and what might be coming in the future. "When it's done (tm)" is a totally acceptable timeline.
Maybe even a thread, where users can suggest new features or changes? Which then could be voted on, or just curated and approved/rejected by yourself.
The original links no longer worked
I thought I caught all the links. Can you share where you saw the bad ones at? I'll double check what I remember... I just may have missed some.
Another suggestion is a roadmap for each of the assets, or a list of planned features and things you currently are working on.
So, this one I'm less excited about.
I did this a long time ago and then when life slowed me down, I got some mean emails: "I only bought the MC because you promised feature X."
While I do talk about some of the things I'm doing, I don't want to set wrong expectations. I figure people should buy based on what exists and no undelivered promises are left lingering. 🙂
The original links no longer worked
I thought I caught all the links. Can you share where you saw the bad ones at? I'll double check what I remember... I just may have missed some.
The ReadMe files in each of the assets (ootii XX_ReadMe) still point the the PDFs, but that is the only place I've found.
Another suggestion is a roadmap for each of the assets, or a list of planned features and things you currently are working on.
So, this one I'm less excited about.
I did this a long time ago and then when life slowed me down, I got some mean emails: "I only bought the MC because you promised feature X."
While I do talk about some of the things I'm doing, I don't want to set wrong expectations. I figure people should buy based on what exists and no undelivered promises are left lingering. 🙂
OK, fair point. People can get really demanding, especially when their wrongly set expectations are not met.
I was more interested to get an outlook of things to come, so I do not start building/changing parts on my own that get reworked anyways. But I understand where you are coming from. especially when working solo or in a very small team.
PS: Even I am guilty of this; I got excited when I saw your old videos where you talked about the ripper AI, and then was quite disappointed when I found out that sensors and memory never made it into the MC.
The ReadMe files in each of the assets (ootii XX_ReadMe) still point the the PDFs, but that is the only place I've found.
Ah... thanks for that.
PS: Even I am guilty of this; I got excited when I saw your old videos where you talked about the ripper AI, and then was quite disappointed when I found out that sensors and memory never made it into the MC.
I haven't given up on it. In fact, it's one of the reasons I cleaned up the Graphics Manager stuff the other week. 😉