OTOY Forums

t_3 wrote:note @all: i'm going to be rather quiet for the next 2 days; as much i love to discuss things here in the forum i still need to also get some homework done for the next update; means less talking but focus on writing (code)...

I was under the impression you had 8 hands and 4 brains!

t_3 wrote:note @all: i'm going to be rather quiet for the next 2 days; as much i love to discuss things here in the forum i still need to also get some homework done for the next update; means less talking but focus on writing (code)...

Sounds good.

linvanchene wrote:@ autosave

I noticed that there is a field to enter an autosave number and there are also autosave options when click on the "Save" button in the plugin viewport.
Are those linked? Are is one the autosave option for the scene and the other an autosave option for the image? Are there any other settings (paths) etc. that need to be set up in order for autosave to be triggered?

in the preferences the autosave interval and the general jpg quality (also when using jpg for autosaves) can be set up...

linvanchene wrote:I just naivly clicked on autosave png 16 bit and expected some autosave images to be created every 5 minutes in the normal octane image folder. But ended up not finding anything there when I returned to the workstation later.

this is how it normally should work; autosave needs to be activated/deactivated in the viewport save menu; if you change the interval, you'll need to de/activate again, in order to have the change immedieatly taking effect, otherwise it'll change after the next autosave (using the old interval).

but: i have mixed up the triggers the gpu cooldown timeout is going to do an autosave (at least if autosave is on), and vice versa - so usually nothing happens in both cases.

linvanchene wrote:@ saving when an image is still rendering

About every 500 to 1000 spix I tend to do a manual save to have some kind of backup in case the workstation deceides to shut down for some reason.

I recall in the "old" / june 2013 version of the plugin whenever I would click "Save" in the plugin viewport windows save dialogue would be triggered and fully responsive.

Nevertheless when I tried to save during my last project the whole process was slowed down to a crawl.

do you experience that in general?
have you had render priority set?
how was/is the overall system responsiveness at the time when you tried to save?

at the time the file selection dialog opens, octane is still rendering, there is not much going on but to open the system file dialog. if this is an issue under certain circumstances, i can add a render pause/unpause as soon save is clicked/finished...

here you are...

does Octane and/or the plugin support the 5.0 Compute model used by the new 750Ti?

jimgale wrote:here you are...

does Octane and/or the plugin support the 5.0 Compute model used by the new 750Ti?

cuda compute models are backward compatible;
as long as octane doesn't require anything higher than 2.0, everything above should work...

[edit] ...but apparently it doesn't; so we'll need to wait for a new octane build that takes care of whatever nvidia might have changed.

just a general note about lags, slowdowns, vram max-outs, etc.: i now got a gt640 with "only" 2gb vram, to do some optimisations when such conditions occur; at least when maxing out vram the plugin should be able to maintain a working state instead just freezing ds.

the extreme ui-lag when saving that linvanchene reported is hopefully gone because of other optimisations to the viewport handling and save process; just in case... has somebody seen something similar?

Where did my OcDS installation go? I have it installed but and showing in activation manager. But Daz studio is not showing the plugin. And in About Daz Plugins it shows up as red..... whats the procedure to reset this. I have been away from Daz for a little bit and just restarted it... Could it be a reality based issue or new camera setting issue that wipes OcDS compatibility somewhere?

wlebrun wrote:Where did my OcDS installation go? I have it installed but and showing in activation manager. But Daz studio is not showing the plugin. And in About Daz Plugins it shows up as red..... whats the procedure to reset this. I have been away from Daz for a little bit and just restarted it... Could it be a reality based issue or new camera setting issue that wipes OcDS compatibility somewhere?

having the plugin showing up in red in "about plugins" only happens if it could not be at all loaded - most probably because a file is missing or of a wrong version.

so the first thing to try is to run the installer again; if you did dl the installer a while ago and like to skip copying meanwhile released updates, you might want to download the installer again from the otoy user account download page, as it already contains the latest 1.2 build...