CCIP Cockpit Mod
-
Caustion!
In case you have experienced the cockpit issue while using my mod, please don’t report it to BMS development team.
It will waste their time to confirm whether the issue is caused by BMS’s original work or my modifications.About This Mod
This mod replaces the cockpit of F-16CM Block 50.
More information and download links are available in 35th VFW official website.Acknowledgement
I would like to thank BMS developers, especially Nanard for giving me a permission to modificate his original cockpit.
And also thank people who’s supporting this great simulator.Update History
July 6, 2017 - Version 6.0.4 released Added Block 40 cockpit. Added reflection effect to Block 50's WAC HUD. Changed the background color of RWR Azimuth Indicator. December 28, 2016 - Version 6.0.3 released Fixed indication error in Engine RPM Indicator and Vertical Velocity Indicator. Fixed Left AUX panel backlight. November 19, 2016 - Version 6.0.2 Open Beta released Fixed back light issue on OSBs. Fixed the issue "ILS" letter doesn't show up on EHSI. November 18, 2016 - Version 6.0.1 Open Beta released Fixed some issues. Replaced Speed Brake Position Indicator with own made. November 11, 2016 - Version 6.0.0 Open Beta released Got compatibility with Falcon BMS 4.33 for the first time. Replaced HUD glass with own made. Replaced RWR Azimuth Indicator with own made. Replaced flood lights with own made. Replaced analog instruments with own made. Replaced canopy lock handle with own made. Replaced canopy grips with own made. Integrated UV maps of additional parts to two textures. Changed panel lights. Added glass plate into the surface of some instruments. Changed the color and design for entire cockpit. Added several new parts. March 12, 2015 - Version 5.0.0 Closed Beta released Fixed Bank Angle Indicator of ADI. Fixed the UV map of Speed Brake Position Indicator. Fixed DOF of JHMCS Magnetic Emitter Unit. Changed EHSI for more realistic shape. Changed color and design of entire cockpit. Changed the texture of HUD Render-To-Texture for more realistic look. December 8 2013 – Version 4.6.6 released Fixed digital indicator of altimeter. Changed the color of canopy holder. Increased transparency of canopy. September 10 2013 – Version 4.6.5 released Fixed shape/size of NVIS lights which based on real world dimentions. Changed the color of eyeblow warning lights. Changed the color of panel/instrument backlights. Changed the color of ejection seat and some other parts. Fixed backlight issue on trim panel. August 27 2013 – Version 4.6.1 released Fixed Altimeter needle. August 27 2013 – Version 4.6.0 released Added paint peeling to some panels. Fixed Fuel Flow Indicator. Fixed Course Deviation Indicator. August 23 2013 – Version 4.5.0 released Added reflection effect of EHSI window film. Fixed RWR Azimuth Indicator. Fixed the backlight of RPM Indicator. Changed the color of air conditioner duct. August 17 2013 – Version 4.0.0 released Fixed Altimeter.
-
No screenshots?
-
Nice! However …
Please remove link now.
And tell us first that you have Nanard acknowledgment for his pit modification.
Sorry for releasing without Nanard’s permit (cockpit creater?).
I didn’t know it’s necessary for release. -
(cockpit creater?)
Yes.
I didn’t know it’s necessary for release.
[Q: Can I modify any BMS component freely and distribute my work?
A: Each part of the BMS community add-on is the intellectual property of its creator. Therefore, you should not modify and distribute something derivative without asking the original creator if that would be OK. Some may give you this authorization, others may not, and others may ask that you work collaboratively on improvements to the baseline. This applies to all the elements contained in BMS release materials; including but not limited to 3D models, sounds, campaigns, data and configuration files, documentation, etc.](https://www.benchmarksims.org/forum/content.php?131)
-
Yes.
[Q: Can I modify any BMS component freely and distribute my work?
A: Each part of the BMS community add-on is the intellectual property of its creator. Therefore, you should not modify and distribute something derivative without asking the original creator if that would be OK. Some may give you this authorization, others may not, and others may ask that you work collaboratively on improvements to the baseline. This applies to all the elements contained in BMS release materials; including but not limited to 3D models, sounds, campaigns, data and configuration files, documentation, etc.](https://www.benchmarksims.org/forum/content.php?131)
Oops… I had forgotten it.
Thank you for quotation, Dee-Jay.And I’m sorry, Nanard.
-
Anyway, apart from the -correct- copyright issues… (although Nanard is vanished long ago)
Very interesting mod, @PeCa_Chuck i would like to know how you managed to implement it. Do you have the original Nanard’s model or you worked directly on the lod model?
BTW, i have full info of what you try to replicate, plus for many different versions. If the copyright issues were solved somehow, i could provide you all the info you need.
And please, how you modeled the eHSI???
-
i would like to know how you managed to implement it. Do you have the original Nanard’s model or you worked directly on the lod model?
I mainly used 3ds Max.
Once exported the 3d model as lod file, I imported it to original lod file by using LOD Editor.
I would like to thank Nanard (BMS F-16 cockpit creator) and BaldEagle (LOD Editor creator).BTW, i have full info of what you try to replicate, plus for many different versions. If the copyright issues were solved somehow, i could provide you all the info you need.
Thank you for your suggestion, Raptor!
And please, how you modeled the eHSI???
I used same method which Mr.Nanard did.
Symbols (arrows, course deviation, desired heading etc…) are implemented as texture over the poly.But I have to report about issues.
First, Range and Course scale looks little bigger than real one.
Second, direction symbol is displayed over course arrow.First issue can be fix.
I will to do.
Second issue probably won’t be able to fix. -
well u could also create a light version of the cockpit which I believe will greatly improve fps. meaning a less poly version. maybe 2 one mid and one very low. so three in total… one high as is, one mid, and one low.
Which is mostly what is needed in my heierarcy list. rest are all secontaries I would say.How many poly’s are there now?
-
well u could also create a light version of the cockpit which I believe will greatly improve fps. meaning a less poly version. maybe 2 one mid and one very low. so three in total… one high as is, one mid, and one low.
Which is mostly what is needed in my heierarcy list. rest are all secontaries I would say.How many poly’s are there now?
I’m sorry, I have no plan to create lighter version.
This mod increases 15,000 triangles in total. -
This post is deleted! -
@RPG:
Lod 2 is conflicting with PL_Harpoon’s pilot mod which also uses 7318, anyway around this?
I don’t have right to integrate this mod with Harpoon’s mods, sorry.
-
I don’t have right to integrate this mod with Harpoon’s mods, sorry.
You can collaborate though ….
-
This post is deleted! -
Will there be a relinking of this mod soon?
-
Other than the HSI, what are the differences between this pit and the stock one?
-
Will there be a relinking of this mod soon?
+1. Missed this thread. Hope to try it out.
-
… just wait for Nanard clearance … should be ok (?)
-
You can collaborate though ….
It will be nice, if I could be.
@RPG:
Well when you do can you please do an alternative Lod 2 with PL_Harpoon’s pilot mod incorporated into the lod?..…otherwise its going be a case of choosing this mod OR the pilot mod, and I’m greedy, I want it all. ;)…good luck getting permission PeCa_Chuck, its a great mod this.
You can use those mods simultaneously.
Just append parrent number 2 lod, and replace lod number by using LOD Editor when you want to use the other.
Or append parent record, and replicate parrent number 2. (of course except lod number)
After it process, you only do is just replcae parent number in 3dcockpit.dat.… just wait for Nanard clearance … should be ok (?)
I hope so, but future is unclear…
-
I hope so, but future is unclear…
Did you sent him a PM? (If yes, just wait him to come here … I’ve sent him a PM also. His last visit was on July 30th, 2013 .)
-
Did you sent him a PM? (If yes, just wait him to come here … I’ve sent him a PM also. His last visit was on July 30th, 2013 .)
Yes, I sent PM to him.
Thank you for support, Dee-Jay.