Wrench

wouldn't it have been easier to zip up the data ini, and then just attach the zip file (the boards do/allow for that!)

all the SAMS seem to work ... from SA-2 throuh SA5 (I don't have the 10, 11, or 12 atm) Stingers and strela's are ok all AA guns, SPAAA (Roland, ADATS, the hummers and strykers) ok. very much narrowed it down to a ship .... I'd start looking at the MV series; the RO-ROs that we've all 'liberated' from the Falklands mods. The smallcargoships is fair -- I've updated it, as is the USNCargoShip attached are some ships that I've fixed so far... most are replacement for thos that came in some terrains; the FSS is a brand NEW vessel, that comes from the Persian Gulf terrain mod -- you all get to see it first (it's a general "Fleet Support Ship" FSS HEC (Hig Endurance Cutter, USGC, from cubaotc) Oiler OreCarrier (from CenUS) SmallCargoShip Tanker2 USNCargoShip please unzip and allow the overwrites for whatever they replace there are several other 'new' ships (ie: repaints/repurposed), but they'll have to wait edit: these arejust the ship, without the guns and stuff

As is seems that something between 30-50% of our add-on terrains have "malfunctioned" to some degree or another since the April 2012 patch; the question is as stated.

ini edit = something not right in the ships -- and of course, now that we've found an issue, I'm not going to be home for the next 72 hours ... got 3 or 4 ships updated, and with all but a few ships in the GO folder, CubaOTC, Libya and another I forget, are working again -- even with carriers. of course, KAW is a hole 'nother story ... since we're lacking straight-decked Essexes (Essesi??)

Libyans shoot SAMs at us, we gonna shoot HARMs back at them! aka "You did NOT shoot that telephone pole at ME!!!"

ok, right now I can tell you what it's NOT... a tank (including IFVs) a truck a SAM launcher a SAM radar an EWR a AAA gun, MAPADS, or AD vehicle a group of infantry (including my Zombies & Hangar Hos!) an artillery gun (incudling rocket arty) are we seeing a pattern emerging??? my USNCargoShip seems to work ok ... although I DID update it as per the stock cargoshop, with a _COL.lod unfortunately, I'm leaving in a couple of hours, won't be back till late tonight, and then gone all weekend, with no comp/net access until Sunday night. so, somebody pleaset start testing all the 'little boats'. I've got a feeling it's either one or more of the warships or the various cargo vessels; even though many are being used at terrain objects (albeit called from the GO folder) when docked in port.

dave, here: http://combatace.com/topic/71809-game-crashes-at-80-loaded-with-add-on-terrains-and-sf2na/

well, than I guess you're one of the lucky ones, eh Dave?

Yup, that most certainly works!! (just tried it) so, now begins the diagnostic ... adding back GOs until it f***s up again.... I"ll start by readdind AD units (Hawks, bofors, skysweeper, other sams and such) before starting with ships

never mind ... I just tried it, and it changed nothing on either cubaotc or libya. now, i'm running this mostly in my SF2 'all is everything mod'. I wonder if something hasn't been fully updated for SF2/E/V/I odd thing is, they all worked before the April patch.

kodiak: try renameing all the ships EXCEPT all the SF/SFNA stock one, to something like xtrawler, for example. if we remove all the add-on cargoships, trawlers, tugs, combatants...maybe it can be narrowed down to those. just an idea.

you also have to tell it how LARGE a parking span is used, as per the stock Cruds.... MinBaseSize=SMALL CarrierBased=TRUE CarrierParkSpan=7.20 CarrierParkAnimationID=6 (btw, the above IS for the F-8A mod)

no, pulling it sort of creates a 'copy' in the extract to ... folders. adding a hangar (or loading) screen is a simple matter editing the relevant line inthe main ini, and placing the new screen directly into the aircraft's folder (example, would be my F-16A pak, made from TK's F-16A Netz, it has both new hangar and loading screens) [AircraftData] AircraftFullName=F-16A Blk 10 Falcon (3W) AircraftShortName=F-16A AircraftDataFile=F-16A_data.ini LoadoutFile=F-16A_loadout.ini UserList=F-16A_UserList.ini CockpitDataFile=F-16A_Netz_cockpit.ini LoadoutImage=F-16A_Netz_loadout.TGA HangarScreen=F-16A_Hangar.jpg <---- LoadingScreen=Falcon_Loading.jpg <---- AvionicsDLL=Avionics70.dll AvionicsDataFilename=F-16A_Netz_avionics.ini

Yah, nothing has jumped out at me either. I've compared all the 4 stock terrain data inis, freshly pulled, with ALL the terrains, and they're exactly the same. well, there's only one way to test that....remove the docked warships by renaming their callouts in the targets inis, like so: Target[063].Type=xHMASAustralia Target[063].Offset=-1385,233 Target[063].Heading=90 Target[064].Type=xHMASMelborne Target[064].Offset=-1370,88 Target[064].Heading=90 Target[065].Type=xSUMNERFRAM2 Target[065].Offset=-1300,335 Target[065].Heading=90 (note the "X" on the Type= line Here's a partial list of terrains in my 'all is everything SF2 install', full updated and Full-5 merged, of terrains taht lock at 80% (mind you, 2 listed are NOT yet available) ASW Anatolia (V2) Libya CubaOTC -which WAS working before the April patch, btw! (as was seemingly most things) Darwin (modern) Korea (KAW mod) these terrains seem to 'hang' at 80 for 30 sec-1 minute (or more), but eventually start Iran/Iraq IR 2003 SoCal Persian Gulf Sweden of the 'naval maps', DBS Panama seem ok. Panama has a wealth of docked ships, but not too many combatants. PG has several docked warships, and a working 'carrier zone', and althoug loading slow -also a consequence of my heavy hand in populating maps- seems relatively ok. Those that DON'T have oceans, Himalaya Afghanistan Eritrea/Ethopia (ok, a small ocean, but NO carrier zones) have no issues (obviously!) So, I don't have a frakking clue as to what causing it; other than something introduced with the 4/12 patch. Stary: yes you did. I was just in Egypt about the whole thing (ie: in DeNile )

actualy, Alt/D

it ain't going nowhere!

I didn't want to say this on an open fourm, but... I fear the days of modding might be nearing their end. and I have 4 or 5 terrains still in the works...

how true allen!! That one's based off the stock A-7D_78. of course, dumba$$ me totally forgot there's 2 by TMF! A-7E(H), and A-7H (H seen below). Pretty easy to upgrade the avionices to SF2; FM will no doubt need some tweeking. prolly be MUCH quicker and easier to fiddle the TMF versions! (harder then hell to try to find a now-working terrain to take a screenie one ... the April patch really f***ed things up! Half my terrains -including MANY of my own, have just stopped working -locks/freezes at 80%. oh man...this is so frakking tiresome....)

a quick redecaling (ie: rerused off the TMF version) of a stock Corsair ... any interest??

depends on WHAT year your flying ... the question has been asked and answered over at the 3rdWire forums. Also depends on the terrain ... very few have been upgraded for the new 'naval zones' (and those that are, are a bit wonky) meaning: NONE of the stock carriers exist before 1956. also, have you added the new, correct statements in the F-8A's data ini, for carrier ops?

does the cockpit in have the necessary shader and effects statements for HUDs???? pull the F-15A or the F-16A Netz, and LOOK at the HUD statements ... I"ll bet money those statements are missing

gettung the same issues with Anatolia and a couple others (have to recheck) I don't understand WHY it's breaking non-naval maps....

yup, the LODs are locked away, but all the inis/skins/decals are still available. You just have to browse (ie: open with the 3W extractor) each cat and see what's where -- and things sometimes are pretty scattered

and DO NOT TOUCH THE ALPHA LAYER in ANY TGA!!! to change the color, you're going to paint below that alpha, directly onto the RGB layers. It's pretty easy; I've done it lots of times