I am curious as to what the update schedule and possibly feature list looks like. Currently, its almost impossible to test, as the viewport navigation is completely off. Trying to navigate in the viewport is a nightmare.
It would be able to get some guidance on when at least some of the fundamental features are going to be fixed/implemented (such as render settings as well)
viewport navigation not working
heimlich wrote:I am curious as to what the update schedule and possibly feature list looks like. Currently, its almost impossible to test, as the viewport navigation is completely off. Trying to navigate in the viewport is a nightmare.
It would be able to get some guidance on when at least some of the fundamental features are going to be fixed/implemented (such as render settings as well)
Hi Heimlich,
Thank you so much for the post.
As you know this is our 2nd Beta and the updates/feature are available on every release post.
Would you please share your system configs and the GPU also maybe a video with the viewport `Draw time` info?
Please try to increase the `SubSampling` from the RenderSettings node to see if it helps.
cheers
Kind Regards
bk3d
bk3d
sure thing. here's a quick vid...
System currently has two 2080TI's (non nvlink) and is an intel 5960x, nvidia display drivers 456.38
System currently has two 2080TI's (non nvlink) and is an intel 5960x, nvidia display drivers 456.38
- Attachments
-
- viewportnav.mp4
- (3.98 MiB) Downloaded 3057 times
Hi Heimlich,heimlich wrote:sure thing. here's a quick vid...
System currently has two 2080TI's (non nvlink) and is an intel 5960x, nvidia display drivers 456.38
Thank you so much for the video.
The viewport navigation works okay when we test, not sure if anyone is having the same issue.
We used 2x2070 super with the latest Nvidia studio driver 456.71.
Would you please try to reinstall the plugin from the 2nd beta post [https://render.otoy.com/forum/viewtopic.php?f=141&t=75948]?
cheers
Kind Regards
bk3d
bk3d
hi BK,
I think the reason why it works on your end, and not on mine, is because of the existance of other renderers. I see in your video, that you have the octane Tab in render settings (which is missing on my end). I'll try to disable some of the other renderers to see if I can figure out why they cant co-exist.
I think the reason why it works on your end, and not on mine, is because of the existance of other renderers. I see in your video, that you have the octane Tab in render settings (which is missing on my end). I'll try to disable some of the other renderers to see if I can figure out why they cant co-exist.
Hi Heimlich,heimlich wrote:hi BK,
I think the reason why it works on your end, and not on mine, is because of the existance of other renderers. I see in your video, that you have the octane Tab in render settings (which is missing on my end). I'll try to disable some of the other renderers to see if I can figure out why they cant co-exist.
Thank you! Sure, please let us know if how it goes. Also, just to confirm if you have installed the plugin manually copying or using the .env path?
Cheers
Kind Regards
bk3d
bk3d
I made a json package that i run alongside the regular houdini package. I really dislike stuffing up the .env file.
Code: Select all
{
"enable" : "houdini_version >= '18.5.351'",
"env":
[
{
"HOUDINI_PATH" :
{
"value": "$HOUDINI_PACKAGE_PATH/../_PLUGINS/Octane_2020.1.5.3_Houdini_18.5.351_Win64",
},
"PATH" :
{
"value": "$HOUDINI_PACKAGE_PATH/../_PLUGINS/Octane_2020.1.5.3_Houdini_18.5.351_Win64/bin",
},
"PXR_PLUGINPATH_NAME" :
{
"value": "$HOUDINI_PACKAGE_PATH/../_PLUGINS/OctaneHydraSolarisEnterprise_2020.1.5.0_Houdini_18.5.351_Win64/dso/usd_plugins",
},
}
]
}