OTOY Forums

Whilst I remember, the 'interfering' with Reality issue would be good to get cleared up

SimonJM wrote:Whilst I remember, the 'interfering' with Reality issue would be good to get cleared up

i'm going to add a simple config file, to be edited with notepad or the like, to add switches that can be used in such cases.

but it would be better if paolo changes this behavior eventually...

Confession time. Because my system is less than a year old, it never dawned on me that my frustrations with the new plugin version was something other than teething problems from Octane. I just updated my nVidia drivers. <POOF> Problem gone that quick. Render times are smokin' fast.

Sorry for doubting you T3.

rbennett2040 wrote:Confession time. Because my system is less than a year old, it never dawned on me that my frustrations with the new plugin version was something other than teething problems from Octane. I just updated my nVidia drivers. <POOF> Problem gone that quick. Render times are smokin' fast.

Sorry for doubting you T3.

BIG thanks for telling!

this could - for a part - explain very different experiences that some ppl have. i usually upgrade drivers whenever new whql versions come with the windows update. honestly, i also didn't expect big problems because of a little older driver versions (of course i can't test them all), as otherwise this'd me my first advice when there are problems.

do you remember what the version was you had before updating?

as far i can tell from the stats the range of nv driver version in use with the plugin reaches from 296.44 to 332.5, where i would call anything below 314.x as not recommended. i'll write that on top of the next update post.

ps: apart from that there are still a few parts of the plugin that date from early versions, and even if they seem to work all the time, there is a chance that they mess up things at some point; sometimes quite old problems just get visible because the surrounding did change that much... i'm just now rewriting the method which copies the render image from octane into the viewport, as it contained a potential buffer overrun (=memory leak =likely crash here and then).

t_3: perhaps a 'warning light' (yellow) in the About of your plugin to tell users that their nvidia drivers (may be) out of date.

Emitter temperature picker populates the field, but the value is not applied.
The value is locked at 6500.

vortex3d wrote:Emitter temperature picker populates the field, but the value is not applied.
The value is locked at 6500.

Seen this too, the presets dont work and some times manually inputting the temp dont either.

michael_g wrote:

vortex3d wrote:Emitter temperature picker populates the field, but the value is not applied.
The value is locked at 6500.

Seen this too, the presets dont work and some times manually inputting the temp dont either.

... will take a look (of course).

jimgale wrote:t_3: perhaps a 'warning light' (yellow) in the About of your plugin to tell users that their nvidia drivers (may be) out of date.

good idea. is going to come...

t_3 wrote:

jimgale wrote:t_3: perhaps a 'warning light' (yellow) in the About of your plugin to tell users that their nvidia drivers (may be) out of date.

good idea. is going to come...

I have to say ... er, why? Surely it would be better for that to be handled by whatever upgrade mechanism nVidia provide? It'd depend on nVidia making no changes to their website/upgrade processes to be accurate and could cause 'wait issues' if no network connection is available.