14 threads found!
Thread | Author | Replies | Views | Last Reply |
---|---|---|---|---|
rainfrey | 23 | 342 | ||
rainfrey | 2 | 112 | ||
rainfrey | 23 | 433 | ||
rainfrey | 4 | 149 | ||
rainfrey | 6 | 187 | ||
rainfrey | 14 | 240 | ||
rainfrey | 4 | 132 | ||
rainfrey | 4 | 192 | ||
rainfrey | 5 | 151 | ||
rainfrey | 18 | 428 | ||
rainfrey | 10 | 200 | ||
rainfrey | 5 | 227 | ||
rainfrey | 10 | 224 | ||
rainfrey | 1 | 100 |
27 comments found!
Good idea Phantast!
For those cases where you absolutely must use large hi-res textures.
If you read the top of this thread, you know that my final output is Giclee prints 22" X 28" at 300 DPI. However, I may also be doing some really huge blow ups of select image parts . . . for example, using just a character's face to take up the entire sheet . . . so it takes pretty large textures to hold up under these conditions.
But it never occurred to me to create low-rez tex for WIP. Great idea, thanks!
vue doesn't store the textures in the vue scene file.
FYI, Vue can store textures if asked to. It's a save option in V5I. Makes files easily portable and helps avoid problems with network rendering.
Thanks again.
R.
Come by and say "hello!"
http://rainer.us
Thread: Out of resources? | Forum: Vue
Thank you all for your comments.
The situation described by Phantast is exactly what is happening here. And I have been doing just that, relaunching Vue after X operations.
Maybe Vue 6 will handle memory more efficiently . . . sigh.
R.
Â
Come by and say "hello!"
http://rainer.us
Thread: Out of resources? | Forum: Vue
Thank you both for your thoughtful suggestions.
I think you're probably right, Diolma, it's most likely a memory fragmentation problem. After all, we've been dealing with that issue on PC's since the beginning, haven't we . . .
Maybe I'll pickup a ram de-fragger and run it periodically to see if that helps. Meantime, it's not that big of a deal to shut down the program occasionally and re-launch it. I just thought maybe there was a tweak I was not aware of that might help.
Cheers,
R.
Come by and say "hello!"
http://rainer.us
Thread: Out of resources? | Forum: Vue
Did you check "collapse identical materials" when importing your pz3?
Yes . . .
Also, I think you get the OOM because you want to render at such a big resolution.
No -- the current problem happens at small rez -- 550 X 700 px at 96 DPI. They are spot renders -- I do many of them for Work In Progress long before I render the big ones. And I always render the large images to disk.
If you have another computer around, even an older one, use Hypervue network rendering.
Yes, I have a few comparable systems with render cows on a small LAN connected via Firewire. If If I needed large WIP renders, I would use the network. However, render cows have been somewhat problematic since their introduction. I usually get the most trouble-free results by rendering final images to disk.
But as I said, the problem occurs on a modest image with small, partial WIP renders at low resolution. Â The issue is the ability to work efficiently while developing a scene. Final renders are not the problem.
It seems like Vue uses memory once for the render, then marks it as "used" and next time takes a different chunk of RAM and marks that as 'used" and so forth, until Vue is convinced there is no memory left (even though physically there is still over 1.2 GB of RAM in the pool).
Hey Bruno, thanks for all the input.
R.
Â
Come by and say "hello!"
http://rainer.us
Thread: Out of resources? | Forum: Vue
Thank you Bruno,
I switched off hardware OGL and am using software GL. I also switched all windows to wireframe except the main preview.
That seems to help, but it's not a satisfactory solution.
I appreciate your previous suggestions, but I cannot reduce rez on textures -- I am doing Limited Edition signed Giclee prints, 22" X 28" at 300 DPI. That requires high resolution textures. And right now, the available textures for most objects barely cut it for that size output.  Though I create some of my own textures to appropriate scale, I mostly modify existing ones. I think that's what most of us try to do instead of having to re-invent the wheel each time, n'cest pa?
But I'll tell you, it's a bit disappointing. I've been a Vuer since the first version I have pretty much first-rate equipment. I really didn't expect such poor memory management from the latest version of Vue -- really -- not after all this time.
In this case, my document is only one Poser adult, a few props, some clothes and 4 cats. IMHO, that shouldn't present such a huge challenge to the Vue render engine. It's doubly annoying because I really do enjoy using Vue for landscape and as a rendering environment.
The point is, as I'm sure you know, being creative is tough enough -- I don't want to be forced to become a hyper-techie as well. I've been a power user since the PC was invented and that's always been enough. But these kind of problems are beyond what I can deal with in the day-to-day of things. And it would be no small task for me to "switch horses" at this point, so to speak.
So I have to ask out of my own ignorance, why is it that I can work 150 MB images in Photoshop with multiple layers and undos, and no memory problems -- but Vue can't handle a 50 MB file without slowing to a crawl?
Even Poser doesn't struggle with large files -- it just won't render beyond 4096px, plus it takes all night to do it, and IMO Firefly is not nearly as good a ray tracer as Vue.
Anyway, I will check into SkinVue with more attention to detail. Thanks for the suggestion. If it can help solve this problem without destroying custom textures, I'm on it tomorrow.
Thanks for all the help, Bruno.
Cheers,
Â
Come by and say "hello!"
http://rainer.us
Thread: Out of resources? | Forum: Vue
Thank you Bruno . . .
The message from V5I is about "resources" -- not memory specifically. At best, Vue is only using 200- 300 MB of the 2 GB ram that I have. At the time the message occurs I still have 1.2 GB of available RAM. I don't see how Vue could be literally "out of memory" . . . but apparently it thinks it is.
Thaks for the info about SkinVue -- I have read the revues and visited their site, but I have not tried it yet. How does it handle highly customized, hand painted Poser textures? For example, aged skin with many lines and wrinkles painted onto an M3 texture?
How can it keep those details when converting to a procedural texture?
Thanks for your feedback.
R.Â
Â
Come by and say "hello!"
http://rainer.us
Thread: Rendered image size vs. RAM | Forum: Vue
Thanks for the feedback . . . I started using the incorporation feature during network rendering -- it seems to speed things up quite a bit since Vue does not have to collect textures before sending them to the other computers. It also eliminated some problems I was having with transparencies getting reversed on the network machine. As for the rest, I ran out of time and I am now piecing this together in Photoshop with parts rendered in different applications. Thank you all for your help, maybe I can attack this again on my next print project. R.
Come by and say "hello!"
http://rainer.us
Thread: Rendered image size vs. RAM | Forum: Vue
Hi and thanks for taking time to comment.
I don't mean to be obstinate, but my copy of Vue Pro with Mover 5 very specifically has the option to "Incorporate All Texture Maps" and still retain a link to their source (only to check for changes) -- or break the link and use only the version stored inside the Vue file.
The results are quite evident in file sizes before and after "incorporation" of texture maps.
And after incorporating textures, they are no longer listed in the World Browser under "Imported Materials" - - - they instead appear under "Standard Materials."
If this is not "incorporating textures" then I am totally confused.
Please explain.
Oops! -- I just noticed that I neglected to mention I was using Vue Pro in my first post -- terribly sorry for that. I guess I thought my references to network rendering and Render Cows would make it obvious. Is that causing some confusion?
Come by and say "hello!"
http://rainer.us
Thread: Rendered image size vs. RAM | Forum: Vue
Hi Wabe, In this particular Vue Pro file all the textures are incorporated -- not linked. It is a self-contained file of about 30 MB. The Poser file before import is about 28 MB. BTW, the original Poser file renders correctly in Poser at 300 DPI and 9" X 12" using the firefly engine. It's only Vue Pro that fails to render. R.
Come by and say "hello!"
http://rainer.us
Thread: Rendered image size vs. RAM | Forum: Vue
Thanks Phil, yes I did. No go . . . BTW, according to Task Manager this 30 MB Vue file blooms to 348 MB RAM when Vue loads it. Does that seems right?
Come by and say "hello!"
http://rainer.us
Thread: Rendered image size vs. RAM | Forum: Vue
Thank you Guitta, both my harddrives have caches set at 2535 each -- that's 5070 MB total VM. I don't think that is the problem.
Come by and say "hello!"
http://rainer.us
Thread: Dual What? | Forum: Vue
Thanks to all for your input -- and Forester, I'll send you a note separately.
Come by and say "hello!"
http://rainer.us
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Thread: Out of resources? | Forum: Vue