Can you explain more? Do you mean "LOCKRES" icon functionality?sdanaher wrote:Some of these new features are great (zoom window, A/B).
Would it be possible to have the zoom window re-render 1:1 at the higher resolution (perhaps as an option)? For high-res print work it would be absolutely amazing to quickly inspect sections at a higher res.
Version 3.03.4-R3 (19.09.2016) - TEST
Moderators: ChrisHekman, aoktar
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Can you share some screenshots? I didn't get the issue...Weirdpictures wrote:Hey Ahmet,
great new version - just a quick thing and that might be absolutely intended, but when rendering with the new version we now get most of the time only 3 of our 4 GPU's to show up in the render stats bar while rendering final image. The 4th GPU is only showing as a non moving line in the picture viewer. Once i go and activate any background app like GPU z to measure the GPU load and temp it shows that GPU with 0% load as well. I do have to say, that it might be also a problem of my render temps, since they are always hovering around 88 C, even though if i check the GPU that is not running in GPU -Z it shows the temp of that GPU as only 64 C.
Any way around this and getting all 4 GPU's to render again like before?
Thanks Ahmet, awesome work as always
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
It's a combined bug with maxon's bug on alpha enabled custom materials. I think you missed my posts about it. I've tried to work-around this bug and consequence of this behavior. Sometimes it happens, i think i should disable opacity support on materials for opengl viewport. And better to add an option to activate. Maxon will not fix this bug for R17 or older versions as i understood.miohn wrote:Hi Ahmet,
working with latest R3 and latest nvidia driver 72.90 and still have the
problem with transparent/unvisible objects in the main 3D-view.
Do you think there will be a fix for that soon or do you recommend to
go back to a previous version?
Or is there another workarround for that problem?
thanks
Mike
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Not yet. I'm adding a parameter to settings. But we need to finish some other work before making a new release.miohn wrote:can I disable it somewhere in the settings?
regards
Mike
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Lockres is extremely slow and laborious on a 10k+ pixel image especially moving the image plane around to get to the part you're actually interested in. I prefer to create a separate camera just to zoom in, but this is also a slow workaround requiring multiple tools. If the new zoom feature allowed you to zoom in and render at a higher magnification quickly and simply it would be a huge benefit for print. Panning the LV buffer around while it tries to redraw is no fun.aoktar wrote:Can you explain more? Do you mean "LOCKRES" icon functionality?sdanaher wrote:Some of these new features are great (zoom window, A/B).
Would it be possible to have the zoom window re-render 1:1 at the higher resolution (perhaps as an option)? For high-res print work it would be absolutely amazing to quickly inspect sections at a higher res.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
We notice a render performance hit with the newest version compared to the latest STABLE version.
Newest one is 20% slower on preparing and saving sequences compared to the last stable. Also noticed that our GPUs only run at 75% load (no priority set).
We can't pin it down to what is causing it though and will keep investigating. Too many changes in the Standalone from 3.03.3 to 3.03.4 to be sure what the problem is. Or its in the plugin itself.
Newest one is 20% slower on preparing and saving sequences compared to the last stable. Also noticed that our GPUs only run at 75% load (no priority set).
We can't pin it down to what is causing it though and will keep investigating. Too many changes in the Standalone from 3.03.3 to 3.03.4 to be sure what the problem is. Or its in the plugin itself.
Last edited by DinoMuhic on Fri Sep 30, 2016 1:23 pm, edited 2 times in total.
what's crashes mean? Cuda errors?mrom wrote:lots of c4d crashes with the 372.90 driver, rolling back.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw