jason1025
-
Posts
1,855 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Events
Posts posted by jason1025
-
-
I was surprised that it beat my 8core mac pro tower 3.0GHZ which rendered at 9:58
-
AM 15.H
Mac Book Pro intel core Duo
2.8GHZ
2 cores
4GB 1066 MHZ Ram
9.08 seconds
-
Thank you, great work
-
I agree, this was just a test so far, not the actual animation.
-
so what exactly is this for because it looks cool...and gets me to wishing I hade FCpro
(but I might be getting FC Express this XMas which is cool!)Thanks
I am working on a presentation of all my skills and talents. It will be made entirely in AM ironically showing off skills in Final cut, color, and many other programs.
-
That's a great result. Of course your 8 seconds would be like 20 on mine.
My main beef with kleig lights is it's hard to do daytime outdoor scenes with them.
Another software has z-buffered Sun lights. I have no idea how that can work. How do you map the shadows from a light that is infinitely wide?
But it would be handy.
I wish we could bake lighting onto objects, that would be really handy.
Do you think its worth doing a feature request?
-
okay i found 15.0g.
anyone else have library issues in 15.0h?
yes so I went back to G
-
For clarification
I had made a too aggressive speedup optimization in V15.h . (shame on me ...)
This affects only multicore/hyperthreading systems (except mac's)
Symptom
- App crash
Happens
- when You switch to any shaded mode , with some cp's/ groups selected
- decals applied to the model , and they need to recalculated (importing model , changing decals etc .)
possible workaround
- deselect all, before switching
- set realtime decals to off
I think (fingers crossed) , I have catched this problems now , and hope we can release 15.i before christmas .
That's great news. I for one am appreciative you are continuing to advance the programs efficiency and speed in addition to fixing problems. So keep up the good work. My self included I know a group of us would be glad to beta test new versions and give detailed feed back if your interested. Even if you need us to test theories or tests that you are curious about before moving forward.
-
Those two previous scenes had three "Sun" lights using 25 rays apiece to cast their shadows. If I cut that to 5 rays I get a render time of 3:55...
It's hard to see in this small image size but the shadows are visibly grainier. But obviously the lighting was the major slow down in the first two scenes, rather than reflections or the refraction of the clear teapot. The biggest surprise is that anti-aliasing is also much briefer. I would have thought edges were edges but apparently lighting makes a difference.
If I was OK with razor sharp shadows I could cut the rays to 1 and get a time of 1:09...
This seems to be the sweet spot that most closely represents the original at this resolution.
Thanks for the great work Robert. I think you are collecting enough data to come up with a cheat sheet of options to under crank before a render that may have little visually negative impact on your scene but decreases render time.
In a perfect world I see AM recommending render options and giving tips interactively and intelligently to get the highest gain at the lowest cost in regards to render time.
-
AM I correct that when combining most models, rather than copy past one model into another you would combine them with an action or chor based on your description above?
One usually assembles sets or high patch count models in an action or in the chor when the patch count for a model starts to get too high to comfortably work with in modeling mode. So it depends on your patience level. The slow down in response for adding new splines to a model starts becoming noticeably draggy around 10-15,000 patches.
Yes the slow down happens with copy and paste as well.
Thanks for the info folks.
-
I have found that it is best to assemble sets in an action - with those elements that are static - ie won't eventually be moving in the chor.
For example, if you will be moving the apples in the bowl (someone picks it up - eats it) - then those should be added in the chor - they will be easier to get ahold of and animate.
But the bowl (if doesn't move) could be assembled with the table, chairs, walls, etc in an action as action objects. And then that action is added to the chor.
You could add everything into the chor (without making an action) - but a set assembled in an action can be reused in multiple chors.
Thanks Nancy
one quick question
AM I correct that when combining most models, rather than copy past one model into another you would combine them with an action or chor based on your description above?
-
Im confused
SO if I have table some fruit in a bowl, a person who will be eating fruit from the bowl, all these elements should be combined in an action or a chor or a combination of the two?
-
I am modeling a room but I am adding lots of other elements that will animate and models that have been created independatly. I am getting frustrated because when I add them into the room I loose stuff like bone position.
WHat is the best method to proceed on large scale things with lots of elements and animation?
I am assuming adding everything into one model is the worst procedure.
Do I add everything in an action?
Do I add everything in a chor?
WHat are the advantages and disadvantage?
Thanks
-
Closing all windows/pallets in AM before rendering as well as setting AM as a high priority in the task manager decreased my render time from 10:03-9:58.
Every little bit helps
Any other suggestions
-
15h
8:52
Intel 8400
3 GHz
2 core
8 GB DDR2 RAM
Windows Vista Premium 64 bit
I also closed all AM windows. If this does save so much time, maybe it could be an automatic thing when anything is rendered. Not everyone will know that trick.
can you make a feature request?
Not for me...I multitask while A:M is rendering. I don't care if it slows me down...I'm rendering right now as I surf the forum.
I think hes referring to closing all the pallet windows in AM before rendering.
-
15h
8:52
Intel 8400
3 GHz
2 core
8 GB DDR2 RAM
Windows Vista Premium 64 bit
I also closed all AM windows. If this does save so much time, maybe it could be an automatic thing when anything is rendered. Not everyone will know that trick.
can you make a feature request?
-
Robert
I am really happy you did this. This data has helped me out in making a decision for my small render farm. I dont think you need to change a thing. It would be great to keep this topic open so we can continue to see results. In my opinion this is a definitive official benchmark test for a system and AM. It may not be perfect but now that I have seen this data, I can run this test on any computer and some up its performance in regards to Am and other systems. I can also compare new versions of AM against old ones.
I think in the years to come as technology improves and the code gets cleaner we will see this number get into 1 minute or less. To make a less intensive benchmark may not as clearly show the drastic range we have seen in results such as the difference between your results and the i7 3.3GHZ results.
Bottom line
Great job
-
Impressive
-
What was your conclusion based on the data below? It looks to me that AM14c is a screamer when it comes to rendering.
Jason, I was surprised by the difference in these three processors:
Robcat2075:
19:59
AMD Athlon XP 3200
1.921 GHz
1 core
2 GB RAM
Windows 2000
----------------------------------------
Ludo_si:
19:00
AMD ATHLON 64 X2 DUAL
core processor 3800
2.01 GHZ, 2GO RAM
windows xp
---------------------------------------
Paul Forwood:
A:M14c: 11:40
A:M15g: 15:43
A:M15h: 15:11
AMD ATHLON 64 X2 DUAL (4200+)
(utilising one core)
1.79 GHz
3 GB RAM
XP Pro
---------------------------------------
I didn't think there would be so much difference between Ludo_si's machine and mine, in particular. That's all.
Almost time to look for a new machine but I can hang on for a little longer. I still get alot of use out of my old P4. smile.gif
By the way, I'm no genius.
-
Thanks Matt
It cost me 1200.00 dollars for my fish eye lens on my Sony EX1. Your lens is very valuable to me. Thanks for the clear instructions on how you use it.
-
version of A:M 15H
render time 6:38
CPU Brand and model Intel I7 975
Actual CPU speed in 3.33 GHz
how many cores A:M is using 1
RAM 3GB
OS. Windows 7
WOW and the winner is the i7 975. That is so fast. Can you run 4 instances at the same time and six instances at the same time after that. I am curious how well it keeps that record time when rendering multiple instances.
Am I correct that that is a 4 core system? How many cores come up in the task manager? does hyper threading create suit o extra cores?
-
-
27:42
AM 13l
Intel Core 2 Duo 2.44ghz
2gb Ram
Mac OSX 10.6
Ill test it on my windows partition tonight for comparison.
Photoman
I am guessing the windows side will be around 9-11 minutes
-
You see, you must set a standard base for bench tests.
-----------------------------------------------------------------
Please don't anyone confuse this example as a benchmark for versions of A:M. There are too many other variables that would have to be added to compare one version of A:M to another. There are many improvements in later versions of A:M that are not reflected in this test. This is simply to show that when collecting data, to compare render times on different machines, you must ensure that everyone is using the same setup, (software version and render settings).
-----------------------------------------------------------------
I forgot to add that these were all rendered on a single core.
Background activity was minimal: I had a QT movie open, (but not playing), and a live browser window onto a text and image website.
I mention this because I am surprised by the results others have shown.
Surprised in what way?
The only thing that surprised me was how poorly the render works on mac, I am convinced the application of AM is running through some sort of translation instead of a truly mac coded app.
Are you surprised that your computer is 2nd to last in the race,
just kidding I know its not a race.
CPU Render Benchmark
in Benchmarks
Posted
Yes its was closed, along with all the other windows, including the model window that defaults to being open. Oddly on the mac pro tower closing all the windows only dropped the time by 6 seconds or so.