Page 5 of 11 FirstFirst 1234567891011 LastLast
Results 81 to 100 of 201

Thread: PFM Schema Update Thread

  1. #81
    Matmannen's Avatar Ordinarius
    Join Date
    Dec 2012
    Location
    Norrköping, Sweden
    Posts
    738

    Default Re: PFM Schema Update Thread

    I have two updates for you. Tables are abit obscure, but the obscure ones can be used to do some fine effect tuning. Sadly, I was unable to deduct all in audio_abilities_tables.

    EDIT: Seems I needed to take a look at another obscure table while I was at it, so I decided to fis the string names while I was at it.

    Code:
    <table table_name='audio_abilities_tables'
             table_version='5' >
        <field name='key' type='string_ascii' pk='true' />
        <field name='ui_enable_event' type='optstring_ascii' />
        <field name='ui_disable_event' type='optstring_ascii' />
        <field name='ui_event_targetting_start' type='optstring_ascii' />
        <field name='ui_event_targetting_stop' type='optstring_ascii' />
        <field name='ui_select_event' type='optstring_ascii' />
        <field name='enable_event' type='optstring_ascii' />
        <field name='unknown7' type='boolean' />
        <field name='max_distance' type='float' />
        <field name='use_reverb' type='boolean' />
        <field name='unknown10' type='boolean' />
        <field name='wind_up_target_enable_event' type='optstring_ascii' />
        <field name='unknown12' type='boolean' />
        <field name='wind_up_target_max_distance' type='float' />
        <field name='wind_up_target_use_reverb' type='boolean' />
        <field name='unknown15' type='boolean' />
      </table>
    Code:
    <table table_name='audio_ability_phases_tables'
             table_version='1' >
        <field name='group_sound' type='optstring_ascii' />
        <field name='key' type='string_ascii' pk='true' />
        <field name='max_distance' type='float' />
        <field name='start_event' type='optstring_ascii' />
        <field name='stop_event' type='optstring_ascii' />
        <field name='use_reverb' type='boolean' />
        <field name='switch' type='boolean' />
        <field name='looping_group_sound' type='boolean' />
      </table>
    Code:
    <table table_name='area_of_effect_displays_tables'
             table_version='8' >
        <field name='unknown0' type='boolean' />
        <field name='key' type='string_ascii' pk='true' />
        <field name='unknown2' type='boolean' />
        <field name='vfx_central' type='optstring_ascii' />
        <field name='vfx_ring' type='optstring_ascii' />
        <field name='spline_width' type='float' />
        <field name='unknown6' type='int' />
        <field name='unknown7' type='int' />
        <field name='unknown8' type='int' />
        <field name='unknown9' type='int' />
        <field name='unknown10' type='int' />
        <field name='unknown11' type='int' />
        <field name='unknown12' type='boolean' />
        <field name='spline_animation_speed' type='float' />
        <field name='spline_tile_count' type='int' />
        <field name='composite_scene' type='optstring_ascii' />
        <field name='is_targetting_per_entity' type='boolean' />
        <field name='vfx_ring_segment_length' type='int' />
        <field name='use_model_time' type='boolean' />
      </table>
    Last edited by Matmannen; July 12, 2018 at 03:31 AM.

  2. #82

    Default Re: PFM Schema Update Thread

    Rome 2 updated schema

    Code:
    <table table_name='action_results_additional_outcomes_tables'
             table_version='3' >    
        <field name='outcome' type='string_ascii' />
        <field fkey='action_results_tables.key' name='action_result_key' type='string_ascii' />
        <field name='value' type='float' />
        <field fkey='effects_tables.effect' name='effect_record' type='optstring_ascii' />
        <field fkey='campaign_effect_scopes_tables.key' name='effect_scope_record' type='optstring_ascii' />
        <field name='key' type='string_ascii' pk='true' />
        <field name='unknown6' type='boolean' />
        <field name='opportune_failure_weighing' type='string_ascii' />
        <field name='unknown8' type='float' />
        <field name='unknown9' type='float' />
        <field name='unknown10' type='float' />
      </table>
      <table table_name='political_actions_tables'
             table_version='2' >
        <field name='political_action_key' type='string_ascii' />
        <field name='unknown1' type='string_ascii' />
        <field name='unknown2' type='optstring_ascii' />
        <field name='unknown3' type='float' />
      </table>
      <table table_name='unit_category_tables'
             table_version='3' >
        <field name='unknown0' type='string_ascii' />
        <field name='unknown1' type='optstring_ascii' />
        <field name='unknown2' type='float' />
        <field name='unknown3' type='float' />
        <field name='unknown4' type='float' />
        <field name='unknown5' type='int' />
      </table>
      <table table_name='centralised_upgrade_building_level_junctions_tables'
             table_version='1' >
        <field name='unknown0' type='string_ascii' />
        <field name='unknown1' type='string_ascii' />
      </table>
      <table table_name='character_trait_levels_tables'
             table_version='1' >
        <field name='unknown0' type='string_ascii' />
        <field name='unknown1' type='int' />
        <field name='unknown2' type='string_ascii' />
        <field name='unknown3' type='int' />
        <field name='unknown4' type='optstring_ascii' />
      </table>
      <table table_name='culture_subculture_politics_government_types_tables'
             table_version='6' >
        <field name='unknown0' type='string_ascii' />
        <field name='unknown1' type='string_ascii' />
        <field name='unknown2' type='boolean' />
        <field name='unknown3' type='string_ascii' />
        <field name='unknown4' type='string_ascii' />
        <field name='unknown5' type='optstring_ascii' />
        <field name='unknown6' type='optstring_ascii' />
        <field name='unknown7' type='boolean' />
        <field name='unknown8' type='string_ascii' />
        <field name='unknown9' type='optstring_ascii' />
        <field name='unknown10' type='string_ascii' />
        <field name='unknown11' type='optstring_ascii' />
        <field name='unknown12' type='optstring_ascii' />
      </table>
      <table table_name='culture_subculture_character_portraits_tables'
             table_version='0' >
        <field name='unknown0' type='optstring_ascii' />
        <field name='unknown1' type='optstring_ascii' />
        <field name='unknown2' type='string_ascii' />
        <field name='unknown3' type='string_ascii' />
        <field name='unknown4' type='optstring_ascii' />
      </table>
      <table table_name='portrait_types_tables'
             table_version='0' >
        <field name='unknown0' type='string_ascii' />
      </table>
      <table table_name='politics_government_actions_tables'
             table_version='0' >
        <field name='unknown0' type='string_ascii' />
      </table>
      <table table_name='marriage_types_tables'
             table_version='0' >
        <field name='unknown0' type='string_ascii' />
      </table>
    
      <table table_name='political_parties_loyalty_effect_bundles_tables'
             table_version='0' >
        <field name='unknown0' type='string_ascii' />
        <field name='unknown1' type='int' />
      </table>
    
    
      <table table_name='ancillaries_tables'
             table_version='12' >
        <field name='unknown0' type='string_ascii' />
        <field name='unknown1' type='string_ascii' />
        <field name='unknown2' type='string_ascii' />
        <field name='unknown3' type='boolean' />
        <field name='unknown4' type='boolean' />
        <field name='unknown5' type='int' />
        <field name='unknown6' type='boolean' />
        <field name='unknown7' type='int' />
        <field name='unknown8' type='int' />
        <field name='unknown9' type='int' />
        <field name='unknown10' type='int' />
        <field name='unknown11' type='optstring_ascii' />
        <field name='unknown12' type='string_ascii' />
        <field name='unknown13' type='int' />
        <field name='unknown14' type='int' />
        <field name='unknown15' type='int' />
        <field name='unknown16' type='int' />
        <field name='unknown17' type='optstring_ascii' />
      </table>
    Last edited by Dresden; August 09, 2018 at 06:29 PM.

    ----> Website -- Patreon -- Steam -- Forums -- Youtube -- Facebook <----

  3. #83
    Morticia Iunia Bruti's Avatar Praeses
    Join Date
    May 2015
    Location
    Deep within the dark german forest
    Posts
    8,421

    Default Re: PFM Schema Update Thread

    Thank you Dresden for decoding.
    Last edited by Morticia Iunia Bruti; July 12, 2018 at 07:01 PM.
    Cause tomorrow is a brand-new day
    And tomorrow you'll be on your way
    Don't give a damn about what other people say
    Because tomorrow is a brand-new day


  4. #84
    Matmannen's Avatar Ordinarius
    Join Date
    Dec 2012
    Location
    Norrköping, Sweden
    Posts
    738

    Default Re: PFM Schema Update Thread

    I needed to get another one done.

    Code:
    <table table_name='battle_entity_stats_tables'         table_version='2' >
        <field name='key' type='string_ascii' pk='true'  />
        <field name='primary_melee_weapon' type='optstring_ascii' />
        <field name='primary_missile_weapon' type='optstring_ascii' />
      </table>
    Last edited by Matmannen; July 13, 2018 at 12:51 AM.

  5. #85
    Matmannen's Avatar Ordinarius
    Join Date
    Dec 2012
    Location
    Norrköping, Sweden
    Posts
    738

    Default Re: PFM Schema Update Thread

    Nothing fancy here. The bombardment_projectiles_table simply lacked its pk='true' line and I fixed the boolean.

    Code:
    <table table_name='projectile_bombardments_tables'
             table_version='6' >
        <field name='arrival_window' type='float' />
        <field name='bombardment_key' type='string_ascii' pk='true'  />
        <field name='num_projectiles' type='int' />
        <field name='projectile_type' type='string_ascii' />
        <field name='radius_spread' type='float' />
        <field name='start_time' type='float' />
        <field name='launch_source' type='string_ascii' />
        <field name='launch_vfx' type='optstring_ascii' />
        <field name='launch_height' type='int' />
        <field name='audio_type' type='optstring_ascii' />
        <field name='launch_height_underground' type='int' />
        <field name='randomise_launch' type='boolean' />
      </table>

  6. #86

    Default Re: PFM Schema Update Thread

    Code:
    <table table_name='agent_actions_tables'         
    table_version='4' >
        <field fkey='abilities_tables.ability' name='ability' type='string_ascii' pk='true' />
        <field fkey='agents_tables.key' name='agent' type='string_ascii' pk='true' />
        <field fkey='agent_attributes_tables.key' name='attribute' type='string_ascii' pk='true' />
        <field fkey='action_results_tables.key' name='cannot_fail' type='string_ascii' />
        <field fkey='action_results_tables.key' name='critical_failure' type='string_ascii' />
        <field fkey='action_results_tables.key' name='critical_success' type='string_ascii' />
        <field fkey='action_results_tables.key' name='failure' type='string_ascii' />
        <field fkey='action_results_tables.key' name='opportune_failure' type='string_ascii' />
        <field fkey='action_results_tables.key' name='success' type='string_ascii' />
        <field name='localised_action_name' type='string_ascii' />
        <field name='localized_action_description' type='string_ascii' />
        <field fkey='agent_action_message_events_tables.key' name='your_message_events_male' type='optstring_ascii' />
        <field fkey='agent_action_message_events_tables.key' name='your_message_events_female' type='optstring_ascii' />
        <field fkey='agent_action_message_events_tables.key' name='their_message_events_male' type='optstring_ascii' />
        <field fkey='agent_action_message_events_tables.key' name='their_message_events_female' type='optstring_ascii' />
        <field name='unknown15' type='optstring_ascii' />
      </table>
     <table table_name='faction_politics_government_actions_junctions_tables'
             table_version='0' >
        <field name='unknown0' type='string_ascii' />
        <field name='unknown1' type='string_ascii' />
        <field name='unknown2' type='string_ascii' />
        <field name='unknown3' type='string_ascii' />
        <field name='unknown4' type='string_ascii' />
        <field name='unknown5' type='string_ascii' />
        <field name='unknown6' type='int' />
        <field name='unknown7' type='int' />
        <field name='unknown8' type='int' />
      </table>

    ----> Website -- Patreon -- Steam -- Forums -- Youtube -- Facebook <----

  7. #87
    Jake Armitage's Avatar Artifex
    Patrician

    Join Date
    Apr 2011
    Location
    apartment 6
    Posts
    4,694

    Default Re: PFM Schema Update Thread

    ^ Thx Dresden

  8. #88
    Clint_Eastwood's Avatar Tiro
    Join Date
    Sep 2015
    Location
    San Francisco/Los Angeles
    Posts
    276

    Default Re: PFM Schema Update Thread

    Can someone update the start_pos_family_relationships_tables please?

  9. #89
    Morticia Iunia Bruti's Avatar Praeses
    Join Date
    May 2015
    Location
    Deep within the dark german forest
    Posts
    8,421

    Default Re: PFM Schema Update Thread

    Quote Originally Posted by Clint_Eastwood View Post
    Can someone update the start_pos_family_relationships_tables please?
    Is important, if you want use PFM to add childs and spouses to your characters.

    At the moment only doable with Assembly Kit.
    Cause tomorrow is a brand-new day
    And tomorrow you'll be on your way
    Don't give a damn about what other people say
    Because tomorrow is a brand-new day


  10. #90

    Default Re: PFM Schema Update Thread

    Please update schema to see female_character_culture_details_tables, female_character_faction_details_tables and female_character_subculture_details. PFM show them as red.

  11. #91

    Default Re: PFM Schema Update Thread

    I have released schema 113, if PFM's autoupdater is enabled, it will be downloaded automatically the next time PFM runs. Schema 113 features Rome 2's schema up to date and free of obvious unknown values and unopenable tables (except for models_naval_tables). I also included Matmannen's schemas after correcting the unknown values in them and inserting the fkeys that TW Warhammer 1 uses. Since the projectile_bombardments_tables Matmannen submitted uses a newer version number than that used for TW Warhammer 1, I'm going to assume that the schemas they submitted were for TW Warhammer 2, so I can't guarantee the fkeys are correct as I don't have Warhammer 2 and used Warhammer 1's fkey values instead. I also corrected some broken tables for Warhammer 1 although I haven't done a thorough pass over all of them.
    Last edited by Genreless; August 26, 2018 at 06:58 AM. Reason: Fixing formatting errors

  12. #92
    Jake Armitage's Avatar Artifex
    Patrician

    Join Date
    Apr 2011
    Location
    apartment 6
    Posts
    4,694

    Default Re: PFM Schema Update Thread

    ^ Thanks, man!

    Btw, and sorry for the ignorance, why some lines are blue (empty) and that one is red?
    They are someway hardcoded or are they too difficult to "decript"?
    Just a question not a request.
    Last edited by Jake Armitage; August 24, 2018 at 07:28 AM.

  13. #93

    Default Re: PFM Schema Update Thread

    Quote Originally Posted by Jake Armitage View Post
    ^ Thanks, man!

    Btw, and sorry for the ignorance, why some lines are blue (empty) and that one is red?
    They are someway hardcoded or are they too difficult to "decript"?
    Just a question not a request.
    Black tables have a schema available for decoding the table (though this occasionally bugs out and says tables that can't be decoded can).
    Blue tables have at least one empty table in the category.
    Yellow Highlighted tables have a table in the category that is being decoded with a schema for the wrong table version (this is a bug, it should only be happening on the table using the wrong version schema)
    Red tables lack a schema to decode the table.

    I didn't decode models_naval_tables because it contains model data for naval units that doesn't follow a clean enough format for me to find a combination that works in under 120 columns (where I gave up) and I don't know enough about how list columns work to figure out a way to combine the so it can deal with the complex structure of the model data.

    Edit: clarified comment about yellow highlighted table behavior
    Last edited by Genreless; August 26, 2018 at 06:57 AM.

  14. #94
    Jake Armitage's Avatar Artifex
    Patrician

    Join Date
    Apr 2011
    Location
    apartment 6
    Posts
    4,694

    Default Re: PFM Schema Update Thread

    Thx, I appreciate the answer

  15. #95

    Default Re: PFM Schema Update Thread

    Schema 114 is now out. It updates all the formerly blue, red, and yellow tables for Warhammer 1 to be complete and correct (except maybe some of the empty model tables). It also updates all the Warhammer 1 tables up to cai_personalities_technology_researches_tables to be complete and correct. Schema 115 should contain the rest of the Warhammer 1 tables corrected. As always, if you have the latest version of PFM, the autoupdater should download the new schema automatically if you have it run by default.
    Last edited by Genreless; September 06, 2018 at 12:54 AM. Reason: spelling

  16. #96

    Default Re: PFM Schema Update Thread

    Schema 115 is now out. It finished my pass over Warhammer 1's tables so they are now free of unknown values (except for one table) and all have the proper keys. This is as much as I can do for Warhammer 2's tables until I actually get Warhammer 2. If you have version 5.0.2 or newer of PFM, the auto-updater should work for downloading the new schema.

  17. #97

    Default Re: PFM Schema Update Thread

    Schema 116 is now out. It ensures almost all of Attila's tables are free of unknown values and have the proper keys. Those that are still flawed are either not available in Attila, Rome 2, and Warhammer's DAVE or fail to export from the above DAVE versions. Some of these will be corrected later when I go over Shogun 2's tables due to being tables inherited from Shogun 2 or earlier Total War games. As always, if you have version 5.0.2 or newer of PFM, the auto-updater should download the new schema version the next time it runs.
    Last edited by Genreless; September 26, 2018 at 04:50 AM. Reason: grammar

  18. #98
    Jake Armitage's Avatar Artifex
    Patrician

    Join Date
    Apr 2011
    Location
    apartment 6
    Posts
    4,694

    Default Re: PFM Schema Update Thread

    talking about rome 2, is there the possibility to fully decode db > political_action/dilemma/incidents_junction_tables or they are simply hardcoded?
    sorry for the answer but i have no idea about such things.

    thx anyway, your work is greatly appreciated

  19. #99

    Default Re: PFM Schema Update Thread

    Quote Originally Posted by Jake Armitage View Post
    talking about rome 2, is there the possibility to fully decode db > political_action/dilemma/incidents_junction_tables or they are simply hardcoded?
    sorry for the answer but i have no idea about such things.

    thx anyway, your work is greatly appreciated
    If you are referring to the tables: political_actions_dilemma_junctions_tables, political_actions_incidents_junctions_tables, and/or political_actions_mission_junctions_tables, then I unfortunately can't obtain a decoded schema for them. This is because they all use version one of their respective tables, are currently empty, and Rome 2's DAVE encounters an error when it tries exporting those tables. PFM has a decoded version of version two of those tables, but since they are different versions than what Rome 2 uses, I wouldn't count on them working for Rome 2. Also, since Rome 2 has those tables as empty and DAVE can't export them, there is a decent chance that Rome 2 doesn't use those tables anyway.

  20. #100
    Jake Armitage's Avatar Artifex
    Patrician

    Join Date
    Apr 2011
    Location
    apartment 6
    Posts
    4,694

    Default Re: PFM Schema Update Thread

    thank you genreless.

    there is a decent chance that Rome 2 doesn't use those tables anyway: don't know nothing about decoding, but i'm quite sure there is something inside, they should link the fact that you push an intrigue button to dilemmas/incidents tables. Without them there is a missing step that is most probably not surpassable (or at least this i noticed through the trials i've done). Think that cdir tables (the ones for dilemmas/incidents) should be linked to "political_actions" through those blue tabs. without them i haven't been able to link dilemmas/incidents to intrigues.
    Anyway they have been added by this summer's CA political update, and seems strang to me that they did something that is completely empty.
    Hoiwever, as i've already said, i have no knowledge about informatics, so i really can't understand how these kind of processes works.
    Last edited by Jake Armitage; October 01, 2018 at 04:55 AM.

Tags for this Thread

Posting Permissions

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