SupGen

Rogeo on the F-23.

The thing about Dogfights was that it a documentary so much as a real-time dissection of some of the more famous dogfights in history that (mostly) knew what it was talking about. They actually got most of the tactics right, most of the time. Where else have you ever seen a literate explanation of High/Low speed Yo-Yos' that was even close to the actual manuver? And with video, to boot, video, I might add, that made it seem you were watching a well made, narrated video of StrikeFighters2. The last thing I ever watched regularly on TV.

OK, I think thats got it. Migbuster, you're a genius. What I had to do was, because my SF2 install is on another drive, was to delete the folder in C: SavedGames, rename the folder in F: SavedGames after deleting the Options and Versions inis., run the game, delete everything in the C: SavedGames/FLAT TOP folder but the Options/Versions inis., change the dates and the pointers to match the F: SavedGames/FLAT TOP location, copy those to that folder and, VOILA there ya go. Still don't understand why Falklands wasn't affected, though. Oh well, don't borrow trouble, I guess. Anyway, thanks for pointing me in the right direction, Migbuster.

Thanks for the response, Migbuster. Whaddaya mean by old? I hadn't made a new install, as I said, my SF2 stuff is on a separate hard drive that was unplugged when I re-installed the OS. I just plugged everything back in and all of it works fine except for this. My Falklands install, for instance, which also has all of the stock aircraft deleted, works. I will try replacing those inis., though, at this point I'll try anything. One thing I am going to do is create a re-named Objects folder so I don't have to manually delete everything every time this happens.

To allay any fears that I might have been sitting here like a lump, waiting for someone else to work this out for me, I have already tried both of Wrench's fixes here: http://combatace.com/topic/71179-stock-aircraft-return-after-creating-stand-alone/ and neither one helps. This isn't a first run problem; no matter how many times I delete them, they come back.

I built my WWll PTO install about a month or so ago, left one blue and one red modern aircraft in the aircraft folder. This worked fine until I had to re-install my OS last week. SF is on a separate hard drive that was unplugged during the re-install so it should not have been affected, however since then all the stock planes return every time I start the game. Any help would be much appreciated. Thanks in advance.

Boy, this sounds like almost as much fun as amputating your pinky with a cigar cutter . Thank heavens I'm (at the moment) mostly interested in the PTO, I've got most of the USN squadrons now; I'll keep plugging away.

Bump.

Is there a full up, all inclusive Squadron List for WWll installs? Right now I'm using a modified one from Baltika's Midway Campaign. I looked around the d'loads section and drew a blank. The one I'm using works okay, just curious.

How do ya get zoomed in as tight as ravenclaw is in post# 1828? I've been messin' with the Viewlist ini and this is as close in as I can get.

Thank you, Ravenclaw-those are gonna look great on here:

Hey Spectre8750, long time, no see. Do you have Soviet listed as the first EnemyNation in the terrains' Nations list? Check out my trials and tribulations here: http://combatace.com/topic/77300-carrier-vs-carrier-not-happening/ trying to set up a WWll PTO install. In my case, if IJN was not the first in the Nations list, no Jap carriers. When I put it first, Hallelujah!, Jap carriers every time! Hope this helps you out.

Thank you sir, that is all I can ask.

Um, Ravenclaw it came to me on my commute home this afternoon (one+ hour commute, plenty of time to think) that this wouldn't call for any 3D work at all; just two skins and an opaque seeker head for the A model. The A, C, and D shared basically the same body, rocket moter, fins, warhead etc. The major differences would be in the Data inis which I would be glad to help with, if necessary. (I've got all the USAF Standard Missile Characteristics publications and other documentation for the Falcons and their prime launch platform, the F-102A Delta Dagger.) Please consider this; the Razbam F-102A with Ravenclaw Falcons would be awesome in the extreme.

Ravenclaw, I don't often ask you 3D guys for much, even ini work can be time consuming (I have 3ds Max and so far I can't make heads or tails of it, or Blender, or , so far 3D and me is not to be). I'll figure it out eventually, tho, but until then the AIM-4As and Cs are really cryin' out for a little love. Could you...maybe?

Ravenclaw, I'm glad you showed up here, the whole reason for my original post was information here: http://www.ausairpower.net/Falcon-Evolution.html#mozTocId264424 indicating that the AIM-26A and B Falcons had HOJ capability and I couldn't figure out how to add it. I saw that you are doing some awesome AIM-26s in the screenie thread so you might want to check that site out. I also saw some gorgeous AIM-54s in the same thread, are you doing any of the rest of the Falcons (specifically A thru D)? And last, don't take this as asking you to rush on your latest Weapons Pack, far from it, but I need a drool cup every time you post a new screenshot; this may be a first, in many cases the weapons are going to look better and have more detail than the planes carrying them.

Understood. Whoa, just went back and checked the RIM-66Bs' Data ini, as I said in my first post I'd just got done going thru umpteen Data inis, its Min/Max Freq range is 2-20. I think I was a little confused there. I was correct about its CCM and NR values though, I still think it's a little strange that its got no rejection capabilities at all as it is a fairly modern missile. As a further note, there are a lot of third party missiles with a zero frequency range, I assume from what you've said that this is incorrect.

Fubar, this is one of the questions I have. The stock (TW) RIM-66B for instance has HOJ checked in the Weapons Editor but the Min/Max Freqs are both zero. How does that work? It also has zeros for CCM and Noise Rejection, which seems kind of wierd. Craig, I checked in the W.E., the Phoenix has HOJ.

Thanks, EricJ I know what it does in RL; I meant how it works in-game. Now that you mention it, I think you're right about the editor, I think maybe a check box? I'm off to check. Craig, I've got no idea, hpoefully Fubar512 will check in with, as always; the definitive answers.

Can anyone tell me if this is modelled in-game? I could swear it is, and that I've seen references to it in these very pages; now however, when I want to find a reference I can't. I just spent an hour going thru weapon data inis for missiles I thought must have it; no dice. If it is modelled I would appreciate a quick run-down; what do the ini entries look like, how it works, etc. Thanks in advance.

The Phoenix is most definitely part of the Falcon family. It is a direct descendant of the AIM-47, originally developed as the GAR-9 for the Air Forces' Long Range Interceptor project, theF-108 Rapier. When the Rapier was cancelled, the AIM-47 continued development for use on the F-12A (the precursor to the SR-71), when this project was cancelled in turn the AIM-47 and its radar, the AN/ASG-18 were further developed into the AIM-54 Phoenix/AWG-9 Radar combination, first for the Navys' cancelled F-111B project, and finally for the F-14 Tomcat. As you can see, the Phoenix was well named, having survived several cancellations. Take a look at these pictures:

Wrench didn't say they don't exist; he merely said no-one uses Gun0, for some reason Ndicky did, the left and right System Files do match and all eight guns fire properly with the above entries. The last statement of my post said The loadout ini doesn't affect internal guns; phantom had posted a picture of his and I wanted to make sure he knew it didn't enter into it.

phantom, I don't see where you've changed any thing; the Gun entries should look like this: [RightGun0] SystemType=FIXED_GUN GunTypeName=303CAL_Browning GunGroup=2 InputName=FIRE_PRIMARY_GUN MuzzlePosition=2.050,0.76,-0.52 LightPosition= 2.050,0.88,-0.52 AimAngles= 0.715,0.0,0.0 MaxAmmo=350 EjectShells=TRUE EjectPosition=2.05,-0.04,-0.59 EjectVelocity=0.0,0.0,-2.0 MinExtentPosition=3.05,-0.13,-0.49 MaxExtentPosition=3.19, 0.73,-0.33 [LeftGun0] SystemType=FIXED_GUN GunTypeName=303CAL_Browning GunGroup=2 InputName=FIRE_PRIMARY_GUN MuzzlePosition=-2.050,0.76,-0.52 LightPosition= -2.05,0.88,-0.52 AimAngles= 0.715,0.0,0.0 MaxAmmo=350 EjectShells=TRUE EjectPosition=-2.05,-0.04,-0.59 EjectVelocity=0.0,0.0,-2.0 MinExtentPosition=-3.05,-0.13,-0.49 MaxExtentPosition=-3.19, 0.73,-0.33 ,etc. The Loadout ini doesn't affect internal guns. Here's screens of my Loadout page:

usafphantom2, one question: did you install the Mk1_19Sqn aircraft? The readme for the other Mk1s states that you'll be missing "important bits" if you haven't. If you have, do this: First-install Wrenchs' WW2 Guns pack, available here: http://combatace.com/files/file/13268-guns-pak-for-ww2-mods-folders/ Second-change the GunTypeName to 303CAL_Browning for all guns. Third-change FIRE_SECONDARY_GUN to read FIRE_PRIMARY_GUN for all guns. I've done this for the Mk1_19Sqn and the Mk1_54Sqn so far and they work perfectly. Remember, it's easier to change a couple of lines in a Data ini than to have multiple weapon or gun types; this way your install is standardized with everyone elses-much easier for someone else to figure out your problem if you're using the same guns, weapons, NationNames, and whatever as they are. baffmeister, the Browning in the Gun pack above has an AmmoWt entry; it seems interchangable with CartridgeWt (they both result in a Weight entry in the loadout screen) but I think your figure of 0.025400 must be closer to reality; it results in a Full Load weight of 250Lbs vs 160. Considering that the full load is 2800 rounds, even that seems light.

Boy, are they in for a rude awakening.