--- title: "Tutorial Guide" canonical: "https://documentation.chaos.com/space/DOCSGUIDE/113289552/Tutorial%20Guide" format: markdown --- > Macro (floatingpagetoc) ## **Workflow for V-Ray HOW To tutorials** --- ![image](media://f61802c1-0eee-4d9f-b11e-2341a7f4f9f5) **Prepare: ** 1. First step is to do an action plan and prepare a suitable scene. A QA can help with finding the proper scene and writing down an action plan. 2. Log a JIRA issue with the action plan and the scene. The action plan can be exposed as a page in the docs. The important thing is to have all the requisites of the tutorial - steps, parameters, etc ready and shown, including the final beauty render. **Verify:** 3. When ready, two different QAs from two different teams (Max and Maya) should review it. This step is to settle on the correct workflow and prevent from future iterations on the content. All content edits should be done in this step and only if two QAs have verified it, you can move on with the next step.  The final beauty render is the goal of the tutorial, so make sure that you have this agreed on. Alex Yolov can review the beauty render and approve the artistic side of the tutorial. > Macro (ui-text-box) > > Make sure to tag the people in the comments so they know it's their turn to review and what to review. **The page: ** 4. Work on the page and require the platform QA to approve it. (The action plan can actually be the page itself, if so just polish the layout and the language) **Video:** > Macro (ui-text-box) > > Submitting a request to upload a video to YouTube is done through Jira. Tag Jake Denham in your "Create Video" Jira task, and he will handle the upload. It's crucial to inform Jake at least one month in advance if a video task is in progress so he can schedule the upload accordingly. This is especially important for videos that will be publicly listed. > > ~~Submitting requests to upload a video to YouTube happens through the Monday platform. You need to submit a form, which can be any one of these three:~~ > ~~[https://chaos.monday.com/boards/1296126158/views/7713365](https://chaos.monday.com/boards/1296126158/views/7713365)~~~~ – Video Production form, includes fields for a thumbnail and AI voiceover if needed. Sent by Shawn.~~ > > ~~[https://forms.monday.com/forms/952193ce81258e2de54a4b864b78ba79?r=euc1](https://forms.monday.com/forms/952193ce81258e2de54a4b864b78ba79?r=euc1)~~~~ – Social Media Posting Request. Includes field for urgency. Sent by the Marketing team~~ > > ~~[https://forms.monday.com/forms/c0eddd58534e0766f7c24d77c1bff0a3?r=euc1](https://forms.monday.com/forms/c0eddd58534e0766f7c24d77c1bff0a3?r=euc1)~~~~ – Website and Campaign Ops team request. This is mainly useful for analytics etc.~~ > > ~~It is also worth noting that any request submitted to the marketing team can be re-distributed within their team. Sometimes, even sending an email works.~~ 5. The video and the script can be logged in two different JIRA issues. The script issue should be "dependant on" the video issue and the video issue is basically dependant on the page issue.  The video should not show Windows task bar and the white header of Max/Maya. Record in FullHD resolution. The video content should follow the steps and parameters values from the page, if not specified otherwise.  > Macro (ui-text-box) > > Don't forget to create all issues from the EPIC HOW TO tutorials issue. 6. Alex Yolov approves the video artistically, as he knows good user practices and approaches within the platform.  7. Once the video draft is verified - log in a separate JIRA issue for record of the voiceover. At least one QA and a member of the DOCs team should approve the script.  8. Log a separate JIRA issue for voiceover recording to Kristin Ivanova (or whoever records). Print the script. 9. The voiceover is recorded in at least two different audio file options (.wav). The audios are edited with proper effects and cutouts. When the recorded voiceover is ready, the creator of the tutorial and Alex Yolov should review and pick an option. 10. Log in a new JIRA issue for a final edit of the tutorial in Premiere (final adjustments of timings to the video are made along with the recorded voiceover). At this step, it is a good idea for few people to verify the video - the platform QA, a member of the Docs team, Alex Yolov. Tag their names in the comments.  11. Marketing team can upload the videos to Youtube.  12. Once you have the link, add it to the page.  13. Make an info tile for the Tutorials page (this can be done at any point of the workflow) with a link to the page.  14. Add a link at the end to at least one other tutorial video (Recommended: XXX how to tutorial) 15. First batch of videos can be release together, but after that every following can be published on its own.  ### Additional Notes --- - Always use the latest official release when recording a video!!! - Prepared scenes should be packed as .zip and uploaded in the Shared Drive for future reference. - Don't forget to create and add a tile image to the main Tutorials page. - It is a good idea to have a link on a related or close topic at the end of the tutorial page. For example, you are working on glass tutorial, put a link to the water tutorial, plastic tutorial, etc - whichever seems relevant and can be linked. - Videos can be then forwarded to the Marketing team. ## **VMAYA Backlog Tutorials** --- 1. First contact Alex Yolov. He will review the old JIRA issue and make a brand new action plan. He will also provide you with some guidance on what kind of scene is needed for the tutorial. In addition, in this step you should both clarify who will be the MAYA QA who will assist further. 2. Review old scenes that would fit the tutorial. You can also check 3ds Max scenes. As long as the tutorial is written, you can fake it (show screenshots of UI in Maya, etc. and renders from 3ds Max). The appointed QA will review your suggestions and give comments whether the scene is okay. They can either assist you in optimizing a Maya scene, or narrow down what should be shown in a brand new scene.  2.1 If a brand new scene is the way, you can ask Niki Bulev for assistance (3ds Max). Please make a separate JIRA issue for creating the scene and assign it to him after confirmation that he can actually assist. 3. Once you have a scene and action plan, you are free to go further with compiling the tutorial. ## **3ds Max Hack for loading .aur files** --- .aur files cannot be set in the Asset Tracker, so this means you have to load the file every time you open the scene/transfer the scene to someone else. The "hack" is to set the path in the following format: ``` $(dir)\Assets\Fire_Trail.aur ``` where "Assets" is the name of the asset folder and "Fire_Trail.aur" is the .aur file name.