Nightly build naming

[GoodbyeKansas]

Would be great if you could rename the nightly builds a little.

Currently they are named as for example:

vray_adv_41203_houdini17.5.293_383fae7_4915_window s.zip

It would be great if we could remove the "4915" part as it appears to be random/unique for each package. Makes it harder to script the unpackage and environment setup.

-- Erik

[chakarov]

This is not a random number, it's a build number and it is more easy to track the issues by build number, instead of the hash "383fae7". Every time VFH is build this number is increased by 1.

[GoodbyeKansas]

I see. Guess I'll have to add some directory name wrangling.

-- Erik

[Aleksej Skrypnik]

It would be helpful if this number would also appear in the console entry at start-up. Currently it shows only the hash.
Like: VFH [Info] * Build 724e01b from 26 Aug 2019 04:17

Is there also any way to figure out the Build Number in a already running Houdini? Something like an "About V-Ray" button?

[bdancer]

You could use Python:

>>> import _vfh_ipr
>>> _vfh_ipr.getVfhHash()
'f62c84b2'
>>> _vfh_ipr.getVRayVersion()
(4, 12, 3)
>>> _vfh_ipr.getVRayHash()
'fddb2d28'

[Aleksej Skrypnik]

Is there a documentation of the commands?

I'd like to get the build as number.

vray_adv_41203_houdini17.5.293_383fae7_4915_windows.zip

The 4915 in this case.

[bdancer]

There is no documentation for that now and I haven't added build number access api yet.
You could use Python's dir():

>>> import _vfh_ipr
>>> dir(_vfh_ipr)
['__doc__', '__file__', '__name__', '__package__', 'deleteOpNode', 'exportOpNode', 'expo
rtView', 'getMaterials', 'getOpList', 'getVRayHash', 'getVRayVersion', 'getVRayVersionSt
ring', 'getVfhHash', 'init', 'isFatalError', 'isRopGPU', 'isRopValid', 'logClearCollecte
d', 'logGetErrors', 'logGetWarnings', 'logMessage', 'logPrint', 'logSetCollect', 'render
IPR', 'syncScene', 'transferAutoCorrections']

Just note that all those commands (except version methods) are not supposed to be used by the end-users.