typed too q_ickly apparently. wish all bugs would be on this level...SimonJM wrote: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 ...![]()
![]()
![]()
OcDS 1.2.120.34xx - BUG REPORTS
Moderator: BK
Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
„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
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
Browse disk always work for the same folder.t_3 wrote: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?AlfaseeD wrote:Looks like I have some problem with the
-Browse recent
The window don't appear.
Here a test I do right now (I use the code, so you can check the length of the strings):
Code: Select all
D:\Poser Pro 2014\Runtime\Textures\DAZ\TH --- WWORK
D:\Poser Pro 2014\Runtime\Textures\Aslan_Court_1 --- NOT
D:\Poser Pro 2014\Runtime\Textures\alfaseed\x8 --- NOT
D:\DAZStudio4.6\My Library\Runtime\Textures\aeonsoul\skylys --- NOT
---Note : almost any folder in the Daz Studio folders works ...
D:\AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA --- NOT
D:\BBBBBBBBBBBBBBBBBBBBBBBBBB --- WORK
D:\CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC --- NOT
D:\DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD --- NOT
D:\EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE --- NOT
D:\FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF --- WORK
D:\GGGGGGGGGGGGGGGGGGGGGGGGGGGG --- WORK (tested also with file with a very long name) with a very long file name
D:\HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH --- NOT
D:\LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL --- WORK
Test without the slash
D:\Poser Pro 2014RuntimeTexturesRHSAMS --- WORK
D:\Poser Pro 2014RuntimeTexturesAslan_Court_1 --- WORK
D:\Poser Pro 2014RuntimeTexturesAslan_Court_1Z --- NOT
thanks for the indepth testing. got it!AlfaseeD wrote: Browse disk always work for the same folder.
Here a test I do right now (I use the code, so you can check the length of the strings):
„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
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
Looks like in the attached file (hope it's modest enoughtt_3 wrote: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)...

*EDIT*
Did a complete reinstall of DAZ+plugin, and it works again. Chalk this one up to me pressing a wrong button somewhere or DAZ being weird

GTX 780, 6 gigs of VRAM - Win 7 Home Premium 64 bits
Installed the new public release from Daz yesterday (4.6.2.118)...
After some testing and hints from the Daz support, to be able to save a scene you have to deactivate the octane plugin.
If not, DS freezes instantly when saving!
There was no problem with the octane plugin and the previous public release (4.6.1.39).
Daz says they can't do more about it...
Do you have the same problem with the .118 release?
After some testing and hints from the Daz support, to be able to save a scene you have to deactivate the octane plugin.
If not, DS freezes instantly when saving!
There was no problem with the octane plugin and the previous public release (4.6.1.39).
Daz says they can't do more about it...
Do you have the same problem with the .118 release?
going to check it; at least until 4.6.2.72 there was no such problem... except a plugin bug when saving a scene with unassigned daz surfaces - could it be this particular bug? if so it will be sorted out within the next days, otherwise i need to look about what daz may have changed...Peken wrote:Do you have the same problem with the .118 release?
„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
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
Some additional informationt_3 wrote:going to check it; at least until 4.6.2.72 there was no such problem... except a plugin bug when saving a scene with unassigned daz surfaces - could it be this particular bug? if so it will be sorted out within the next days, otherwise i need to look about what daz may have changed...Peken wrote:Do you have the same problem with the .118 release?

I'm on Win8.1 -64. An octane render (or DS) will save as it should.
So all is working perfectly until you want to save the scene as .duf...
Yep does it for me too, theres some thing that has changed in DAZ 4.6.2.118, it only seams to do it if try to save with the unassigned surfaces, works fine with the materials set up before the save.Peken wrote:Some additional informationt_3 wrote:going to check it; at least until 4.6.2.72 there was no such problem... except a plugin bug when saving a scene with unassigned daz surfaces - could it be this particular bug? if so it will be sorted out within the next days, otherwise i need to look about what daz may have changed...Peken wrote:Do you have the same problem with the .118 release?
I'm on Win8.1 -64. An octane render (or DS) will save as it should.
So all is working perfectly until you want to save the scene as .duf...
ok, but this is more of a plugin bug; fix to appear soon...michael_g wrote:Yep does it for me too, theres some thing that has changed in DAZ 4.6.2.118, it only seams to do it if try to save with the unassigned surfaces, works fine with the materials set up before the save.
„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
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