ndicki

Ok, so I'm being too clever... Thanks, pcpilot, off to see!

Anybody tried? I attempted to add the New Guinea terrain, all duly cat filed using the new utility, but I got two "Desert"s in the menu, and both were the desert. No New Guinea. The inis all seemed the same, but I couldn't find the trick. Has anybody else had a go?

Thanks, Crab - my own conclusion, too. There must be the sort of incompatibility between them that we had with CFS1 and 2. You could get CFS1 models to work well in CFS2, but the inverse wasn't true. It does work with the original WOX LODs, so at least we have it running, even if it isn't quite as good as the new one. If you use the LOD 100 model at all distances, it'll do nasty things to your FPS, though - that's a cleaner version of the one I tried. My computer's not that fast any more...

OK, success. If you copy ALL the new SF2 cockpit files into the cockpit folder, and the LODs from the old WOX/SFG/SFP1 F-4E into the folder too, it'll work. So basically although cockpits from SF2 seem to fit models from SF2, there are some incompatibilities when it comes to mixing model types. Bloody hell, though, life can be complicated.

OK, so the SF2 F-4E uses LODS with a different name - F-4E_LOD2.LOD in place of the SFG F-4E_LOD002.LOD etc. BUT if you modify the entries in the ini file to reflect that, you get a shock - in cockpit view you're looking out over your left shoulder (with the gunsight), and from outside, your aircraft is invisible... I'm going to try the original SFG LODs. Maybe...

Just for info, the decals need to be dumped into a central "decals" folder in your objects folder. Then you need to go into decals.ini and remove the path leading to the "D" subfolder in the skin folder. Like this: [Decal001] MeshName=vertical_stabilizer DecalLevel=2 DecalFacing=RIGHT FilenameFormat=F-4E_IDF/1/d/f42kn Position=-3.90,1.30 Rotation=0.0 Scale=0.85 DecalMaxLOD=3 becomes [Decal001] MeshName=vertical_stabilizer DecalLevel=2 DecalFacing=RIGHT FilenameFormat=f42kn Position=-3.90,1.30 Rotation=0.0 Scale=0.85 DecalMaxLOD=3 The trouble is that some of the more obvious decal names have already been used, so you'll need to change them.

So far, I've added a number of WOX/SFP1 aircraft to SF2 without any great trouble. But the TMF Kurnass is a problem I can't work out. It shows in the menu, etc, etc, and you get into the sim to find you don't have a cockpit. Known problem. Then you go to outside view and you find your ordnance is flying along by itself - with no aircraft. So... Back into F-4E_IDF.ini to look for the trouble. It's the LODs. This is whay you get: [LOD001] Filename=Kurnass.lod Distance=200 [LOD002] Filename=F-4E_lod002.lod Distance=350 [LOD003] Filename=F-4E_lod003.lod Distance=500 [LOD004] Filename=F-4E_lod004.lod Distance=1000 [LOD005] Filename=F-4E_lod005.lod Distance=8000 I have loaded the F-4E LODs into the same folder, so they should show. They don't. Nor does kurnass.lod. When you change all the LODs for the 100% Kurnass one, it works, even if I still have a problem with the now-visible-too cockpit textures. So if you have this: [LOD001] Filename=Kurnass.lod Distance=200 [LOD002] Filename=Kurnass.lod Distance=350 [LOD003] Filename=Kurnass.lod Distance=500 [LOD004] Filename=Kurnass.lod Distance=1000 [LOD005] Filename=Kurnass.lod Distance=8000 It works perfectly well, but it'll kill your FPS. Weird. This aircraft runs perfectly in SFG... So why won't it here?

That Hunter is fabulous! Well done! Now all I need is to do a No1 Sqn Rhodesian Air Force skin, and I'm off chasing that Jungle Dustbin...

Desktop???? Perplexed. Confused. Etc... OK, I've got there. I didn't see the second set of folders. Don't laugh, I only got it this afternoon!

Next problem is that in my objects folder, I don't have the usual WOX style subfolders - you know, aircraft, ground objects, objects, weapons, etc - but four cat files - ObjectData001.cat to ObjectData004.cat. I've got the tool, opened them up and had a poke around, but they won't run unless they are recompiled. Pain. But I've seen screenies of people's installs with the classic subfolders. How is this? I'm running the downloaded version, if that makes any difference, on WXP SP3 Home.

Cheers, mate! And with any luck, while I'm installing it, I'll find out where the problem was...

I'm trying to make the SF2 Hunter Mk6 player-flyable... I've extracted all the Hunter 6 parts (ini, data, loadout, LODs) to another file, renamed them to HUNTERF6 and aliased the cockpit etc to the stock A-4F by pasting the following: CockpitDataFile=A-4F_cockpit.ini LoadoutImage=A-4F_loadout.tga UserList=A-4F_UserList.ini HangarScreen=A-4F_hangar.bmp LoadingScreen=A-4F_Loading.bmp AvionicsDLL=Avionics60.dll AvionicsDataFilename=A-4F_avionics.ini straight into the ini file. I've transferred the two textures folders as well, and dumped the lot into ObjectData003.cat with the other flyable aircraft. I don't know if it matters which file they are in, but I've discovered they have to be in a cat file, in any case. And although I can't see what I'm doing wrong - and I reassigned it to USN, just to play safe! - it won't show in the single mission select aircraft menu. So I'm doing something wrong... Can anybody help, please?

You have to set the Gun Editor to run in Windows 98 mode - that might be the problem. Right-click on the .exe file, and select "Properties". Go from there.

And it isn't systematic either. Weapons, then??? Perhaps it depends on the loadout... Also, where can I find which aircraft have been spawned in missions? Sometimes in "Quick Combat", I get a CTD with the installs these two aircraft are in, and I'd like to check that it really is their spawning that causes the CTD. My other installs don't do it, so that is a clue already - but is there a mission file which records not only the last aircraft used, but also the aircraft generated randomly?

Try anything once, but I'm not sure this is the problem...

I've been getting CTDs from time to time with thses two aircraft, and don't know why. I'm on SFG, but have replaced the avionics files where appropriate with ones which should be compatible, from aircraft which do not give any trouble. The weapons are correctly installed, and I can't see where I may be going wrong... Any ideas?

Got it - you're right. Just had the chance to test it, and it's never worked better! Thanks again.

That might just be it - as SFG is hardly the latest game around, despite its qualities! It did use to run correctly, so it may well be a problem with too up-to-date drivers. The monitor drivers are Windows, but have worked well for years. Off to try and find 93.71 - thanks!

Yet another challenging problem - from time to time, never at any one moment but always as a result of moving from one screen to another (loading to play, play to result, etc), I suddenly get horizontal black-white-grey snow, in lines which vibrate up and down vertically. Pressing Esc or ctrl+alt+del has no real effect, except that the lines of snow go vaguely the same colour as my desktop. All my installs of SFG do this. Other games (CFS3 and 2) and applications run correctly. Specs: Windows XP Home, English, P4C 2.8GHz on Asus P4V-800X with 1.75GB DDR1 RAM, Nvidia 7600GS. Updating the drivers - updated today to 175.19_geforce_winxp_32bit, release date 16/05/2008 - does not help. I ran Driver Cleaner after disinstalling the old drivers prior to updating. Previous drivers were 169.21. After each "crash", I'm obliged to use the escape button, as there seems to be no other way out. Anybody got any suggestions?

Now that pre-empts another question I wanted to ask - good one! Edit, later: Well, at least I don't have to watch the video before finding that it still won't load. Good try.

Cheers, Kevin - I'd assumed that that was the answer, but I wanted to be sure that one of the old hands didn't have a work-around. I would assume that the A-Team are not that welcoming of newbies who have yet to make a contribution to the world of SF/WOX? I have no idea why they withdrew their material, and I'm not going to ask - at least, not in so many words.

Drivers are the latest released, and I'm using a relatively recent DX9 version - if I use an earlier one, CFS3 won't run...!

To all intents and purposes, it is; only the static aircraft are anachronistic. I have replaced them, but the problem is moling. Even aircraft models which are released as statics, such as the Lightning F.6, mole when used directly as a terrain object.

I'm using the New Guinea terrain, but with modern flyables; I'd like to know how to set up a modern replacement for the WW2 aircraft types used in the scenery. I've tried adapting a flyable LOD model, but it "moles" - only the parts above the centre of gravity appear above ground. In other words, the C-130 is liveable with, but the Mirage looks ridiculous. I'm currently using the LOD 2 level, as anything higher wastes FPS. Any suggestions? The knowledge base does not (seem to) mention incorporating aircraft into the terrain.