GwynO

You raise some very good point here Typhoid, I do not dispute the fact that computer aids are not one hundred percent accurate, merely that they are and have been for quite some considerable time, the norm. I intend to continue this in another thread so as not to hijack this one further. I will say though that I disagree with your view that the reality of military aviation is to fly a depressed reticle over a target with absolutely no fire control whatsoever other than "one potato two potato" that strikes me as pure fantasy to be honest, that such dead reckoning bombing has been used since the 2nd World War is no doubt true, but it is by and far the exception to the rule. As for the fact that you correctly state, that fire control is prone to error, my attitude is to model it into the code. I believe there is or was an entry for CEP in the old weapon editor, perhaps TK has already been thinking along those lines, certainly I am not proposing he add something to the game that makes bombs magically fall off the aircraft and always hit the target, that would be just as bad as not having any fire control at all imho. With respect sir, Gwyn.

I knew that you knew about those, some people do, but too many don't. The OP brought up one of the most important issues of playability in the Thirdwire gamesm chiefly that what we do in game with "multi million dollar" jets is little more than what was expected in a Stukka divebomber or other such craft with a dumb gunsight reticle (i.e. no fire control). Yes LORAN A had its problems by all accounts, yes fire control was shoddy even into the 1960's but the important thing is it was the backbone of how it was done. I put my two pence in because I feel too many people on CA would be shocked to realise that in a real life shiny 1960's jet fighter like an F-4 well before CCIP or even a proper HUD to show it on ever saw the light of day, the norm for bombing was for the pilot to give permission to a computer to drop the bombs at the right time. Accurate or not, that is what the OP was enquiring about but when it crops up it seems to end up boiling down to the same argument of.. it didn't have a CCIP/HUD so it had nothing, which is wrong, it means rather that we have nothing in game as is to even begin to hint at the vaguest, slightest accuracy of what 1950's onwards bomer/attack fighters did because what they certainly did not do was rely on doing the all math themselves with only a depressable gunsight to help!! The game is fantastic at making things look good though, and there are ways to suspend the disbelief factor. I like to imagine for example that every time I fly a phantom on a strike mission in the Thirdwire games, that it took a hit in the avionics or they caught fire or something, or maybe the groundcrew tied one one the night before and installed it upside down. Other than that I turn on CCIP as a next best thing, I would suggest the OP to check out the knowledge base on adding it to aircraft if that might help to resolve the issue for now. Glorified stop watch! I don't know about that, from what I read it was quite a complicated glorification to say the least! Besides, the nuclear application of over the shoulder lob bombing grew from the low altitude level bombing for iron bombs that required a much smaller CEP. Dive toss as another preferred method had accuracy at least as good as the early CCIP enabled HUD's and all.

My thoughts and prayers go out to all those affected by these fires. Saw the news reports yeaterday, looks nasty.

Sorry to but in on this but Fubar you really do know what the OP is referring to is fire control, I suspect that you are well aware of the fact that radar bombing, loran, labs and ins based bombing modes where the norm for most bombing profiles since the 1950's. CCIP and hudology is something related but not the same thing at all. Plenty of aircraft had bombing computers to do the math without a hud, B-29 over Korea for example. As for the AIM-7 not giving you a clue when to fire, that guide is excellent, but in an F-4 you also have the in range light in the cockpit.

Horrible feeling to be drawn out to sea in a rip, luckily though, you can get out two ways. If you are feeling energetic, swim as hard as you can 90 degrees against the current, a rip is usually narrow enough that you can swim out to the side of it and then turn in to shore. Failing that if you are too tired, weak or lazy but casual about survival, float with it and hope it dissipates out until you can then start swimming at an angle away from it toward shore. The second way will require a lot more swimming in total but less frantic swimming to start with. In different circumstances, had you had the luxury of knowing that your dad and other people could summon help in the shape of a boat and the kids were slipping under with you, I would have probably suggested to you to get them to lay back and float with it. I think you should get some recognition for this mate! Takes a real hero to jump in like that when you know it can go pear shape. Well done!

AFAIK the settings in the missioncontrol ini effect all the aircraft, normal will be the level that they appear during most parts of the flight through their waypoints, low level effects how low they will go during ACM I think, as does high altitude, I may be wrong though. Also I thought perhaps the low level effects the altitude that the AI drop weapons from but doesn't seem to be the case as my big bombers drop from 30,000 as soon as I tell them to. The only irritant is that when you fly as a stirke fighter, you don't always want to alt N to the IP as you will have a very steep decent into the target area before you can attack, my solution is to keep two seperate instances of the file and swap out the appropriate one as needed. Also a word on setting the low altitude, if you fly on enemy skill level hard, this reduces the skill of your wingmen while increasing the AI so setting this value too low will result in more deaths by ACM to your AI flights, setting the enemy skill level to normal and reducing to 40 gives a better balance IMHO.

I think you edit the values for that in the MISSIONCONTROL.INI file, extract it from one of the cat files in the flight folder if it is not already in there. My section looks like this: [Altitude] Normal=9000 Low=1500 VeryLow=100 High=9500 VeryHigh=13000 When I alt N I find all aircraft are usually at 30,000ft. I think this alteration was reconmended with one of the Buff releases a while ago.

No worries, glad to be of some small use!

Sometime around 02/03 I was getting into Flanker 2.0, wondered if it was possible to mod the game and came upon Biohaz which brought LOMAC to my attention. I wish it hadn't because I have never ever managed to get it to work on any system I have owned (been able to afford owning!) since. I bookmarked the site and never bothered to make a membership until some time after getting into SFP1, in 2004 I became j0072132, downloaded a few files, don't think I ever posted anything on the forum back then though. I drifted away from PC games in general due to real life priorities (drinking/sleeping around) at uni. Drifted back into PC games sometime in 06 (glad I did) but couldn't logon anymore, hence new membership as MG subsequently KNX Edit: sight for site! Duh and supposed to be an English teacher (slaps head)

Thanks for the link! TK seems to remember that the Cobra they did was not for the USAF sim after all, maybe from the Jane's Longbow game? Didn't he work on that?

Neither: Star Wars is a glorified Western in space, Star Trek has silly weapons but the ideas of a laser beam that can be be stopped at a metre and half or so by soem unknown "force" is too unreal for me. Perhaps the least amount of suspension of belief is required by something like the Alien or Predator mythology than either of these clunky special effects and waffle fests. Oh and another thing that really, really gets on my wick about Star Wars is the incessant muzac that plays whenever anything at all happens, even more noticeable and annoying in the last round of films than the originals.

And many more!

in the nose section, purely nominal, you could as easily put it in the tail, but as the "nose section" better corresponds with where it was in reality, best stick it there :yes: It works as Tannethal says. Better than nothing, I may have missed something, I am determined tomorrow morning to look why I can't seem to get it to work with the nicer F-14 specific tga's, it is in my older install. As of now, off to dream circa 1991. Once again, thanks to all involved for a free addon equal to if not greater than a whole new release. :

To delete the pilots: Open the B-52D_DATA.INI, ctrl F "pilot" to take you to this part that says: SystemName[001]=Pilot SystemName[002]=CoPilot , I think the game likes everything to be sequential 1,2,3,4, etc. so delete both these and then change the next entry (SystemName[003]=NoseGearL) to SystemName[001]=NoseGearL and so on so it looks like 1,2,3,4,5 etc again with no missing 1 and 2. You only have to finish it for that paragraph. Ctrl F again to find next entry with "pilot" in section: // Crew --------------------------------------------------------- [Pilot] SystemType=PILOT_COCKPIT SeatID=1 SetCockpitPosition=FALSE Position=-0.74,18.78,1.64 MinExtentPosition=-1.35,18.18, 0.08 MaxExtentPosition=-0.14,19.38, 2.10 CanopyNodeName= HasArmor=TRUE ArmorMaterial=STEEL Armor[FRONT].Thickness=6 Armor[RIGHT].Thickness=6 Armor[LEFT].Thickness=6 Armor[REAR].Thickness=6 Armor[TOP].Thickness=6 Armor[BOTTOM].Thickness=6 Delete the pilot paragraph and the co pilot paragraph, leave the tail gunner alone. If it doesn't work, I don't know what else to suggest. The deleted parts that read: Position=-0.74,18.78,1.64 MinExtentPosition=-1.35,18.18, 0.08 MaxExtentPosition=-0.14,19.38, 2.10 .. those are the numbers to change where the pilot sit, but it will take a lot of trial and error to figure them out. Hope it works for you.

I noticed that although the Tiseo tga files are present in the flight folder, the F-14A makes no use of them, stick this in the data ini to fix SystemName[009]=TISEO and [TISEO] SystemType=EO_CAMERA ModelNodeName=TV CameraFOV=15.00000 SightTexture=F-14_tiseo.tga SeekerRange=30.000000 SeekerGimbleLimit=40.000000 SearchFOV=5.000000 SearchTexture=F-14_tiseo2 then this into the avionics ini [TVDisplayData] UseRadarTexture=TRUE ApplyFilter=TRUE FilterMaterial=DTVFilterMaterial OverlayTexture=cockpit\F-14A_DTV.tga [DTVFilterMaterial] IRImage=TRUE DepthBufferCheck=FALSE DepthBufferWrite=FALSE RenderedInOrder=FALSE AlphaTestEnabled=FALSE CullMode=NO_CULL LightEnabled=TRUE SpecularEnabled=FALSE EmissiveEnabled=FALSE FogEnabled=FALSE AmbientColor=1.000000,1.000000,1.000000,1.000000 DiffuseColor=1.000000,1.000000,1.000000,1.000000 ZBufferOffset=0.000000 PriorityLevel=2 BlendOp=MODULATE NumTextureStages=1 TextureStage[01].TextureName=cockpit\GreenTVFilter.bmp TextureStage[01].MipMap=TRUE TextureStage[01].FilterEnabled=FALSE TextureStage[01].StageColorOp=TEXTURE TextureStage[01].StageAlphaOp=DIFFUSE And the avionics are miles better looking from the previous version, well done to whoever did them! Edit: Ok the above noted method requires some additonal tga's from Typhoid's excellent D model, if you haven't got them try this instead: SystemName[009]=TCS [TCS] SystemType=EO_CAMERA ModelNodeName=TV CameraFOV=15.00000 SightTexture=TISEO_search.tga SeekerRange=30.000000 SeekerGimbleLimit=40.000000 SearchFOV=5.000000 SearchTexture= It's late, i'm confusing myself.

Couldn't you just delete the pilot entries from the data ini for the new Buff and fly it without those sticky out pilots? Or better still reposition them to fit (would take quite a bit longer)

At least in a game we don't have to put up with that kind of frustration, see mig, shoot, kill, go home and fly another day..

YAP yes The USAF recruitment game by TK, unfortunatley not available as far as I know. But if enough people ask TK for it, who knows?

The Cobra depicted on the Thirdwire page is from a recruiting sim TK created for the US military according to Streakeagle.

Awsome mod! Big thank you to all involved! Was having a blast going through single missions in all the aircraft, but when it came to the SU22 stand in, noticed a problem, the swing wings deploy the wrong way around making it next to impossible to fly. AI can't fly it well like that either, saw my wingies crash into the ground like flies trying to land. Here is the section of the data ini needing change: [swingWings] SystemType=HIGHLIFT_DEVICE CLiftdc=0.1081 CDdc=0.0264 DeltaStallAlpha=6.00 AreaRatio=1.00 DeploymentMethod=AUTOMATIC_MACH Setting[1].Angle=28.0 Setting[1].DeployValue=0.60 <---- I believe maybe swapping these lines does things right Setting[1].RetractValue=0.70 <---- Setting[2].Angle=45.0 Setting[2].DeployValue=0.70 Setting[2].RetractValue=0.85 Setting[3].Angle=63.0 Setting[3].DeployValue=0.85 Setting[3].RetractValue=0.80 MaxDeflection=63.0 MinDeflection=0.0 ControlRate=1.0 AnimationID=2 No biggie just thought I would point that out, have already changed mine for this one http://forum.combatace.com/index.php?autoc...p;showfile=5712 There may be one in Lindr's pack also http://forum.combatace.com/index.php?autoc...p;showfile=8096 haven't checked it out yet.

You watch how different it will be when (if?) we get the F-35B and a new carrier! All the best to you mate!

Seriously, I couldn't believe this email I had today, not the bit about the $20 bill but the first part. Can all that really be true? I am not usually a tinfoil hat kind of person but it's hard not to wonder sometimes. I know that probability and possibility are very different things, I don't for one minute think it is impossible for such coincidence to happen but still... makes my brain hurt! Anyways, for those of a Fortean bent, you may enjoy to read it and check yourselves the details in other sources, that is what I'm doing now. History Mystery Have a history teacher explain this----- if they can.. Abraham Lincoln was elected to Congress in 1846. Jo hn F. Kennedy was elected to Congress in 1946. Abraham Lincoln was elected President in 1860. Jo hn F. Kennedy was elected President in 1960. Both were particularly concerned with civil rights. Both wives lost their children while living in the White House. Both Presidents were shot on a Friday. Both Presidents were shot in the head Now it gets really weird. Lincoln 's secretary was named Kennedy.. Kennedy's Secretary was named Lincoln . Both were assassinated by Southerners. Both were succeeded by Southerners named Jo hnson. Andrew Jo hnson, who succeeded Lincoln, was born in 1808. Lyndon Jo hnson, who succeeded Kennedy, was born in 1908. John Wilkes Booth, who assassinated Lincoln, was born in 1839. Lee Harvey Oswald, who assassinated Kennedy, was born in 1939. Both assassins were known by their three names. Both names are composed of fifteen letters. Now hang on to your seat. Lincoln was shot at the theater named 'Ford'. Kennedy was shot in a car called ' Lincoln ' made by 'Ford'. Lincoln was shot in a theater and his assassin ran and hid in a warehouse. Kennedy was shot from a warehouse and his assassin ran and hid in a theater. Booth and Oswald were assassinated before their trials. WHO FIGURED THIS OUT? INCREDIBLE 1) Fold a NEW $20 bill in half... 2) Fold again, taking care to fold it exactly as below 3) Fold the other end, exactly as before < /B> 4) Now, simply turn it over... What a coincidence! A simple geometric fold creates a catastrophic premonition printed on all $20 bills!!! COINCIDENCE? YOU DECIDE As if that wasn't enough... Here is what you've seen... Firstly The Pentagon on fire... Then The Twin Towers. .And now .. look at this! TRIPLE COINCIDENCE ON A SIMPLE $20 BILL Disaster (Pentagon) Disaster ( Twin Towers ) Disaster (Osama)??? It gets even better 9 + 11 = $20! Creepy huh? Send this to as many people as you can, cause: Hey, this is one history lesson most people probably will not mind reading! The pictures haven't come out but text was the startling bit anyway.

$$ Kerching!

Here's to hope!