martinlest2

I tried to make an exclude to get rid of default scenery at LSGG (Geneva), but it didn't work. Turns out the buildings are contained in OB9EURW1.BGL (EurW). Is there any way to get an exclude to work on this file? I used ADE9x to make the exclude/ALL, covering the whole airport, but the default buildings are still there. Thanks

I should have known it wouldn't be that simple!! Removing the bgl file removes all the taxiways and aprons, so that most of the airport is on grass. The default scenery isn't there because there is a particularly 'vicious' exclude file in the folder. If you remove that, you get the taxiway and aprons back, but all the FS9 default buildings come back as well. I tried making my own exclude, but no luck because it turns out that the FS9 default buildings at LSGG are contained in the file OB9EURW1.BGL. I suppose that excludes don't work on that file? Looks like I'll have to put up with the dirt* and poor ground textures. If FSDT have a sale, I'll get their Geneva scenery instaed perhaps... :mad: * .. well, I can just disable the fx file for the duration of course|!

OK, by trial and error I found the problem is with one of the airport bgl files. When I remove it, the dirt effect stops. I also lose (some rather ugly "r8" type) concrete, so that taxiways now run over grass. There are also some scenery objects, unfortunately, in the same bgl. I have extracted the scenery objects and made a new bgl of them, so that should be OK. And I will simply fill in the grass spaces where there should be concrete using AFCAD2 to make some new polygons. Never a dull moment! Thanks for the ideas...

Anyone any ideas here please? I still have this problem. Not fixed via the FS9.cfg file and I get it just as often in the default Cessna as any addon aircraft. Reloading the aircraft doesn't help - only restarting FS9.

Thanks Dave - I thought that that was going to be the solution, but the links are already all marked 'Concrete' under 'surface', so back to square one!

Thanks for the reply Hans - but all aircraft that I have tried kick up dirt on the tarmac at LSGG, including the default Cessna. It doesn't happen when I move airports in those planes, so despite what you say, I think it is the airport that has the problem...

Anybody able to help??

I have one or two airports (my version of LSGG for instance) at which, when you taxi along the apron and taxiways, dust/dirt is kicked up by the wheels from the concrete, as per fx_tchdrt.fx. Only on the runways is it OK. Anyone know how to stop this from happening at individual airports, without disabling the fx file? The AFCAD does show concrete in the areas where this happens, so I am not sure why the problem occurs. Thanks, Martin

The helicopters are much more awkward about panel and sound combinations - I think it's that which stops them starting up properly. I kind of sorted this out by using a panel (with HUD) that I know works, but this is one of those cases where you leave FS9 working one week, come back to fly the same chopper the next, and it won't start again. No wonder I rarely fly them!

Hi. Thanks for looking at the post... As so often, when I decompile a stock airport bgl file (using NewBglAnalyze.exe), recompiling it (with bglcomp.exe from the SDK), fails to produce a bgl file again. With CompileHelper.exe I get a whole list of errors. I assume that these were introduced by NewBglAnalyze (??). In this case, I am simply trying to change the ICAO code FAJS to FAOR (AP955410.BGL), but if I can't recompile even before I make any changes, I am off to a really bad start! Can anyone help me with the "errors" that come up (below) on this one? The result below is from trying to recompile the stock bgl to xml, no changes made by me inbetween. Is there a more reliable way to edit stock bgl files (without a huge learning curve!)? Maybe I need to purchase AFX? Or, I do have ADE9x, but not the full ProKey - it would be a lot cheaper to buy the ProKey than the relatively expensive AFX.... but as far as I can see the ADE ProKey is only good for stock airports (I am running the 15-day evaluation version at the moment, to test it out). Basically I can't see how to change the ICAO of a third party airport (which uses an AFX type AFCAD) other than buying AFX - I can do it in AFCAD2, but will lose data. Thanks, Martin Parsing document: E:\FS9 Utilities\BGL Decompilers\AP955410.xml ERROR C2033: XML Parse Error (line, column, error) ERROR: 12730, 10, enumeration constraint failed. The attribute: 'fixType' has an invalid value according to its data type. ERROR: Bad Fix Type.ERROR C2031: Failed element parse <Leg> ERROR C2032: XML Parse Error! Element tree follows: ERROR: <FSData ERROR: version = 9.0 ERROR: > ERROR: <Airport ERROR: ident = FAJS ERROR: region = ERROR: country = South Africa ERROR: state = ERROR: city = Johannesburg ERROR: name = Johannesburg Intl ERROR: lat = S26 8.02167 ERROR: lon = E028 14.53900 ERROR: alt = 1694.08M ERROR: magvar = 16.90 ERROR: > ERROR: <Approach ERROR: type = ILS ERROR: gpsOverlay = FALSE ERROR: runway = 3 ERROR: designator = LEFT ERROR: fixType = TERMINAL_WAYPOINT ERROR: fixIdent = OM03L ERROR: fixRegion = FA ERROR: heading = 15.18 ERROR: altitude = 8000.00F ERROR: missedAltitude = 8000.00F ERROR: > ERROR: <MissedApproachLegs ERROR: > ERROR: <Leg ERROR: type = VM ERROR: fixType = ERROR: fixRegion = ERROR: fixIdent = ERROR: turnDirection = L ERROR: magneticCourse = 213.0 ERROR: altitudeDescriptor = A ERROR: altitude1 = 8000.00F ERROR: > ERROR: ERROR C2033: XML Parse Error (line, column, error) ERROR: 12917, 10, enumeration constraint failed. The attribute: 'fixType' has an invalid value according to its data type. ERROR: Bad Fix Type.ERROR C2031: Failed element parse <Leg> ERROR C2032: XML Parse Error! Element tree follows: ERROR: <FSData ERROR: version = 9.0 ERROR: > ERROR: <Airport ERROR: ident = FAJS ERROR: region = ERROR: country = South Africa ERROR: state = ERROR: city = Johannesburg ERROR: name = Johannesburg Intl ERROR: lat = S26 8.02167 ERROR: lon = E028 14.53900 ERROR: alt = 1694.08M ERROR: magvar = 16.90 ERROR: > ERROR: <Approach ERROR: type = ILS ERROR: gpsOverlay = FALSE ERROR: runway = 3 ERROR: designator = RIGHT ERROR: fixType = TERMINAL_WAYPOINT ERROR: fixIdent = OM03R ERROR: fixRegion = FA ERROR: heading = 15.61 ERROR: altitude = 8000.00F ERROR: missedAltitude = 8000.00F ERROR: > ERROR: <MissedApproachLegs ERROR: > ERROR: <Leg ERROR: type = VM ERROR: fixType = ERROR: fixRegion = ERROR: fixIdent = ERROR: turnDirection = R ERROR: magneticCourse = 213.0 ERROR: altitudeDescriptor = A ERROR: altitude1 = 8000.00F ERROR: > ERROR: ERROR C2033: XML Parse Error (line, column, error) ERROR: 13104, 10, enumeration constraint failed. The attribute: 'fixType' has an invalid value according to its data type. ERROR: Bad Fix Type.ERROR C2031: Failed element parse <Leg> ERROR C2032: XML Parse Error! Element tree follows: ERROR: <FSData ERROR: version = 9.0 ERROR: > ERROR: <Airport ERROR: ident = FAJS ERROR: region = ERROR: country = South Africa ERROR: state = ERROR: city = Johannesburg ERROR: name = Johannesburg Intl ERROR: lat = S26 8.02167 ERROR: lon = E028 14.53900 ERROR: alt = 1694.08M ERROR: magvar = 16.90 ERROR: > ERROR: <Approach ERROR: type = ILS ERROR: gpsOverlay = FALSE ERROR: runway = 21 ERROR: designator = LEFT ERROR: fixType = TERMINAL_WAYPOINT ERROR: fixIdent = OM21L ERROR: fixRegion = FA ERROR: heading = 195.60 ERROR: altitude = 8000.00F ERROR: missedAltitude = 8000.00F ERROR: > ERROR: <MissedApproachLegs ERROR: > ERROR: <Leg ERROR: type = VM ERROR: fixType = ERROR: fixRegion = ERROR: fixIdent = ERROR: turnDirection = L ERROR: magneticCourse = 37.0 ERROR: altitudeDescriptor = A ERROR: altitude1 = 8000.00F ERROR: > ERROR: ERROR C2033: XML Parse Error (line, column, error) ERROR: 13292, 10, enumeration constraint failed. The attribute: 'fixType' has an invalid value according to its data type. ERROR: Bad Fix Type.ERROR C2031: Failed element parse <Leg> ERROR C2032: XML Parse Error! Element tree follows: ERROR: <FSData ERROR: version = 9.0 ERROR: > ERROR: <Airport ERROR: ident = FAJS ERROR: region = ERROR: country = South Africa ERROR: state = ERROR: city = Johannesburg ERROR: name = Johannesburg Intl ERROR: lat = S26 8.02167 ERROR: lon = E028 14.53900 ERROR: alt = 1694.08M ERROR: magvar = 16.90 ERROR: > ERROR: <Approach ERROR: type = NDB ERROR: gpsOverlay = FALSE ERROR: runway = 3 ERROR: designator = LEFT ERROR: fixType = NDB ERROR: fixIdent = JS ERROR: fixRegion = FA ERROR: heading = 15.17 ERROR: altitude = 6800.00F ERROR: missedAltitude = 8000.00F ERROR: > ERROR: <MissedApproachLegs ERROR: > ERROR: <Leg ERROR: type = VM ERROR: fixType = ERROR: fixRegion = ERROR: fixIdent = ERROR: turnDirection = L ERROR: magneticCourse = 213.0 ERROR: altitudeDescriptor = A ERROR: altitude1 = 8000.00F ERROR: > ERROR: ERROR: Compilation errors detected, compilation failed! Parse complete!

I still have XP on another couple of PCs and I use AVG free - I checked several (last year) and that seemed the best overall Yes, it took time to find the bgl files, but removing the three I mentioned solved the problem. Makes no sense though..

Dijvid, even if drivers were installed (unlikely) they are removable via the Cotrol panel. I have Dell Windows XP installation discs that came with previous Dell computers I owned, and they just install the O/S - the drivers are on a separate disc.

Thanks, but if you (please) read what I originally posted you'll see that I did exactly that before I even wrote anything here, and fixed it - I gave full details. I posted, not to get help with the (solved) issue, but because I was interested (as I keep saying) to know if anyone with a technical knowledge might know what there could be in the mesh bgl files that would stop FS9 loading scenery. Maybe I should have posted this in the scenery design forum... Great people bother to reply, but probably good idea to read the earlier posts first - or at least the original one? :smile: And no, I'm not into the 'fad' of knocking Microsoft either. I am ever grateful that they gave us this flightsim. And Windows 7 is pretty wonderful to boot (so to speak!)

Please can you copy me some links where this exact point is explained (by someone who knows, like Microsoft, rather than is expounding an opinion). Maybe you just meant it has caused no issues in your setup. It's written everywhere not to install FS into one of the C drive programme folders, and I think most people have gone along with that. Very possible, which is why I don't do it... :biggrin: Basically, you've got to be joking. :smile: I don't have a spare six months to do that (+ reactivating licenses online etc. etc.etc) and I see no reason to anyway. The problems come from what is installed, not where. Basically, I have everything installed where it should be/"wants to go" anyway. Yes, after so many years adding 3rd. party stuff my FS9 setup is huge and very complex and so I expect to have some problems from time to time... though I agree, I do seem to get something new at least once a week! Mostly nothing 'serious' - probably amazing that so much disparate software works together flawlessly so much of the time! As I said here, I just posted this thread as it'd be good to know exactly how the bgl files might be interacting with each other in this way. I manage to sort out the problems myself (or with people's advice on this forum) 99% of the time..

Worth having a look maybe - it allows a lot more options than doing it in FS9 and it just takes a mouse click or two to activate/deactivate multiple scenery files. It's in the file library.

That's OK, but thanks for the offer! As I say, I used to do that in days gone by, but with a proper PC running FS9/FSX (rather than the Dell XPS laptop I used to use) there's no advantage - I get no discernible performance gain (I've tried it). My airports are also arranged by country, all in separate folders. In fact, like you perhaps, my whole setup is highly 'automated' with scripts I have written and so on. But I still have enough setting up to do with all my addon software without adding on extra 'work' (labour of love though it may be) by selecting which sceneries to activate/deactivate before I fly. The only advantage would be that, with the FSGenesis bgl files for Micronesia absent, I wouldn't have had the issue at the Marshall Islands - but it's so rare as to be not worth the change. I posted here to see if any 'guru' could explain why the files might be preventing FS9 from loading scenery, at an 'under the bonnet' level. By the way, do you use Scenery_Align, to activate/deactivate sceneries? It is a great tool for automating that, if that's how you like to work things in FS. I still use it to align the scenery numbers in the scenery.cfg file after adding new scenery (I can't do it in the FS9 interface - I went way of the maximum visible there years ago). Thanks again.

Never heard of that - I can certainly try it. But I doubt I have any wx files, as I am fairly sure they are created along with .flt files, when you save a flight - and I load my flights from flight plans these days, not saved flights.

Because you install FS Genesis mesh from the CD-ROMs and they go into their own folder - you don't (can't) install and uninstall bgl files continuously according to where you are flying. It's not even clear from many of the names the geographical areas that they govern. Yes, that's usual. I suppose 99% of people will have, that's the FS9 scenery library. I used to use Scenery_Align to do what you do, but only on my spare FS9 laptop: unless you have a very feeble PC, it's not necessary - it gives me no performance gain, just extra hassle before I can fly. No, it copes brilliantly with everything I throw at it, even in FSX for the most part. The reason for the problem is nothing to do with resources - this problem is very specific and caused by a couple of 'rogue' bgl files. Your choice, but for most modern PCs, it's quite unnecessary to do that, I assure you. It's loading a lot of aircraft (especially if you have a large AI collection) that takes the time and resources, not scenery. You could try removing all but the default C172, leaving every airport scenery active - FS9 starts up in a fraction of the time. You can also see what's loading with Process Monitor as FS9 starts up - lots and lots and lots of aircraft files...

I tried today to fly from PKMA, Marshall Islands and found that, although I didn't get a CTD, FS9 stops working as it tries to load the scenery files... it never gets past 0%. At the same time I can see in Task Manager that the CPU usage also drops to zero, and stays there... Thought it might be my 3rd. party addon for the Marshall Islands, but no, without that scenery, just the same thing happens. So I spent hours, well, a couple at least, tracing the problem by trial and error (I was sure it was a problem due to an addon I have, as an 'out of the box' FS9 installation has no problem, whether the 3rd party Marshall Island scenery is installed or not) and eventually found it was FSGenesis mesh. Delete that entry from the scenery.cfg file, and all is OK. So, another hour to track down the precise culprit within FSG, which turned out to not be the Marshall Island mesh, oddly, but the terrain mesh "dem76m_pacificisl_micronesia...". Remove those files and all is OK: put them back, FS9 won't load at the Marshall Islands, it just goes dead in the way I've explained. Tried several times to be sure... no doubt about it. It's not the first time I have had to remove a bgl file which causes a problem in some other part of the world (sometimes very remote), and not the first time it's been a mesh file. Can anyone say why, in this case, an FSG mesh file for Micronesia might stop sceneries from loading in another part of the world and cause FS9, basically, to stop, even though the FS9 window remains open" (no FS9.exe activity at all in Process Monitor)? I'd be interested to know what might be going on: even if I fixed the problem by removing some bgl files, I don't know what is actually happening within FS9.exe If you have the FSG mesh files above (there are three: I removed them all though maybe only one is to blame), maybe you could try to see if you also get this problem? As I say, it seems to happen with the default scenery too.. Thanks. Martin

I have three 'FS9 folders' for that reason. My full installation ('FS9'), one clean 'out-of-the-box' installation ('FS9-Clean') and one made by a batch script which copies the latter, but adds no files, so you just have the folder structure ('FS9-Blank'). So long as these all have the same root drive, you can just change names so that one of the 'dummies' is now called 'FS9' (renaming your full FS setup folder first of course) and then installers put all their files there - the registry information, if entered, is the same of course. Especially useful to install to the 'blank' version (you have to add an fs9.exe and scenery.cfg so that it is recognised as a valid FS9 installation), as a search for 'All Files' in that folder will then show every file that has been installed. Or you can copy them to the 'Clean' installation and see the files working there in the sim. (I wrote another batch file to clean them up when you've finished and just have the 'virgin' installation there again for next time). When happy, you can then copy and paste the files & folders across to your real FS9 folder, taking note of what you move/copy of course, and well, no worries as to an installation being messed up, as of course can happen, with key files being 'silently' replaced, as everything is now done manually and you are asked about overwriting any files... Rename things back as they were and you're done.

I've updated my nVidia Inspector to v.1.9.7.6 and will try again.. thanks. LATER: OK, good have the latest version, but changing the settings has made no difference to the rippling when I pan in FSX. If other people don't have this issue, I can't help but wonder what the problem is with my setup, as I say. I've had FSX (Acceleration) on at least three different PCs over the years and it's always been like this - one good reason I hardly ever fly with it. My current PC really should have no problem with FSX.. I don't know what else to try tweaking. Thanks again for the input.

Actually, now I've rebooted, reloaded and retested, there is an appreciable difference with the 'windowed mode' line added to the fsx.cfg file. Flyable, certainly, so thanks... On the other hand, the 'wobbling jelly' effect is still there, it's just that the 'jelly' is 'stiffer' and the wobble tighter. It is certainly, even now, no match at all for the rock-solid stability of the scenery drawing in FS9...

It'd be good if people were able to post screenshots of their grass and say which detail1.bmp file they are using. I find you have to be very careful, as the one I was using, although it made the grass look good, had unwanted side effects. You could look here - one downside from the file I was using is shown in post #16. http://www.avsim.com/topic/488055-odd-ground-texture-problem/page-2 I have tried several and currently gone back to the fs9 default file, but an improvement, without these side effects, would be very welcome.

Hmmm, still not right. In mountains I am getting this ugly effect, pink snow (algae?? Haha..) with a demarcation line: When I replace my downloaded detail1.bmp with the FS9 default, it goes away, all white and even. But then grass is not crisp any more. Can't have your cake and eat it, it seems. Does anyone have a recommended detail1.bmp file? I could keep switching between the two, depending on where I am flying (snow or not), but that's not ideal of course.

Googling told me that they should be in the Graphics section