Hi, before make the jump I need to get a confirmation if it's possible to do and manage in long term process. So what I want to make (it's an extract). ---------------------------------------- I have several category and several car by category. My structure will be this one (ModDev view in the folder Vehicles) MY MOD - Category 1 (GT1) -- Car 1 (Aston Martin DBR9) ---- Year1 Team Group (2007) ------ Team 1 ------ Team 2 ------ Team 3 ---- Year2 Team Group (2008) ------ Team 1 ------ Team 2 -- Car 2 (Corvette C6R) ---- Year3 Team Group (2008) ------ Team 1 - Category 2 (GT2) -- Car 1 (F430) ---- Team 1 ---- Team 2 -- Car 2 (P997) ---- Team 1 ---- Team 2 ---- Team 3 How I expect to structure my components. ----------------------------------------- I want to make one component by car. ans have clear separated mas to manage the part of a car. The aim is to manage each car independently. Example: -- Aston Martin DBR9 - GT1 = ---- GFX_astonDBR9.mas = DDS+GMT+GEN ---- PHYSX_astonDBR9.mas = TIRES+HDV+ENGINE+SUSP+GEAR ... ---- SND_astonDBR9.mas = SFX+WAV (is it possible ? seems non due to the separation of sound component in packaging tool). ---- 2007_DBR9_TEAM_01 (including VEH+DDS) ---- 2007_DBR9_TEAM_02 (including VEH+DDS) ---- 2007_DBR9_TEAM_03 (including VEH+DDS) ---- 2008_DBR9_TEAM_01 (including VEH+DDS) ---- 2008_DBR9_TEAM_02 (including VEH+DDS) -- Corvette C6R - GT1 = ---- GFX_corvetteC6R.mas = DDS+GMT+GEN ---- PHYSX_corvetteC6R.mas = TIRES+HDV+ENGINE+SUSP+GEAR ... ---- SND_corvetteC6R.mas = SFX+WAV (is it possible ? seems non due to the separation of sound component in ---- 2008_C6R_TEAM_01 (including VEH+DDS) -- Common GT1 elements = ---- GFX_GT1_COMMON.mas = common textures like leds and stickers ---- PHYSX_GT1_COMMON.mas = Headphysics Common CARS elements = -- GFX_COMMON.mas = common textures to all cars GT1 + GT2 (like chrome texture) And same structure for the GT2 cars. QUESTION 1/ Is this way of grouping the mas and structure is correct to make a components and mod makable? What I need to manage with updates and questions. -------------------------------------------------- Step 1/ I create my first car with this structure. I regroup the car mas with only one team in a component named : GT1_AstonMartinDBR9.cmp (1.0) I regroup the GT1 common mas in a component named : GT1_common.cmp (1.0) I regroup the ALL_CAR common mas in a component named : CARS_common.cmp (1.0) QUESTION 2/ Can I make is this way ? This is important because I can make an evolution mod with this way. I create a mod MYMOD (1.0) with only One car and 1 team containing the previous components. GT1_AstonMartinDBR9.cmp (1.0) GT1_common.cmp (1.0) CARS_common.cmp (1.0) GT1_AstonSounds.cmp (1.0) And Virtual Tracks QUESTION 3/ Can I make is this way ? QUESTION 4/ Can I make the mod a virtual mod pointing to components (to share components separately)? (this is to avoid to make a BIG package mod because I know it will change often). Step 2/ Now I make the missing teams for the already provided car, and so I decide to make an update of my component (new version of my component). So only the GT1_AstonMartinDBR9.cmp is updated and change this version to 1.1 QUESTION 5/ Is there in this case a better choice to make an update of the component or create a new full 1.1? I create a new version of the mod with only the updated component = GT1_AstonMartinDBR9.cmp (1.1) GT1_AstonMartinDBR9.cmp (1.0) (I keep the 1.0 previous component if it's an update only) GT1_common.cmp (1.0) CARS_common.cmp (1.0) GT1_AstonSounds.cmp (1.0) And Virtual Tracks So now I publish my new component GT1_AstonMartinDBR9.cmp (1.1) and my new version of the mod : MYMOD (1.1) QUESTION 6/ Can I make is this way ? Step 3/ Now the complicated things arrives. I add my new GT1 car, and the GT1 common and ALL CAR common part are impacted. So I decide to diffuse my updated content. The GT1_common.cmp (1.0) pass to GT1_common.cmp (1.1) The CARS_common.cmp (1.0) pass to CARS_common.cmp (1.1) GT1_CorvetteC6R.cmp (1.0) is created GT1_CorvetteSounds.cmp (1.0) is created I create a new version of the mod with the updated component and new one added MYMOD (2.0) = GT1_AstonMartinDBR9.cmp (1.1) GT1_AstonMartinDBR9.cmp (1.0) (I keep the 1.0 previous component if it's an update only) GT1_common.cmp (1.1) CARS_common.cmp (1.1) GT1_AstonSounds.cmp (1.0) GT1_CorvetteC6R.cmp (1.0) GT1_CorvetteSounds.cmp (1.0) And Virtual Tracks QUESTION 7/ Can I make is this way ? Can ISI confirm this way of working is ok with the new components and mod management system for rF2? NB : I make my tests in parallel, but if I can safe some time on that it will be cool.
I promised i wouldnt answer when drunk. But it seems what you've typed is correct except the virtual track part. you,at this stage must combine an actual track to you rFMod file
Yes, it's in that way I wrote "virtual" track => Track not included in the mod, but linked as virtual component because it's today mandatory in the tools. (And I hope one day, the mandatory link to track will be removed but it's not the subject of my post). Thank you for you help, if ISI experts can confirm theses points (each question) (Scott ?) because it's a huge work to adapt to this, and I don't want to make the job many times with component. This is important to get ISI green light on this, because the distribution of multi cars mods is impacted if this use case is not possible.
Based on what you typed, this all looks correct. Sounds HAVE to be their own component--they can't be included with the car comp. That's the only part that is "wrong" with what you had listed. You can include references to track components, thus making your mod partially virtual (I did this with Portugal in the new packaging vid tut that was posted). However--were I you I would REALLY wait until the upcoming beta update is released (which is weeks, not months, from release). There are a couple bugs that were discovered and fixed in mas2, and potentially you would need to remake ALL of these components again from the ground up. As Gjon stated, sometimes the format may change as we squash bugs and add features.... So, other that holding off until the next update, you're thought process looks good. Feel free to give a shout at each stage just to make sure you're on the right path...
Ok, I have no problem to make the component creation again and again during the beta phase, my interest is to valid the way of working from mas to components and from components to mod distribution for the rFactor2 release. So You confirm what I expect to make will be ok for rFactor2 release (and testable in the next Beta update (good news)). I will get you informed of my progress.
