OcDS 2.1 PRE RELEASE 5th

[sikotik13]

Is the checkbox under preferences for auto converting mats checked? There should also be an Octane icon somewhere in your main toolbar with either "man," "duf," or "auto" above it. Clicking this icon alternates between these three modes. if you want auto conversion, this needs to read auto. This icon selects these options in the preferences tab, so if you don't have the icon, manually check those boxes.

[Zenrel]

Thanks! yeah apparently they were uncheck somehow.

[t_3]

While I was working on a scene, my nodegraph editor got stuck on top of the screen somehow where I cant even grab the taskbar of it anymore. When I close it down, it gave me a fatal error. Even if I restart Daz Studio it's still stuck, so I disabled and enabled the plugin to get rid of it and it worked and the fatal error stopped. And now a major issue, now everything I put on the scene doesn't auto material now so I have to manually do it. I even reinstall the plugin and still hasn't fixed the problem. Anyone knows what's going on?

you should take a look at these:

probably the saved settings got messed up when the crash occured.
(clicking the icon cycles three states of the two checkboxes: both checked, both unchecked or .duf loading checked)
[edit] just noticed i was overtaken during writing the answer
anway this miht also be helpful...

in case of panels floating off screen
(what i can't avoid an the plugin side, since panels placing is done by studio)

you can save the current layout by
main menu > windows > workspace > save as...

and of course also load it back from there - it'll put anything in place again. this also helps when i.e. the tabs order is messed up (happens to me at least twice a day, so i even have assigned a keyboard shourtcut to layout loading)...

[Zenrel]

While I was working on a scene, my nodegraph editor got stuck on top of the screen somehow where I cant even grab the taskbar of it anymore. When I close it down, it gave me a fatal error. Even if I restart Daz Studio it's still stuck, so I disabled and enabled the plugin to get rid of it and it worked and the fatal error stopped. And now a major issue, now everything I put on the scene doesn't auto material now so I have to manually do it. I even reinstall the plugin and still hasn't fixed the problem. Anyone knows what's going on?

you should take a look at these:

OcDS_saving.png

probably the saved settings got messed up when the crash occured.
(clicking the icon cycles three states of the two checkboxes: both checked, both unchecked or .duf loading checked)
[edit] just noticed i was overtaken during writing the answer
anway this miht also be helpful...

in case of panels floating off screen
(what i can't avoid an the plugin side, since panels placing is done by studio)

you can save the current layout by
main menu > windows > workspace > save as...

and of course also load it back from there - it'll put anything in place again. this also helps when i.e. the tabs order is messed up (happens to me at least twice a day, so i even have assigned a keyboard shourtcut to layout loading)...

Thanks for the panel placement tip!

[larsmidnatt]

btw I noticed that the reload texture button no longer automatically keeps updating the texture. You need to manually press this each time you want to get an update. Is this intentionally?

[t_3]

btw I noticed that the reload texture button no longer automatically keeps updating the texture. You need to manually press this each time you want to get an update. Is this intentionally?

in case you mean the "watching for updates": there is a logic that sets an image map on disk to be watched for updates automatically, when it is thrown at an external editor by using the edit button (next to the reload button). if you like it to be watched for any other reason, you need to activate that manually in the image menu - afair this logic hasn't changed (apart from that reloading didn't work in a nbr. of past versions); if activated, there is a small icon next to the file name that notifies you about a map being watched.

the reason to not automatically watch any image, i.e. that was once reloaded, is that this can get quite hefty - the plugin needs to monitor the filesystem for writing, and doing so for dozens of files can be a killer for slower systems (or slow disks)...

[larsmidnatt]

btw I noticed that the reload texture button no longer automatically keeps updating the texture. You need to manually press this each time you want to get an update. Is this intentionally?

afair this logic hasn't changed

Well I get the reasoning behind not keeping an eye on things, I figure it was a resource thing, but just an FYI this did change. In the past even if i didn't use the editor button it would keep track and update for me as needed. I would just press the reload button once, and then going forward for the rest of the session it would keep reloading for me.

For the record I barely use the edit with image editor option because most of the time I edit PSD's and not the flattened files. The only time I ever use the editor button is to get photoshop open and with a file that is in the correct folder. its kinda like a shortcut but once PS is open I close the image and File>Open the actual PSD in the folder. But I'll deal. I can just use the editor button to trigger that watch mode going forward. thanks for the info.

[DrHemulen]

Anyone else having an issue with not saving material presets? When I select "Copy to my presets", the material appears down there, but on reload of DAZ it's gone.
I upgraded over my old 1.2 install, and my old presets are in the list, maybe there's a permission error somewhere?
Running Daz as administrator.

[sikotik13]

That would make at least two people, as I posted earlier that I was wondering if anyone else had this issue (it was at the end of a wall of attempting to be helpful text, so don't feel bad if you missed it). I reported it to t_3, but no info on cause as of yet. At least I know it's not just me now, lol.

[gaazsi]

mh... maybe someone could explain whats the (technical?) difference between the "final" button and if i let render without? i cant see any differences or mistakes when i do renders without pushing that button. atm it isnt working anyway so there is no choice