Apex files (redfur,redcloth) about wolvenkit

[SkacikPL]

Technically both are possible with more or less hassle.
IIRC WKit has nearly finalized APEX import but i don't think it's 100% ready yet.

[Traderain]

• This is what NVIDIA uses to serialize xml files: https://github.com/NVIDIAGameWorks/PhysX-3.4/blob/3dfe2108cfab31ba3ee5527e217d0d8e99a51162/APEX_1.4/NvParameterized/src/XmlSerializer.cpp
• And this to read them: https://github.com/NVIDIAGameWorks/PhysX-3.4/blob/3dfe2108cfab31ba3ee5527e217d0d8e99a51162/APEX_1.4/NvParameterized/src/XmlDeserializer.cpp

[SkacikPL]

wcc_lite has importer for apx and apb files (hairworks/cloth/destructibles) it's essentially all same file type but game forcibly expects apx for hair and apb for cloth/destructibles. Wcc import expected apb seems to be compatible with publicly available creation tools however apx seems to be expecting 1.0 hairworks type file which is not publicly available.

[Traderain]

@SkacikPL So you can import an apb file succesfullly with it?

[SkacikPL]

Yes, wcc won't throw a shit fit when you attempt to do that. Other question is whether it would work, given proper testing would require a brand new asset made from ground up with proper rigging and skinning which is something nobody tested.

As far as import itself goes, you can import apb files with no issues using wcc_lite using currently available nvidia tools and plugins. It's only apx that can't be imported.

[Traderain]

Alright but the apx importing problem roots from that we don't have a version 1.0 file right?

[SkacikPL]

Yeah, apx is the XML variant of apex file type so technically it can't be that hard to get it right or downgrade it to 1.0 compliant version. However there are no public samples so all that's left is guessing or blindly cutting down 1.1 and newer samples till it imports.

[Traderain]

So the file format of apb is defined here: https://github.com/NVIDIAGameWorks/PhysX-3.4/blob/3dfe2108cfab31ba3ee5527e217d0d8e99a51162/APEX_1.4/NvParameterized/include/ApbDefinitions.h It can be used to make a converter.

[Traderain]

Apex format documentation:
PhysX_APEX_architecture_design_File Formats - engwiki.pdf

[redwoodgroves]

Wondering if there is still being work done with hairworks files. Or if you still think it's going to be possible? Thanks

[Traderain]

It kinda works but I got really fustrated with how the vertexes and such work so I lost interest for a bit but I plan to finish it.

…

On 2018. Aug 18., Sat at 11:10, SkacikPL ***@***.***> wrote: Technically both are possible with more or less hassle. IIRC WKit has nearly finalized APEX import but i don't think it's 100% ready yet. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#43 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGHV1Ow3AZ1xyVmHShFOtCmmec-cd_6Iks5uR9npgaJpZM4NBkWf> .

[redwoodgroves]

Well that is great news. Good luck. I'm very excited to make some hairs 😁 and also thank you, wolvenkit is amazing can't wait to see improvement

[Traderain]

Do we still need this?

[ja-to]

Fuzzo completely solved the apb/redcloth pipeline. Cloth files (apb) are imported by the Import Utility, and WolvenKit correctly builds collision cache and handles the cooked redcloth in the background. WolvenKit now also reads the collision cache from installed game and can export to raw apb.

Redfur can be handled correctly, but we don't have a tool to import/encode it. rmemr already has a really nice solution to encode redfur from apx format with an additional definition YML for all the in-game properties. I think his project is closed source, but it should be (according to Fuzzo) relatively easy to write a custom non-wcc import function.

[Traderain]

Fuzzo completely solved the apb/redcloth pipeline. Cloth files (apb) are imported by the Import Utility, and WolvenKit correctly builds collision cache and handles the cooked redcloth in the background. WolvenKit now also reads the collision cache from installed game and can export to raw apb.

Redfur can be handled correctly, but we don't have a tool to import/encode it. rmemr already has a really nice solution to encode redfur from apx format with an additional definition YML for all the in-game properties. I think his project is closed source, but it should be (according to Fuzzo) relatively easy to write a custom non-wcc import function.

Hm that seems doable. a form where you select the apx+some fields for the aditional features.