OTOY Forums

Hi t_3,

Another issue. I saved a HDR environment. Then later selected it. Once the environment was loaded, all button and options in the Environment tab became disabled as shown in the attached screen shot.
Best regards,
Rajib

edited and removed by user

I loaded up OcDS 2.1 PRE RELEASE 4th and it says "This pluggin account XXXXX is not valid for version 2.x."
I have already bought Octane 2 and when I did it said "Users with v1.x licenses can now upgrade the license to access to OctaneRender™ Standalone Edition v2.0. The upgrade is EUR99. For a limited time, users who upgrade to OctaneRender™ v2.0 can also upgrade an existing plugin license at no additional cost to make use of an available OctaneRender™ v2.0 plugin or receive a voucher towards the v2.0 plugin when it’s available.
How do I/can I upgrade OCDS to version 2? Any help/links appreciated.

REPLY FROM ADMIN WAS VERY QUICK - REPLY BELOW SO NO NEED FOR OTHER TO HELP - THANKS
When you upgraded your Standalone licenses to v2.x, you were eligible for the free plugin upgrade voucher promotion.
You'll be pleased to know that as of now, there is an unclaimed 'free plugin upgrade voucher' set against your customer area account. You can go back to the upgrade page:http://render.otoy.com/account/upgrade_license.php (you'll need to be logged in with your customer area account to access the page) and then tick on the plugin you want to upgrade to v2.x. This will automatically use the voucher to pay for the upgrade and, in effect, the plugin upgrade would be free.

rajib wrote:Hi t_3,

Using 4th release V2.1 R2.12.

1. I am using the RedSpec SSS for the G2F and it has many nodes. I am getting hangs whenever I click on one of its node in the NGE. This is consistently happening for me. Need to kill DAZ Studio once that happens.
2. Copy / paste seems to be temperamental.
3. In the color dialog, if by mistake a text is typed or pasted, clicking on the color does not update the HEX RGB readout. Have attached a screenshot.

Color Selection Dialog.png

Getting better though. Currently just trying a scene with Miho and hair. Going to load a more complex scene and see how it goes.

Cheers,
Rajib

To be honest, I wouldn't use an addon/content that is dependent on a beta/pre-release software. But for point 2, yes I have that issue too and I think it's been mentioned in this thread already. So you aren't the only one.

You are right there. In fact this situation has forced me to learn the standalone Octane and I have been using that mostly. Export the scene from Daz and then deal with it in the standalone version.

I am a software developer too and basically do a lot of stress test to break my own product. And to t_3, knowing about these kinds of issue will help him to resolve the issues whether immediately or a few releases down the line. And the more we all use it in different ways and find issues, the better it will be for t_3 and all of us.

larsmidnatt wrote:
To be honest, I wouldn't use an addon/content that is dependent on a beta/pre-release software. But for point 2, yes I have that issue too and I think it's been mentioned in this thread already. So you aren't the only one.

This current version of 2.1 has proven somewhat more reliable than my limited play with the previous version for me so far. I've again had it crash when creating an emitter, however this time it didn't leave me with a corrupt scene, which I'm very thankful lol! Ive had to run very long sessions on account of the materials not saving, have relied allot on saving out material presets to keep them recoverable (The presets loose their previews when octane/DS is rebooted though), I really cant wait for the octane mats to save with scenes

When the storm is over, and I can power up my render rig again, I can send T-3 another crash log, in regards to the emitter creation resulting in crash.

One other thing as mentioned earlier, the tabs issue, (where it snaps off screen and unable to be closed/moved without lowering screen resolution) occurred to a friend of mine also using OcDS. When opening the Node Editor it is defaulting to dockable state each time its opened, and I think its the main one that is having the issue. Each time I open it I set it to undockable to avoid the issue.

Other than that, I cant wait to polish off my first real render project in octane

Installed 2.1 and I like the direction things are going.

Note for animators though... this one has a ton of animation bugs so best to skip it. Hopefully v5 addresses the animation bugs and i will be incredibly happy.

Animations dont take camera movement nor figure movements at all... but it does take focus changes which is weird. if you try to render out a 10 second animation all you get is the first frame over and over and over again at different states of focus, until about half way when the camera turns 180 degrees for some weird reason and then renders the rest of the scene out from that.

Focus is hit or miss... no matter what autofocus or manual setting you do. sometimes it lets you choose the AF-s window at the bottom of the viewport so you can select the focus points at the top, but sometimes it is greyed out... seemingly at random.

Thanks for the new release!

A major issue that makes the new build unusable for em:

After I save, close and reopen my project, all my materials are unlinked. Which means I have to relink every mat after I close the project or shutdown my computer.

I´ve changed directly from version 1.2 to build 4, so is this something build 3 maybe doesn´t have so I could switch back to that? I´m working with the RedSpec SSS for Genesis 2 which doesn´t work with 1.2, so going all the way back isn´t really an option!

best wishes

Maybe you can try the standalone Octane. It does support animation. I personally have not used it. But it works with alembic file. I think you can try to export your Daz animation scene as an alembic file and then import it in Octane to render.

Liagriest wrote:Installed 2.1 and I like the direction things are going.

Note for animators though... this one has a ton of animation bugs so best to skip it. Hopefully v5 addresses the animation bugs and i will be incredibly happy.

I also was facing the same problem. To overcome it, instead of right clicking and selecting "Create a new light material", I opened the texture in NGE and manually added an emitter. Doing it this way works for me and it does not crash.
Attaching one of my renders where I have used the emitters (ceiling lights and the lights on the CamBots). Hope this helps.

SpyroRue wrote:This current version of 2.1 has proven somewhat more reliable than my limited play with the previous version for me so far. I've again had it crash when creating an emitter, however this time it didn't leave me with a corrupt scene, which I'm very thankful lol!