christian59

have you try with my weapondata?

hello i think your problem come from the FLIGHTENGINE.ini (in the flight folder) replace old [GraphicsSettings] by [GraphicsSettings] ZBufferDepth=24 MaxVertexCount=16384 MaxIndexCount=32768 MaxTextureCount=16384 MaxModelType=2048 MaxMeshPerScene=4096 MaxModelPerScene=4096 MaxLightPerScene=1024 AspectRatio=1.333333 MinPixelSize=1.0

hello 1- Add the entries in the WeaponData.txt to your WeaponData.ini - Be sure to correct the weapon entry to be sequential to your own WeaponData.ini 2- Load the Weapon Editor and Save to create a new WeaponData.Dat file here it's my WEAPONDATA you can try with them it's a WEAPONDATA with all the pack a have found hope it's help you

i think it's a Monty_CZ plane

all new plane a wellcome thank you

in the flight folder you have a FlightData use cat extractor on it and you can extract the flightengine.ini look at http://forum.combatace.com/index.php?autoc...mp;showfile=343

ww2 soviet tank most used in 1941/43

in the flight engine.ini try this [GraphicsSettings] ZBufferDepth=24 MaxVertexCount=16384 MaxIndexCount=32768 MaxTextureCount=16384 MaxModelType=2048 MaxMeshPerScene=4096 MaxModelPerScene=4096 MaxLightPerScene=1024 AspectRatio=1.333333 MinPixelSize=1.0

thank you good job

here http://forum.combatace.com/index.php?autoc...mp;showfile=343

find this on my computer sorry don't know the author WARNINGS: The skill level stuff doesn't work independently of ai data in the FMs, so you can't completely change the ai behavior of the plane unless you mod that too - I don't recommend you do that unless you test extensively. Do not mod the {aidata] section in the Aircraftobject.ini under ANY circumstances - Big Problems. This is overrridden by whats in the FMs themselves, and where these are not present, its for good reason, the generic ones work well, eg most of TKs. Finally, if you try out changes like below, and at some time in the future, some planes (not all necessairly), the AI are funny/out of control either in dogfighting or in formation, delete your changes. The changes you have made are probably the cause of AI problems - most of the AI are fine now. Don't blame the game, don't blame me. All the parameters will effect the AI, but some of the major ones are (from Ace skill level in the default Aircraftobject.ini that came with the game), and remember that capability and aggressiveness are different: DefensiveAngle=120 MaxRollForGunAttack=180 MaxPitchInput=1.0 MaxRudderForGunAttack=1.0 MaxRudderForManeuver=1.0 Most important from a capability perspective is MaxPitchInput=, max value is 1.0. Its how much the pitch values in the FM and aidata section of the FMs are used by the AI. If you find AI planes turn too tightly, too manoeuvrable, too capable - ie, too difficult - then reduce for all skill levels. Values higher than 1.0 do not work, its reduced to 1.0. Secondary from a capability perspective are the MaxRudderForGunAttack= and MaxRudderForManeuver= parameters. I use 3.0 for MaxRudderForGunAttack= and it works, but it would be limited to some value, TK always does this, its good programming practise. The first is how much rudder the AI will use WHEN it starts a gun attack (ie, lines you up and decides to attack, or is shooting at you), the second is rudder generally for both defensive actions (sideslipping), and offensive how quickly it comes around (eg, using rudder together with roll will mean it turns quicker). The AI uses rudder very effectively now since EP, so these are important, but not as important still as MaxPitchInput=. If you were making AI harder or easier, I'd vary these a bit, but not much. Lastly, are MaxRollForGunAttack=, and DefensiveAngle=. They sort of work together, and are the MOST important from an aggressiveness perspective. MaxRollForGunAttack= measured from the front of plane basically "says", if an enemy is within this arc, undertake aggressive actions. Now, if you make this 360, as I do, it means, that say in 1:1 (1:1s are a good way to see how an AI performs, in a pure form, and its how they will be in furballs too), the AI will continually be trying to attack you, rather than being defensive. If you set it at 90, it will be mainly defensive. DefensiveAngle= works somewhat with MaxRollForGunAttack=. It tells the AI if an EA is within that arc (measured from rear), then take defensive action. It seems to mostly take precedence over MaxRollForGunAttack=, ie, if you are say at rear of AI, it will do defensive maeouvers like sideslip turn dive climb, until it has you in the MaxRollForGunAttack defined arc, then it attacks. The AI is far better if it attacks more. I have tried reducing DefensiveAngle= to 30, but thats a problem. You can be on its tail, and it does nothing, even tho MaxRollForGunAttack= is 360, it should be attacking. Optimal seems 60, they are pretty tough then. What happens is they jig about when you are on their tail, until you are out of their 60 degree angle (which is easily done), and then turn around because of the MaxRollForGunAttack=360 angle and attack. My conclusion is that MaxRollForGunAttack=360 isn't actually 360, maybe less, or more logically, there is a range of around 60 where the defensive action takes precedence over aggressive. All guessing of course. Increasing MaxRollForGunAttack= over 360 doesn't make any difference ...its probably the limit defined by TK.

look at http://forum.combatace.com/index.php?showt...9&hl=import have a good day

thank you good to have many cockpit of mig fighter ps:mig 17pf/pfm will come???

thank you very good work just UK_Foxhole and UK_Milan_Foxhole are argentina may be RAF better???

me too files damaged

thank you may be later we can test the new airbase

don't forget to use FE by peter 01 the game is not the same http://forum.combatace.com/index.php?autoc...amp;showcat=213 thank peter

what is DBS terrain please??????????????????

when you play in a campaing just in the xxxxcamp1_data you can choice the weapon that is in use like this [AirUnit054] AircraftType=MiG-21F UnitName=31 Gv.IAP 'Nilopolskyi' ForceID=2 Nation=SOVIET DefaultTexture=SovietCamo1 BaseArea=Alt-Lönnewitz Airbase BaseMoveChance=10 RandomChance=100 MaxAircraft=16 StartAircraft=16 MaxPilots=16 StartPilots=16 Experience=80 Morale=100 Supply=100 Intelligence=50 MissionChance[sWEEP]=70 MissionChance[CAP]=50 MissionChance[iNTERCEPT]=70 MissionChance[ESCORT]=90 MissionChance=10 MissionChance[CAS]=10 MissionChance[sEAD]=10 MissionChance[ARMED_RECON]=10 MissionChance[ANTI_SHIP]=0 MissionChance[RECON]=10 UpgradeType=NEVER Supply[001].WeaponType=FAB250 M62 Supply[001].Quantity=120 Supply[002].WeaponType=FAB500 M62 Supply[002].Quantity=120 Supply[003].WeaponType=RBK-500 PTAB Supply[003].Quantity=80 Supply[004].WeaponType=UV16 Supply[004].Quantity=40 Supply[005].WeaponType=UV32 Supply[005].Quantity=80 Supply[006].WeaponType=R-13M Supply[006].Quantity=360 Supply[007].WeaponType=Tank490_Mig21 Supply[007].Quantity=120 Supply[008].WeaponType=RecPod_MiG21 Supply[008].Quantity=24

hello if i don't make mistake the N16 is a N11 with 110hp engine and weight 375 kg empty (80 hp and 320 kg for N11) if we add a 110hp in the N11 data and change weight to 375 will be a N16??? thank you

a new plane is alway a good new

excellent idea thank you

File Name: A6M2 Sen Baku File Submitter: christian59 File Submitted: 8 May 2008 File Category: Axis Fighters A6M2 Sen Baku in the Battle of the Philippine Sea Ryan Toews from j-aircraft.com The fighter-bomber version of the A6M2 is probably the least documented Zero variant. This article is an attempt to shed some light on some of the distinguishing details of this plane. First, allow me to offer a few a words on the proper nomenclature. Most published sources call this Zero a “Bakusen”. However, in the last year Manabu Kawasaki wrote a new study entitled A New View of the Battle of Philippine Sea. This book points out that the official records term the Zero fighter-bomber the Sen Baku; this is also supported by the memories of a number of pilots. My thanks to Kenji Miyazaki for drawing this to my attention. The A6M2 Sen Baku was introduced in early 1944. The D3A Val carrier-borne dive-bomber was recognized as becoming increasingly inadequate for front line use and the replacement IJN dive-bomber, the D4Y Judy, needed a longer take-off roll than could be accommodated on the light carriers comprising part of the First Mobile Fleet. Accordingly, a number of A6M2s were modified to carry a 250 kg bomb by replacing the drop tank so as to fit a centre-line bomb rack. These modified Zeros lacked dive brakes and bomb-throwing racks and so were restricted to less effective shallower bomb approaches, but it was thought that the flight decks of the American carriers could be damaged enough to render them incapable of aerial operations. Concurrent with the introduction of the A6M2 Sen Baku was the rebuilding of the Japanese carrier force. Training for both the 601 Kokutai only began in February of 1944 and 652 Ku and 653 Ku began training a month later. Very likely then the Zero Sen Baku only began arriving from the factory sometime in the period from February to April. Mitsubishi had stopped producing the A6M2 in mid-1942, so it can be safely assumed that all of the A6M2 Sen Bakus were built by Nakajima. Gakken 33 gives Nakajima’s monthly production numbers for both the A6M2 and the A6M5. Production of the latter was well underway in March 1944 and it was in full production by April. Yet production of the A6M2 only shut down gradually, with 111 aircraft still being built in April and May 1944. It may very well be that this drawn out production of the A6M2 during the time the A6M5 was being turned out in strength was due to the need for additional Sen Baku variants of the Zero. As will be explained below, the Zero fighter-bombers were not a simple conversion and were much more likely to have been given their necessary modifications on the assembly line. The A6M2 Sen Baku also appears to have been the first Zero to make use of two wing drop-tanks. On page 82 of Aero Detail 7 is a small notation which states that a number of A6M5bs were modified to carry both a centre-line bomb load as well as wing tanks. This was done to maintain the same range performance as regularly equipped Zeros. A photo on pages 20-21 of the recently published Japanese Naval Air Force in Action shows several carrier-borne A6M2s equipped with wing mounted drop-tanks. (Image 1) The tail codes visible on several other aircraft in the foreground help identify the image as having been taken some time before the Battle of the Philippine Sea. Using the evidence from this photo, it can be argued that the bomb carrying A6M2s used during the Battle of the Philippine Sea were also equipped with wing drop-tanks. Further substantiation for this can be found in looking at the battle itself. The Japanese strategy was to use the advantage of their planes’ longer range to be able to attack before the Americans were within range themselves. And to maintain this longer range the A6M2 had to be able to use the additional fuel available in external drop-tanks. A6M2 Sen Baku Markings Information on markings for the Battle of the Philippine Sea Sen Bakus is likewise very sparse, being limited to only one such aircraft. The picture below is form the USMC collection at NARA. It is identified as being taken on Guam in July of 1944. According to Jim Lansdale a second photo in the same series appears to show the same plane in the background of the image with the code of “323“ visible on the tail (Image 12) It is assumed here that the “2” in the “247” part of the tail code identified the role of plane “47” as a bomber instead of a fighter, continuing a practice used previously by IJN carrier units. The tail code prefix of “323” serves to further identify the plane as belonging to the 3rd Carrier (Ryuho) of the 2nd Carrier Division. All of the aircraft of the 2nd Carrier Division were administratively assigned to the 652 Kokutai. According to Hata and Izawa as well as Tillman the 652 Ku launched either 25 or 26 of its full complement of 26 A6M2 fighter-bombers as part of the second Japanese air strike on the 19th of July. This force came in from the north and had minimal contact with American forces. In spite of this, 4 A6M2 fighter-bombers were lost. It seems safe to assume that any of these 4 planes might have crashed on Guam. From all of the above it may be possible to reconstruct the appearance of at least one of the rather elusive A6M2 Sen Baku that took such heavy losses in the Battle of the Philippine Sea. Bearing the tail code of “323-247” it was equipped with two wing mounted drop tanks as well as a flush-mounted bomb rack to carry a 250 Kg bomb. Over the past months Dave Douglas has been allowing me to berate him with endless suggestions concerning his outstanding series of Zero profiles. He has been kind enough to take my contradictory notes and comments and create a profile of the Sen Baku which has been described above. (Image 13) Dave has also provided a drawing of the bomb rack used on the A6M2 Sen Baku. This illustration also provides a better look at the Type 99 #25 Model 1 Ordinary bomb and its markings. The bomb’s markings are of the earlier war pattern which were continued up to July 1944. (Image 14) A6M2 Sen Baku Package: for SF/WoV/WoE WW2, PTO installs This little modification creates a new aircraft based off ArmorDave's A6M5 "Zeke" IJN fighter and Wrench work. Included in this package are the skins, inis, and some various small and sundry bits. The aircraft LOD and cockpit folders are NOT included - you 'll be transfering them over from the stock A6M5. Therefore, it is NOT a complete aircraft package. = You MUST have the latest Weapons Pak installed for the WW2 Weapons!!! = Obviously, you must have AD's Zero's installed to use the package.... --------------------- Install instructions: Unzip, as I always reccomend, the "A6M2 Sen Baku.zip" to a temp folder somewhere that easy to find. Create a new folder, "A6M2 Sen Baku" in your game's main /Aircraft folder. Copy/paste all the new items; inis, skin folder, and the various and sundry bits I've supplied, into the new A6M5C folder. From the original A6M5, transfer over (copy/paste) the following items: A6M5.LOD A6M5.OUT (usefull for decaling) Cockpit folder -- the whole, entire folder :) Copy/paste the "LavEngine.wav" into your sounds folder, if you don't have it already. This is from Hinchbooke, and was (duh!) designed for the Soviet Laggs and the LA-9 and 11. It has a nice raspy radial sound. Hangar and Loading screens are included. They're my old one's for a way's back. That's pretty much it...go fly! --------------------------------------------------------------------------------------- --Credits/Sources: ArmourDave for creating the Zero in the first place; Volksjager and Lansen for the original skins; MoonJumper for finding the PappaRomeo EAW sight pack; Hinchbrooke for the LavEngine sound; All the other WW2 Junkies out there; TK for creating the open sourced marvel for use to play with Famous Airplanes of the World #55: Mitsubishi A6M, Model 11-21 Aero Detail #7: Mitsubishi A6M Zero Fighter Aircam #16: Mistubish A6M Vol.1 Osprey Aircraft of the Aces #22: Imperial Japanese Navy Aces 1937-1945 Kagero: 3/202 Kokutai Mushroom YS 3: Mitsubishi A6M Zero Profile #236: A6M5-A6M8 Profile Aircraft #129: Mitsubishi A6M2 Zero-sen Squad/Signal #1059: A6M Zero In Action ----------------------------------------------------------------------------------------------------- Any problems, questions, comments or other ideas can be directed to me on the CombatAce and SimHQ message boards. -------------------------------------------------------------------- Legal BS: This is freeware; it CAN be distrubuted as such if permission is granted by me, AD, and the original readme and all pieces of the package remain intact. The Mitsubishi A6M5 remains the intellectual property of ArmourDave (and Mitsubishi Aircraft, it's heirs and/or successors) See the original readme documentation for further allowances and restrictions Any persons wishing to make further modfications of the aircraft inis, skins, cockpit, etc, MUST obtain permission from the whole of the developers/moders. This package may NOT in any way, shape or form be used in any payware addition without permission of myself, ArmourDave, or anyone associated with it. Percentages of payment are -always- open for negotiation. ----------------------- Click here to download this file

don't use on WOI he don't work properly i use on WOE, WOV and strike figher all full patch christian