We’d love to understand what resources would be helpful to you when using Muse Chat!
See one you agree with? Like the comment to vote on it’s relevancy.
I think ingesting Every manual and documentation site for all the tools section on the asset stores would be a good idea.
Adding the Best Practices too, and Theoretical in Unity Learn and Updated sample projects (DOTS & Netcode for Entities).
Updates
On VR/XR
XR interaction toolkit
Editor scripting knowledge attributes and so on.
Troubleshooting. Dealing with errors is very time-consuming, as the workflow is something like this:
- Search for the error message on the Internet.
- Recopilate all the possible solutions.
- Order them from the most promising to the least.
- Try them one by one.
It would be great if Muse would give us a list of possible solutions, ordered by the most successful ones according to the data gathered from manuals, forums with solutions, etc.
anything relevant on Github especially if there is sufficient documentation
Good documentation and examples for all the little checkbox and settings that you can enable/disable for better perfomance / optimazation.
Forum posts from Unity staff and whatever they were replying to
It would be great if you can add knowledge from important SDKs like Meta’s OVR Oculus integration. It would greatly improve iteration of basic development like interactables and interactors and the many associated parts that have to be plugged in while working with these SDKs
Many of the DOTS packages have lacking or unfinished documentation so they need to be rewritten for the purpose of being understood by Muse. When that is done then all the DOTS package documentation should be included in the knowledge base.
The next step after that would be to churn out example code for how to implement certain features in DOTS as well as Unit Test examples. The cheat-sheet is a good starting point but I’m thinking a massive amount of example code so that the AI truly understand how to write DOTS code.
When we have a good example code base and unit tests for each example then we can truly start to automate code generation, and iteration, using a future Muse API.
@martina_johannesson do we have a list to know what doc sections have been currently tailored for muse use and what might be previous training data? might help us give some better recommendations too.
Design patterns! And maybe SOLID but not in basic responses.
Muse should be able to suggest improvements but on cases where the user is asking for a cheat sheet, an explanation or a simple example muse should return the most basic use case.
Another awesome addition would be asset management, where the AI could suggest how assets could be orginized.
And some basic things that would be awesome if implemented:
-
basic knowladge of blender and maya, maybe 3D modeling techniques and general 3D software
-
design suggestions, especially for ui/ux
-
shader programming is already awesome, maybe allowing urp and hdrp higher level shaders would be cool
-
general knowledge of the assets in the asset store and package manager
Hi @HIBIKI_entertainment, You can see what resources we have already ingested in the FAQ! Thank you for continuing to suggest resources we should add to our knowledge base 
compute shaders specifically. I find some of the toughest jobs I have are converting existing shaders into compute shaders. How to optimize scripts with DOTS would be a great resource for it to have in more detail or to even suggest. Often I’m looking for optimization suggestions on a complete script.
It would be great if Muse could learn to send screenshots (or drafts) with nodes for Shader Graph or Visual Efefct Graoh
I know that my proposal will raise some issue (copyrights) but wouldn’t it be interesting to feed Muse with Unity projects created by external game developpers? I also thinking about all the content that is proposed on Youtube : the watch & learn materials, best practices… What about Github (among other), some projects are freely accessible, they could be a good base also. Of course, the feed should be authorized by their authors!!
Make deals with popular assets on the asset store because they often struggle with keeping up with documentation and support. Offering some kind of deal to add their codebases to Muse would be super helpful when working with these tools and make them more effective.