| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 82 online users.
» 0 Member(s) | 81 Guest(s)
yandex
|
| Latest Threads |
Lifeguard tower addon toy
Forum: REQUESTS
Last Post: daspex
Yesterday, 12:40 PM
» Replies: 3
» Views: 276
|
Need help?
Forum: Developer Help
Last Post: Eager-Player
04-02-2025, 09:38 AM
» Replies: 107
» Views: 5,571
|
Rooms addons
Forum: Room Addons
Last Post: K17
04-01-2025, 06:58 PM
» Replies: 367
» Views: 76,755
|
Jewelry Textures
Forum: Dress Item Textures
Last Post: Russian Vodka
04-01-2025, 04:58 PM
» Replies: 13
» Views: 1,563
|
Real Female Models
Forum: Klub 17 V11 Models
Last Post: Russian Vodka
04-01-2025, 11:42 AM
» Replies: 59
» Views: 13,259
|
Dual Poses
Forum: Klub 17 V11 Poses and sequences
Last Post: Russian Vodka
03-30-2025, 07:43 AM
» Replies: 26
» Views: 4,660
|
|
|
| 3d/Uv Mesh Vertex Blend |
|
Posted by: Richter Belmont - 07-24-2024, 08:53 PM - Forum: Raistin Kane - Research Center
- No Replies
|
 |
CollaTKane already export 3d mesh vertex blend (called shape key in blender)...
but do not support uv mesh blend: I never seen such thing in blender and do not know if such paremter exist for .dae file.
Hook5 won't render mesh that use uv mesh blend.
3d mesh vertex blend are blend that "reshape" the value of the mesh 3d vertex, while uv mesh blend are blend that "reshape" the value of the mesh uvmap vertex.
For using these feature, your mesh must be of "SkinPolygonGeometry" type. (or MeshGroup)
If your mesh is of "PolygonGeometry" type, you simply need to change its node type to "SkinPolygonGeometry".
Code: //TPolygonGeometry :local_R9Crown036_MESH . {[/color]
[color=#000000]TSkinPolygonGeometry :local_R9Crown036_MESH . {[/color]
[color=#000000]// TNode.SNode SPolygonGeometry :local_SR9Crown036_MESH;[/color]
[color=#000000]TNode.SNode SSkinPolygonGeometry :local_SR9Crown036_MESH;[/color]
[color=#000000]TGeometry.Shader RenderShader :local_R9Crown036_MATERIAL;[/color]
[color=#000000]TNode.Parent TTransform :local_R9Crown036_NODE003;[/color]
[color=#000000]TNode.BoundingSphere Spheref( 0, 0, 0, 1.000000027e+016 );[/color]
[color=#000000]Object.Name "R9Crown036_mesh";[/color]
[color=#000000]};[/color]
[color=#000000]...[/color]
[color=#000000]//SPolygonGeometry :local_SR9Crown036_MESH . {[/color]
[color=#000000]SSkinPolygonGeometry :local_SR9Crown036_MESH . {[/color]
[color=#000000]SPolygonGeometry.PrimCount I32(9068);[/color]
[color=#000000]SPolygonGeometry.IndexArray Array_I32 [ ... ];[/color]
[color=#000000]SPolygonGeometry.VertexData [ ... ];[/color]
[color=#000000]SPolygonGeometry.VertexArray Array_Vector3f [ ... ];[/color]
[color=#000000]SPolygonGeometry.NormalArray Array_Vector3f [ ... ];[/color]
[color=#000000]Object.Name "SR9Crown036_mesh";[/color]
[color=#000000]};
BlendControl are node that control the "influence" of the blend.(how much effect it has)
We often link the BlendControl to the game slider.
It is possible to link the same BlendControl to multiple mesh.
Exemple:
Code: BlendControl :local_stomachBulgeX_blendCtrl Object.Name "stomach_bulge_x";
For each of your mesh 3d vertex blend, you gonna need to link a BlendControl node to its "SSkinPolygonGeometry.BlendControl" array.
Code: SSkinPolygonGeometry.BlendControl [ BlendControl :local_stomachBulgeX_blendCtrl ];
For each of your mesh uvmap vertex blend, you gonna need to link a BlendControl node to its "SSkinPolygonGeometry.BlendTexCoordControl" array.
Code: SSkinPolygonGeometry.BlendTexCoordControl [ BlendControl :local_pupilLDilation_blendCtrl ];
[i]For meshgroup, it is MeshData.BlendControl and MeshData.BlendTexCoordControl[/i]
For each element in SSkinPolygonGeometry.BlendControl array, you gonna need to link a VertexDataVector3f node to the SPolygonGeometry.VertexData array.
These must have a number of vertex equal to the mesh 3d vertex.(SPolygonGeometry.VertexArray)
Their value must be relative to the mesh 3d vertex. (newValue - oldValue = relativeValue)
For exemple, if your mesh 3d vertex is (0.1, 0.7, 0.3) and want your blend to change its value to (0.4, 0.3, 0.2), you gonna write (0.3, -0.4, -0.1).
The VertexData.Usage value of the VertexDataVector3f must be equal to:
655360 + the element position in the SSkinPolygonGeometry.BlendControl array.
The "position" of first element is 0, second is 1, third is 2, etc.
Code: VertexDataVector3f :local_stomachBulgeX_vertexData . {[/i][/color]
[color=#000000][i]VertexDataVector3f.DataArray Array_Vector3f [ ... ];[/i][/color]
[color=#000000][i]VertexData.Usage U32(655360);[/i][/color]
[i][color=#000000]};
For each element in SSkinPolygonGeometry.BlendTexCoordControl array, you gonna need to link a VertexDataVector2f node to the SPolygonGeometry.VertexData array.
These must have a number of vertex equal to the mesh uvmap vertex.
[i]Unleast your using a meshgroup, your mesh already require its number of uvmap vertex to be equal to its number of 3d vertex.[/i]
Their value must be relative to the mesh uvmap vertex. (newValue - oldValue = relativeValue)
For exemple, if your mesh uvmap vertex is (1, 0.5) and want your blend to change its value to (0.3, 1), you gonna write (-0.7, 0.5).
The VertexData.Usage value of the VertexDataVector2f must be equal to:
786432 + the element position in the SSkinPolygonGeometry.BlendTexCoordControl array.
The "position" of first element is 0, second is 1, third is 2, etc.
Code: VertexDataVector2f :local_eyePupilLDilation_vertexData . {[/i][/color]
[color=#000000][i]VertexDataVector2f.DataArray Array_Vector2f [ ... ];[/i][/color]
[color=#000000][i]VertexData.Usage U32(786432);[/i][/color]
[i][color=#000000]};
|
|
|
| AcRoom hybrid Light (bring support for both HS and no-HS user) |
|
Posted by: Richter Belmont - 07-24-2024, 08:49 PM - Forum: Raistin Kane - Research Center
- No Replies
|
|
Like people making room should already know it, a "light source" must be writed in the AcRoom...or else, only a black screen will be show.
This one is the default and will make sure all room using have light.
Code: [/color]
[color=#000000]AppImportScene . {[/color]
[color=#000000].NodeName "Lights" + :room;[/color]
[color=#000000].ParentPath "/RoomRoot";[/color]
[color=#000000].SceneFile "Shared/Room/lights01";[/color]
[color=#000000]};
If someone want to bring the special light feature of the HairSizer mod, the precedent script must be replaced by:
Code: [/color]
[color=#000000]AppImportScene . {[/color]
[color=#000000].NodeName "Lights" + :room;[/color]
[color=#000000].ParentPath "/RoomRoot";[/color]
[color=#000000].SceneFile "Shared/Room/lights01mod";[/color]
[color=#000000]};[/color]
[color=#000000]AppPoseBlend . {[/color]
[color=#000000].PoseBlend "SFHlight_poseBlend";[/color]
[color=#000000]};[/color]
[color=#000000]AppPoseBlend . {[/color]
[color=#000000].PoseBlend "FLLlight_poseBlend";[/color]
[color=#000000]};[/color]
[color=#000000]AppPoseBlend . {[/color]
[color=#000000].PoseBlend "BLlight_poseBlend";[/color]
[color=#000000]};[/color]
[color=#000000]AppPoseBlend . {[/color]
[color=#000000].PoseBlend "AMBlight_poseBlend";[/color]
[color=#000000]};[/color]
[color=#000000]AppPoseBlend . {[/color]
[color=#000000].PoseBlend "SFHrot_poseBlend";[/color]
[color=#000000]};[/color]
[color=#000000]AppPoseBlend . {[/color]
[color=#000000].PoseBlend "FLLrot_poseBlend";[/color]
[color=#000000]};[/color]
[color=#000000]AppPoseBlend . {[/color]
[color=#000000].PoseBlend "BLrot_poseBlend";[/color]
[color=#000000]};
...The problem with this is that if the user do not have the the HairSizer light, the room will be blacked out. (=same as not having light)
People may considering writing both light source...but this will make light to become way to bright and blind all HairSiser user.
So the solution was to write both light source...and adding a element that will "desactivate" the default light one if the user have HairSizer light.
So there it is.
By writing this as your light script, you you bring up support for both user with HairSizer light and the one wihout it.(except the blind effect no more occur  )
Code: AppImportScene . {[/color]
[color=#000000].NodeName "Lights" + :room;[/color]
[color=#000000].ParentPath "/RoomRoot";[/color]
[color=#000000].SceneFile "Shared/Room/lights01";[/color]
[color=#000000]};[/color]
[color=#000000]AppImportScene . {[/color]
[color=#000000].NodeName "LightsHS" + :room;[/color]
[color=#000000].ParentPath "/RoomRoot";[/color]
[color=#000000].SceneFile "Shared/Room/lights01mod";[/color]
[color=#000000]};[/color]
[color=#000000]AppReplaceSkeleton . {[/color]
[color=#000000].SourcePath "/Lights" + :room + "/lights_group";[/color]
[color=#000000].SourceRootPath "/Lights" + :room + "/lights_group";[/color]
[color=#000000].TargetPath "/LightsHS" + :room + "/lights_group";[/color]
[color=#000000].TargetRootPath "/LightsHS" + :room + "/lights_group";[/color]
[color=#000000]};
|
|
|
|
| ActiveMod Texture for Everthing |
|
Posted by: Richter Belmont - 07-24-2024, 08:46 PM - Forum: Raistin Kane - Research Center
- No Replies
|
|
Since I readed about Addon Toy having not been ActiveModed yet...well I just decided to check it out.
Took me not even 5 minute to figure out the mod*.bs line usage...but yet maybe a hour or two to get result in-game (was overlooking the fact that my ActiveMod texture was in a subfolder) [To see links please log-in or register here]
I case you don't know it, having the texture in your addon is not require when you use ActiveMod texture.
So if you use ActiveMod, you can delete the texture and the .txf from the addon
So there we go.
If you look into one of the various mod*.bs file (the original mod.bs simply got divided), you will see line, each containing a group of 3 string.
Each group represent the information for a ActiveMod Texture.
Code: "Shared/Item/R9Toy309_Object01" , "R9Toy309_Object01" , "Tool38309_ToolDescription" ,[/color]
[color=#000000]"Shared/Item/R9Toy309_Object02" , "R9Toy309_Object02" , "Tool38309_ToolDescription" ,[/color]
[color=#000000]"Shared/Item/R9Toy309_Object03" , "R9Toy309_Object03" , "Tool38309_ToolDescription" ,
The first string represent the path of the original texture (in addon) and so the one written in your scene file.
Code: ...[/color]
[color=#000000]FileObject :local_16 FileObject.FileName "Shared/Item/R9Toy309_Object01";[/color]
[color=#000000]...[/color]
[color=#000000]FileObject :local_27 FileObject.FileName "Shared/Item/R9Toy309_Object02";[/color]
[color=#000000]...[/color]
[color=#000000]FileObject :local_38 FileObject.FileName "Shared/Item/R9Toy309_Object03";
The Second string represent the path of the ActiveMod texture.
Please note that you can add subfolder to the name.
If I was using png image for example:
Code: "R9Toy309_Object01" = /Mod/ActiveMod/R9Toy309_Object01.png[/color]
[color=#000000]"R9Toy309/Item/R9Toy309_Object02" = /Mod/ActiveMod/R9Toy309/Item/R9Toy309_Object02.png
The last string represent your object "script bloc" name.
For tool, you will find it in your "Scripts/Shared/Common/TcTools*.bs" file
For hair and cloth, inside "Scripts/Dress/DcDress*.bs"
For room, "Script/Luder/Common/Room*.bs".
Taking my Syringe Addon Toy for example...
Code: ToolDescription :Tool38309_ToolDescription . { //HERE THE SCRIPT BLOC NAME[/color]
[color=#000000].Category "Cat_Special";[/color]
[color=#000000].ToolID :toolBase + I32(38309);[/color]
[color=#000000].ToolIconID I32(39309);[/color]
[color=#000000].SceneScriptFile [ "Item/AcTool38309" , "Tool38309" ];[/color]
[color=#000000].ToolGroupName "Tool38309:tool_group";[/color]
[color=#000000]...[/color]
[color=#000000]};
That's pretty all you need. 
|
|
|
|
| Adding Extra Hair Color Slider |
|
Posted by: Richter Belmont - 07-24-2024, 08:41 PM - Forum: Raistin Kane - Research Center
- No Replies
|
|
Modders should know it, making hair work with the default game hair color slider is a real pain.
You need to create layer files, link you texture to it, write DressCmd using these layer and [To see links please log-in or register here] ...
For other dress type however, thing are way more simple.
DressCmd using the tex2d your scene as target.
So why not make thing as simple for hair?
I added a extra hair color slider for making the required scripts for color slider as simple of everything other type of dress for hair.
The script should be added to \Scripts\Shared\Person\CcPersonDefaultBody.bs
Code: CustomParameter :Parameter_DressWigColor . {[/color]
[color=#000000].ParamID I32(401);[/color]
[color=#000000].IconID I32(3599);[/color]
[color=#000000].ParamName "DressWigColor";[/color]
[color=#000000].ParamDescription "Hair Color:";[/color]
[color=#000000].CategoryID :Cat_Body;[/color]
[color=#000000].ParamType CustomParamType .HSV;[/color]
[color=#000000].DressZoneID I32(15);[/color]
[color=#000000].DefaultAddHSV ( I32(0) , I32(0) , I32(0) );[/color]
[color=#000000].DefaultMulHSV ( I32(1) , I32(1) , I32(1) );[/color]
[color=#000000].SliderDefault F32(0);[/color]
[color=#000000].LookAt "Person" + :person + "Anim:Model01:head_joint01";[/color]
[color=#000000].LookAtID :LookAtHair;[/color]
[color=#000000]};
As for the requirement for your addon hair dcdress_*.bs file, it's the same as other dress type. (except .ParamID use I32(0) instead of 2)
Example:
Code: .SceneScriptFile [ :HairBaseDir + "AcR9Hair007" , :P + "R9Hair007" ];[/color]
[color=#000000].CmdArray [ DressCmd . {
.Target :P + "R9Hair007:XXXX"; //this XXXX is actually the name of a Texture2d node in the scene file
.ParamID I32(0);
.Attr @ TransformLayer .ColorAddHSV;
.Value @ ( I32(0) , I32(0) , I32(0) );
};
];
|
|
|
|
|
