quack74

As of now there is no way for big bombers to take off together on airfields. The spacing of aircraft at take-off is set up for fighter aircraft. So the wingspan of the bombers makes it a bit tight. You can manually change the spacing of aircraft by editing the WWI_AIRFIELD.ini found in any of the terrains' folders. The spacing is done by X,Y coordinates. But the spacing might look too big when using fighters. I just start in the air. As far as the flight model is conserned, Peter01 has created great new flight models for all the aircraft. Including the GothaGIV. They can be found in the CombatAce download section under First Eagles/Flight Models. There might be a couple of them. Just choose the one you like best. My Gotha works flawlessly now. The AI bombing when you do is still a bit rough though. Hope this helps

This is something I've done for awhile now. Figured I'd share with you guys. It's a simple tweak to get different skins for the same aircraft to appear in the same missions. eg. In one mission I'll see an enemy flight of FokkerDr1's in Jasta 11 colors. Then in a matter of minutes I'll be jumped by a flight of Fokker Dr1's from say Jasta 27 (sometimes ). The aircraft do appear at random. The chances are pretty slim the same aircraft with different skins will appear at the same time. But it has happened. Before I would just put my favorite skin as [TextureSet001] in the aircrafts's Config.ini file to make it appear all the time. Gets kind of boring after awhile seeing the same skin over and over.. So I just copied an aircraft folder (or as many aircraft as you want or as many times as you want) and put one skin inside. For the stock game aircraft you have to unpack the CAT security folders in the C: /First Eagles /objects/ CAT.ini folder using the SFP1 Extract Utility found here at CombatAce in the SFP1 download section under "Utilities". Once you unpack everything copy then paste the aircraft's Config.ini file and DATA.ini file (from the aircraft you're copying ofcourse) into the new folder. Then rename a couple of things. See below. 1. Copy any aircraft folder and rename it. Ex: From FokkerDr1 to FokkerDr1J27 (for Jasta 27 skin to appear). 2. Then copy the original aircraft's Config.ini file and the DATA.ini file from the /Objects/ folder and paste them into the new aircraft folder. 3. Rename these two files from FokkerDr1.ini to FokkerdR1j27.ini and FokkerDr1_DATA.ini to FokkerDrJ27_DATA.ini 4. Open the FokkerDr1J27.ini file and change ONLY the lines in the [AircraftData] section as follows then save: [AircraftData] AircraftFullName=Fokker Dr.1 J27 <--------here AircraftShortName=FokkerDr1J27 <--------here AircraftDataFile=FokkerDr1J27_data.ini <-------and here CockpitDataFile=FokkerDr1_cockpit.ini HangarScreen=FokkerDr1_hangar.bmp LoadoutFile=FokkerDr1_Loadout.ini LoadingScreen=FokkerDr1_Loading.bmp 5. From the new AC folder open the Config.ini file again, select only ONE skin (TextureSet), the one you like best, and delete the rest. Renumber it [TextureSet001] and save. 5. That should be it if I remember correctly. Remember this is just for AI aircraft. You should select the original aircraft to use and from there select the skins you want. The new folders will only have one skin. The add on aircraft from Skunkworks and other third-party developers have all the aircraft info already in the aircraft's main folders. So you wont need to unpack anything for these aircraft. Only change the names of the .ini files and the names inside the aircraft's Config.ini files. Might get confusing but just post questions here at this thread for help. This seems very long but it's really not. If it doesnt work then I must have left something out somewhere. Just yell at me in the next post. But this is well worth it. Variety is always best

Do custom skin appear in MP? Do you see EA's custom skins or only default?

He also said the next EP was atleast a year away. Not very exciting. But will be great when it comes out I'm sure.

As far as I know the only DH-4 and F2b for FE is only available at Skunkworks. Why it's so hard to obtain a password or download them from Skunkworks, I have no idea. Many people have complained about this before. You would think they would want more people using their stuff. Thirdwire needs to release more of these planes themselves so there are no more problems. But I dont even know if Thirdwire is going to release anything new as far as aircraft. If they do plan on it, nobody knows what planes. I have found with these sims and their site, they dont fill you in on anything or answer too many questions. You just have to wait like the rest of us

Where and how do you guys play FE online? I would like to start myself. And around what times do you play?

The Dr.1 was notorious for being an unstable gun platform anyway. So it will take some time to get used to it anyway. I find with the flight model I use for my Dr.1, It is hard to get a good bead on an EA. But as Tailspin said, You need to train your eye on those tracers. Practice shooting balloons at level flight.

These all appear at random during missions.

I'm trying to make a few more balloon schemes. They will appear at random along with the stock ones. So at one time there will be multiple balloons for each side with different color schemes. So far it's working. Need to work on it some more. And yes I've seen pics with lozenged balloons BTW, this will be a new GroundObject. It's not just a repaint of the original.

I just added a new readme file for the No.202 Squad DH-4 in the download section. I forgot to add the fix for the DATA.ini file to make the wheel hubs rotate. You can re-download it for the readme file or just add the below fix to the DH-4's DATA.ini file. Found at the bottom in the Landing Gear section. // Landing Gears ------------------------- [LeftMainGear] SystemType=LANDING_GEAR Retractable=FALSE ModelNodeName=Gear_L ShockAnimationID=-1 //ShockStroke=0.07 ///ShockStroke=0.20 ShockStroke=0.25 //SpringFactor=1.3 SpringFactor=3.0 //DampingFactor=2.0 DampingFactor=3.0 WheelNodeName=Hub_L <--- add this line //WheelNodeName=Tire_L <---add the two back slashes to the front of this line RotationAxis=X-Axis //RollingRadius=0.40 RollingRadius=0.40 CastoringWheel=FALSE RollingCoefficient=0.15 MaxLoadFactor=4.0 [RightMainGear] SystemType=LANDING_GEAR Retractable=FALSE ModelNodeName=Gear_R ShockAnimationID=-1 //ShockStroke=0.07 ///ShockStroke=0.20 ShockStroke=0.25 //SpringFactor=1.3 SpringFactor=3.0 //DampingFactor=2.0 DampingFactor=3.0 WheelNodeName=Hub_R <---add this line //WheelNodeName=Tire_R <----add the two back slashes to the front of this line RotationAxis=X-Axis //RollingRadius=0.40 RollingRadius=0.40 CastoringWheel=FALSE RollingCoefficient=0.15 MaxLoadFactor=4.0 Thanks to Heck for this fix

Here is a link to a great forum I found with hundreds of WWI photos. There are some graphic ones too. But some incredible pics. It is a forum so there will be some comentary along with some pics. http://www.militaryphotos.net/forums/showthread.php?76040-World-War-One

Just a note Peter01, I installed your new FM to my DH-4 and found all ailerons and elevators are reversed. The input and response is correct. Justr the models' parts move in the opposite dirrections.

I dont know if you read the part about the DH-4's elevator response I was having problems with. At all speeds the elevator function works just fine and very responsive up till about 75% up. This is where the response is minimal. If I pull back full up on the stick the DH-4 seems to just flatten out. Hardly any positive pitch response. So I have to let up just a bit for it to grab again. Kind of har to explain. But I was wondering if you have fixed this problem? The DH-4 is the only that has this problem. And I never messed with the DATA file before. Some new flight models for the bigger planes and two-seaters would be great.

That all sounds like it'll do the trick. Thanks Peter01 . I'll give it a go tomorrow and will report back. I do find some 2-seaters are way too accurate and some are horrible shots. I need to find a good middle ground for sure. I do like attacking the ones that are horrible shots though

Wow you're right. Didn't even think about that. Need to make some more I guess

View File No.45 Squadron Camels This is a generic skin pack of No. 45 Squadron in mid 1917 to 1918. No.45 Sqn first flew in France in mid 1917 and was transfered to Italy. Then to return to northern France in late (September) 1918 to finish out the war. These Camels were covered almost entirely in PC10 with a white dumbell on the rear fuselage and up on the rear decking. For this Camel I used the F1_130 version. Enjoy, quack74 Submitter quack74 Submitted 01/31/2010 Category Sopwith Skins

View File No. 202 Squadron DH-4 2-pack Thanks to the SFP1 A-Team SkunkWorks and Capun1950 for the DH-4 model and permission to use the skin template. This DH-4 skin pack is from No.202 Squadron France 1918. Flown in the Flanders region around Northern Belgium. Previously 2RNAS before the creation of the RAF. 1. Serial N-5779 (lightning bolt on fuselage sides). I dont know the pilot or observer. 2. A generic No.202 Squadron skin (red and white wheel discs and white nose lettering with red shadowing. There are a few different versions of the DH-4 according to engine and date. They are available in the FE forum section thanks to Panama Red and Sinbad I believe. Goes back a few months. But place these skins in any folder you wish. you may only have the one DH-4 folder anyway. Enjoy, quack74 Submitter quack74 Submitted 01/31/2010 Category Other Entente Aircraft Skins

The No.45 Squadron skin of the CamelF1_130 (the one I used) is now in the download section. You could also add the skin to the CamelF1_150 for later service.

This DH-4 2-pack is now in the download section. I just added a new readme file for the No.202 Squad DH-4. I forgot to add the fix for the DATA.ini file to make the wheel hubs rotate. You can re-download it for the readme file or just add the below fix to the DH-4's DATA.ini file. Found at the bottom in the Landing Gear section. // Landing Gears ------------------------- [LeftMainGear] SystemType=LANDING_GEAR Retractable=FALSE ModelNodeName=Gear_L ShockAnimationID=-1 //ShockStroke=0.07 ///ShockStroke=0.20 ShockStroke=0.25 //SpringFactor=1.3 SpringFactor=3.0 //DampingFactor=2.0 DampingFactor=3.0 WheelNodeName=Hub_L <--- add this line //WheelNodeName=Tire_L <---add the two back slashes to the front of this line RotationAxis=X-Axis //RollingRadius=0.40 RollingRadius=0.40 CastoringWheel=FALSE RollingCoefficient=0.15 MaxLoadFactor=4.0 [RightMainGear] SystemType=LANDING_GEAR Retractable=FALSE ModelNodeName=Gear_R ShockAnimationID=-1 //ShockStroke=0.07 ///ShockStroke=0.20 ShockStroke=0.25 //SpringFactor=1.3 SpringFactor=3.0 //DampingFactor=2.0 DampingFactor=3.0 WheelNodeName=Hub_R <---add this line //WheelNodeName=Tire_R <----add the two back slashes to the front of this line RotationAxis=X-Axis //RollingRadius=0.40 RollingRadius=0.40 CastoringWheel=FALSE RollingCoefficient=0.15 MaxLoadFactor=4.0 Thanks to Heck for this fix

I got all my two-seaters' rear gunners to fire. But I'm having a problem with the DH-4 rear gunner. He doesnt seem to fire 99.9% of the time and when he does it's just one burst maybe every 10 seconds. But will only shoot twice or three times. Aso doesnt seem to be locking on to any close enemy aircraft. I've checked all info in the DATA.ini file and all gunner info seems to be the same as other RAF two seaters that work just fine. Any ideas? Can someone post there DATA.ini file for their working gunner so I can compare? Thanks in advance.

Very cool trick. How'd you figure that one out? Wish I knew that before . That was one of those things that bugged me about the Pfalz wings. I guess I have a lot of fixing to do . Thanks again Heck.

Awsome! Thanks Heck. Good to hear from you too.

The problem with the No.202 Squad wheel discs being red and white halves is the wheels themselves don't rotate. Only the tires rotate. Can anyone fix this? For now I just changed the position of the red and white on one of the wheels to make them appear uneven. But for now they don't spin. Oh, and thanks for the compliments . Always nice to hear.