I've been on the main/official release, for many years.
Significant releases, are increasingly far & few between.
Which is expected/understandable, but...
(1)
Are things more 'lively' with build releases on this branch?
(2)
Perhaps there's Sw used with* Everything, that's seeing more activity?
Lastly, If you're aware of anything you can point to;
(3)
Are there any exciting 'forks' (or similar Sw) out there?
sauljhl wrote: Thu Aug 22, 2024 4:17 am
I've been on the main/official release, for many years.
Significant releases, are increasingly far & few between.
Which is expected/understandable, but...
(1)
Are things more 'lively' with build releases on this branch?
(2)
Perhaps there's Sw used with* Everything, that's seeing more activity?
Lastly, If you're aware of anything you can point to;
(3)
Are there any exciting 'forks' (or similar Sw) out there?
Thank you very much!
*modules et al
Is this asking if there is good reason to move to 1.5?
Because I held off thinking it wasn't worth it to go beta, but it's really just a name. It can mean a higher risk of issues, but I haven't found any major ones and minor ones he fixes a bit here and there as you report them.
If you like this software, 1.5 is just more of it and is worth testing out at least.
Of course, when I say major I don't necessarily mean crashes. There was one for "Color Representation" property, but I just disabled it. I suppose it's a major issue if you are using that property in a workflow. Just a personal issue, there are other causes for crashing but I don't know the other ones.
Aside from the official/built-in documentation;
Do you know of any top resources for making the learning curve toward fully/properly utilizing 1.5x, a bit flatter?
e.g. YT channels/tutorials etc I'll check out that alternative.to link.
Herkules97 wrote: Thu Aug 22, 2024 9:58 amBecause I held off thinking it wasn't worth it to go beta, but it's really just a name. It can mean a higher risk of issues, but I haven't found any major ones and minor ones he fixes a bit here and there as you report them.
If you like this software, 1.5 is just more of it and is worth testing out at least.
Thanks for your insights! So far, I too haven't had (or hit/observed) any "major" issues on x.1383a.
I've been occasionally running the stable build alongside, can that be problematic, must it be 1 or the other?
Maybe I'm offtopic here, and though I regognise that version number is just a number, naming it version 1.5 doesn't give justice to all the features added since the first 1.5a. Version 2, IMHO, would be much more fitting.
Herkules97 wrote: Thu Aug 22, 2024 9:58 amBecause I held off thinking it wasn't worth it to go beta, but it's really just a name. It can mean a higher risk of issues, but I haven't found any major ones and minor ones he fixes a bit here and there as you report them.
If you like this software, 1.5 is just more of it and is worth testing out at least.
Thanks for your insights! So far, I too haven't had (or hit/observed) any "major" issues on x.1383a.
I've been occasionally running the stable build alongside, can that be problematic, must it be 1 or the other?
You can name instances using shortcuts, so you can run multiple 1383a if you want.
I run 11 instances at all times at home with varying builds since 1366a because I am bad at updating software.
So after the target or whatever the field is called, it can end with " -instance 1383a-1.
