Home1.0.5.4 Good News, Bad News
2 posters
Page 1 of 1
1.0.5.4 Good News, Bad News
by MrMechano Sat Nov 26, 2016 11:55 pm
Thanks for getting a new build finished so quickly 
Everything seems working great on the DIM tab. The GlobalIDList bug seems fixed. Config files were created in Documents folder OK. Store ID on the DIM tab is working great. Supplement.dsx creation works. Maybe at a future time you might want to make it possible to have compatibility (ProductTags) setting besides DAZStudio4_5 I guess. A Multi-Selection pop-up world probably work well for that.
Smart Content Good News: Artist section and the Actor selection works perfectly. Support Asset "/" bug is fixed and Compatibility "\" bug is fixed.
Didn't have a chance to try No Compatibility option yet but I will try to test it with a light set soon.
Smart Content Bad News 01: Small bug - the file list on the Smart Content tab now shows everything in lowercase letters. Example: "Makeup 01 Iray.duf" becomes "makeup 01 iray.duf". This seems only a cosmetic issue in the GUI and does not have any effect on contents of the created Support .dsx file.
Smart Content Bad News 02: Two Bugs - First time the Update does not work for Actor/Character. It seems to have all necessary info if you check by clicking the .duf file in the list but when you try to Create Zip it shows an error that that Actor file wasn't done. If you do it second time the info shown when selecting in the file list seems to be same as the first time but now the Create Zip works okay. Result in Support .dsx file is double entry of ObjectCompatibility:
A worse problem is that all of the Mats, Shaping Presets, etc have empty Compatibility sections in the asset entry:
Everything seems working great on the DIM tab. The GlobalIDList bug seems fixed. Config files were created in Documents folder OK. Store ID on the DIM tab is working great. Supplement.dsx creation works. Maybe at a future time you might want to make it possible to have compatibility (ProductTags) setting besides DAZStudio4_5 I guess. A Multi-Selection pop-up world probably work well for that.
Smart Content Good News: Artist section and the Actor selection works perfectly. Support Asset "/" bug is fixed and Compatibility "\" bug is fixed.
Didn't have a chance to try No Compatibility option yet but I will try to test it with a light set soon.
Smart Content Bad News 01: Small bug - the file list on the Smart Content tab now shows everything in lowercase letters. Example: "Makeup 01 Iray.duf" becomes "makeup 01 iray.duf". This seems only a cosmetic issue in the GUI and does not have any effect on contents of the created Support .dsx file.
Smart Content Bad News 02: Two Bugs - First time the Update does not work for Actor/Character. It seems to have all necessary info if you check by clicking the .duf file in the list but when you try to Create Zip it shows an error that that Actor file wasn't done. If you do it second time the info shown when selecting in the file list seems to be same as the first time but now the Create Zip works okay. Result in Support .dsx file is double entry of ObjectCompatibility:
- Code:
<ObjectCompatibilities>
<ObjectCompatibility VALUE="/data/DAZ%203D/Genesis%203/Female/Genesis3Female.dsf#Genesis3Female" REF="/Genesis 3/Female"/>
<ObjectCompatibility VALUE="/data/DAZ%203D/Genesis%203/Female/Genesis3Female.dsf#Genesis3Female" REF="/Genesis 3/Female"/>
</ObjectCompatibilities>
A worse problem is that all of the Mats, Shaping Presets, etc have empty Compatibility sections in the asset entry:
- Code:
<Compatibilities>
</Compatibilities>
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by Admin Sun Nov 27, 2016 1:52 am
I'll look into the bugs you reported and wait for the rest of your test feedback.
Admin- Admin
- Posts : 683
Reputation : 14
Join date : 2016-11-16 -
Re: 1.0.5.4 Good News, Bad News
by MrMechano Sun Nov 27, 2016 1:54 pm
More Test Results.
With clothing set this time. There are a few bugs.
1) Minor Bug: The lowercase file names bug carries into the suggested names for Custom Compatibility. Example: The Suggestion for Product named "My New Product" and clothing piece called "My New Skirt" is "My New Product/my new skirt".
2) More Serious Bugs: The First "/" is missing for Custom Compatibilty and CompatibilityBase. Also the "d" in data is missing from the ObjectCompatibility section. Examples:
Both the incorrect path and the missing "/" result in broken metadata.
Some Good News: It seems that Base Compatibility does not need to be set twice and the ObjectCompatibility VALUE= does not have double lines. So it seems that bug is related to the "Is Actor?" Selector only. Might have something to do with the first Compatibility box being greyed out when Is Actor?" is checked?
Have not tried with a prop but should be no different from Wardrobe as they work in the same way. Still need to check a light set and use the "No Compatibility" setting.
With clothing set this time. There are a few bugs.
1) Minor Bug: The lowercase file names bug carries into the suggested names for Custom Compatibility. Example: The Suggestion for Product named "My New Product" and clothing piece called "My New Skirt" is "My New Product/my new skirt".
2) More Serious Bugs: The First "/" is missing for Custom Compatibilty and CompatibilityBase. Also the "d" in data is missing from the ObjectCompatibility section. Examples:
- Code:
<CompatibilityBase VALUE="Fashion Hot Outfit for G3Fs/fashion minitop"/>
- Code:
<Compatibility VALUE="Fashion Hot Outfit for G3Fs/fashion minitop"/>
- Code:
<ObjectCompatibility VALUE="/ata/xtrart-3d/Fashion%20MiniTop/Fashion%20MiniTop/Fashion%20MIni%20Top.dsf#Fashion%20MIni%20Top" REF="Fashion Hot Outfit for G3Fs/fashion minitop"/>
Both the incorrect path and the missing "/" result in broken metadata.
Some Good News: It seems that Base Compatibility does not need to be set twice and the ObjectCompatibility VALUE= does not have double lines. So it seems that bug is related to the "Is Actor?" Selector only. Might have something to do with the first Compatibility box being greyed out when Is Actor?" is checked?
Have not tried with a prop but should be no different from Wardrobe as they work in the same way. Still need to check a light set and use the "No Compatibility" setting.
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by MrMechano Sun Nov 27, 2016 2:03 pm
OOPS.
Found one more bug: The wrong version of Product Name is used in the Supplement.dsx. Result is :
Found one more bug: The wrong version of Product Name is used in the Supplement.dsx. Result is :
- Code:
<ProductSupplement VERSION="0.1">
<ProductName VALUE="My_New_Product_for_Genesis_3_Female"/>
<InstallTypes VALUE="Content"/>
<ProductTags VALUE="DAZStudio4_5"/>
</ProductSupplement>
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by Admin Mon Nov 28, 2016 1:51 am
Thanks for the updated feedback. I haven't had chance to check it out yet I had to go out of town.
Admin- Admin
- Posts : 683
Reputation : 14
Join date : 2016-11-16 -
Re: 1.0.5.4 Good News, Bad News
by Admin Mon Nov 28, 2016 6:49 am
Just uploaded CDDS (1.0.5.5) should fix the problems.
Admin- Admin
- Posts : 683
Reputation : 14
Join date : 2016-11-16 -
Re: 1.0.5.4 Good News, Bad News
by MrMechano Mon Nov 28, 2016 7:22 am
Thanks for the very fast update!
I'll check it out as soon as I have a bit of free time
I'll check it out as soon as I have a bit of free time
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by Admin Mon Nov 28, 2016 7:33 am
You're welcome, hopefully the bugs with this part are fixed now and no new ones show up. 
Admin- Admin
- Posts : 683
Reputation : 14
Join date : 2016-11-16 -
Re: 1.0.5.4 Good News, Bad News
by MrMechano Mon Nov 28, 2016 1:16 pm
This bug is fixed!
MrMechano wrote:OOPS.
Found one more bug: The wrong version of Product Name is used in the Supplement.dsx. Result is :Underscore ("_") should not be used here. Should be VALUE="My New Product for Genesis 3 Female"
- Code:
<ProductSupplement VERSION="0.1">
<ProductName VALUE="My_New_Product_for_Genesis_3_Female"/>
<InstallTypes VALUE="Content"/>
<ProductTags VALUE="DAZStudio4_5"/>
</ProductSupplement>
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by MrMechano Mon Nov 28, 2016 1:17 pm
This bug is fixed!
MrMechano wrote:
1) Minor Bug: The lowercase file names bug carries into the suggested names for Custom Compatibility. Example: The Suggestion for Product named "My New Product" and clothing piece called "My New Skirt" is "My New Product/my new skirt".
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by MrMechano Mon Nov 28, 2016 1:21 pm
MrMechano wrote:2) More Serious Bugs: The First "/" is missing for Custom Compatibilty and CompatibilityBase. Also the "d" in data is missing from the ObjectCompatibility section. Examples:This should be VALUE ="/Fashion
- Code:
<CompatibilityBase VALUE="Fashion Hot Outfit for G3Fs/fashion minitop"/>Again this should be VALUE ="/Fashion
- Code:
<Compatibility VALUE="Fashion Hot Outfit for G3Fs/fashion minitop"/>Should be VALUE ="data and REF="/Fashion
- Code:
<ObjectCompatibility VALUE="/ata/xtrart-3d/Fashion%20MiniTop/Fashion%20MiniTop/Fashion%20MIni%20Top.dsf#Fashion%20MIni%20Top" REF="Fashion Hot Outfit for G3Fs/fashion minitop"/>
Both the incorrect path and the missing "/" result in broken metadata.
I just tested with a Clothing set and Textures. Unfortunately the bugs above still exist. This bug seems to happen ONLY with Custom Compatibility. /Genesis 3/Female for instance works as normal with no problems or errors.
Will test on a Character next.
Last edited by MrMechano on Mon Nov 28, 2016 1:22 pm; edited 1 time in total (Reason for editing : Spelling)
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Mostly Good News
by MrMechano Mon Nov 28, 2016 10:13 pm
Tested with Character and with a Light Set and found no problems with Smart Content at all 
No Compatibility setting works perfect and Is Actor? is also working perfectly.
One fairly small issue: (, ), and ' are not being handled correctly in DIM filenames. Results in filenames like IM500012345-01_MyDressforGenesis3Female(s).zip or IM50054321-01_Vickie'sNewDress.zip
Both of those filenames will fail in DIM though those characters are okay in the Support/*.dsx filenames.
No Compatibility setting works perfect and Is Actor? is also working perfectly.
One fairly small issue: (, ), and ' are not being handled correctly in DIM filenames. Results in filenames like IM500012345-01_MyDressforGenesis3Female(s).zip or IM50054321-01_Vickie'sNewDress.zip
Both of those filenames will fail in DIM though those characters are okay in the Support/*.dsx filenames.
Last edited by MrMechano on Mon Nov 28, 2016 10:21 pm; edited 3 times in total (Reason for editing : clarification)
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by Admin Mon Nov 28, 2016 10:42 pm
I found the bug with the missing "/" but as for the missing "d" I do not get the missing "d" I may have fixed it without realizing it while fix small bug I found.
The " ' " and the " () " shouldn't be in the zip name. I may have accidentally by past a creative check with Is Actor.
I will get that fixed.
The " ' " and the " () " shouldn't be in the zip name. I may have accidentally by past a creative check with Is Actor.
I will get that fixed.
Admin- Admin
- Posts : 683
Reputation : 14
Join date : 2016-11-16 -
Re: 1.0.5.4 Good News, Bad News
by MrMechano Mon Nov 28, 2016 10:54 pm
You made a ton of progress already. Thanks!
I look forward to thenext build
I look forward to thenext build
MrMechano- Posts : 465
Reputation : 2
Join date : 2016-11-18
Re: 1.0.5.4 Good News, Bad News
by Admin Mon Nov 28, 2016 11:31 pm
CDDS (1.0.5.6) uploaded hopefully the bugs have been squashed this time.
Admin- Admin
- Posts : 683
Reputation : 14
Join date : 2016-11-16 -
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum|
|
|