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.
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

AlfaseeD wrote:Looks like I have some problem with the
-Browse recent
The window don't appear.
:)
i assume you have folders listed in the sub menu, so... is "browse disk" working for the same folder? can you test it with some pretty basic folder like i.e. c:\test?
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
DrHemulen
Licensed Customer
Posts: 317
Joined: Thu Dec 26, 2013 7:09 pm

Tried out templating. It works as advertised (it's fantastic) but it's a little wonky.

First time I tried it, nothing happened when I dragged the template material over the current material. After restarting DAZ, it worked perfectly the first time. Second time I applied the material DAZ crashed with "DAZStudio.exe caused ACCESS_VIOLATION at 0033:00000000004B4C43". Report attached.

But MAN that's a good tool, it's going to save sooo much time!
Attachments
DAZStudio_error_report_140212-213120.zip
(57.73 KiB) Downloaded 207 times
GTX 780, 6 gigs of VRAM - Win 7 Home Premium 64 bits
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

DrHemulen wrote:Tried out templating. It works as advertised (it's fantastic) but it's a little wonky.

First time I tried it, nothing happened when I dragged the template material over the current material. After restarting DAZ, it worked perfectly the first time. Second time I applied the material DAZ crashed with "DAZStudio.exe caused ACCESS_VIOLATION at 0033:00000000004B4C43". Report attached.

But MAN that's a good tool, it's going to save sooo much time!
yes, unfortunately; had some testing myself yesterday (usually there is far too little time to do so), and also found out about this - under certain circumstances; did you have the viewport open/octane rendering when applying the template? it seems to be save as long octane is not rendering, at least i had this impression...
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
DrHemulen
Licensed Customer
Posts: 317
Joined: Thu Dec 26, 2013 7:09 pm

Nope this was without the render window open, both times.

Geografting is totally broken in the new update for me, it doesn't hide the old polys anymore, not even in the viewport (Genesis2F/Genesis2Fgenitals). That worked in the 1.2 befor the update. Works fine in the DAZ public beta i have installed in parallel.

Loading files generated with older versions of the plugin still works for some reson, but "clean" DAZ files from the beta doesn't.

(Not trying to be mister negative here, I really love the direction you are taking) :)
GTX 780, 6 gigs of VRAM - Win 7 Home Premium 64 bits
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

DrHemulen wrote:Nope this was without the render window open, both times.

Geografting is totally broken in the new update for me, it doesn't hide the old polys anymore, not even in the viewport (Genesis2F/Genesis2Fgenitals). That worked in the 1.2 befor the update. Works fine in the DAZ public beta i have installed in parallel.

Loading files generated with older versions of the plugin still works for some reson, but "clean" DAZ files from the beta doesn't.

(Not trying to be mister negative here, I really love the direction you are taking) :)
with "even in the viewport" you mean the daz viewport? that would be pretty strange, as of course the plugin only reads information from daz elements and doesn't alter them (apart a few places like aspect ratio settings)...
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

Jazbee wrote:Can't really find a way to reproduce the bug 100%, but the first few times it worked like this:
1. Create a cube primitive
2. Change its material to Mix (mat1:glossy, mat2:mix) while attempting to change mat2 to mix, DS crashes

Hope this helps
this seems to work, um, crash rather reliably...
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

DrHemulen wrote:Nope this was without the render window open, both times.

Geografting is totally broken in the new update for me, it doesn't hide the old polys anymore, not even in the viewport (Genesis2F/Genesis2Fgenitals). That worked in the 1.2 befor the update. Works fine in the DAZ public beta i have installed in parallel.

Loading files generated with older versions of the plugin still works for some reson, but "clean" DAZ files from the beta doesn't.

(Not trying to be mister negative here, I really love the direction you are taking) :)
Agreed something a little strange with geograft on G2F - I found a work round by right-clicking on the base figure and selecting 'Create all 28 as new materials >, Auto materials'.
SimonJM
Licensed Customer
Posts: 198
Joined: Tue Mar 19, 2013 12:28 am

The Opacity setting of -1 seems to be a common thread if a non-standard shader is used (an additional example would be the 'G2F Bot Armor' items).
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

SimonJM wrote:The Opacity setting of -1 seems to be a common thread if a non-standard shader is used (an additional example would be the 'G2F Bot Armor' items).
mh. i have added an exception for that cases; should be gone with the next update...
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

And, just for fun .. a small typo, you have 'Qick Edit' as a tab title instead of 'Quick Edit' in the Materials tab, just above the NGE button. This is, of course, destroying all my artistic aesthetic ... :lol: :roll: :shock: :twisted:
Post Reply

Return to “DAZ Studio”