Piecemeal

Again, my humble thanks bud

I know I'm probably being cheeky but could you upload the afterburner emmiter INI and the Spey afterburner TGA?

Cheers bud Don't worry; I'll be sure to give them a good home

As much as I LOVE Stary's mod, it's just a little too much for my system to handle. It's just SARCASM 1.2 for the time being I think the towerview position (F11) for the stock Essex class carriers are just a tad too high, no? Down day

Johnathan - you're a f*cking GENIUS!!!! :yes: One thing though; I just checked it out and can confirm that using stock objects is OK if you're running a fully merged install.

Do you know where I can pick up those engine sound and afterburner mods, Fubar? Or is it currently WIP?

JohnathanRL and myself have been investigating that ourselves elsewhere: http://combatace.com/topic/71845-desert3-campaign-carrier-ops/

Well I think after discovering this I might just run all of my modded SF2 campaigns via SF2NA. It's something I'll have to live with for the time being (hopefully!!) but the only problem I have with doing this is the "RunCampaignBeforePlayerStart=FALSE". I've always had Operation Quick Sand's US Navy units starting seven to ten days after the campaign starts, kind of imitating a real life scenario where the US government would react to a sudden crisis by send a carrier to the area. When starting a campaign before SF2NA was installed the enemy forces would usually be in control of southern Dhimar - hence the need for a "RunCampaignBeforePlayerStart=TRUE" prompt. Again, I'm not sure if the problems we're having with this are deliberate change by TK or a rewriting error in the game engine.

It works!! It actually f*cking works!!! I copied all my SF2 mod folders to SF2NA and tried out starting a naval campaign. Worked as sweet as a nut! Proper start location and the task force escorts are all present and accounted for: Of course, as you mentioned earlier this is pretty grim news for non SF2NA users. Makes me wonder if this was a deliberate move on TK's part???

Thanks for the INIs Johnathan. Very similar results I'm afraid. The only difference this time round was that the carrier group DID show up on the map. Apart from that my First waypoint was deep in Paran near P14 airfield. HOWEVER - after reading your last post above I think it's dawned on me as to why your campaigns are working and mine aren't. You're using SF2NA and its associated engine. I'm using SF2. I'll try the campaign out tomorrow in SF2NA and let you know what happens. PS: Thanks a millions for your help so far

Fair enough point. on the terrain engine. I've assumed up to now that all terrains used the new game engine. Obviously not. Who was it that said "assumption is the mother of all f*ck ups?" What I meant to say was "the route of the carrier group" or something like that. Again; another example of me reading into the new game engine and assuming things. In the end I decided to go back to the old pre-March 2012 "Carrier station" setup; as you suggested I put back the Carrier Station location in the DESERT3_TARGETS.ini file and left the "RunCampaign,etc" prompt in the Campaign3_Data.ini as it was. Just tried out starting a carrier campaign without any problems. However the downside of that of course is having no escort vessels, but as you said Johnathan; a different terrain engine. If there is a way to include escorts this way in campaigns I'd love to know. Hi TR. Check out what I mentioned above to Johnathan. I think what the problem is is that myself and others have been reading too much into the new IcelandNA terrain and coming up with the assumption that the features in it are workable in older stock and third party terrains also. Maybe they're meant to, I dunno, and it's something somewhere in the INI setup that needed to be changed by TK. One question guys before I have to head out to the kichen to make dinner - does anyone know if there's a fix for carriers not having populated decks when flying campaigns? Cheers BTW, just in case you want have a look at exactly what changes I made to the campaign files, here they are: MY_CAMPAIGN3_updated.rar

Honey!!! I'm ho-ooooome!!

A new day - Another wave

Discovered this very interesting and highly informative website dedicated exclusively to RAF Hunter squadrons deployed in the Middle East during the sixties: http://radfanhunters.co.uk/mainframeset.htm So grab a cup of coffee (or preferrably a beer), check it out and lose yourself in another part of RAF history

THAT is the reason why I can't fly any US service squadrons. When I remove that prompt from the campaign3_data file I can fly with the USAF or USMC (land based) squadrons. If you look at the screenshot above you'll see the resulting problem I'm having AFTER removing the "NavalCampaign=TRUE" prompt. It really is a no-win situation with this updated game engine at the moment. TK doesn't really leave much scope for the campaign modder when it comes to improving stock campaigns.

Good point on the co-ordinates errors. A hangover from something I was trying out recently Forward slash symbols have just been removed from this line. I deleted the carrier stations from the desert3_data.ini as (a) The "IcelandNA_Targets" file doesn't have one (b) The objective position is already in the "campaign3_data" file (I'm assuming that this is the same thing as the old carrier station setup)

That's the weird thing Johnathan. With the "NavalMap=TRUE" prompt I can't fly any American squadrons - not even USAF! I can however fly in an RAF or Merc squadron though. But when I remove the "NavalMap=TRUE" prompt I can fly with the USAF, SUN or the USMC. Only difference is that your Navy campaign starts in the middle of the Desert. Yup. I created one myself but have since started using one from the recent WaterMap pack in the d/l section. Before March 2012 I had numerous Carrier stations in the "DESERT3_TARGETS.ini" file. But after looking through the INIs in the stock Iceland terrain I deleted them since there were none in the IcelandNA_Targets.ini file. I also added the necessary Carrier Group data to the campaign data.ini. Oh, I forgot to include these in my introductory post for this topic: MY_CAMPAIGN3.rar I deleted the "NavalaMap=TRUE" promp from them to at least get USAF squadrons flying in the campaign. If you want to check out what I've recently done to update the Desert3 terrain you can check it out here and see for yourself: http://combatace.com/files/file/12779-desert3-terrain/

It's not so much third party terrains that are my problem; but flying campaigns based from a carrier. This problem has me driven demented at this stage, as I've extensively rewritten all the stock SF2 Desert campaigns so that they could be used by "Desert3 V1.3". Strangely enough I can fly single missions from a carrier, but campaigns are a definite no-no at this time

So here's my dilemma. Some of you may remember me mentioning this on other similar topic discussions elsewhere here, so I thought I'd start a fresh topic so as not to be taking over what other people started. Anyway, I've been having HUGE problems getting my edited campaigns to work with the Desert3 terrain since installing SF2NA and the March 2012 patches. Carrier ops were added to my campaign files a long time ago which placed all USN squadrons and some USMC squadrons away from land bases. After extensive comparing with the SF2NA Northern Sabre campaign and editing of my SF2 campaign files, I was at a stage where I could only fly with either the RAF or Mercenary squadron. Basically, any US units were unflyable. When I chose one unit in the campaign start menu (regardless of the service) the game would freeze as soon as I clicked the "Accept" tab, meaning I'd have to close the game via the Task Manager. After two weeks of head scratching and screaming at the monitor I found a way where I could at least start a campaign by flying with a USAF or land based USMC squadron. In the CAMPAIGN.INI and the CAMPAIGN_DATA.ini files I deleted the "NavalCampaign=TRUE" prompts. I first tried a USAF squadron - no problem; accessed the "Operation Quick Sand" menu, chose my weapons, flew the mission, etc, etc. Then I tried starting the campaign with a USN squadron. I was able to get to the "Quick Sand" menu. The mission menu appeared and as per normal I went to check my waypoints on the map. This is the picture that greeted me: As you can see, there's no carrier group and the starting point. The carrier battle group is situated (for obvious reasons!) in the sea. Just for the heck of it I started the mission to see what would happened next. All that happened was a gigantic explosion, predictably. It's also just occured to me that I should try out the old method of re-introducing carrier stations to the DESERT3_TARGETS.ini. However that would mean having no escort ships and the like, not to mention having no seagoing-type missions such as carrier group CAPs, etc. So here's my questions. 1. Could this be a problem with the new post-March 2012 game engine? Or is there STILL something I'm missing? 2. Has anybody else experienced similar problems with bringing edited and third party campaigns up to speed with March 2012? 3. If anybody's answer to #2 is yes; what methods have they used in rectifying it? Any help and/or advice on this issue would be VERY gratefully received, as I'm literally going nuts over this.

Is this a new reality TV show - Sailing on Ice? This shot brought a specific song to mind; Gallagher & Lyle's "Breakaway" :

I know how you feel guys. My "Desert3" terrain has a problem with regard to my edited Operation Quick Sand, which uses Desert3. I can fly with the RAF or Mercs, but the game freezes in the Campaigns menu after selecting USAF, USN or USMC squadrons when I click the "Accept" tab. Tried it out as well with the stock Desert terrain - same result. This has been going on since I installed SF2NA, despite comparing and editing terrain and campaign files. Driving me f**king mad, this

I've had HUGE problems yesterday trying to reinstall my mods over the new patch. For some reason the game will not recognise the filepath I placed in the Options.INI. All my mods are on an external drive, the filepath was pointing towards it but I could only solve it by placing them back in the C: drive. Also having big problems with anti-ship and CAS missions. CAS has me flying to waypoint 5 but not a tank in sight. Anti-shipping missions consist of flying to an area over land where ships are said to be

Thanks for the feedback, guys. I've had the DLC already but I thought that the '75 model was incorrect in that sense since looking at that clip on "Sailor".

Cheers bud.