- Mon Sep 21, 2009 1:14 am
#307863
I find the Cooperative user interace very un-intuitive, and tricky.
I have esplained this regarding certain uses, but this is a complete conclusion.
1) Benchmark. This is a very important information considering the relative slow speed of Maxxwell Render. When performing a single rendering Maxwell Render have no difficulty calculating the Benchmark, and after some time it gets stabilized, guiving a more accurte reading. There is no reason for the lack of this data when performing a Cooperative Rendering.
It is easily calculable by hand, although it is a mess for the user. If the Next Limit programers could add it in the Cooperative User Interface it would be more usefull.
2) Estimated rendering time. When Cooperative rendering is running, the user interface shows WRONG readings of estimated rendering time. This is obviously a Bug. Or perhaps a mistake of the programmers. We have developed the graphic Maxwell Calculator, several years ago, to estimate the CORRECT rendering time. The MCalculator, was released a few month later, and both methods estimates the rendering time in single mode as well as in cooperative mode with accuracy. There is no reason to show totally wrong estimated rendering times for each machine, which disorient the user. Perhaps the people of NEXT LIMIT do not understand the importance of predictability in our daily work. Perhaps they do not knoe the equations to calculate the right rendering time, if so please contact me that I can help you. Finnally it is really tricky to show the data provided by the user interface that is totaally useless, or worse it can be diissorienting.
3)It seems that the current (1.7) UI is a work in progress since there are a lot of empty boxes, and what is worse there are lot of OBSOLETE commands buttons and boxes that again do NOT HELP, and what is WORSE can disorient the user.
4) Redundant options are a trap for Users. It is not logical that you have two diferent OPEN mxs file deppending on the rendering mode (cooperative and single) the logical option would be to have a SINGLE OPEN button, and inside it add two options. The current way is fooling the first time users. The manual do not warn the user about all these tricks and traps, perhaps because the people who wrote the manual were used to the software and didnt explored all the posibilities for a newbee.
5) It is Obvious that someone DESIGNED the UI, because it is quite fancy. But it is only astetic!
The real good design must be fully functional. In order to design a Functional UI, you need more than a graphic design professional. You need also someone specuialis is semiotic, and graphic language, as well as psicologist specialist is human intuition. (just in case you want to inprove it)
Sincerely Yours
Ernesto Lacalle
I have esplained this regarding certain uses, but this is a complete conclusion.
1) Benchmark. This is a very important information considering the relative slow speed of Maxxwell Render. When performing a single rendering Maxwell Render have no difficulty calculating the Benchmark, and after some time it gets stabilized, guiving a more accurte reading. There is no reason for the lack of this data when performing a Cooperative Rendering.
It is easily calculable by hand, although it is a mess for the user. If the Next Limit programers could add it in the Cooperative User Interface it would be more usefull.
2) Estimated rendering time. When Cooperative rendering is running, the user interface shows WRONG readings of estimated rendering time. This is obviously a Bug. Or perhaps a mistake of the programmers. We have developed the graphic Maxwell Calculator, several years ago, to estimate the CORRECT rendering time. The MCalculator, was released a few month later, and both methods estimates the rendering time in single mode as well as in cooperative mode with accuracy. There is no reason to show totally wrong estimated rendering times for each machine, which disorient the user. Perhaps the people of NEXT LIMIT do not understand the importance of predictability in our daily work. Perhaps they do not knoe the equations to calculate the right rendering time, if so please contact me that I can help you. Finnally it is really tricky to show the data provided by the user interface that is totaally useless, or worse it can be diissorienting.
3)It seems that the current (1.7) UI is a work in progress since there are a lot of empty boxes, and what is worse there are lot of OBSOLETE commands buttons and boxes that again do NOT HELP, and what is WORSE can disorient the user.
4) Redundant options are a trap for Users. It is not logical that you have two diferent OPEN mxs file deppending on the rendering mode (cooperative and single) the logical option would be to have a SINGLE OPEN button, and inside it add two options. The current way is fooling the first time users. The manual do not warn the user about all these tricks and traps, perhaps because the people who wrote the manual were used to the software and didnt explored all the posibilities for a newbee.
5) It is Obvious that someone DESIGNED the UI, because it is quite fancy. But it is only astetic!
The real good design must be fully functional. In order to design a Functional UI, you need more than a graphic design professional. You need also someone specuialis is semiotic, and graphic language, as well as psicologist specialist is human intuition. (just in case you want to inprove it)
Sincerely Yours
Ernesto Lacalle
Last edited by Ernesto on Tue Sep 22, 2009 3:01 pm, edited 1 time in total.