Z09SS

I'll admit in my excitement at the plane list for those that I missed that they were AI only myself. I even reinstalled the whole game before I saw the giant capital letters staring me in the face... Thanks to here the plane I was most excited about got a cockpit and is flying regularly.

Never. Save. Your. Wingman. I ingressed, hit the target, and was egressing nicely when wingy starts screaming that he can't shake someone. MiG-17F had padlocked on his butt so I went back to help. Then I departed the aircraft and couldn't recover. Nylon let-down into the waiting arms of some damn commie army unit. Since he didn't actually die, I think Oberleutnant Winter will reappear in 1968 in Red Hammer.

Tactical Reconnaissance is such a milk-run if you don't chase rabbits.

I got my blood up and fangs out and just HAD to nail a MiG-19S that jumped us on egress. As a result I had to divert to Köln-Hahn instead of landing at my home base of Nörvenich. Considering I'd taken some 14.7mm fire over the target, I should have just called for help and beat feet. Still, the Starfighter gets decent mileage at 30k feel MSL and 210 KIAS.

I think I'm overachieving. I think the "rules" are per day of playing not per day of game. But I'm having fun and not hurting anyone but digital communists...

Progressing... I missed the warehouse and I'd ordered my wingman to drop his bombs on something else. Two MiG-17F objected to our egress, one putting moderate damage to the wingman before I could hit him with the gun. As usual, the AIM-9B was useless on fighters.

I stopped using alt-n to get around because the game keeps track of fuel weight and the F-100D I was flying at the time was too tubby to turn. I've been relatively happy with these settings... I was using hard weapons but on most planes the mean rounds between failures was way too high. Enemy Skill Level Normal Flight Model Hard Weapons Normal Radar Display Hard Visual Targeting Normal HUD Display Normal Landing Normal Collision Normal Blackout Normal Ammo Usage Hard Fuel Usage Hard

How come some clocks in some pits work and don't in others? And how would I go about fixing them? Is this a simple ini edit of taking a working clock from one plane and inserting into a broken one? I just noticed that the clock works in the F-104 pit but I can't tell what time it is in a Phantom.

New campaign, better record keeping! Day 2: The warehouse mission went near textbook except for accidentally punching off my tanks when they still had some usable vapor left in them. I've noticed that when my survival matters for the purposes of posting here, I am a lot less greedy about going after non-targets and simply getting MY mission done and getting home.

I started this campaign long before the rules for daily progress were added... But flying one mission a day or less sure helps my survival rate! Almost as if I was getting tired, bored or complacent if I sit at the stick too long. That's The Six Day Way by the way. Took two tries through to get a clean campaign, and since dead is dead, I had to make a whole new pilot!

I agree as well, paid for them too! Heck, I paid for every DLC just to keep him interested... alas.

And the glass returns to being 99/100 empty.

Someone's glass is 1/100th full! Especially since anything new has to account for an OS shift (or two).

USAF F-104C(66) in the Six Day War (on Israel's side).

I had that problem too and it was a graphics setting for the game and nothing I'd done to the plane.

I know your pain!

And his F-102A! So you can mod it with downloads from here...

I recall that this topic went round and round with TK once on the TW forums. I don't remember why he didn't allow the pods to be carried on the TER, but he didn't and it's not an easy fix now. Often accompanied with a $500k price point... I too wonder what fallenphoenix1986 is wondering about. A new weapon that looks like a TER with three pods on it...

Did some tweaking myself... Set the nose to TRUE again. Double checked the seat/pilot location: [Pilot] SystemType=PILOT_COCKPIT PilotModelName= SetCockpitPosition=TRUE Position=0.00,6.70,0.61 SeatModelName=seat_f-104 SeatPosition=0.00,6.65,0.10 MinExtentPosition=-0.25, 6.06,-0.14 MaxExtentPosition= 0.25, 7.19, 0.82 CanopyNodeName=canopy_mid_outer CanopyAnimationID=5 changed [CockpitSeat001] ModelName=f-104G_cockpit // Position=0.0,5.801,0.616 // Position=0.0,6.201,0.616 // Position=0.0,5.52,0.545 // Position=0.00,6.65,0.10 Position=0.00,6.70,0.61 I know the // means ignore... With it set at 0.00,6.65,0.10 the view was: With it set to 0.00,6.70,0.61 the view changes to: I think that looks about right, especially since the double canopy frame is gone and the probe is visible: I did a before and after comparison too. Before making any changes from what I'd downloaded: After your suggested changes, Fubar: Thanks for the help!

This is what I found in my ini... The cockpit ini ModelName=f-104G_cockpit // Position=0.0,5.801,0.616 // Position=0.0,6.201,0.616 Position=0.0,5.52,0.545 Data ini Position=0.00,6.70,0.61 Looks like someone tweaked it twice before I got there.

I wouldn't doubt it. I am not sure how motivated I am to fix on it though. Mostly because I'm not sure WHAT to change to correct it.

Same trick works so the fuselage shows in the mirrors! I added "ShowFromCockpit=TRUE" to the fuselage section and that makes the intake trunking show. Making the nose visible gives a double canopy frame, not sure what to do about that.

I didn't say it right, what would it take to see the intakes in the mirrors? If I don't say what I mean, how can I mean what I say? Right now there's open space where the wing ends, the top of the intakes or fuselage should be visible in the mirrors no?