OcDS 1.2.120.34xx - BUG REPORTS

DAZ Studio Integrated Plugin (Integrated Plugin maintained by OTOY)

Moderator: BK

Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Post Reply
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

please post found bugs here
  • pls keep things short and descriptive - a step by step instruction in how to reproduce an issue will be quite helpful.
  • if you need screenshots or longer descriptions to point the problem out, feel free to create a new topic in this subforum.
  • a pm containing the a DAZ Studio crash report (if it was a crash) and the scene file that caused a problem will help quite a lot.
    note: don't send crash reports to DAZ, as they usually have no way to verify a problem with this plugin.
subscribe this topic
general discussion
subscribe this forum
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

how to keep independent running versions of DAZ Studio and/or the plugin:
  • copy the complete DAZ Studio program dir (and create a shortcut to the DAZStudio.exe i.e. on the desktop).
    note: you can have as much ...\DAZStudio4* folders as you like, they'll all run independently and share their settings.
  • run this DAZ Studio copy at least once before starting the plugin installer.
  • run the plugin installer and make sure to select the DAZ Studio program dir you just have created.
  • note: you may use this also to quickly switch between a DAZ Studio instance running the plugin, and another one that doesn't run it, i.e. in case you'd like to complete some work while the plugin is rendering another project.
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
SimonJM
Licensed Customer
Posts: 198
Joined: Tue Mar 19, 2013 12:28 am

Sparked up a scene created a couple of hours ago (just used 3Delight with it) to try out the new OcDS. My scenery (or most of it!) disappeared. On looking various materials were set to have Opacity of -1 (really, REALLY see-through? ;)) Correcting them to be 1 made them reappear. The items in question were to mention just one, the alleyfloor material from FirstBastion's Ambush Alley.
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

i'm going to get that product myself to check this; pls report back if you notice this with other mats also; did this even happen when you choose to recreate the auto mat (right click the surface in question > create as new auto material)?
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
SimonJM
Licensed Customer
Posts: 198
Joined: Tue Mar 19, 2013 12:28 am

When looking at textures in NGE focus will often go back to the main OcDS panel or to the Viewport window. Sometimes the main OcDS panel will be above the NGE window, but the NGE window will be active (inasmuch as it will respond to mouse wheel scrolls) and it is not possible to get round that except by shutting main panel.
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

you mean when hovering over the image selector button and/or images in the image menu?
have you docked the nge window into a tab area of studio or have it free floating?

ps: if you answer as expected i can already sort of imagine why this might happens, and should have a fix quite soon...
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
SimonJM
Licensed Customer
Posts: 198
Joined: Tue Mar 19, 2013 12:28 am

I tend to have the Octane windows as free-floating and not docked.
<edit>
And yes, when mouse hovers over image selector
</edit>
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

SimonJM wrote:I tend to have the Octane windows as free-floating and not docked.
that's the awaited answer. apparently neither me nor the testers of the closed group use it that way so this wasn't covered. but as said already, i expect to have a straightforward fix for that - the image preview widget is singular and global, so it shifts the focus to the daz main window but never back to where it was opened (at least natively); setting the focus explicitly back to the opener during or after it was displayed will most probably sort this out...
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
SimonJM
Licensed Customer
Posts: 198
Joined: Tue Mar 19, 2013 12:28 am

t_3 wrote:i'm going to get that product myself to check this; pls report back if you notice this with other mats also; did this even happen when you choose to recreate the auto mat (right click the surface in question > create as new auto material)?
Ahhh, think I have spotted the reason - the shader used is Default, not DAZ Studio Default - he uses the same thing with Ambush Alley desert road - the Opacity setting is just a strength specified by RGB, there is no percentage involved.
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

SimonJM wrote:
t_3 wrote:i'm going to get that product myself to check this; pls report back if you notice this with other mats also; did this even happen when you choose to recreate the auto mat (right click the surface in question > create as new auto material)?
Ahhh, think I have spotted the reason - the shader used is Default, not DAZ Studio Default - he uses the same thing with Ambush Alley desert road - the Opacity setting is just a strength specified by RGB, there is no percentage involved.
ah, thanks! never stumbled over sthg.; will have a look into who this is to handle best...
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
Post Reply

Return to “DAZ Studio”