Results 1 to 9 of 9

Thread: Skin And texture problem,

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Skin And texture problem,

    Hello Again, I sorted out my last problem of actually adding the units and cards, Of "Roman_Veteran.cas" KLA imperial 2.0, but when i add the skin and texture straight from Model_unit, it looks JUST like a normal triarii on the battlefield, nothing has changed.

    So what im wanting is, to you guys to tell me if anything is wrong with my descr model battle etc :

    type roman_veteran
    skeleton fs_slow_spearman ; combat spear
    indiv_range 40
    texture romans_julii, data/models_unit/textures/Roman_Veteran.tga
    texture romans_brutii, data/models_unit/textures/unit_roman_triarii_brutii.tga
    texture romans_scipii, data/models_unit/textures/unit_roman_triarii_scipii.tga
    texture romans_senate, data/models_unit/textures/unit_roman_triarii_senate.tga
    model_flexi_m data/models_unit/Roman_Veteran.cas, 15
    model_flexi_m data/models_unit/Roman_Veteran.cas, 30
    model_flexi_m data/models_unit/Roman_Veteran.cas, 40
    model_flexi data/models_unit/Roman_Veteran.cas, max
    model_sprite romans_senate, 60.0, data/sprites/romans_senate_roman_triarii_sprite.spr
    model_sprite romans_scipii, 60.0, data/sprites/romans_scipii_roman_triarii_sprite.spr
    model_sprite romans_brutii, 60.0, data/sprites/romans_brutii_roman_triarii_sprite.spr
    model_sprite romans_julii, 60.0, data/sprites/romans_julii_roman_triarii_sprite.spr
    model_tri 400, 0.5f, 0.5f, 0.5f

    Can someone tell me whats wrong with this, as the skin/texture is not working, its just the normal triarii skin.

    my dictionary for it is roman_veterans

    Roman_Veteran.cas
    Roman_Veteran.tga

    thanks if i sort this out, i can do the whole pack, just im confused on whats wrong with this -,-

    Last edited by Martin N; March 05, 2008 at 05:22 AM.

  2. #2

    Default Re: Skin And texture problem,

    You need to slow down and read carefully some instructions first. Or at least ask before you do odd things. The title of the above entry has clearly been changed (to roman_veteran). As with the EDU, why in heaven do you change those titles? Those are important for the game and are the internal names only. You don`t see those in game. Furthermore, they are related to other files and if you change one title you`ll need to edit other texts too. Leave those as they are if you only want to change the aspect of the unit.
    In your case, you`ve changed the DMB title, but have you also changed the soldier entry in EDU to lead to the new title? Of course, these steps are completely futile as I`ve said. I was just underlining what might be wrong.

    I also suggest you keep the whole discussion in only one thread. It`s hard to follow all of them.

  3. #3

    Default Re: Skin And texture problem,

    i see florin, thankyou for your responce, i will try that now. i did it this way editing all those files as thats what it said to do in tutorials, oh well the hallmark of a beginner is never good i apoligize for the other thread, it was about a diff subject

  4. #4

    Default Re: Skin And texture problem,

    Well, good luck! Post again if needed. About the other thread. You may think it was a different subject, but it`s the same actually. You learning how to implement a new unit with all there is to it. You need to develope a basic understanding of how these files work and after that you`ll find it easier to understand the rest.

    EDIT: About the units cards. Do you have new ones for them? If you do you`d need to edit some text, otherwise the vanilla files will be loaded because those are packed. Basically you edit the entry in export_units and change what is in the brackets. For example:
    Code:
    ¬----------------
    
    {new_roman_hastati}	Hastati
    
    {new_roman_hastati_descr}
    Hardy\nSapping Ability\n\nHastati are among the younger men in an early Republican Legion, and form the front line in any battle. They are supposed to wear down an enemy and hold him before the next Roman battle line attacks and carries on the fight. They are, as a result, capable troops in their own right.\n\nThey are armed with two pila that are thrown at the enemy at close range before they close to fight hand-to-hand. They are equipped with a sword, a bronze helmet, a large shield and a breastplate. The pilum (plural, pila) is a cleverly designed spear with a soft iron shaft behind the point; it bends on impact so that it can’t be thrown back and if it’s stuck in someone or something it is a real hindrance to movement.\n\nHistorically, hastati spent their own money on their equipment and often couldn’t afford anything much better. This, along with the age and property requirements, was why they fought as hastati.
    
    {new_roman_hastati_descr_short}
    Hastati fight as the leading edge of a Legion, wearing the enemy down for the next wave of attackers.
    
    ¬----------------
    Then go to the EDU entry and change the line for the dictionary to reflect the new name in export_units. For example:
    Code:
    type             roman hastati
    dictionary       new_roman_hastati      ; Hastati
    category         infantry
    class            light
    voice_type       Light_1
    soldier          roman_hastati, 40, 0, 1
    attributes       sea_faring, hide_forest, can_sap
    formation        1, 2, 2, 3, 4, square
    stat_health      1, 0
    stat_pri         11, 2, pilum, 35, 2, thrown, blade, piercing, spear, 25 ,1
    stat_pri_attr    prec, thrown ap
    stat_sec         7, 2, no, 0, 0, melee, simple, piercing, sword, 25 ,1
    stat_sec_attr    no
    stat_pri_armour  5, 4, 5, metal
    stat_sec_armour  0, 1, flesh
    stat_heat        3
    stat_ground      2, 0, 0, 0
    stat_mental      6, normal, trained
    stat_charge_dist 30
    stat_fire_delay  0
    stat_food        60, 300
    stat_cost        1, 440, 170, 50, 70, 440
    ownership        roman
    You then need to rename the ui cards proper. They need to contain the name of what is next to the dictionary entry in EDU. In the example above:
    new_roman_hastati

    You need to have two cards. One should be named according to the example:
    new_roman_hastati_INFO.tga
    and it goes in this location:
    Rome - Total War\data\UI\UNIT_INFO\ROMANS_JULII

    and the other should be named:
    #new_roman_hastati.tga
    and it goes in this location:
    Rome - Total War\data\UI\UNITS\ROMANS_JULII

    Note: those locations do not exist in the RTW vanilla folder so you`ll have to create them.
    Last edited by florin80; March 05, 2008 at 08:58 AM.

  5. #5

    Default Re: Skin And texture problem,

    Quote Originally Posted by florin80 View Post
    Well, good luck! Post again if needed. About the other thread. You may think it was a different subject, but it`s the same actually. You learning how to implement a new unit with all there is to it. You need to develope a basic understanding of how these files work and after that you`ll find it easier to understand the rest.

    EDIT: About the units cards. Do you have new ones for them? If you do you`d need to edit some text, otherwise the vanilla files will be loaded because those are packed. Basically you edit the entry in export_units and change what is in the brackets. For example:
    Code:
    ¬----------------
    
    {new_roman_hastati}    Hastati
    
    {new_roman_hastati_descr}
    Hardy\nSapping Ability\n\nHastati are among the younger men in an early Republican Legion, and form the front line in any battle. They are supposed to wear down an enemy and hold him before the next Roman battle line attacks and carries on the fight. They are, as a result, capable troops in their own right.\n\nThey are armed with two pila that are thrown at the enemy at close range before they close to fight hand-to-hand. They are equipped with a sword, a bronze helmet, a large shield and a breastplate. The pilum (plural, pila) is a cleverly designed spear with a soft iron shaft behind the point; it bends on impact so that it can’t be thrown back and if it’s stuck in someone or something it is a real hindrance to movement.\n\nHistorically, hastati spent their own money on their equipment and often couldn’t afford anything much better. This, along with the age and property requirements, was why they fought as hastati.
    
    {new_roman_hastati_descr_short}
    Hastati fight as the leading edge of a Legion, wearing the enemy down for the next wave of attackers.
    
    ¬----------------
    Then go to the EDU entry and change the line for the dictionary to reflect the new name in export_units. For example:
    Code:
    type             roman hastati
    dictionary       new_roman_hastati      ; Hastati
    category         infantry
    class            light
    voice_type       Light_1
    soldier          roman_hastati, 40, 0, 1
    attributes       sea_faring, hide_forest, can_sap
    formation        1, 2, 2, 3, 4, square
    stat_health      1, 0
    stat_pri         11, 2, pilum, 35, 2, thrown, blade, piercing, spear, 25 ,1
    stat_pri_attr    prec, thrown ap
    stat_sec         7, 2, no, 0, 0, melee, simple, piercing, sword, 25 ,1
    stat_sec_attr    no
    stat_pri_armour  5, 4, 5, metal
    stat_sec_armour  0, 1, flesh
    stat_heat        3
    stat_ground      2, 0, 0, 0
    stat_mental      6, normal, trained
    stat_charge_dist 30
    stat_fire_delay  0
    stat_food        60, 300
    stat_cost        1, 440, 170, 50, 70, 440
    ownership        roman
    You then need to rename the ui cards proper. They need to contain the name of what is next to the dictionary entry in EDU. In the example above:
    new_roman_hastati

    You need to have two cards. One should be named according to the example:
    new_roman_hastati_INFO.tga
    and it goes in this location:
    Rome - Total War\data\UI\UNIT_INFO\ROMANS_JULII

    and the other should be named:
    #new_roman_hastati.tga
    and it goes in this location:
    Rome - Total War\data\UI\UNITS\ROMANS_JULII

    Note: those locations do not exist in the RTW vanilla folder so you`ll have to create them.


    Yeh ive got both cards for every skin.

    So BASICally. go to export units, change to new_roman_hastati, so put new next to the name of the card i wanna change ? then add the cards to the UI folder. i see

  6. #6

    Default Re: Skin And texture problem,

    Yes, but I used roman_hastati as an example. I don`t know what unit you want to edit exactly. The idea was to change the internal name so that the game won`t look for the vanilla cards. Don`t forget to change all the 3 entries inside the brackets in export_units. And don`t leave spaces inside those brackets. If you want to separate words use a _
    Also, the path above does not exist as such. The vanilla cards and that path are part of a pak file that`s harder to edit. A longer process too. So you need to create those folders yourself following the path I gave.

  7. #7

    Default Re: Skin And texture problem,

    WOOT! 3 days of hard work for nothing...all i had to do was change 1 lines lol....well anyways it works, and there looking awesome,

    How do i edit the vannila unit card florin ? as i added the unit card to romans_julii and it didnt do it like i should, do i have to remove the previous hastati one before this one will work ? if so, how do i find the hidden files ?

  8. #8

    Default Re: Skin And texture problem,

    finally i got em working, and now know how to do any unit, thanks man atleast theres some helpful and honest people left in this world i got one error on a peasant out of about 30, because i did auxillia instead of auxilia -.0 oh well no harm done, thanks again

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •