malibu43

There's a similar command that is "target closest to center of view" or something like that. I've used it for a while (I think I assigned it to U). It helps eliminate the mindless cycling of the E and T keys.

This part was easy enough. Entering all the node entries and ground units for a campaign takes a while though... And then of course we'll have to see if it actually works.

Good idea. I'll try that.

Okie dokie. Wrench, can you point me to a map of Korea that uses city/location names that match what you used in the targets.ini file? I'm going to try to create a campaign with a ground war (probably using this as a starting point http://combatace.com/topic/76391-campaign-for-kaw/). I found some maps online and started mapping out nodes but I found that a lot of the city names were not in targets.ini. I'm guessing names have changed over time, and I want to make sure I'm starting on the same page as your targets.ini file.

For whatever reason (whether you did it or the game did it automatically), the action that is the 'E' key by default is assigned to your Joystick Button 2. So that button should cycle through your ground targets. All the other 'E' related key combinations are just different ways of cycling through the same targets (previous target, closest target). You can use any one of those to lock up a ground target. The little red box on your screen will show you which ground target you actually have locked up. As far as actually hitting targets with LGB's, it's tricky in this game since the game lacks some of the other avionics/indicators that help real life pilots drop within the correct parameters. The F-16 in real life would have additional symbology on the HUD that would tell you where to steer and when to release to get the highest chance of a hit. Since we don't have that, you'll just have to practice. I would suggest starting pretty high up (8K-10K feet...?) and about 10+ miles out from the target*. Fly a nice steady approach and pickle off the bomb when you think you're about where a regular dumb bomb would score a hit. Take note of whether the bomb falls short or long, and then go back and try it again, adjusting the distance from the target you pickle based on whether the previous bomb was long or short. *If Erik's pdfs or someone with more recent experience suggests a different altitude and distance from target to pickle the bombs, start with those numbers. I'm just making mine up as I type.

Hey guys. I just downloaded everything linked in this thread to build a KAW install. Is there anything that's been released since that I might be missing? Also, any good suggestions for how to make my install KAW only? Can I delete unwanted aircraft and ground objects after I run the .exe and then drop in all the KAW files?

Can you drop laser guided bombs are tanks in a CAS mission? If you can, the designator is working and it's just getting the image to show on the display. Compare the avionics.ini files for both F-16s and look for something regarding "TV" or "EO Display" listed under Radar Modes that might be missing from your Blk40.

As Fast Cargo said, stop spamming multiple threads. Especially when they're threads that haven't been active in 6 years. It makes it hard for people who are actually trying to help you follow your progress. 1. Where exactly did you post "SystemName[xxx]=LaserDesignator" and what numbers did you use for "XXX"? 2. Regarding your question of where to post the rest, I believe it can be posted anywhere. Just add it to the very bottom.

Maybe I misunderstood you here, but by "get your hands dirty" we didn't mean keep posting in multiple threads until someone does the work for you. What we meant was dig into some .ini files to try to figure it out for yourself. When you run into issues, people will be more than happy to help you if you post exactly what you're trying to do, what changes you made (actually post the modified lines in the post using quote tags so we can see), and what result you got. Folks will be more than happy to help you find the other changes/corrections that need to be made. Also, just so you understand, there is no secret "link that explains how to do it" that we are hiding from you. There is no link that specifically tells you how to add a laser pod from whatever weapons pack you have to whatever F-16 you've downloaded. For me to give you step by step instructions, I'd have to download all the pieces, experiment and try it myself, and then write step by step instructions for what I did. I don't really have time to do that right now, and even if I did I don't have the gen1 games installed anymore, so I couldn't. When people tell you the information you're looking for is out there, they mean it's burried in bits and pieces in the knowledge base and posts throughout the forums. So, along the lines of my previous post. Why don't you tell us specifically what you tried and what the result was. Then maybe we can help you.

I just did a quick look through the D/L section and couldn't find the GAU8 Avenger sound files I've downloaded before. I have the Avenger sound .zip saved on a external drive at home. I will try to get it to you later if I remember.

First of all, it may feel overwhelming, but don't be discouraged. Everyone started with questions like yours at some point. My first questions regarding WoE back in 2007 were... wait for it... how to drop LGBs against tanks from an A-10 and then how to add a laser designator to the A-10 when I was told that's why they wouldn't drop. One thing you have working against you is that you're using WoE (gen 1) when pretty much everyone else is using SF2E (gen 2). That means that most of the people that would be able to solve your issue are limited in how much they can help since they don't have the gen 1 games and mods to play around with. If you can get SF2E, you'll be in a much better position to ask for help and also learn at the same time. In fact, there are already F-16C's with LGB/laser pod capability in the downloads section for the gen 2 games. It would be a simple download and drag-n-drop. If you can't get SF2E, you're either going to be limited to what's already available or you're going to have to roll up your sleeves and start "learn by doing". I can point you to this download that includes an F-16C with LGB/laser pod capability. http://combatace.com/files/file/6970-linebacker-iii-beta/ I would create a separate "test" install of WoE to add this to. Make sure to follow the instructions carefully and install all the required files. Once you do, see if that F-16C suits your needs. You could probably just stop there if you wanted and use that install if it works OK for you (there may be some issues since you don't have the Vietnam terrain). However, I recommend that you then start reading through each of the .ini files associated with the F-16C to see how that laser pod has been added and works. You know the old saying - "give a man fish, feed him for a day. teach him to fish, feed him for life..." I have learned so much about military aviation from the 60's onward by digging under the hood with this game and trying to do things. It's almost more fun than actually playing the game.

And some fun in the AV-8A:

The question in this thread isn't about whether or not clouds are locked. It is why do they show up at different heights in different terrains?

I think this is the one I have installed: http://combatace.com/files/file/11067-sf2-series-range/ I would LOVE to get the clouds in my other terrains down as low as the clouds on this terrain...

Do you have any WIP files you can share?

It's not that each terrain has it's own environment.ini file - unfortunately it's not that simple. It's something secret that's hard coded somewhere, but I haven't been able to figure out what it is. You'll notice that the Range 2 terrain has clouds that start at around 6K!!! It looks so much nicer than in the other terrains. My guess is that it's hard coded somewhere to start X thousands of feet above the highest point on the terrain (does India include the Himalayas?). The Range 2 is a very flat terrain.

Cool! Looks like you are already on it! No need to double effort, then. If you want any help or would like me to test, let me know.

Folks, I recently downloaded and installed the F/A-18A from the latest package listed at CA. After playing with it for a while and tweaking some things, I have a couple of questions. I'm hoping someone with SF2 Avionics/HUD expertise can help me out. 1. Bank Angle Indicator - The little "carat" or triangle pointer part of the gage is very far off to the left so that it's actually off of the HUD. You can only see it slip onto the HUD briefly when you bank to the right, or if you zoom way in on the HUD and pan slightly to the right. Here, is the entry from the avionics.ini file: [HUD_BankIndicator] SymbolType=ROLL_INDICATOR ImageFilename=cockpit\hud\HUD_BKI.tga ImagePosition=0.0,0.030 ImageSize=0.35 ScaleImageFilename=cockpit\hud\HUD_bankindic.tga ScaleImageSize=0.133 ScaleImagePosition=0.0,0.030 Scale=1.0 MaxValue=31 MinValue=-31 HorizontalAlignment=CENTER VerticalAlignment=CENTER I tired adjusting the ScaleImagePosition= to all sorts of different values to move it onto the HUD, but it seemed to have no effect. Does anyone know why it behaves the way it does and what needs to be changed to get it to work? 2. Adding a waypoint marker under the heading scale - The HUD landing mode currently has an instrument called HUD_Steerline. [HUD_SteerLine] SymbolType=STEERING_CUE ImageFilename=cockpit\hud\F-18_steering.tga ImageSize=0.100 Scale=0.50 I added the instrument to NAV mode as well, but it utilizes the large, vertical steering line that you would expect to see in ILS/landing mode. I wanted to change it to a smaller tick mark that would sit near the heading scale. I made modifications to F-18_steering.tga using gimp, but was not able to get my new tga to show up. Is there anything special I need to know about format, alpha layers, etc... to ensure my new HUD symbols display properly? Also, can I use the MinValue= and MaxValue= entries so that the tick mark rests at either edge of the heading scale instead of disappearing when the waypoint is off to one side or behind the aircraft? Thanks! PS - While I was in there, I created a new gage called HUD_Courseline that is identical to HUD_Steerline only the symbol type is COURSE_DEVIATION, and added this gage to landing mode in place of HUD_Steerline. Now the ILS properly guides me to the course line of the carrier instead of straight to the carrier from wherever I'm at.

Piecemeal, I'm really enjoying this terrain. I was just trying out some soviet weapons and was assigned to strike an offshore oil rig. When I got there, there was nothing there. It looks like the desert4_types.ini is calling for a ground object called "oilrig", but it's not included with the mod. Did I miss something?

Thanks, Blaze95. I missed that. I'll add it in an update.

I stand corrected, then. It's been a while since I looked at the SF2E campaigns...

Where is that ground noise map from? I really like it. Required screen:

Just throwing my 2 cents in here, full of generalizations and lacking any actual data... The F-35 might not be cost-effective and could be "overkill" for the job we're expecting it's potential customers to need it to perform 98% of the time (air policing, current conflicts in the Middle East and Asia, etc...). But if/when "WWIII" breaks out, all those potential customers no longer need to worry about just intercepting hijacked airliners or dropping bombs on 4 guys behind a rock. The other 2% of the time has now arrived, and the concern is now taking on other Gen 4+/5 fighters and penetrating advanced SAM/air defense networks and the F-35 is looking a lot better compared to an F/A-18E. Let's not be too short sighted... ...and, at the very least, it is a deterrent.

What you are seeing is directly copied over from the stock campaigns. All I did was change airfield names to match Desert4 and move USN and USMC units to carriers. I can also say, though, that it is that way intentionally and for a good reason. It allows you to have, in this example, only one USAF F-100D unit in the campaign (as defined in the campaignx_data.ini), but give the player the option of choosing which unit/squadron it will be (as defined in campaignx.ini). If you scroll down you'll see that other unitID's are eventually called out as well. I believe the SF2E campaigns are done this way as well. I also think that the SF1 and WoE campaigns were like this, but I can't remember off the top of my head. As eburger68 pointed out, this was not correct.