Skypat Posted March 29, 2010 Share Posted March 29, 2010 Hello, ModMan 7.2 will be released this week fully supporting FC2 Like ModMan 7.1 done the job for BS, ModMan 7.2 will be able to add skin as new slot (modders always need to make your 'skin.lma' text file describing the skin settings) best regards Skypat 7 Link to comment Share on other sites More sharing options...
Argant Posted March 29, 2010 Share Posted March 29, 2010 merci :') [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Thunderbird Posted March 29, 2010 Share Posted March 29, 2010 great cant wait for the release, will keep track of this thread for the update Link to comment Share on other sites More sharing options...
Frazer Posted March 29, 2010 Share Posted March 29, 2010 Awesome, thanks! Forum | Videos | DCS:BS Demo1 / Demo2 | YouTube Channel [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Mirtma Posted March 29, 2010 Share Posted March 29, 2010 Great! Gigabyte Z490 Gaming X | i5 10600K@4700 | 32 Gb DDR4 @ 3200Mhz | Gigabyte Aorus GeForce GTX 1080 Ti 11G | MONITOR IIYAMA 24,5" LED LCD @ 1920 x 1080 | Windows 11 | Saitek X-55 Rhino | TrackIR 5 Pro Link to comment Share on other sites More sharing options...
Axion Posted March 29, 2010 Share Posted March 29, 2010 Excellent news, cheers Skypat! Asus Z390 Code XI, i9-9900K, RAM 32 Gig Corsair Vengeance @ 3200, RTX 2080 TI FE, TIR 5, Samsung 970 EVO 1TB, HOTAS WH, ASUS ROG Swift PG279Q, HTC Vive Pro, Win 10 x64 Link to comment Share on other sites More sharing options...
Sarge55 Posted March 30, 2010 Share Posted March 30, 2010 Thanks Skypat, sure is a great tool. [sIGPIC][/sIGPIC] i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog Link to comment Share on other sites More sharing options...
Boulund Posted March 30, 2010 Share Posted March 30, 2010 Great stuff! Keeping the community in good health Core i5-760 @ 3.6Ghz, 4GB DDR3, Geforce GTX470, Samsung SATA HDD, Dell UH2311H 1920x1080, Saitek X52 Pro., FreeTrack homemade cap w/ LifeCam VX-1000, Windows 7 Professional x64 SP1. FreeTrack in DCS A10C (64bit): samttheeagle's headtracker.dll Link to comment Share on other sites More sharing options...
Muse Posted March 30, 2010 Share Posted March 30, 2010 merci :thumbup: courage and dedication [sIGPIC][/sIGPIC] http://www.checksix-fr.com/ [FC2] packs de Francisation Link to comment Share on other sites More sharing options...
Ells228 Posted March 30, 2010 Share Posted March 30, 2010 Great news for us mod teams Link to comment Share on other sites More sharing options...
104th_Crunch Posted March 30, 2010 Share Posted March 30, 2010 merci beaucoup! Link to comment Share on other sites More sharing options...
RICARDO Posted March 30, 2010 Share Posted March 30, 2010 super, et encore bravo pour ton travail:thumbup: Link to comment Share on other sites More sharing options...
McDaniel Posted March 30, 2010 Share Posted March 30, 2010 Good news indeed! Thank`s Skypat :thumbup: McDan out |AMD 7800x3D | 64GB DDR5-3600| GTX 4090 | Virpil Stick, Collectiv, WW MIP, WW Throttle, MFG Crosswind V2 | Windows 11 64-bit | SSD Samsung | 4K LG Oled 48 | Oculus Q3 | Simlab based Cockpit Link to comment Share on other sites More sharing options...
USSR_Gys71 Posted March 30, 2010 Share Posted March 30, 2010 Is it possible to make modman replacing an exising skins? Thats actual for integration new models without replacing db_countries.lua. And thats will solve at last the problem of different mods compatibility . Link to comment Share on other sites More sharing options...
PoleCat Posted March 30, 2010 Share Posted March 30, 2010 Thank you! Out http://www.104thphoenix.com/ Link to comment Share on other sites More sharing options...
Toast Posted March 30, 2010 Share Posted March 30, 2010 Once BS patch comes out, will we need to get a new version of Modman for BS? Toast Aviate, Navigate, Communicate. and When All Else Fails, Aviate More :pilotfly: Link to comment Share on other sites More sharing options...
Phoenix FR Posted March 30, 2010 Share Posted March 30, 2010 super, et encore bravo pour ton travail:thumbup: On attend tes pits, histoire d'alimenter Modman. :smilewink: Link to comment Share on other sites More sharing options...
51GRIZZLY Posted March 30, 2010 Share Posted March 30, 2010 Can't waaaait :D Link to comment Share on other sites More sharing options...
Skypat Posted March 31, 2010 Author Share Posted March 31, 2010 Is it possible to make modman replacing an exising skins? Thats actual for integration new models without replacing db_countries.lua. And thats will solve at last the problem of different mods compatibility . since 7.1 version, mod replacing db_countries.lua was made in the wrong way. For a new skin slot, modman add the entries to db_countries.lua automatically. There are plenty of DCS BS ka-50 skins around the place which work in the good way. for month this modman feature is working fine on BS FC2 have now the same 'skin' file structure so it's working in the same way. btw, i seen that somebody posted a modman.ini settings to make modman 7.1 version working with FC2. these settings are wrong because it's disabling the skin DCS feature . i have posted in the same thread the good settings. the skins feature is described in modman/docs/DCS_new_skin_slot.doc word document. best regards Link to comment Share on other sites More sharing options...
USSR_Gys71 Posted March 31, 2010 Share Posted March 31, 2010 Well. Thanks for answer. But i do not mean new skin slot. Is it possible to let modman replacing an existing skin slot? Without replacing an existing skin slot mod replacing db_countries.lua was made in the wrong way. but is only one way Link to comment Share on other sites More sharing options...
Maximus Posted March 31, 2010 Share Posted March 31, 2010 Nice to see the modman being upgrade. ;) Maximus, The only real Maximus in DCS World. :music_whistling: I am not associated to viper 33 | Maximus. he is the imposter. Link to comment Share on other sites More sharing options...
Skypat Posted March 31, 2010 Author Share Posted March 31, 2010 (edited) Well. Thanks for answer. But i do not mean new skin slot. Is it possible to let modman replacing an existing skin slot? Without replacing an existing skin slot but is only one way replacing db_countries.cfg file is a wrong and bad way because you are corrupting completely the skin database if some skins was installed before yours. It's not a way to choose at all to pack such a file in a mod. (BTW like *.skins file too...) To preserve the database integrity, the good way is to add entries to this file not to overwrite it. (you just need to make a skin.lma file) modifying db_countries..lua file is only required for NEW SLOT. for new 3DMODEL, no need to owerwrite/modify db_countres.lua, just re-use the same skin name entries (skin ID and skin name) and use these ID/NAME in your dedicated .skins files. in fact i don't understand at all why are you modifying db_countries.lua file ? (even for new 3DMODEL) what is the real problem to solve in this file ? A+ Edited March 31, 2010 by Skypat Link to comment Share on other sites More sharing options...
USSR_Gys71 Posted March 31, 2010 Share Posted March 31, 2010 (edited) for example default F-15 USA colorschemes color_scheme("{2e57406b-0ad2-4531-8dc4-e9ba59be6167}", "32nd TFS (CR) AB Soesterberg (early)"), color_scheme("{3506c4fe-4c3a-4d79-b232-fd000ec65b9c}", "58th FS \"Gorillas\" (EG) AFB Eglin"), color_scheme("{abd15535-a4ba-451a-8583-6d796c35747b}", "59th FS \"Proud Lions\" (EG) AFB Eglin"), color_scheme("{8238d333-c109-43dc-8cae-74e92799270a}", "27th FS \"Fighting Eagles\" (FF) AFB Langley"), color_scheme("{a4492e44-06bd-4ed8-b744-f5fd4be4b2c8}", "71th FS \"The Ironmen\" (FF) AFB Langley"), color_scheme("{c0ee4ef9-9328-4a38-871e-1dfbd1efd41f}", "67th FS \"Fighting Cocks\" (ZZ) AB Kadena"), color_scheme("{1a27ede8-236a-42c6-b7c5-2f2f2620fd26}", "48th FW 493rd FS (LN) RAF Lakenheath (GB)"), color_scheme("{2a31c5f8-df20-4af3-bd7d-ccbb8a64b5cf}", "52th FW \"The Tigers\" (SP) AB Spangdahlem"), color_scheme("{8e75a77d-c944-4f43-9441-787e03d6b68f}", "54th FS (AK) AFB Elmendorf (early)"), and ours new model color_scheme("{2e57406b-0ad2-4531-8dc4-e9ba59be3535}", _("48th FW 493rd FS (LN) RAF Lakenheath (GB)"), 0), color_scheme("{3506c4fe-4c3a-4d79-b232-fd000ec63535}", _("173th FW ANG Oregon"), 1), color_scheme("{abd15535-a4ba-451a-8583-6d796c353535}", _("57th FW 65th Aggressors 28"), 2), color_scheme("{AK475535-a4ba-451a-8583-6d796c35AK47}", _("57th FW 65th Aggressors 10"), 3), color_scheme("{M166c4fe-4c3a-4d79-b232-fd000ec63M16}", _("173th FW ANG Oregon Shark"), 6), color_scheme("{ALASKAfe-4c3a-4d79-b232-fd000eALASKA}", _("3th FW 19 FS Elmendorf"), 7), color_scheme("{Fictiona-4c3a-4d79-b232-fd000eALASKA}", _("Fictional DC"), 8), color_scheme("{JASDF4fe-4c3a-4d79-b232-fd000ecJASDF}", _("JASDF F-15J 303SQ"), 9), 9 skins default and 8 skins-ours. I know that names have no value in db_countries, it is important only CLSID. But how to be with quantity? sorry for my english Edited March 31, 2010 by USSR_Gys71 Link to comment Share on other sites More sharing options...
USSR_Gys71 Posted March 31, 2010 Share Posted March 31, 2010 (edited) I only wish to replace one code with other code. It is possible? If we shall replace one code with other code and we shall make it for other country - all ours skins will be established automatically. It will not be necessary to add their one behind one. Edited March 31, 2010 by USSR_Gys71 Link to comment Share on other sites More sharing options...
Skypat Posted March 31, 2010 Author Share Posted March 31, 2010 ok i understand. in fact you want 'good skin name' for and not reusing 'old id and old skin name' in example: if your new 3D model skin is (color) yellow, you don't want the old skinname 'The green team' you want 'the yellow team' skin name. in fact you want to replace all the F-15 section in db_countries.lua files. that's not possible. you have 2 solutions 1- using the old id and skinname for referencing several new 3D model skin 2- adding new skin slot for the new 3D models (but the old skin slot will make artefact/bug on the new 3D model) you can add the word 'new' to these skin name so users will be able to see what are the skins to use with the new 3D model #2 is the best solution if you want absolutely use new skin name (and new id) the last solution is to install A10/F15 before all others mods... A+ Link to comment Share on other sites More sharing options...
Recommended Posts