0 of 0
About this mod
Kazified port of kartoffels' UniqueTav mod - Features: Unique body models, unique textures for face and body (Tattoo, Makeup, Glowmap) and new VT-enabled materials. Huge credits to kartoffels for the original structure.
- Requirements
- Permissions and credits
- Changelogs
Kazified port of kartoffels' UniqueTav mod - Features: Unique body models, unique textures for face and body (Tattoo, Makeup, Glowmap) and new VT-enabled materials. Huge credits to kartoffels for the original structure. Ty to Volno for the Tattoo image(s)
INCOMPATIBLE WITH NORMAL UNIQUE TAV PAK - USE ONLY ONE
However it IS compatible with all the various Unique-Tav DATA files (Though for body textures this requires converting the CLEA,NM,HMVY into a singular GTP/S)
WHEN INSTALLING DATA FILES - YOU NOW MUST RESTART THE GAME TO SEE CHANGES
This is because of how the VT batching works
"WHY USE THIS???" - You, maybe
Kaz Virtual Tav is essentially an expansion and future proofing for the framework you've
already come to know and love, I worked with Kart to make sure things
would be kept consistent while also allowing for access to new shaders that were previously unusable. The biggest draw in this vein is the base body shader we can now utilize as it contains the exact same triple channel tattoo atlas capabilities in addition to a vertex mask compatible glow map which effectively acts as a 4th tattoo channel if configured to, it also has restored the use of vitiligo, freckles, and wrinkles. The usage of VirtualTexture compression allows for full overhauls to
upscale farther than previously possible while retaining a reasonable
filesize. (I've run an 8k Tattoo/GM to test with 4k Body textures)
Differences TL;DR is as follows, wider range of shaders for creators, additional map for glowing tattoos, restored freckles, vitiligo all in the same setup and structure you know and love (with minor folder location changes)
Required mods and files:
BG3 SE
ModFixer
How to use (without creating your own assets)
Install via BG3MM and place at the end of your load order
How to use to create your own assets
Usage almost identical to UT by kartoffel with a few exceptions:
Difference No.1
Due to the nature of virtual textures, we are required to pack with LSLIB - They will not work if packed via any other method
Difference No.2
We have a new map (GM) - the file must be named "UVTT_KAZ_GlowMap_GM.DDS" and must be Bc1/Dxt1 compression (docu coming soon)
GM located here
Difference No.3
We now utilize VirtualTextures for our body materials (CLEA,NM,HMVY) - these are generated via LSLIB (post version 1.19.3) but you do NOT need LSLIB to simply RUN this pak, only to edit/generate VT files (Docu also coming soon)
GTP/GTS files are broken up by RACE and M/F - you MUST match the GTP/GTS name that is defined in the mappings file, to keep this consistent and easy I have created them - each corresponds to a race with the racecode (3 letters) followed by M or F
I have quick generation assets coming soon so you dont need to worry about mapping configuration.
Acceptable GTP/GTS filenames for overrides
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGTYF.gts"
"GTP": "Public/unique_tav/Assets/VirtualTextures/KazGTYF.gtp" <= to save on time im adding this once *know that you need a gtp for EVERY gts
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGTYM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazTIFF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazTIFM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazNRMF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazNRMM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHRCM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHRCF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHFLM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHFLF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGNOM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGNOF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazDWRM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazDWRF.gts"
GTP/GTS files located here *NOTE* you need BOTH a .gtp AND a .gts with the SAME name
Difference No.4
We have access to vastly more shaders than what we do when restricted to exclusively non-vt shaders. Any shader setup to take skin GTP/GTS files is easy to swap to with minor (and sometimes none at all) editing - HOWEVER there are two types of shaders usable via VirtualTextures : Those that support skin and internally are comprised of CLEA,NM,HMVY and then there are shaders that support non-skin PBR and are comprised of ALBEDO,NM,PM these two types CANNOT be changed out as the CLEA and ALBEDO are structurally different as well as are the HMVY and PM
image credit : kartoffels
INCOMPATIBLE WITH NORMAL UNIQUE TAV PAK - USE ONLY ONE
However it IS compatible with all the various Unique-Tav DATA files (Though for body textures this requires converting the CLEA,NM,HMVY into a singular GTP/S)
WHEN INSTALLING DATA FILES - YOU NOW MUST RESTART THE GAME TO SEE CHANGES
This is because of how the VT batching works
"WHY USE THIS???" - You, maybe
Kaz Virtual Tav is essentially an expansion and future proofing for the framework you've
already come to know and love, I worked with Kart to make sure things
would be kept consistent while also allowing for access to new shaders that were previously unusable. The biggest draw in this vein is the base body shader we can now utilize as it contains the exact same triple channel tattoo atlas capabilities in addition to a vertex mask compatible glow map which effectively acts as a 4th tattoo channel if configured to, it also has restored the use of vitiligo, freckles, and wrinkles. The usage of VirtualTexture compression allows for full overhauls to
upscale farther than previously possible while retaining a reasonable
filesize. (I've run an 8k Tattoo/GM to test with 4k Body textures)
Differences TL;DR is as follows, wider range of shaders for creators, additional map for glowing tattoos, restored freckles, vitiligo all in the same setup and structure you know and love (with minor folder location changes)
Required mods and files:
BG3 SE
ModFixer
How to use (without creating your own assets)
Install via BG3MM and place at the end of your load order
How to use to create your own assets
Usage almost identical to UT by kartoffel with a few exceptions:
Difference No.1
Due to the nature of virtual textures, we are required to pack with LSLIB - They will not work if packed via any other method
Difference No.2
We have a new map (GM) - the file must be named "UVTT_KAZ_GlowMap_GM.DDS" and must be Bc1/Dxt1 compression (docu coming soon)
GM located here
`...\Baldurs Gate 3\Data\Generated\Public\Shared\Assets\unique_tav\BODY\GLOWY\UVTT_KAZ_GlowMap_GM.DDS`
Difference No.3
We now utilize VirtualTextures for our body materials (CLEA,NM,HMVY) - these are generated via LSLIB (post version 1.19.3) but you do NOT need LSLIB to simply RUN this pak, only to edit/generate VT files (Docu also coming soon)
GTP/GTS files are broken up by RACE and M/F - you MUST match the GTP/GTS name that is defined in the mappings file, to keep this consistent and easy I have created them - each corresponds to a race with the racecode (3 letters) followed by M or F
I have quick generation assets coming soon so you dont need to worry about mapping configuration.
Acceptable GTP/GTS filenames for overrides
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGTYF.gts"
"GTP": "Public/unique_tav/Assets/VirtualTextures/KazGTYF.gtp" <= to save on time im adding this once *know that you need a gtp for EVERY gts
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGTYM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazTIFF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazTIFM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazNRMF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazNRMM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHRCM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHRCF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHFLM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazHFLF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGNOM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazGNOF.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazDWRM.gts"
"GTS": "Public/unique_tav/Assets/VirtualTextures/KazDWRF.gts"
GTP/GTS files located here *NOTE* you need BOTH a .gtp AND a .gts with the SAME name
`...\Baldurs Gate 3\Data\Public\unique_tav\Assets\VirtualTextures\FILENAME`
Difference No.4
We have access to vastly more shaders than what we do when restricted to exclusively non-vt shaders. Any shader setup to take skin GTP/GTS files is easy to swap to with minor (and sometimes none at all) editing - HOWEVER there are two types of shaders usable via VirtualTextures : Those that support skin and internally are comprised of CLEA,NM,HMVY and then there are shaders that support non-skin PBR and are comprised of ALBEDO,NM,PM these two types CANNOT be changed out as the CLEA and ALBEDO are structurally different as well as are the HMVY and PM