Tried to access null node pin + out-of-core memory

Generic forum to discuss Octane Render, post ideas and suggest improvements.
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
Post Reply
hqhempen
Licensed Customer
Posts: 24
Joined: Fri Mar 11, 2016 10:52 pm

I've gotten out-of-core memory log errors before but this is a scene in C4D I just had open that was working fine and now isn't. So don't think it's a polygon issue, or maybe it is not sure. Just weird behavior. At one point I was getting a FumeFX error in the log (don't have anything Fume installed on this machine at all) but that went away, also some weird thing about accessing a null node pin that isn't working. Either way all leads to a render failure on again, a project that was working fine and now isn't.


Tried to access pin via an invalid ID P_SUB_TYPE (703)
Tried to access null node pin
can't read int/enum from static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 00007FF8D7DA6DE0)
Export materials time= 37246.341 ms
*** Calculating motion blur on frame:679
*** Calculating motion blur on frame:679.4
*** Calculating motion blur on frame:680
TIMES=679 679.4 680 motionCnt=8453/20000 MT:0 Time=5102.694 ms.
Collect objects time= 5781.263 ms
Mesh creation time = 3021.564 ms.
Api update time: 20.517 ms.
Out-of-core memory limit exceeded
MB:1/1 ST/MOV:0/1137 Nodes:2615 Tris:22.577m DispTris:285k Hairs:0 Meshes:2k
Textures Grey8/16:1/1 Rgb32/64:67/0

Any help much appreciated. Thanks.
User avatar
aoktar
Octane Plugin Developer
Posts: 16066
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

Not sure what's high here but it's giving OOC errors. Other error is not important and doesn't causes any render errors. Increase your OOC amount or better to do some optimisation on your scene.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
hqhempen
Licensed Customer
Posts: 24
Joined: Fri Mar 11, 2016 10:52 pm

Feel free to close thread, ended up being a displacement error, guess it wasn't tripping it the first few times around
Post Reply

Return to “General Discussion”