Vram limits
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
-
FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm
Anyone with tens of millions of polys really needs to learn how to retopo and bake...
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles
Retopology is one way and then using a normal map extracted from the high res model in order to fake the detail. However, some scenes are in fact really big; I'm not talking about single models. I can sometimes have a scene that is a few billion polys and I still consider that a small poly count. In some cases Octane is out of the question and we have to use for example Clarisse IFX (which can handle trillions of polys), which is CPU based and quite fast, as a scene builder and renderer. In any case, 40 million polys is not a lot; if your card can't handle it and you really can't afford in your workflow to retopo and bake (for whatever reason), then you might have to consider outsourcing to an octane render farm (there's currently only one, just use Google).
Hi Ibycus,
have you tried also in Standalone v3 alpha 4/5 or only with c4dOctane v3.1?
ciao beppe
have you tried also in Standalone v3 alpha 4/5 or only with c4dOctane v3.1?
ciao beppe