Houdini Indie

Houdini Indie

kizzer Dec 19, 2018 @ 4:45pm
Access to Previous Updates/Versions
Hi,

Just wondering if it is possible to access previous versions of Houdini via Steam?

For example the V-Ray Beta for Houdini currently only works on version 17.0.352 so I would need to have that version installed to use it.

I have read that you can access the latest version of 16.5 but couldn't find an answer as to whether you can access any version like you can through SideFX licensing.

Thanks in advance, Kieran.

< >
Showing 1-15 of 16 comments
happywafflemonkey Dec 20, 2018 @ 6:27am 
I'm curious as well. Both Redshift and V-Ray are typically behind in releasing compatible packages for Houdini's latest build. For example we're on 17.0.416 now, but V-Ray beta only supports 17.0.352. I can't find any option to either wait to update, or roll it back.
kizzer Dec 20, 2018 @ 8:56am 
I think it's something that needs to be on the FAQ as many conflicts and issues are caused by not having access to a specific version, another example being GPU drivers.

I'm about to purchase an Indie license but this will determine whether or not I use Steam (my preference) or SiddeFX.

Hope someone can answer this soon, although judging by you not being able to find a way to do it then I assume it is not possible.
DamienSideFX  [developer] Dec 20, 2018 @ 11:52am 
Hi,

Thanks for the feedback.

I've just submitted an update to the available builds, and added a houdini17.0_previous branch, that gives access to the previous houdini production build.

The different branches can be accessed in the betas tabs of the Houdini Indie properties:
daily_17 gives access to the latest Houdini 17.0 build
houdini_17.0 is for the latest production build (currently 17.0.416)
houdini_17.0_previous is for the previous production build (17.0.352)

The default branch uses the latest 17.0 production build.

I think you'll need to restart Steam for the new branch to appear.
kizzer Dec 20, 2018 @ 12:45pm 
Hi Damien,

Thanks for the quick response and solution, I'll be sure to purchase my license via Steam because of this.

Have a good day, Kieran.
happywafflemonkey Dec 20, 2018 @ 12:51pm 
Perfect! Thanks for the quick response.
kizzer Dec 20, 2018 @ 2:43pm 
In relation to my original question, I have been trying to get the V-Ray beta to work with Indie on Steam.

However, while I can get it to launch by editing the file paths in the supplied 'batch file', the V-Ray features (toolbar, materials, render node etc) are not present.

Any ideas?

Below is the unedited batch file.

Thanks again.

:: V-Ray For Houdini Windows Launcher
::
@echo off

setlocal

:: Houdini install location
set VFH_HFS=C:/Program Files/Side Effects Software/Houdini 17.0.352

:: DO NOT EDIT STUFF BELOW (well, only if you really know what you're doing)
::
:: This script location.
set LAUNCHER_LOCATION=%~dp0

:: V-Ray for Houdini Begin
::
set VFH_ROOT=%LAUNCHER_LOCATION%

set VRAY_APPSDK=%VFH_ROOT%/appsdk
set VRAY_OSL_PATH=%VRAY_APPSDK%/bin
set VRAY_UI_DS_PATH=%VFH_ROOT%/ui
set VFH_HOME=%VFH_ROOT%/vfh_home
set VRAY_FOR_HOUDINI_AURA_LOADERS=%VFH_HOME%/libs
set VFH_PATH=%VRAY_APPSDK%/bin;%VFH_HOME%/bin;%VRAY_FOR_HOUDINI_AURA_LOADERS%

set PATH=%VFH_PATH%;%PATH%
set HOUDINI_PATH=%VFH_HOME%;%HOUDINI_PATH%;^&

set HOUDINI13_VOLUME_COMPATIBILITY=1
set HDF5_DISABLE_VERSION_CHECK=1
::
:: V-Ray for Houdini End

where /Q dbgcore.dll
IF ERRORLEVEL 1 set PATH=%VRAY_APPSDK%/bin/compat;%PATH%

set QT_QPA_PLATFORM_PLUGIN_PATH=%VFH_HFS%/bin/Qt_plugins/platforms

:: Start Houdini
::
start "V-Ray For Houdini" /D "%USERPROFILE%\Desktop" "%VFH_HFS%\bin\houdini.exe" %*
happywafflemonkey Dec 20, 2018 @ 3:15pm 
You need to change the bat file "Houdini install location: to the Steam exe location which is different from a default sidefx license install. My path is:

set VFH_HFS=C:\Program Files (x86)\Steam\steamapps\common\Houdini Indie
kizzer Dec 20, 2018 @ 3:21pm 
I changed that line to
- set VFH_HFS=C:\Program Files (x86)\Steam\steamapps\common\Houdini Indie

and the bottom line to
- start "V-Ray For Houdini" /D "%USERPROFILE%\Desktop" "%VFH_HFS%\bin\hindie.steam" %*

This results in Houdini launching via the Batch File but with no V-Ray shelf or materials, render node etc.
happywafflemonkey Dec 20, 2018 @ 3:30pm 
Did you append the your houdini.env file with the example snippet from the vray installation folder? Be sure to change the VFH_ROOT="</Path/To/Unpacked/Archive>" to match your location.
kizzer Dec 20, 2018 @ 3:37pm 
I haven't touched the .env file.

I'm probably being a dummy as I don't have much experience but I had it working outside of Steam.

Can you just confirm where the 'VFH_ROOT' is please?

Thanks for your help.
kizzer Dec 20, 2018 @ 3:57pm 
found it and set it to VFH_ROOT=D:\Houdini\vray_adv_41101_houdini17.0.352

Still doesn't work so I assume I have done this incorrectly?

Not sure what location I actually need to put there, have tried various.
kizzer Dec 20, 2018 @ 4:24pm 
If all else fails, I'll have to request a refund and purchase via SideFX licensing instead.
happywafflemonkey Dec 21, 2018 @ 6:18am 
Sorry you're having a hard time with this. Keep at it and I'm sure you'll get it. To get things up and running I only had to;

1.) edit two lines of the .bat file which were:

<LINE 8> set VFH_HFS=C:\Program Files (x86)\Steam\steamapps\common\Houdini Indie
.
.
.
<LINE 41> start "V-Ray For Houdini" /D "%USERPROFILE%\Desktop" "%VFH_HFS%\bin\hindie.steam.exe" %*

2.) append the .env file with the sample snippet and change the VFH_ROOT to the location where I put the "vray_adv_41101_houdini17.0.352" folder.
kizzer Dec 21, 2018 @ 7:03am 
Thanks for all the help, very much appreciated!

However, I think for the sake of simplicity and so I don’t have to worry too much about conflicts like these in future allowing me to concentrate on actually learning the software, I’m going to get my license through SideFX instead.

Thanks again and I’ll be sure to stay active on these forums, Kieran :)
kizzer Dec 21, 2018 @ 7:36pm 
Ran into the same issue with SideFX licensing (despite not in the past) so refunding through Steam was unfortunately all in vain...

All working now thanks to your help though.

I appologise for my lack of knowledge and taking your time, at least I learnt a lot from messing up haha.

Thanks once more, Kieran.
< >
Showing 1-15 of 16 comments
Per page: 1530 50