tag:blogger.com,1999:blog-5889495575745143427.post1811758709638859860..comments2023-05-23T08:18:00.386-04:00Comments on How much mesh can a MeshWeaver weave?: Geekness à la GTX560 Ti (long post!)Anonymoushttp://www.blogger.com/profile/01656771386784572107noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5889495575745143427.post-46427596891736800112012-06-08T01:09:19.126-04:002012-06-08T01:09:19.126-04:00Well, that could be a problem with GPU technology ...Well, that could be a problem with GPU technology itself - as far as I know, GPU-based rendering uses the card's own memory, which in this case is 1GB...at least, that's how it works in the Cycles engine. I've also not tested OpenCL yet, I've been running only the CUDA tech for rendering... but like I said, I think it's more a general GPU limitation than an actual fault with Anonymoushttps://www.blogger.com/profile/01656771386784572107noreply@blogger.comtag:blogger.com,1999:blog-5889495575745143427.post-31639872614616191882012-06-07T10:52:22.754-04:002012-06-07T10:52:22.754-04:00I have this card and is really excellent relation ...I have this card and is really excellent relation price velocity, the problem is when you want to render a scene in a larger size, eg A3 300DPI (print) and then he did not pick up the scene, it's a problem I'm still looking for a solution, unfortunately, Open-CL also not pick up the scene even though I have 8GB ram.Anonymoushttps://www.blogger.com/profile/02468277215955199582noreply@blogger.com