JSF_Aggie

File: F-15 C and D Release.7z The README has a date of 21 Sep 09: [CockpitSeat001] ModelName=F-15CPit Offset=0.0,0.0,0.040 Position=0.0,4.35,1.55 ViewAngles=0.0,0.0,0.0 MaxYaw=160 MinYaw=-160 MaxPitch=90 Is that what you're looking for?

Also, in each aircraft's _data.ini, there's a variable: MinBaseSize=. Only aircraft with MinBaseSize=SMALL should ever be put on a highway airfield, unless that stoped working just recently. But again, make sure you're using the files in the link above. It just contains the objects, an airbase.ini, and a modified GermanyCE_targets.ini and GermanyCE_types.ini

I think the very first one I did for WOE had some trees. I think just a new .tga only. Go with this one, for WOE2, no trees or terrain _data.ini in here: http://combatace.com/files/file/10311-highway-airfield-mod-for-sf2-europe/

Going to try and get this posted tomorrow. Short runway for STOVL practice....

Happy Birthday

Logitech released software & firmware updates on 05-18, to among other things, fix the sloppiness. Personally, I don't like the changes in the force curves when playing StrikeFighters. Once you update the firmware, there's not going back to the previous firmware and software. Others, playing other sims, have been happy with the changes. http://forums.logitech.com/t5/PC-Gaming/Logitech-G940-Software-Update-Official-notice/td-p/447921

Humbley request more cockpit shots.

Logitech put out a software and firmware update earlier this week. Since applying both, the stick's force vs. deflection curve isn't set by SF2 anymore. It keeps the default force vs. deflection curve instead, which feels like crap compared to what I had before. The old software won't recognize the G940 with the new firmware, and they have no way to go back to the previous firmware version. Others have posted similar complaints on Logitech's forums, for other games. You may want to hold off on updating if you have a G940.

I got it working. If I define a new "RANGE" nation in the terrain's _nations.ini, like Dhimar and Paran are defined in the stock desert terrain, it doesn't seem to work for limiting only the "RANGE" nation to the bombing range terrain. I had to define it in the global NATIONS.INI file to get it to work. I would have perfered not to have to touch this file, but at least we get parked aircraft, and only un-armed "drones" will show up flying around the range. I plan to include three drones in the update, QF-100, QF-106, QF-4. I have to finish the skin of course....

I have one I can send you this weekend. Send me a PM if I forget.

That was going to be the last thing I try. I was going to make them a seperate aircraft, with no weapons, and RECON as their only role. This will get them parked on the airfield. They'll also be a few flying around, but I don't think it's a bad thing. There shouldn't me more than one flight of two, and they won't be shooting at anyone. This way we'll have a believeable target flying around if we want to do some A2A. I can make a new "nation" for the range and that will keep them from showing up on other terrains, at least those that are limited to specfic nations. I'll make their availability "RARE", which will also help. I'll try it tonight.

I'm making a small dirt runway for the for STOVL aircraft that I'm going to place next to the main runway. I'll see if I can get this to fit with the larger runway4. No luck with the sim's static aircraft. If I do enough to get them to appear on the range's runway, you end up with MiG's spawning in the air, even if the airfield's data.ini doesn't have takeoff or touchdown points. I think I'm going to have to keep the old aircraft targets since there's not a static RED aircraft model we can use for a parked aircraft. Here's some updated shots....

Jedi, It's both. On the Logitech site you'll just see a download link for the software. Once you install the software, it'll put an .exe in your program folders that you can run to update the firmware. Some of the new features are not available in the software until the firmware is updated. Once you update the firmware, there's no way to go back, at least not yet. I don't know if it is the firmware or the software driver that changes the stick forces. I didn't try the stick until I updated both. Once you update the firmware, the old software won't recognize the HOTAS. People keep asking on the Logitech forms if they will provide a way to roll-back the firmware, but they have not answered.

Was deffinately going to do that for the BLUE airfield. I was also going to see what happens if I give the runway way at the range an airfield_data.ini with parking spots, but no takeoff and landing points. I'm hoping it will give us RED parked aircraft, without any CTD's or MiG's chasing us around the range. Julhelm, thanks for the offer.

Before the firmware update, the force curve was very smooth and ramped up as your defection increased. Also, the stick stiffened up as you approached mach 1.0 Now, the feel is very mechanical, and the force is linear across the curve. Now, one axis effects the other, and it did not before. For example, if you were in the top left corner, and went directly to bottom left corner, you feel a detent as you pass through zero pitch. Before the update, you would not feel it. Now, there is a slight effect based on airspeed, but is very little, even if you compare zero airspeed on the runway, vs. mach 1+. I wouldn't count out this HOTAS. I really liked it before the firmware update. I would think Logitech will give us a fix or a way to go back, however many are asking how to go back to the previous firmware version, and they have not yet answered.

Damn daughter's dance recital.....

Thanks, this is great.

The SF2 series are set up to do a "merged install" automatically, unless you intentionally install them into seperate directories. Install them in order released: SF2, SF2V, SF2E, SF2I. They've also added a few hooks to allow the merged titles to play nice with eachother, such as limiting Vietnamese aircraft from showing up over Europe, for example.

I believe mytai did this on purpose. He has decals that are set to level=2 for each AC num, that cover the nose cones.

Happy Birthday!

I don't have a complete set of templates, but I have what I used to make the skins below. It has panel line & weathering layers for the tail, and layers for the different nose cone colors. The nose cone and several other details have been redrawn at 1024x1024. This was for WOV, and I don't know if anything on the A-6 was re-mapped for SF2:WOV. If you want them, I can dig them out tomorrow night. http://forum.combatace.com/index.php?app=downloads&showfile=3826 http://forum.combatace.com/index.php?app=downloads&showfile=2568 http://forum.combatace.com/index.php?app=downloads&showfile=2482

File Name: Operation Desert Storm, Part 3 of 3 File Submitter: JSF_Aggie File Submitted: 31 Jan 2009 File Category: User Made Campaigns Operation Desert Storm for Wings Over Europe This is a complete addon for WOE, containing a Desert Storm dynamic campaign, as well as scripted single missions. This installer is 3 of 3. Click here to download this file

File Name: Highway Airfield Mod For SF2 Europe File Submitter: JSF_Aggie File Submitted: 02 Dec 2009 File Category: SF2 Series Add On Terrains This is a mod to SF2 Europe's GermanyCE Terrain, that modifies 13 sections of highway into airstrips that are usable in single missions, any mission editor, and campaigns. Click here to download this file

Happy Birthday Otto!

In addition to the Ground Objects setting, there is a %chance a spot will be filled that is defined in each airfield's _data.ini. These files live in the terrain's .cat. You can extract these files and up the number, but the Ground Object setting route is probably good enough. I see them much less in campaigns than single missions. I assume this has to do with campaigns having a finite number of aircraft stationed at each base.