chriszolezzi,
Thanks for your efforts to let other know about the performance of ArchiCAD with the worlds fastest desktop.
GS is totally lame for not posting pertinent information regarding this topic.
I hope GS reads this and say to themselves,"Boy I really hate that Burginger guy for the way he puts down GraphiSoft". Ya - right.. like they read our posts.
Thanks for your efforts to let other know about the performance of ArchiCAD with the worlds fastest desktop.
GS is totally lame for not posting pertinent information regarding this topic.
I hope GS reads this and say to themselves,"Boy I really hate that Burginger guy for the way he puts down GraphiSoft". Ya - right.. like they read our posts.
Burginger wrote:
"Boy I really hate that Burginger guy for the way he puts down GraphiSoft".
Actually, we do read your posts, and we have already contacted LightWorks about this. The fact is, not all LightWorks functions are multi-threaded. So some rendering settings can cause LW use one core only. I was hoping that we can give you a detailed answer as to what those functions are, but we are going a second round with LW on that subject.
It is nice to know Big Brother is watching 
On this subject, a very good and useful item might be this:
a) Take a standard ArchiCAD project.
b) Use Quickkeys to create a script that puts the file through several changes, involving layout updates, etc. - A rendering test could be separate. Daily work processes are more important.
c) Capture the screen conducting the test on a "slow" machine. Then capture the same test running on a "Fast" machine.
d) Post the .mov file for everyone to watch. This way we can all see the difference in performance between the current machines and the "Newest Machine - which many of us cannot afford but we are interested in what it can do for us.
Cinema does something like that on their web site. Rendering is a fine test, but the majority of my time is spent modelling and updating, etc. That's where I would like to see the speed improvements most.
Where is all of this taking us?
http://forums.macrumors.com/showthread.php?t=232507
1 core for constant background layout up dates, 4 dedicated to rendering, 1 for web, etc. ?
On this subject, a very good and useful item might be this:
a) Take a standard ArchiCAD project.
b) Use Quickkeys to create a script that puts the file through several changes, involving layout updates, etc. - A rendering test could be separate. Daily work processes are more important.
c) Capture the screen conducting the test on a "slow" machine. Then capture the same test running on a "Fast" machine.
d) Post the .mov file for everyone to watch. This way we can all see the difference in performance between the current machines and the "Newest Machine - which many of us cannot afford but we are interested in what it can do for us.
Cinema does something like that on their web site. Rendering is a fine test, but the majority of my time is spent modelling and updating, etc. That's where I would like to see the speed improvements most.
Where is all of this taking us?
http://forums.macrumors.com/showthread.php?t=232507
1 core for constant background layout up dates, 4 dedicated to rendering, 1 for web, etc. ?
