its not an engine feature, more of an organizational request
versioning....
is there a way to have Octane follow a normal versioning system?
for example,
1.0.0.0 would be version 1, THE major release.
1.0.2.46 would be the current beta version we have
just say you add another new feature like moblur, but it still follows under 1.xx, but it's more than a bugfix or utility build, then you could have
1.1.x.x, etc and so on... nice part of this is, you could end up with, in our current build's case:
1.0.2.945678 for a build if you like.. The point is, its always a number, and always up. You can add the beta to it if you like, but i'd assume unless its a full x or a x.x point release build that it IS beta.
anyways, just a request, makes for keeping archived builds organized locally easier to
cheers!
Im finding it difficult to quickly see if there's a new version of octane out because of the "1.0 beta 2.45 pre" and "1.0b beta 2.XX" style versioning that's going on atm.. When I increment a file version, there's never any text in the name at all.. if it's a new build, its a new version number, period
