Which feature do you need the most?
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
I could use a "split screen render" option. And by that I mean I don't have enough memory to render highres images (really high). So it would be nice to split up the resolution in smaller parts - save them out - and stich them back together in photoshop. Is it even possible now?
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
Hi Zay,
I already have the solution for this issue, I need only to polish the code, and then I'm going to publish a Lua script that solves this and other related issues, stay tuned
ciao beppe
I already have the solution for this issue, I need only to polish the code, and then I'm going to publish a Lua script that solves this and other related issues, stay tuned

ciao beppe
Wow, that sounds awesome! Can't wait to try it outbepeg4d wrote:Hi Zay,
I already have the solution for this issue, I need only to polish the code, and then I'm going to publish a Lua script that solves this and other related issues, stay tuned
ciao beppe

Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
I assume that you are running out of system memory, not GPU memory, since the film buffer in version 3 is stored in system RAM. Only the post-processing buffer is still on the GPU and requires 10 bytes per pixel. But you can't do post-processing effects with tiled rendering either.Zay wrote:I could use a "split screen render" option. And by that I mean I don't have enough memory to render highres images (really high). So it would be nice to split up the resolution in smaller parts - save them out - and stich them back together in photoshop. Is it even possible now?
So please be aware that if you run out of system memory rendering a large resolution in Octane v3, chances are that you will also run out of memory in Photoshop.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- itsallgoode9
- Posts: 893
- Joined: Thu Apr 03, 2014 9:04 am
- Location: New York City
- Contact:
Maya v3 would be nice. 6 months later, we have nothing. Otoy talked about v4 before maya users even had an "alpha" (i use that term lightly) of v3.
Intel i7-3930K, 64gb RAM, Asus X79 Deluxe mobo, 2x EVGA 780 6gb (for rendering), 1x PNY quaddro k4000 (for display)
Windows 8.1 x64, Maya 2014, Octane Render v2
Windows 8.1 x64, Maya 2014, Octane Render v2
- tobyauberg
- Posts: 1
- Joined: Mon Sep 01, 2014 7:35 am
This please! https://www.youtube.com/watch?v=v9tyA9dM15k
Got v3 just for the that, bummed it wasn't included but ok, been waiting patiently for 3.1 since but I'm really really hungry for it. Any word on when 3.1 might be coming? Rough estimate?
Got v3 just for the that, bummed it wasn't included but ok, been waiting patiently for 3.1 since but I'm really really hungry for it. Any word on when 3.1 might be coming? Rough estimate?
- voltaire585
- Posts: 91
- Joined: Sun Jun 08, 2014 7:37 am
Noise reduction inbuilt. Adaptive + altus type pass reduction. Both would be good
- itsallgoode9
- Posts: 893
- Joined: Thu Apr 03, 2014 9:04 am
- Location: New York City
- Contact:
Pascal Compatibility on Maya V2, seeing as we still don't have a V3 release.
Intel i7-3930K, 64gb RAM, Asus X79 Deluxe mobo, 2x EVGA 780 6gb (for rendering), 1x PNY quaddro k4000 (for display)
Windows 8.1 x64, Maya 2014, Octane Render v2
Windows 8.1 x64, Maya 2014, Octane Render v2
The toon shading system and other postFX features shown in OctaneImager are all ready and done (this was a live screen-grab of the feature working in a custom app we made for GTC). We do need to finalize the Octane module SDK API for OctaneImager and similar post plug-ins to work inside the engine seamlessly. We have this partially up and running in 3.0 via the module SDK, and if it the imager API work gets fully completed before 3.1, then we will expose these modules sooner. We have been planning on making modules an officially supported feature by 3.1 (vs. experimental support for devs to test in 3.0, while there are ongoing changes to API).tobyauberg wrote:This please! https://www.youtube.com/watch?v=v9tyA9dM15k
Got v3 just for the that, bummed it wasn't included but ok, been waiting patiently for 3.1 since but I'm really really hungry for it. Any word on when 3.1 might be coming? Rough estimate?