Beginnger's Guide: How to Add or Replace a Weapon to BMS
-
Per Guldager’s request HERE I made a video showing how to add a new weapon to the database (in this example a training AIM-9M) that doesn’t already exist in the database. At the end of the video I also show how to replace an existing model in lod editor since I get asked that a lot too.
I want to say that I’m far from an expert working with the Lod Editor and most of this is self taught. A while back Echo and JanHas were kind enough to give me some direction on how to work with LE and add the training weapons and I used Echo’s ITO theater as an example while I learned. I also used Ranger822’s guide on how to add a new aircraft to the database on the PMC wiki site as a reference, and I have provided a link below to that article. The process in the video is how I added the JanHas training weapons to our 1st VFW Korea theater and how I installed the JanHas ALWs too. We’ve never had any issues using this process.
If you have a question or a request for another video let, let me know. Experts - feel free to correct any information that is inaccurate.
Watch in 1080HD fullscreen to see the text on my screen (was still processing the HD at time of posting, but I’m going to bed)
ALWAYS BACK UP YOUR INSTALL You will be sorry if you don’t make a backup and screw up your install.
======Video Table of Contents======
00:00mins - How to add a weapon to the database
14:26mins - Another example (faster) on how to add a new weapon (ACMI pod)
21:25mins - How to Replace an Existing Model in Lod Editor (i.e. weapon, aircraft, object)======LOD Editor 6.23======
http://www.firstfighterwing.com/Public2/1.%20LOD%20Editor%20v6.23.rar
======F4Browse 2.31======
http://www.firstfighterwing.com/Public2/F4Browse_v2.31.rar
======Guide for adding a new aircraft by Ranger822======
http://tactical.nekromantix.com/wiki/doku.php?id=falcon4:database:editingtutorial
======Guide for linking the weapon files in F4 Browse======
CT# on Class Table = CT INDEX on the Weapon Page
FILE OFFSET on Class Table = WEAPONID on Weapon Page
ALT OFFSET on Class Table = ManeuverDef on Weapon Page
ALT OFFSET on Class Table = SWD No on the Sim Weapon Data list
SWD No on Sim Weapon Data = manueverDEF on Weapon Page -
Nice 1 Demo!
-
Awesome work!
-
Was a long way to learn that. With your tutorial it gets damm easy. I was working on a tutorial but didn’t finish it due other stuff. Great work!
-
In my opinion this quick and dirty mods of the DB is what makes BMS a nightmare for compatibility between mods.
Just to copy a entry of the CT table and put a new name, but keep the same “Domain/Class/Type/Subtype/Specific” (DCTSS Numbers) is not the way to go. What defines a given vehicle, weapons, etc is not the CT. The CT can change from DB to DB (is just a value), but the DCTSS number should be always the same for a given type of aircraft or weapon.
I think the best way for the community would be to have a MASTER DB, where the DCTSS numbers are kept up to date. In the example of PMC, a MIRAGE IIIR2Z should have a different TSS number because it is a different platform. If we act this way, people would be able to import a new vehecile/weapon/etc to his/her DB, put some CT number, and ready to go.
-
And where is the tool to do such?
the tool is there but the info ain’t there… and the tools is way from User Friendly for such works.What u are talking are the CT Index Type info…
Well CT number is the master index number as I understand it… so if u change this then u are ok for working…The Master Database as u call it can never happen. Unless BMS locks the Database and to implement a new weapon u will have to wait for BMS release. Along side BMS dev’s u have the Theater Developers. BMS dev’s don’t know and can’t be responsible for specific Country - theater data. The responsibility is the theater developer’s to do his job correctly and not play around.
Also for the guides like for this platform use this value well those must be declared and publish somewhere as a reference so dev’s follow. Right now that we all are ignorant on the subject we just go and put whatever comes to our head.
Now for different theaters theater developers can build their own Databases with data for Aircraft Weapons etc. Now one theater has x changes another has y changes and BMS has z changes…
BMS changes is our master database. Now the think is to have the tool and quickly merge the changes we want.
First the ones from BMS so to ensure compatibility issues.
Second Ok I like and want the changes the other theater has done x changes but not all… Example I know Greek F-4 can carry this weapons (a.b.c.d.e.) but Israel not or carry more (a.b.c.d.e.h.i.) I don’t want them all… but I forgot h. let’s get the data from h. and merge those to my database.BMS removed some weapons and changed the Database structure… I want to use that as my new base and quickly update the new database structure with my changes… This is the thrill and essence of theaters… else it’s only the Terrain and models. The point is the whole package.
-
Can you make a similar video that how can you do a new aircraft dof in 3d max?
What are the most important things which I have to do? -
where can we find those JanHas models?
-
I think the best way for the community would be to have a MASTER DB
I do 100% concur. (This is a pure personal POV … I’m not talking for BMS Team)
-
-
I do 100% concur. (This is a pure personal POV … I’m not talking for BMS Team)
Only problem that theater makers have their own aspect, regardless how big and detailed a core/mater DB at least minor edits are required. Sq. sizes, battalion rosters, available weapos, etc. mean different demand to DB.
From my aspect DB creates very different issues, concerning on updates an and features. All 3D models - vehicles and cockpits - theoretically can be updated for 3rd party DB as long as they are just replacing existing stuff. For example current old AV-8 3D model is replaced with a new one. A bit harder issue integrate new cockpit what is not exist currently in DB or creating new DB entries for a new AC. Direct import - export form core DB can be prevented, because other DBs it may can use DB entries and skin numbers what has not been used in core DB before the upgrade. This is one of the aspect, this is just eye candy part.
What about DB related issues which have strong impact on gameplay…? Each theater may need different role scores, different squadron sizes, different sq. stores. Etc.
I would like to see a fine master DB but this is such a huge task what seems to me not doable. Alway will be a core DB as “base” but DB of 3rd party theaters have to be updated manually. The “base” can mean that a theater uses with olny minor changes or can mean that DB is just a resoruce, sutff can be exported (3D models) and featues can be applied for another DB.
IMHO the current DB is filled with too many garbage. It has many vehicles, weapons, etc. which are not used or 100% important for any campaign in Korea even counting with 3rd party theater. Just using only the existing DB entries, parents, LOD number make possible to get a much better DB. I have shown many of these possible upgrades in my “Korea MOD thread”. We can create functional battalions using the same vehicles and model the unit which has different AD support, we can model different subvariant of different AC, etc.
As long as a goal is not defined what should be included in master DB is illusory to believe that we have one. All 3rd party devs. should listed the missing, required items and what can be deleted - use their DB entries and LODs - because some of the items are just garbage. Of course the process is painful and long but I can list dozens of vehicles which are useless but many what should have at least placeholder DB entries. Basic AD vehicles are missing from DB but n+1 not modeled or used vehicles are in the DB. The task is so huge and requies so much coopeation that I have no idea how can be done. I can do it in my DB fast, because I do not have to consider any requestes besides mine…
(Currently BMS4 DB is behind every 3rd party theaters, all updates what have been done in core DB can be done in 3rd party theaters. I can’t recall update except the range edit of bombs.)
-
For once I completely agree with you Molni and thanks for the insightful post. How about your MOD, has that been released already and I missed it?
-
thanx but file not found… anyone care to share please?
Also do they work with BMS?
-
For once I completely agree with you Molni and thanks for the insightful post. How about your MOD, has that been released already and I missed it?
There were a very WIP release exactly one year ago. The level of progress of current is very good but it still haven’t been finised. The DB is “99%” done, the rest is what I have to figure out what campaigns files should be used, because of the conctent update 5. In the WIP release only one campaign were tweaked therefore it sounds logical choice useing U5’s campaign files but I have to examine at least one issue. Some campaigns requires carriers but for the first release Bad Boy made the the necessary changes.
-
thanx but file not found… anyone care to share please?
Also do they work with BMS?
Sorry about the link… Yes they work great with BMS.
I have the files at my desktop PC, but i’m not at home ATM. Ultimately i can upload them tomorrow.Guldager
-
Only problem that every theater makers have their own aspect, regardless how big and detailed a core/mater DB at least minor edits are required. Sq. sizes, battalion rosters, available weapos, etc. mean different demand to DB.
…
What about DB related issues which have strong impact on gameplay…? Each theater may need different role scores, different squadron sizes, different sq. stores. Etc.
Sure … but as you said … it is a big (or evn huge) work to rebuild everything each time… furthermore when code changes makes DB out to date and change in-games behavior. Non talking about the fact that BMS is not FF and we will not be able to give an access to DEV forum to follow the when & why of each single changes … etc …
So … you will have to restart “from scratch” each time we will have a new major update (hopefully not every years).
It is a choice that theater DEV has to make:
- Run with Korean stock DB (with skin change and maybe some minor change in DB)
or - Deeply change the DB to make a/c country depended, with some new/other weapons etc … in that case, they will have to accept the fact that they will have to restart ll their job from scratch each major BMS release.
A tool would make their life easier … if they could save/export their data edit, and import them again in the new DB (paying attention to updates what it should do if code change require it etc…)
- Run with Korean stock DB (with skin change and maybe some minor change in DB)
-
A tool would make their life easier … if they could save/export their data edit, and import them again in the new DB (paying attention to updates what it should do if code change require it etc…)
Who has the skill to make such a tool?
-
This post is deleted! -
Who has the skill to make such a tool?
https://www.benchmarksims.org/forum/showthread.php?14734-BMS-Database-Manager-%28WIP%29
And maybe some BMS guys will work on a dedicated tool… but no more info ATM. There is no official, nor non-official statement ATM.
-
In my opinion this quick and dirty mods of the DB is what makes BMS a nightmare for compatibility between mods.
Just to copy a entry of the CT table and put a new name, but keep the same “Domain/Class/Type/Subtype/Specific” (DCTSS Numbers) is not the way to go. What defines a given vehicle, weapons, etc is not the CT. The CT can change from DB to DB (is just a value), but the DCTSS number should be always the same for a given type of aircraft or weapon.
I think the best way for the community would be to have a MASTER DB, where the DCTSS numbers are kept up to date. In the example of PMC, a MIRAGE IIIR2Z should have a different TSS number because it is a different platform. If we act this way, people would be able to import a new vehecile/weapon/etc to his/her DB, put some CT number, and ready to go.
Agree. This video was really just to show how to replace a model and how to add training weapons which are eye candy only.