From ca7f75ec6f2123208b80bdefe10a332da6a63a46 Mon Sep 17 00:00:00 2001 From: Ondrej Samohel Date: Mon, 10 Jul 2023 19:02:27 +0200 Subject: [PATCH] :memo: fix docs --- website/docs/artist_hosts_houdini.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/artist_hosts_houdini.md b/website/docs/artist_hosts_houdini.md index 8a9d2e1f93..940d5ac351 100644 --- a/website/docs/artist_hosts_houdini.md +++ b/website/docs/artist_hosts_houdini.md @@ -139,7 +139,7 @@ There is a simple support for publishing and loading **BGEO** files in all suppo ### Creating BGEO instances -Just select your SOP node to be exported as BGEO. If your selection is object level, OpenPype will try to find there is `output` node inside, the one with the lowest index will be used: +Select your SOP node to be exported as BGEO. If your selection is in the object level, OpenPype will try to find if there is an `output` node inside, the one with the lowest index will be used: ![BGEO output node](assets/houdini_bgeo_output_node.png) @@ -147,8 +147,7 @@ Then you can open Publisher, in Create you select **BGEO PointCache**: ![BGEO Publisher](assets/houdini_bgeo-publisher.png) -You can select compression type and if the current selection should be connected to ROPs SOP path parameter. Publishing -will produce sequence of files based on your timeline settings. +You can select compression type and if the current selection should be connected to ROPs SOP path parameter. Publishing will produce sequence of files based on your timeline settings. ### Loading BGEO