SF2 Series Range

[+JSF_Aggie]

View File

SF2 Series Range

---

*******************************************************************************

********* Bombing Range For SF2 ********

*******************************************************************************

 

This is an update to the original bombing range to make it compatible with the

SF2 series, and take advantage of some of the new features now available. It

also has terrain tiles redrawn at 1024x1024.

 

A QF-100D drone is included in this download. You'll see these flying around

the range, and parked at the simulated airfield. All weapons have been

removed, so they won't shoot at you.

 

Only hostile aircraft with a "NationName=RANGE" will show up on this terrain.

 

A modified version of the NATIONS.INI file has been included. It is the stock

file with the "RANGE" nation added. You need the "RANGE" nation defined if you

want the QF-100D's showing up.

 

Provided your other terrains have their "LimitedNations" setup, you won't see

the QF-100's anywhere except the Range.

 

A quick note, for the most part, this is still the original target layout.

Wrench and others have created target laydowns with a much wider array of

targets. These changes can be easily merged with this update.

 

Feel free to further modify this, but don't sell it, and please include the

credit list below.

 

*******************************************************************************

********* Installation ********

*******************************************************************************

 

Copy the contents SF2_Range.rar into your SF2 mods folder.

 

Edit the line below in RANGE.INI to point to a .cat file that you own:

 

CatFile=Desert.cat

 

SF2: Desert.cat

SF2V: VietnamSEA.cat

SF2E: GermanCE.cat

SF2I: IsraelME.cat

 

*******************************************************************************

********* Credits ********

*******************************************************************************

 

Original Bombing Range:

- Deuces

- Bunyap

- Wrench

 

Objects & Mods used for the SF2 Update:

 

- AirbasesWithSomeSpice: pureblue

Amokfloo: ControlTower, ForkLift, FireExtinguisher, ShelterZu

Ravenclaw: Fire Trucks

Rureblue: FloodLight, SmallGenerator, ConcreteBlock, SunShelter

Comrpnt: QRA and Lights

Gepard: Ahlhorn Airfield with modified Parked Aircraft, QRA

Polak: tools

 

- CH-47: BANIDOS TEAM

 

- Factory Models: Wingwiner

 

- Generic Hangars: CA_Stary

 

- New terrain tiles: JSF_Aggie, based off of original Deuces tiles

 

- QF-100D: JSF_Aggie, with help from Sundowner's template

---

• Submitter
  JSF_Aggie
• Submitted
  06/22/2010
• Category
  Full Terrains

 

[+Wrench]

the drones work great, but I'm getting "live" SAMs showing up and shooting at me!!

 

I have a dummy launcher I'll get set up for upload, probably tommorrow

 

EDIT: since there's no other enemy nations, the Friendly mission statements should look like this:

 

[AllowedMissionTypes]

FriendlyMissionTypes=SWEEP,CAP,ESCORT,STRIKE,SEAD,RECON

EnemyMissionTypes=RECON

 

with the removal of CAS and ARMED_RECON, as there's no routes for them, and no vehicles to run them. Of course, adding the RANGE nation to the Zil Truck and maybe a T-55's UserList would be easy enough to 'reinatalize' those statements (I've got routes alreay plotted) If you try a CAS or AR, the game will freeze.

 

Also, I'd reccomend NOT merging my Range Update targets, as it was predicated on the 'flat' areas around the central bombing range. The Height Field here has been tweeked to a be very rough, with canyons and mountains that would make adding them impossible without re-flattening those target zones.

 

wrench

kevin stein

Edited June 22, 2010 by Wrench

[+Spectre_USA]

Well, I blew it.

 

Merged my carefully tweaked range with this one, and get app hangs on the aforementioned items, along with strike and SEAD.

 

Renamed my "old" folder Bad-Mix_Range and ran with just this one.

 

No joy...

 

[+JSF_Aggie]

the drones work great, but I'm getting "live" SAMs showing up and shooting at me!!

 

I have a dummy launcher I'll get set up for upload, probably tommorrow

 

EDIT: since there's no other enemy nations, the Friendly mission statements should look like this:

 

[AllowedMissionTypes]

FriendlyMissionTypes=SWEEP,CAP,ESCORT,STRIKE,SEAD,RECON

EnemyMissionTypes=RECON

 

with the removal of CAS and ARMED_RECON, as there's no routes for them, and no vehicles to run them. Of course, adding the RANGE nation to the Zil Truck and maybe a T-55's UserList would be easy enough to 'reinatalize' those statements (I've got routes alreay plotted) If you try a CAS or AR, the game will freeze.

 

Also, I'd reccomend NOT merging my Range Update targets, as it was predicated on the 'flat' areas around the central bombing range. The Height Field here has been tweeked to a be very rough, with canyons and mountains that would make adding them impossible without re-flattening those target zones.

 

wrench

kevin stein

 

 

Kev,

 

I added 3 SAMRadar's to parts of the range, but they never showed up for me. The hope was just to get a few more spikes on the RWR. I didn't add any SAMLauncher's, but I also didn't look to see if they were some already existing. I don't have any 3rd party SAMs in my install. Maybe some of the mobile guys are "SAMRadar's" with missiles?

 

If anyone else is seeing this, they can open up the range_targets.ini and change all the SAMLauncher's and/or SAMRadar's to another type.

 

The desert, mountain, and farm tiles have _hm.bmp's now. All of the range specific tiles are still flat, so there should still be pleanty of flat ground to add your additional targets, we just may have to move their locations (or get rid of the _hm.bmp's in range_data.ini)

[+Wrench]

I wouldn't get rid of them ... it's looks MUCH nicer with the rough terrain.

Let me browse the Range region, and see what I can fit in there (btw, the ship adds with no problem in it's 'original' location)

 

Yes, the BombingRAnge target area had "SAMLauncher" still called out; the radars show with no issues (since I have them all installed). Standard fixed at the 'star' location. Scared the daylights outta me with 9 trails coming up after me!!!

 

my 'dummy' missile-less launchers are based off the stock SA2, but I think I'll recreate them with the SA-3 dual, as to not cause issue with uploading 3W items, even editited. Since they're terrain objects, they go right into the terrain folder.

 

wrench

kevin stein

[+EricJ]

So in other words... this one has issues? I might as well stick with what I've done myself then...

[+JSF_Aggie]

I've updated the download to remove the SAMRadars, or you can just grab the Range_targets.ini from this post, and place it in your /Terrains/Range folder.

 

EricJ, I'm not forcing this on you or anyone.

Range_targets.rar

[Russky]

I can't use the Range on the dates prior to 1970. I have SF2 Vietnam standalone and every time I try to create a mission dated in 60's the game freezes even before getting to the hangar screen. Needless to say I can't use about a half of the aircarft with the Range without fiddling with the ini files. What may be the cause of this?

[+JSF_Aggie]

In Range.INI, there is the following:

 

[AllowedDates]

StartDate=1/1/1950

EndDate=1/1/2010

 

I just flew six missions with F-100's, A-4's, and F-8's, all in the '50's, with no problems. However, I have it in a merged install will all titles.

[+Wrench]

To be able to use ANYTHING, ANYWHERE, at ANY TIME, one must have a full-4 merged install.

 

Otherwise, you're trapped with the StartService/EndService dates of the Vietnam War. Not a good idea to go messing around with those in the various aircrft's data inis.

 

like JSF said, I've been flying it as far back as 1950 with Mustangs, etc, with no problems.

 

wrench

kevin stein

[Russky]

Sorry, my bad. It was SF2V Air & Ground War Expansion Pack v2.0 that caused some incompatibility. Deleted the mods folder and the Range worked fine on any date back to 1956 with the clean game, although some objects like hangars and ammo bunkers did not show at the range airfield.

[xclusiv8]

I have installed SF2 Series Range, in my merged SF2+SF2V+SF2E+SF2I+SF2Exp1+SF2_Exp1_update_Jun2010, and I see this:

 

 

 

 

It would seem a river, but in reality it is not!!!!

 

 

 

This is normal, or you can fix it??

+1 i noticed the same thing.

[+EricJ]

It's more of a game issue rather than map related. I get the same thing on the Afghanistan map too.

[+Julhelm]

Is there any reason why a specific aircraft (USN in this case) would cause the game to lock up when selecting this terrain? If I try to create any mission using my AFX the game locks up before loading the hangar screen. However, if I select, say, an A-4 I can then change to the correct plane in the hangar screen. What gives?

[+JSF_Aggie]

Is there any reason why a specific aircraft (USN in this case) would cause the game to lock up when selecting this terrain? If I try to create any mission using my AFX the game locks up before loading the hangar screen. However, if I select, say, an A-4 I can then change to the correct plane in the hangar screen. What gives?

 

Two guesses...

 

Does the AFX's _data.ini have "MinBaseSize=LARGE"? If so, change it to MEDIUM. The only runway is Runway6, of TargetType=MEDIUM_RUNWAY.

 

Are you trying to fly later than 2010? Range.INI has an EndDate of 1/1/2010.

 

If neither of those fix it, I'll install it and see if I can find the problem.

[+Julhelm]

It's definitely something else. If you clean out your inbox I'll pass you the link to the current beta version.

[+JSF_Aggie]

It's definitely something else. If you clean out your inbox I'll pass you the link to the current beta version.

 

Done. I can look at it late tonight.

[+ChampionsVA56]

Can you tell me which variable and where it is located so I can ALWAYS have the QF-100's up during a mission? Right now I only see them periodically.....thanks!

[+JSF_Aggie]

Can you tell me which variable and where it is located so I can ALWAYS have the QF-100's up during a mission? Right now I only see them periodically.....thanks!

 

Unless you edit QF-100D_DATA.INI, it's only available between 1970-1990.

 

For parked aircraft, increase OPTIONS->GRAPHICS->GROUND OBJECTS

 

For airborn aircaft, increase SINGLE MISSION->CREATE MISSION->ENEMY AIR ACTIVITY

[Canadair]

as for the AFX lock and CTD before hangar screen. I had this similar problem in a big isntall I had in series one. . It used to happen within a given range of dates. after NO feedback after the question on any forum I took the plunge and tried each of the planes, in block of tens (I had about 400 in that install) in order to narrow the problem. I succeded in fixing and it appeared that I had static aircraft, that when picked with some combiantion of date and mission types would cause CTD. In this case I have the feeling that the proble should be researched in date availability and data type of the QF-100D, maybe considering also the static version , if any, and the mission types.