[Released] Legacy Set Converter * Commercial *

Totte

Andrew_C said:

Im having a bit of an odd issue with converting FireAngel's FA MUV APC (which is over at Renderosity) in Legacy Set Converter. Basically theres 5 basic varients the basic one, a command vehicle, a turreted one, a flatbed a tanker & an ambulance (which is externally the same as the command vehicle). It thinks that they are all one figure & assigns them all the same ID in data. So only one will load properly, whichever you converted last

I think thats happening becase it seems to partly work like a chassis figure with different attached top bit, which is how I think LSC tries to treat it. except it also seems to work differently & the different top bits cant be separted off into a different prop or figure as far as I can tell. Maybe you could do it by hacking the PZ3 files but thats out of my paygrade. 

Anyway anyone encountered anything like this? Or is the best way to handle it to just do it the old fashoined way, save them all into a scene & save each out as a scene subset or whatever.

ED spelling

Hi, are you selecting the pz3 or have you loaded it into DS, saved it out as a scene or scene subset inside a mounted library and tried to convert that? 
I don't have that item so I cannot really test.
 

jhogenboom_da69c035a9

I see this in the manual:  "Some, not all .daz files will crash or hang Daz Studio on macOS, that is nothing Legacy Set Converter can do anything about, as it happens loading those directly in Daz Studio as well." It's batting a thousand at my house.

I'm running  Daz 4.24.0.4 on Windows 11 on both my computers. So far the converter does 2 files in a props folder, then crashes. It won't do single scene files, either. I've uninstalled and reinstalled the converter. I've obviously restarted DAZ. Can you give me any more advice on what to try?

Thanks.

Totte

jhogenboom_da69c035a9 said:

I see this in the manual:  "Some, not all .daz files will crash or hang Daz Studio on macOS, that is nothing Legacy Set Converter can do anything about, as it happens loading those directly in Daz Studio as well." It's batting a thousand at my house.

I'm running  Daz 4.24.0.4 on Windows 11 on both my computers. So far the converter does 2 files in a props folder, then crashes. It won't do single scene files, either. I've uninstalled and reinstalled the converter. I've obviously restarted DAZ. Can you give me any more advice on what to try?

Thanks.

What types of files are you trying to convert? .pz3, .pp2, cr2, .daz? Can you open those files manually?
The reason .daz files might crash is that the format has been deprecated for ages, and the crashes are deep inside Studio.

 

Andrew_C

Totte said:

Andrew_C said:

Im having a bit of an odd issue with converting FireAngel's FA MUV APC (which is over at Renderosity) in Legacy Set Converter. Basically theres 5 basic varients the basic one, a command vehicle, a turreted one, a flatbed a tanker & an ambulance (which is externally the same as the command vehicle). It thinks that they are all one figure & assigns them all the same ID in data. So only one will load properly, whichever you converted last

I think thats happening becase it seems to partly work like a chassis figure with different attached top bit, which is how I think LSC tries to treat it. except it also seems to work differently & the different top bits cant be separted off into a different prop or figure as far as I can tell. Maybe you could do it by hacking the PZ3 files but thats out of my paygrade. 

Anyway anyone encountered anything like this? Or is the best way to handle it to just do it the old fashoined way, save them all into a scene & save each out as a scene subset or whatever.

ED spelling

Hi, are you selecting the pz3 or have you loaded it into DS, saved it out as a scene or scene subset inside a mounted library and tried to convert that? 
I don't have that item so I cannot really test.
 

Hi sorry about the delay in replying, been distracted by stuff, I was trying to convert the PZ3 directly. Do you mean saving a scene subset then converting materials in Advanced Material Converter?

Totte

Andrew_C said:

Totte said:

Andrew_C said:

Im having a bit of an odd issue with converting FireAngel's FA MUV APC (which is over at Renderosity) in Legacy Set Converter. Basically theres 5 basic varients the basic one, a command vehicle, a turreted one, a flatbed a tanker & an ambulance (which is externally the same as the command vehicle). It thinks that they are all one figure & assigns them all the same ID in data. So only one will load properly, whichever you converted last

I think thats happening becase it seems to partly work like a chassis figure with different attached top bit, which is how I think LSC tries to treat it. except it also seems to work differently & the different top bits cant be separted off into a different prop or figure as far as I can tell. Maybe you could do it by hacking the PZ3 files but thats out of my paygrade. 

Anyway anyone encountered anything like this? Or is the best way to handle it to just do it the old fashoined way, save them all into a scene & save each out as a scene subset or whatever.

ED spelling

Hi, are you selecting the pz3 or have you loaded it into DS, saved it out as a scene or scene subset inside a mounted library and tried to convert that? 
I don't have that item so I cannot really test.
 

Hi sorry about the delay in replying, been distracted by stuff, I was trying to convert the PZ3 directly. Do you mean saving a scene subset then converting materials in Advanced Material Converter?

Load the pz3, save it as a .duf scene subset, convert that with LSC to .duf (real items, with data in /data), then run AMC on those to make them Iray mats.

 

brillstereo

Code 66 converters failing under DAZ Studio 6 on macOS

I am experiencing repeatable script failures with multiple Code 66 products under DAZ Studio 6 on macOS.

Advanced Material Converter

AMC Converter.dse fails at line 2952 with:

ReferenceError: backendVersion is not defined

The log also reports that global include() is deprecated and recommends require().

AMC Shader Config

AMC Shader Config.dse fails at line 584 with:

SyntaxError: Expected token 'identifier'

Legacy Set Converter

LSC Converter.dse fails at line 2457 with:

TypeError: connect requires a signal

Immediately before this failure DAZ Studio reports:

DzHeader::setClickEnabled() is deprecated - it has no effect

and:

Use of the DzListView 'selectionChanged()' function signature is deprecated. Use 'selectionChanged' instead.

All scripts are being located and loaded correctly from the content library. PostgreSQL CMS is now operating normally.

As several Code 66 encrypted .dse scripts are failing with scripting/API/deprecation errors, could you confirm whether these products currently support DAZ Studio 6 and whether Studio 6-compatible updates are planned?

brillstereo

In respect of my previous post : 

Further update / confirmation:
I have now opened the exact same installation of Advanced Material Converter using DAZ Studio 4.24.0.4 (64-bit) on the same Mac, accessing the same DAZ content library.

AMC opens and operates normally in 4.24.

The AMC interface reports Frontend 1.0.0.5 / Engine 1.0.0.4.

Therefore this does not appear to be an AMC installation, content-library, PostgreSQL or macOS permissions problem. The same installed AMC scripts work under 4.24 but fail under DAZ Studio 6 with ReferenceError: backendVersion is not defined.

This appears to be a DAZ Studio 6 compatibility issue with the Code 66 scripts.

I would therefore much rather see these products updated for Studio 6, if that's possible. 

 

Totte

Most scripts with UI fail on DS 6 due to major changes in the scripting engine. Some product will be converted, Legacy Set Converter is not one of them as the .daz format is no longer supported in DS 6 so it is rather pointless to port it as it rely on the .daz support, but as it works in DS 4, you can convert in  DS 4. For Advanced Material Converter, its still not decided, as it also reads .ds material files and .daz material files which no longer are supported for DS 6, but not decided yet. Both products will be rather crippled in DS 6.