Hello
With KEYSHOT 2.3 pro,I try to produce a big definition picture,to print a poster :170 cm * 120 cm whith 72 dpi. Calculation stop at 20 %: "memory crash". Is iet a software problem ? How to proceed ?
Regards
Bonjour
Avec KEYSHOT 2.3 pro,je souhaite faire une image de grande taille,pour imprimer une affiche: 170 cm * 120 cm avec au moins 72 dpi . Le calcul s
Which OS are u using ?
I'm on Windows XP 32bit and the max render size I can do is something like 4000x4000pix, depending on how much space the open project and KS take in.
XP has memory limit way to small.
If you use exr output then you can render any image size.
Also, KeyShot 4 (coming very soon) will have some improvements when rendering very large images.
Quote from: KeyShot on February 08, 2013, 09:51:44 AM
If you use exr output then you can render any image size.
Also, KeyShot 4 (coming very soon) will have some improvements when rendering very large images.
Doesn't higher resolution rendering still require more memory?
I always thought that was the case. ???
Dries
Exr will write to disk once memory fills up.
I must check into that again, but I remember trying that in the past, and since I'm not using it now ... must be a reason why ..
:-[
When is this crash occurring? Right at the beginning of the rendering?
Correct.
Maybe you are out of memory before you start the rendering?
I'm still on silly Windows XP 32 bit and running dangerously close to the limit or sometimes over.
I'm quite sure I could get it to work without a crash if I disable the alpha chanel .. but I need it.
or with smaller models ...
What I think is happening is that you are at the limit and there is no room left to even start writing out the image.
Time for an upgrade!
It's time for many upgrades ... and so it has been for +2j ...
I need KS3 upgraded.
I need KS4 installed.
We have an Adobe pack with FL/PS/IL/.../Premiere .. CS5.5 or so ... stored somewhere .. cuz they can not install it on a WinXP computer. But we DO have a license for it ! ::)
I've got a 64bit workstation that runs 32bit OS
I've got multiple gigs of ram, but can only use 1 / application (thnx WinXP)
I am slowly growing numb of frustration of all those crashes :-\
Can you try and turn off "effects"? I just talked to Henrik about it and he is convinced that this will fix it.
You mean under "Preferences/Advanced/Advanced/Graphics effects" ?
I'll try that.
(What does it do ?)
Quote from: PhilippeV8 on March 19, 2013, 02:08:38 PM
It's time for many upgrades ... and so it has been for +2j ...
...
I am slowly growing numb of frustration of all those crashes :-\
Philippe, not kidding on this one.
I was in the same boat for a while +/- 1.5 years ago.
Working with SolidWorks assemblies with hun-dreds of configurations, easily pushing +2GB memory for SLDWORKS.exe alone. ???
Constant crashes were driving me mad.
I also bumped into Windows 7 64bit implementation reluctance. ::)
What helped me to get a better workstation and modern OS was to make a cost-benefit analysis (CBA). Just like I had to make them in college to evaluate the soundness of investments for ALL stakeholders. ;)
I actually made a spreadsheet, comparing the cost of a new workstation (and accompanying load on IT) to the the time I would win working on projects. A week later I was on W7 x64.
I can really recommend doing that. Try to get IT and finance on board from the get-go.
You have to emphasize that YOU are the expert in your domain for your company. Because frankly, IT probably has no clue about what you're doing. :)
It depends a bit on the company culture and structure too. One advantage I have is that R&D is a relatively small group of people (meaning: not far from being understaffed ;)). I guess the smaller the team is, the smaller the 'tolerance for wasted time' is. ;D At least that's my theory about it.
In all fairness...and I'll just put it bluntly:
Judging by the work that you do, working with the assemblies that you have...it's a disgrace that you can't work on a modern 64 bit OS. Like you said: the OS is crippling the hardware potential. :o
Dries
Hi Philippe,
It is effects under settings (bloom and vignetting). These require a post-process on the framebuffer, so even if you use exr output they require the full framebuffer in memory, which I think is why you see the memory request when you press the render button.
Thnx, I will check.
I rarely use those so I doub't they're turned on. But I will check tomorrow.
(It's 3.33 in the night here ... I'm up cus my youngest won't sleep :-\ )