Quote:
Originally Posted by gap
Let me give you an example of what I mean for "modular" models. Let's say that we are importing different throwers and DC marks in game. As long as we store them in the same file, there is no need that we import each DC model two times (one for the charge loaded on the thrower and one for the actual ammo depth charge): the same mesh can be linked both to the thrower model and to the DC ammo node. This approach will be very useful since your mod features different thrower and DC marks: using it we can create many combinations by still keeping file size acceptable. Moreover, by keeping the harbor mesh saparate from the DC mesh, we can do harbors to disappear once the DC enters in the water using the visible underwater render controller. I hope I am making myself clear...  |
I have meant the following:
In Stock a DC Node in the DC_R_KG.dat is structured in the following order:
DCRack
-> DCRack_base_L
-> DCRack_barrel01
-> SHD_DCRack_barrel01
-> DCRack_BarrelFall01
-> SHD_DCRack_BarrelFall01
-> DCRack_BarrelFall
-> SHD_DCRack_BarrelFall
-> crik
-> stopper
-> parghie
-> SHD_DCRack_base_L
-> DC_man
-> DC_man_cask
My question was if you have structured your models that the existing 3D-models are replaced through these and work so or whether the file structure is built up differently.
Quote:
|
As long as we store them in the same file, there is no need that we import each DC model two times (one for the charge loaded on the thrower and one for the actual ammo depth charge):
|
For me that sentence sounds like that isn´t the case, which would be an improvement in keeping the filesize small if models could be used more than once
Quite apart from that I´m always thankful for any help and suggestion in improving the mod an my knowledge of the game so I´m happy that a person with your know how want to help me
