This would not be a problem if the new builds would be presented in a fashion that clearly states that when downloading this "build" somethings could be broken. That causes a misconception of Andrew's program and might even cause a company to abandon his software. It is downloaded and sometimes what was working is not anymore. Yes it is more work but at least there is no confusion and lost of your customer base.Īgain what happens now is that a stable version(one that can be used for production) is used by a user/company, then a new beta build comes out. I have suggested to Andrew, fix any problems in the official version and run a separate program for the new builds. That would lead a company or person to becoming very frustrated.
FIND MY FONT 3.3.07 SERIAL DOWNLOAD
You download the new build, great the bug is fixed but now something say in the retopo room is broken in the new build. You report a bug, It is fixed but in a "new build" and not the official downloaded version. The problem is now that any bug in the "version" from the main website is fixed in a new beta build. It is confusing to new users when we have several versions floating around that are not clearly defined.Īlso what happens is that the version downloaded from the main website is lagging behind the beta builds. At the present the bug reports for the betas get thrown into the versions jungle or sent directly to Andrew.
I would like to see a new section in the forum that is just for the new builds.
These discussions bring me back to my conclusion that the new builds need to be clearly denoted as "beta builds" Sometimes they are ,sometimes not and heck sometimes I don't even know.
0 kommentar(er)
