Purpose: deployment the nextpcg server in your computer.

Step1: Prepare the workspace

First, we recommended to use Fork as the management tool for Git.

• Click here to download the tool
• If you are not familiar with Git operations, please use git command line.
• Using other Git desktop tools may cause various problems.

Second, the NextPCG server is modular, here are the optional modules

• Houdini Module
  • support the NextPCG server services by Houdini-based algorithms and tools.
  • support you can create your own Houdini files to extend the NextPCG Houdini tools.
• Python Module
  • support the NextPCG server services by Python-based algorithms and tools.
  • support you can create your own Python project to extend the NextPCG Python tools.
• NextPCG Task
  • support the NextPCG server services by Unreal-based algorithms, tools and pipeline.
  • support you can create your own task blueprint to extend the NextPCG Task pipeline.

Third, all modules you can choose to install or not.

• If you don't install the Houdini module, you can create an empty folder as a workspace, this is useful if you only want to use AIGC's features!
• If you install the Houdini module, we've got a workspace ready for you!

  • 【Click here to go to the houdini workspace repository】

  • If the page cannot be opened, Gitlab permissions are required. Please contact cheneyshen.

  • Explore the NextPCG_Houdini repository file structure.

    

    • HoudiniProjects: Stores the Houdini projects. The Houdini project files made by TA are placed here.
      • NextPCG：The official Houdini project, which contains the NextPCG workflow nodes we created, as well as Houdini's functional expansion nodes.
      • NextPCG_Ark：The project Houdini project demo, which contains the examples of Houdini nodes for project-specific made.
      • NextPCG_XXX：For some of the specific requests you have made, we will create additional repositories that only you project will have access to.【Ignore in this process】
        • see the notes for details
    • HoudiniClient: Stores the UE Demo project.
      • We have associated the demos submodule you can get.
      • Your UE project doesn't need to store here.
    • PythonProjects: Stores the python projects. 【Useless in this process】
    • CityEngineWorkspace: Stores the CityEngine-related content. 【Useless currently】
    • SubstanceWorkspace: Stores the Substance-related content. 【Useless currently】
    • Submodules: No need to pull 【Useless in this process】

    <aside> 💡 Warning

    • When creating programmatic tools in Houdini projects, pay attention to the folder conventions:
      • hip: Stores .hip project files
      • hda: Stores the final HDA file, which is used to associate with UE and associated with a .pson file of the same name.
      • otls: Stores custom tool nodes used in the hip file. </aside>

    <aside> 💡 Notes

    Submodule a Project-Specific Repository

    • Explanation
      • For some of the specific requests you have made, we will create additional repositories that only you project will have access to.
      • The HDA files stored in this project-specific repository can be used to provide cloud generation services for your project based on our cloud server.
    • Steps
      • Obtain the project-specific repository address.
        • Contact cheneyshen if you are not sure.
      • Mount the project repository as a submodule to the specified location under the nextpcg_houdini repository.
        • Location: Under HoudiniProjects, at the same level as NextPCG.
        • Mounting operation in Fork:

          • Right-click on Submodules and select "Add New Submodule."

            

          • In the pop-up dialog box,

            • the URL is the address of the project-specific repository,

            • and when filling in the "Folder," pay attention to the following method to ensure that it is set correctly to the specified location as shown in the picture below.

              

          • the result after mounting:

            

    </aside>