malibu43

I give up. What is it?

BEST. RESPONSE. EVER.

GO GIANTS!!!!

Seems pretty smooth to me...

It does that on my laptop, so I don't think it has anything to do with the repair. I'll see mins as low as 2 or 3 and a max as high as 50, but the avg always stays put (20-25 for me depending on the mission, settings, terrain, and weather.).

I found that mirrors cause a much higher FPS drop in SF2 than they did in WoX. I used to be able to run with mirrors on and only see about a 5 fps drop. With SF2, it's much higher. Try mirrors off.

Just a thought - What if you set up the cannon as an EO Rocket (like a Maverick) weapon station with an EO weapon that has no model, but does have a sustainer effect that looks like a burst of tracer fire? Then you could fire at anything you could target with the "E" key. Of course, the turret wouldn't actually move, and the "tracers" would want to accelerate straight out from the chopper and then turn toward the target like an A/G missile instead of head straight toward the target. Maybe that can be worked around by adjusting some of the weapon parameters, though...? *edit* - just read ALL of serverandenforcer's post and see that this piggybacks off of what he already suggested. Still, might be worth a try, though.

Hmmm... sorry. I've never had that problem before. Like Wrench mentioned, it might be an issue with the low end graphics card. If that's the case, there isn't much that can be done.

I don't see any other posts from you... What's your othe issue? Happy to help if I can.

Yes, it is a grahpics card/chipset issue. I'm guessing you're using an Intel Integrated graphics chip...? I had that issue when I updated that drivers for my Intel GMA X3100 graphics chip a few years ago. I reverted to the driver that came with my laptop (a November '07 driver) and no longer have the problem. Your options are to 1) try rolling back to older drivers, if you they exist and you can find them (or try updating the driver), or 2) turn "Cockpit Reflections" off in the graphics options menu.

Please tell us what terrain you are trying to instal exactly (link to it, if possible), what you did to install it, and what the issue is that you're having.

Is it working so far? At one point, I added Dixie Station and the associated carriers and squadrons to the campaigns in the WOV or SF2 expansion pack. I don't remember right now if they made the cut or are still there. I guess not if you're adding them again... The issue I found is that the game does not take the squadron's base location into account when assigning missions and targets. So you'll fly from Dixie station but get tasked to strike targets up at Dong Hoi and Vinh. That's a looonnngggg flight in an A-1H. It kind of defeated the point, so I abandonded the idea. Yankee station worked since it's in more of a central location, and flying missions to any of the target areas is at least believable. The only way to get it to work right would be to set up a new terrain with target areas only in the very South. I guess that would be one way to take the split terrain in the WOV/SF2V exp pack to the next level. Divide it into North Vietnam, Central Vietnam/Laos, and South Vietnam. Then have campaigns associated with reach terrain. That's a lot of work, though...

Is this the campaign update you applied? http://combatace.com/files/file/9777-korean-air-war-ground-object-and-campaign-update/ This is necessary to get the campaigns and carriers to function properly. Honestly, I would just wait for the updated version that Wrench mentioned. The old one takes a lot of work to get it working, and the quality isn't on par with what we're used to now... (no offense obviously to the creators of the first KAW mod!).

Wow. Jealous.

I believe the manual covers this.

Sorry folks. The original LAU_32A entries were correct. If you followed my earlier advice, you can either re-download the files and drop those in, or do a find change and switch things back to LAU_32A. Sorry again for the confusion.

If you can't find Track IR for within your budget, definitely look into Free-Track. $25 for a webcam, $5 in wires and LED's, and 20 minutes with a soldering iron will have you all set. I've used Free-Track for the last 3 years. It can be a little more work than Track IR to get it set up, but it works great in game!

Did you edit LineBackerII.ini or LineBackerII_data.ini? As MigBuster and I both stated earlier in the thread, you need to edit the file that ends in *_data.ini as well.

First, before we move forward, it would be helpful if we made sure you modified the right files. You should have modified LineBackerII_data.ini. Second, make sure you entered the new aircraft as the folder for the aircraft is named in the objects/aircraft folder. Third, yes, they need to go in the campaigns folder. If there are files in there already, you should back those up before overwriting.

From wikipedia: FWIW - I'm sure a functioning DIANE or A/G targeting isn't the feature that will be included with this expansion pack. But it is on the top of my list for things I'd like to see. One of the things I enjoy the most in flight sims is using guided weapons that make use of visual targeting systems (Mavericks, LGB's, etc...). Simply pressing the "E" key to accomplish it just doesn't do it for me. It "seems" (and I don't really know anything about programming) that the functionality and controls that are already in place for the A/A radar could be modified and utilized for A/G radar and simulating some sort of MFD/optical targeting... But I'm sure if was that easy TK would have done it already.

Which files did you edit exactly and can you post the changes you made?

If someone is using this, can you confirm whether or not LAU-32's are showing up on the default Attack, SEAD, and Recon loadouts? I seem to be having some issues all of a sudden...? *edit* - OK. I apparently set these loadouts up at some point using a weapon named "LAU_32A", and in NF4+ the weapon is named "LAU-32A". If you have already installed this, a quick find/replace in both the loadout.ini files should fix it. I'll update the download shortly.

Someone would have to create a "missile launch site" target area. Maybe it could just be some bunkers/silos with a few buildings arranged in some sort of layout. Probably some SAM's and AAA too. 0Those target areas would have to be placed in the targets.ini and the types added to the types.ini. I would make the "type" for the silos something that isn't used in the GermanyCE terrain, like "chemical_wep_plant" or something (I don't remember exactly what the choices are and what they're called at the moment). Then, you'd go into the campaign_data.ini file for each campaign and make whatever type you selected for the silos the primary objective for the first offensive. If all that's done correctly, the first strike missions for the blue side (once blue goes on the offensive, most SF2E campaigns start with red on the offensive) would be directed at those facilities. And, of course, all this just results in targets for strike missions. These would not be functional launch facilities.

Yes, it should work on any aircraft that could carry the regular LAU88.