Hello all,Thank you to Ray Proudfoot for making the IFSD stuff available. It's nice to have a some better quality Irish airports and scenery again.I have a problem though... the file CarnTerm.bgl in the IFSD Scenery package I just installed is causing frequent reloads of the flight if I start at EICM, often before I even start the engine. If I remove the file from its ../IFSD/EICM/scenery folder the flight seems to go OK but that's a bit poor because I'm then missing all Galway's airfield buildings.I've tried altering the afcad to avoid collisions and interference with buildings, and even reinstalled IFSD, but it doesn't seem to make any difference.Does anyone have a good replacement? Or any other solution?Thanks for any help,Dave

Hello all,Thank you to Ray Proudfoot for making the IFSD stuff available. It's nice to have a some better quality Irish airports and scenery again.I have a problem though... the file CarnTerm.bgl in the IFSD Scenery package I just installed is causing frequent reloads of the flight if I start at EICM, often before I even start the engine. If I remove the file from its ../IFSD/EICM/scenery folder the flight seems to go OK but that's a bit poor because I'm then missing all Galway's airfield buildings.I've tried altering the afcad to avoid collisions and interference with buildings, and even reinstalled IFSD, but it doesn't seem to make any difference.Does anyone have a good replacement? Or any other solution?Thanks for any help,Dave

I downloaded that package and installed it (and the update) into a temporary folder - not into my FS2004 setup - just to check it out.I could not help but notice the included AFCADS are for FS2002 - not FS2004. I don't believe FS2002 style afcads work properly in FS2004.I am therefore curious as to what you used as Afcads for these airports? You say you modified at least one of them.

Hi,I'm sorry for being so slow in replying- I have to use the PC at work (no net at home).I didn't install the IFSD afcads... I used afcad221 to have a look at what I already had.There was the MS original and another generated by Ultimate Traffic. The UT version I disabled by altering it to a .xxx file. I then went ahead moving parking spots and taxiways in the MS original before recompiling traffic with UT which I guess generated a new afcad. Did I do something stupid?

Hi,I'm sorry for being so slow in replying- I have to use the PC at work (no net at home).I didn't install the IFSD afcads... I used afcad221 to have a look at what I already had.There was the MS original and another generated by Ultimate Traffic. The UT version I disabled by altering it to a .xxx file. I then went ahead moving parking spots and taxiways in the MS original before recompiling traffic with UT which I guess generated a new afcad. Did I do something stupid?

As a test I installed just the EICM airport - and using just the default Afcad I have no issues whatsoever.I do not have UT (which I presume stands for Ultimate Traffic) so do not know exactly what recompiling with UT would do, but I am guessing it does indeed create another UT afcad.My best guess is that the reloading issues you are having are related to having two active afcads - but that is an educated guess at best.I would use the afcad program to study the UT afcad and note any special parking codes it may have at parking spots and then redo the default afcad in the same manner and save it with your name appended to the file name (just to make it easier to identify). Then I would disable the UT afcad (again) and stop there. There should not be any reason to recompile with UT - especially if it creates another afcad.Try that and see if it solves the problem.Good luck !! :(

Another thought -Don't know why I did not think of this in the first place..........Do you have "crash detect" turned on (Settings/Realism) ??When you used the term "reload" that suggests that you likely do. The terminal building probably has an invisible crash envelope which you are "hitting" casuing the scenery to reload.Turn off crash detect (assuming it is on) and see if that stops the problem.

I just tested it again with "crash" on and was able to duplicate your problem.I did not see the problem before as I always keep the crash detection turned off on my setup.Many enhancements exhibit this problems so I just find it easier to leave that option off.Hope you find that is the issue on your setup also.

Hi,I tried again last night, too, with both afcads and finally noticed the 'crash' sound. Haven't tried turning crash detection off yet though... maybe tonight.Did you find that all the 3-d models are out of line with everything else? I have aircraft parked on the grass at all the IFSD airports, some of them intersecting airport buildings, active runways that aren't on the tarmac and a couple of airports where the AI (only AI- player's aircraft sit correctly) is buried up to the fuselage. Oh and Howff Head (Dublin coast) slipped along a major tectonic fault...I gave up in the end and uninstalled the whole package. I think it's a shame and by this evening may have forgotten my frustration enough to have another go. I might end up disabling the airports and keeping everything else (VFR while gawping at the scenery is what I do most of!).I'll turn off crash detection (didn't think of it before) and see if I can move stuff around in all 3 dimensions with afcad221. I don't think the AI is too low (it's ok everywhere else) so I suppose the airfield ground textures (is that the correct expression?) are slightly too high, as well as too far 'over', although I can't explain why player aircraft still sit upon the ground.Which would be easier to move, the afcads or the 3-d stuff? I guess the former as at present the only utility I have is afcad221. Would you have any suggestions for how to go about it?Regards,D

Hi,I tried again last night, too, with both afcads and finally noticed the 'crash' sound. Haven't tried turning crash detection off yet though... maybe tonight.Did you find that all the 3-d models are out of line with everything else? I have aircraft parked on the grass at all the IFSD airports, some of them intersecting airport buildings, active runways that aren't on the tarmac and a couple of airports where the AI (only AI- player's aircraft sit correctly) is buried up to the fuselage. Oh and Howff Head (Dublin coast) slipped along a major tectonic fault...I gave up in the end and uninstalled the whole package. I think it's a shame and by this evening may have forgotten my frustration enough to have another go. I might end up disabling the airports and keeping everything else (VFR while gawping at the scenery is what I do most of!).I'll turn off crash detection (didn't think of it before) and see if I can move stuff around in all 3 dimensions with afcad221. I don't think the AI is too low (it's ok everywhere else) so I suppose the airfield ground textures (is that the correct expression?) are slightly too high, as well as too far 'over', although I can't explain why player aircraft still sit upon the ground.Which would be easier to move, the afcads or the 3-d stuff? I guess the former as at present the only utility I have is afcad221. Would you have any suggestions for how to go about it?Regards,D

I would be will to bet that turning off crash detection will solve that particular problem.As to the other issues - well there are many possible factors in play here as even though I do not know the complete history of this package, it would appear that it was originally designed for FS2002.Likely there are elevation differences in the default terrain between FS2002 and FS2004 and perhaps you also have some terrain enhancement for this area installed also. All would potentially effect how aircraft "sit" on the tarmac.My best guess it that with a great deal of "tweaking" of the various elements at each of the airports in this package you "might" be able to get most of them working properly.For starters I would work on one airport only and create a new Afcad for it - being sure to disable the one your traffic package uses. This all may be more trouble than it is worth and you likely can find something similar - perhaps a payware package - which is designed to work properly in FS2004.Just some random thoughts on the subject.

Hi Dave,Taking out the crash detect worked nicely, thank you for that.The player aircraft sits on top of whatever ground texture is there but the AI seem determined to use the mesh elevation... All combinations of add-on mesh & scenery, with IFSD disabled, result in a field elevation of 84.7 feet.All combinations, with IFSD enabled, put my aircraft at 86.4 feet. The AI are then buried to about 18 - 24 inches, suggesting they're using the mesh elevation rather than the texture surface.I thought as I was mucking about with things last night that the original problem may be caused by AI crashing into the IFSD ground. Is there a utility available for quick and easy flattening of a piece of ground to a different elevation?Thanks for all your help,D

Hi Dave,Taking out the crash detect worked nicely, thank you for that.The player aircraft sits on top of whatever ground texture is there but the AI seem determined to use the mesh elevation... All combinations of add-on mesh & scenery, with IFSD disabled, result in a field elevation of 84.7 feet.All combinations, with IFSD enabled, put my aircraft at 86.4 feet. The AI are then buried to about 18 - 24 inches, suggesting they're using the mesh elevation rather than the texture surface.I thought as I was mucking about with things last night that the original problem may be caused by AI crashing into the IFSD ground. Is there a utility available for quick and easy flattening of a piece of ground to a different elevation?Thanks for all your help,D

The actual elevation using the default afcad for EICM is shown as 81 feet - the figure you show is apparently taken from whatever aircraft you are using. The height seen at the top left of your screen when in any aircraft, is plotted from the position of the radio in the cockpit - not where the wheels touch the tarmac. Use the afcad figure.Not sure a flatten will solve the problem but if you wish to try, many of use the free utility named FSTFlatten by Steve Greenwood. Works like a charm.You can find it here:http://home.earthlink.net/~smgreenwood/welcome.shtmlClick on Resources (top right of the screen) and download the last item in the list of four possibilies. Be sure to read the documentation carefully.Good luck.

Different elements of FS use different sources to determine elevation.AI will apparently use the first elevation reference that FS finds as it loads scenery starting at the bottom of the Scenery Library and moving up.Try creating a new scenery folder, as an example......\FS9\Addon scenery\Elevation corrections\sceneryPut a copy of the IFSD afcad from the addon in that scenery folder.Start FS and add "Elevation corrections" to the Scenery Library. Move it down to the bottom, right above "Default Scenery".Test and report back.regards,Joe

Hello again,Opa, you were right. Flattening made no difference... Ah well.Time for plan C (plan B was just to ignore the problem). Joe, thanks for the suggestion. I'll give that a go this evening and let you know what happens.Regards,D

Hey!What do you know? It worked. I used an afcad221-made copy of the default from somewhere inside one of those big .bgls in eurw, because I'd taken out the other EICMs. Now I've got airfield at the correct elevation (thanks Joe), all flattened to the extra 1.7 feet & crashes ignored (thanks Opa and Steve Greenwood) and with hard surfaces in the right place & parking spots moved around to avoid interference with buildings (thanks Lee Swordy).The crashes still occur and seem to be related to which parking spot I use, or more accurately, to which part of the airport I start the flight at. Even when I excluded all AI by leaving only one parking spot I still got reloads at most places. If I started at a point where I didn't seem to suffer a reload, AI and the number of other parking spots didn't appear to make a difference. However, I was getting a little tired by then and wasn't being particularly methodical; I'll experiment again over the weekend and maybe use the IFSD afcad.Still, it looks good now and that's what really matters. I just have to remember to turn off crash-detect if I intend to use EICM (not a problem as I have already to remember to reduce the AI traffic at busy airports).As an aside, it's interesting to see that FS9 uses parking spots as a sort of reference location. If you move a parking spot after saving a flight, when you restart you are in the same physical location and no longer on the (moved) parking spot. My first sim was Flight Unlimited 3 which saves your location as 'on the parking spot' and moves your start location around with it when you alter the taxigraph.So thanks again chaps for your help.Before: sunken AIAfter: all sweetness and light