posted 02-18- 12:58 AM               

This is a new plane, the F4U-1A, so it will not replace any existing Corsairs, and you should be able to use it online without mismatches (at least so far).

Get it at www.simfiles.com]www.simfiles.com
Unzip to your Fighter Squadron directory

New stuff:

--Modified version of Condor's engine damage
--Working cowl flaps
--Mace's carrier ops system
--Killable/woundable pilot
--New skin by casualty26ac
--Control surface damage
--Bulletholes and other visible damage
--Flight model reworked extensively

It's primarily intended for use by "real" pilots, and the AI has a few problems with some of the damage you can take. I may release an AI version as well for use as enemy or offline wingmen, depending on the feedback I get.

Give 'er a workout, let me know what to fix...

------------------
--jedi--

posted 02-18- 03:38 AM               

**bugs**

I got into a fast dive while trying to get away from 9 zeros and I pulled to hard and bent the wings up some. The wings was bent but the flap damage was now visible in the place where the flaps use to be. But since the wings is bent that flaps are no longer in the same place.

Couldn't you have put the damage in the flaps and just unhide the damage after a few hits?

CTD

The AI was flying the F4U's cause when I fly it I waxed all the zeros and almost never take any damage. So, I flew the zeros and shot the F4Us down. They had 1900 lbs of fuel so it's not the AI fuel bug. All the other F4U's were still flying and all but another Zero and myself remained on the enemy side and the other zero was being chased by 2 P-51s and one of the F4U's two F4U's was chasing me and I was on the tail of the last one. I put some rounds in the fuse and left wing with the MG's but when I shot it with cannons I hit the right wing and center fuse and it bumped me to desktop. Maybe that will give you a general area to look for the problem.

Other then that is was very cool shooting at it. Need to see how the new F4U handles it's self against my Ki-61s.

I'll test the CTD problem more when I wake up. But for now i'm going to bed.

Great work on the new F4U!

------------------
Tony "Razer" Martin
FS Hangar

posted 02-18- 10:31 AM               

You are just so great to give me this on my birthday! Oh...um, yeah I am changing my birthday to February 18th.

It sounds great. It sounds like a fantastic damage model. Thanks. Have you found a way to let the player no when the pilot has been wounded? That way he/she could head for home immediately.

I will let you know if I get the ctd problem as well.

Thanks again,(btw the f4u is my favorite plane )

posted 02-18- 11:41 AM               

Thanks for this jedi,

posted 02-18- 06:55 PM               

Some testing done with strange results.
First 3 missions got ctd's when the f4u1a impacted the ground at high speed. Then after that, no more ctd's. Very strange.

Only in my opinion but the rudder seems too easy to damage and in slew mode the pilot is always dead with one shot(after the canopy is gone, which is a very cool feature). Is that the way it should be or should he be able to take 2 or 3 shots some times? Hell I know Pappy could take even 6 shots and still fly(alcohol that is ).

In combat pilot hits is usually how I get most of my kills.

On the fm, is tends to flop over in turns under 200mph. Is that the way you have intended it in order to prevent turn and burn fighting with it?

Thanks again for this plane. It is very greatly appreciated.

posted 02-18- 07:41 PM               

The CTD is the only thing that concerns me. Thought I squashed it. I'll have to shoot the thing up some more, and try just crashing it (although it usually just blows up if I crash it fast).

I had the pilot just "redding out" while wounded at one point, but he seems not to want to do it anymore. If you switch to external, you'll see him slumped over when wounded, but you can still fly. So far he will always slump over with one hit. Might be able to make that more random... There is a point where he's wounded and sees red, but can still fly the plane. Thought I had that point picked just right, but I guess not

The control surface thing is a good point, and I saw that one before too. I'll try to do the frames as hidden parts until damaged.

Rudder too easy to damage? OK, maybe a few more obHits. It can also be damaged by spinning the plane, which makes the spin a bit harder to recover from (although a "real" spin is a bit hard to get into in the first place in that plane).

The "squirrelly-ness" below 200 is intentional. If you can get the plane "smoothly" decelerated, you CAN turn at low speeds, but if you use Gs to bleed the speed, it will flop around a bit. It flies like that in Warbirds too. Don't know if the real plane was like that, but at least now if you want to turnfight in it, you need to be "smooth" on the controls You'll probably find that it's a lot more forgiving in vertical manuevering.

All inputs welcome...

------------------
--jedi--

posted 02-18- 08:51 PM               

The Meat Grinder training missions won't load, it immediately CTD's.

Real twitchy. Much more sensitive than the other Corsairs. Interestingly, in the Hangar Mission with bomb/rocket loadout it wasn't nearly so twitchy. COG issue? Maybe I was just flying faster as you noted above?

The top of the gunsite base texture tears at the edges.

Alt Q and Y do nothing.

Deck Launch training mission opens with you in the air, not on the deck. To get on the deck you have to F5 then F6.

In-air-starts begin with the canopy open, which immediately slams shut.

When I blew myself up dropping the bomb in the hangar mission it CTD.

As noted earlier, the flap structure was visible even when the flap was still intact.

At times,(not always) I noticed a separation at the front of the left wing where it folds.

Rudder doesn't seem to create much yaw.

posted 02-19- 01:12 AM               

If alt-Q and Y don't work, check your keyboard.inp file. Alt-Q is cmdCanopyOpen and Y is cmdWingSweepToggle. You may have an old keyboard.inp.

I can get it to CTD occasionally when I shoot a rocket at it on the ground in slew mode, but when I shoot it up in flight, it just blows up. I'll try fragging myself in the hangar mission.

If it CTDs on every mission, make sure you have the F4U1D airfoil in your startup.ppf. I didn't include it with this one since it's been in the last few planepacks.

The canopy is supposed to slam shut on mission start. That "dearms" the new bailout sequence. Without that the pilot sometimes would bail out on his own...

It will be a bit "twitchier" than the earlier one, since I gave it more elevator effectiveness. The previous version literally couldn't pull enough G to bleed down its speed, so the AI were all "master" energy fighters. But not any more

The file has gotten quite large over time. I think some of the other new DM planes are also starting to hog the FR a bit as well. I may be able to do some optimizing of the model parts there (not looking forward to THAT!)

posted 02-19- 08:55 AM               

What happens with the frame rate if you remove the antenna wires? I like them too but maybe if they cause too much fps hit, then consider remaking them or not using them. The fps hits may not even be caused by the wires, really just guessing here.

I did notice on one ctd I got, I was in external view with a damaged right landing gear just hanging down as the plane impacted the ground. It was probably just a coincidence. I hope it helps.

Please don't be discouraged at all though. This is a fantastic plane with a really great dm. I can't stop flying it!

------------------
Condor out

posted 02-19- 11:32 AM               

If you want to help me verify this (or just cut down on your own CTDs), you can get a supposedly "safe" pilot here:
http://sites.netscape.net/jeditaub/Downloads/f4upilot.ZIP

He's not "killable" YET, but I'm workin on it...

As for the wires, I'll try deleting them and see what it does. I suspect I'll need to do a more thorough optimization to get much benefit tho...

------------------
--jedi--

posted 02-19- 12:44 PM               

Would the test work if we delete the pilot file so no pilot would be in the cockpit at all? That way any ctd's that happen would definitely have nothing to do with the pilot file.

posted 02-19- 10:36 PM               

This is the Planepack 5.3 version of the F4U-1D, the "basic" plane for the Corsair set. It contains all the necessary files. Your startup.ppf file will have to be modified to include the airfoil reference.

posted 02-20- 01:39 AM               

Also, whats the 2nd engine sound? int he take off mission i take of and just as i leave the ground i hear the engine shut off sound but the plane is still running and the engine is still going. ideas?

i really like this plane i just wish i could get at the files to fix the smoothing and lighting on the fuse. it's a fast 4 min job and it would be perfectly rounded and look great. but OL crashes when i try to extract it. to much stuff in the plane.

posted 02-20- 10:59 AM               

I get a ctd on every training mission.

posted 02-20- 06:13 PM               

The second engine noise you hear is the catapult system disarming itself. If you hit the D key on the ground with the engine running, you'll hear it right then. If not, you're getting a catapult-assist on takeoff, and then that engine detaches. There are two engines in the damage modeling as well, and you might hear the second one start up sometimes.

Jug--

More info required. Do you actually get into the missions and they CTD later, or do they not even start? Don't use the Meat Grinder mission--there's something wrong with the way I copied it into the Corsair folder, and I can't get it to run any more. Also, do the original Corsairs work OK for you? Are you using Glide? Try D3D just to see if it works there. My gee-whiz Geforce 2 card doesn't support Glide, so I can't tell if my stuff works on Glide any more

posted 02-20- 09:15 PM               

Go to your media/pilot folder. Find the file called "f4u1apilotsit.sm" and rename it to "newpilotsit.sim" or some other catchy name.

This will remove the pilot model from the plane temporarily. I suspect the pilot model may have some "bad" .lods in it.

Try both D3D graphics rendering and Glide. As I mentioned, I don't have Glide capability any more, so I don't know if what I build will work in Glide.

Anybody have this working in Glide, so we can eliminate that as the cause?

posted 02-20- 09:59 PM               

i'm sure he'll include this int he next update and i hope i can fix up a few more things like the front gear doors being mapped on the bottom of the plane and a few more things he's had problems with on the FR department.

heres a pic of the updated F4U..