Hi all
This is a reworking of a very early v0.9 TG render. I have been waiting for the transparency to give this a go in TG2. This is definately a WIP, a lot more to do in this. I LOVE the new transparency and I wanted to see how it would work where the water is too deep realy to see the bottom properly.
The only post work is exposure in Photoshop from saving it as an EXR.
Let me know what you think
Miles
nice ;D
im rendering a tranperant picture at the moment :)
nice job...now for some fish!
Nice, the only thing that bothers me is that the water doesn't seem in scale with the mountains. Can't wait for public transparency.
Inky... Ta. *Thinks.... fish... hmmmmm, now theres an Idea*
Will They're not meant to be mountains, cliffs would be more like it. I have always thought that the right hand side rock slope would be about 3 - 4m from the water to the top? Mind you, I suppose that that is all down to the viewers perception. I intend to add some vegetation etc to the scene. Hopefully that will bring the scale more in line with what I "see"
Miles
Ah I see, I though your veggies to the left were meant to be trees, that threw me off I guess. I like the fish idea.
Will
I see where you were coming from now :D The veggies are meant to be grass (something else I am going to have to do work on) though I think its a bit dense / overpopulated at the moment and I think the scale is a bit out too.
Miles
It's fun and an accomplishment, since getting a completed render from the new Alpha has been somewhat of a challenge for me. Looks nice.
Calico, reduce maximum threads to 2 so that it uses less memory and it should work better. I know you have 4 cores but maybe you could consider 2 threads a compromise until we improve things?
Matt
That's what I'm doing. I presently use 2 minimum and 6 maximum. I'm also finding other ways to seek success by reading about other issues. One issue I was having was mapped images that weren't present. I didn't get an error that they were missing, but the render failed with the out of memory issue. Another issue was simply mapped images (not sure about this one, but I'm experimenting). Yet another issue was extreme negative displacement. I'm cutting back on stuff like that to see what I can do.
Thanks Matt.
Quote from: Matt on May 01, 2008, 10:19:28 AM
Calico, reduce maximum threads to 2 so that it uses less memory and it should work better. I know you have 4 cores but maybe you could consider 2 threads a compromise until we improve things?
Matt
Quote from: calico on May 01, 2008, 10:48:24 AM
That's what I'm doing. I presently use 2 minimum and 6 maximum.
I believe it would be better to set minimum to 1 and maximum to 2, if I understand Matt correctly.
Oh, well dang it. I misread it. Thanks Mohawk20.
Correct, you need to set max threads to 2 or it will use as many as it detects up to and including the 4 physical cores you have.
- Oshyan
??? I am now a little lost? I thought that threads and cores where two different things but the way things are been discussed in this thread (sic) and related ones is that 1 Thread = 1 Core if that is not the case could some on please explain?
Regards to you.
Cyber-Angel
Although there is some variation in use of both terms, a "core" generally refers (collectively) to the primary calculation/execution units of a CPU. A "core" can execute calculations independently and generally encompasses a full set of execution units, in contrast with an individual "execution unit" (like SIMD, or a floating point unit) which is just one part of a "core" and must operate in conjunction with other elements, which form the whole of a "core". In a multi-core CPU there is more than 1 core, each generally operating somewhat independently in terms of execution/processing.
A "thread" on the other hand simply refers to a stream of calculations which form a part or the whole of a "process" (a "process" is generally the active running state of a single application). In a multi-threaded application there may be multiple threads. In a single-threaded application the single thread can be said to comprise the whole of the "process".
I'm sure that's still as clear as mud, but maybe this will help: A thread is *executed on* a "core" which is part of a CPU, either singly or multiply in a multi-core CPU. A single core can calculate multiple threads simultaneously, but is most efficient when concentrating calculations on a single thread. To most efficiently calculate multiple threads, especially when each thread is highly demanding as in a rendering context, it is best to have multiple CPU's or "cores" to which you can assign a thread.
In TG2 since each thread is so resource-intensive, and there is little or no benefit to running simultaneous thread on a single core, we detect how many cores are available for independent calculation and then spawn a number of threads that corresponds to the available cores.
More information in these Wikipedia articles:
http://en.wikipedia.org/wiki/Multi-core_(computing)
http://en.wikipedia.org/wiki/Thread_(computer_science)
- Oshyan
Right, thats it... >:( I've had enough of this "cores & threads" stuff. No body is saying nice things about my lovely render *shakes fist*
Bugger off onto your own post, I need all the space here for people to say nice things about my pic!
LOL ;D ;D ;D ;D
Miles
Hehe, fair point! Well I liked it, I thought it gave a good impression of depth, but I agree with others that the impression of scale seems off. I think this is partly down to texturing and partly the look of the water - the wave size makes it look like a larger body of water than you evidently intend.
- Oshyan
Beautiful work Miles; this approaches realism.
QuoteBugger off onto your own post,
Spoken like a true Brit' ;D ;D
I'm not disturbed by the waves myself, but matey, no way is that grass. That to me is the biggest scale issue but then it is only temporary. Keep going, keep going and ignore the philistines like me. :-*