hjwalter

Thanks Tom for your much appreciated reaction but to cut a long post shorter I did not describe any details about what I had tried afterwards and out of pure inquisitivenes only. I had in fact used DXTBmp to change the texture formats, delete/re-instate alpha channels, mipmaps, etc. but was not able to find anything technically wrong as per your suggestions. It was most probably just one of those unexplainable quirks hiding somewhere within the textures concerned. Anyway, my standard solution to such issues remains my trusty DELETE key. Cheers. Hans

Hi Guys, After much trial and error messing around the solution/fix turned out to be very simple indeed but then again, if you know how to do it, then everything is simple. However, the remaining problem is that no two problems are the same and this one was definately a first of this kind for me. It turned out that it was not the library BGL which was corrupt but the textures it was calling for. After dis-assembling the BGL in question it became possible to find out which texture names were being called for and after simply deleting these, my problem and that of the Abacus program was solved. I had a go at trying to find out what was wrong with the corrupted textures but they seemed perfectly normal mipped DXT3s with alpha channels. The library BGL file, now without it's related corrupt textures, has been deleted as well. Problem solved !! Hans

Hi Guys, I've been using this fantastic program for years to enhance my airport sceneries but now suddenly, because of a selected, probably corrupt (object placement) BGL file, my FS9 crashes with a black screen and a StackHash error message. However, when re-opening my FS9, selecting and re-opening the Abacus program, my FS9 immediately crashes again without giving me the chance to select any other (object placement) BGL file. The program evidently remembers and stores the last selected BGL file somewhere, even although the BGL in question has in the meantime, been deleted. My FS9 seems to work normally but as soon as I open the Abacus program ....... BANG !! Does any of you experts out there know where this last selected BGL file could be stored, so that I can manually change it into a non-corrupt one or how I can somehow initialize it ? An INI file somewhere maybe ? Any ideas anyone ? Any help is most welcome. Regards Hans

I searched for your KLAX scenery, hoping to be able to download and test it for you but the only FSDT version I could find was a payware on their commercial site. The most logical thing would therefore be to put your problem forward to FSDT directly. Good luck Hans

I assume that when you say that you have placed your "äddons" at the top of your scenery library, you also mean the "small airport near KBOS", which you have evidently tried to enhance by adding to it some scenery objects via your "EZ Scenery" program. Are you sure that you have only used the payware "EZ Object Placement" program and not some kind of other "EZ" function or program ? You should also realize that when you move any kind of addon scenery to the top of your scenery library, this scenery will have priority over any other sceneries futher down in your scenery library listing, possibly including your KBOS. If you have then made certain types of errors in this now high priority addon scenery, there is a strong possibility that your KBOS will no longer be visible or at the very least, will cause the types of problems as you describe. As far as I know there are only three existing scenery enhancement programs for FS9, the extremely good and easy to use but payware "EZ Object Placement" program, the freeeware "RWY12" program and the freeware "ADE" (Airport Developement Editor) program. All three have extensive usage instructions. Hope this helps. Hans

Sounds like you have either two Afcad/ADE files or most likely, your existing Afcad/ADE file does not cover your visible airport scenery accurately enough. E.g. Afcad/ADE taxiways, etc. MUST always be positioned exactly on top of any visible airport taxiways, etc. because the Afcad/ADE taxiways are the ones which your AI planes will follow, not the visible ones. Your problem is not caused by the MYTraffic program. Good luck Hans

Thomas, Have you been using your FS2004 normally and problem free before March 2019 ? If this is the case, then your "Flight Simulator Files" folder containing all your saved flights/flightplans, is either corrupt, is no longer positioned where it should be or has somehow been deleted. If it's a problem, which showed up directly or very shortly after installing your FS2004, then it seems that you installed it in it's default positions, which is known to produce a whole range of unpredictable problems and especially with Win10. In both cases I suggest that you un-install your existing FS2004, clear up any risidual files/folders and that you then perform a complete re-install but this time in any other HD partition or separate HD than the one in/on which your Win10 lives. Good luck Hans

If I remember correctly from many moons ago, you need to run the "data base creation" (dbc) utility in order to initially create the necessary data base, which FSNav then uses to create it's map. This utility can be found in the FSNav folder within your modules folder. Hope this helps. Regards Hans

Hey guys, I've had OOM error messages/crashes as well but ages ago. It's a message from Windows and not from FS9 itself. The message means that something from within FS9 is (via Windows) trying to access a memory area outside that allotted to or by Windows and does not mean that there is not enough available memory. This error is almost always caused by something within FS9, which is programable and which contains one or more program errors or has become corrupted, e.g. a cockpit instrument, an effect, a light, etc. As far as AI planes go, I would therefore want to suggest that you look into the effects and lights of any culprit you may suspect and that you choose a trusty default flyable plane when you open your EGKK airport. Hope this helps, in any case to narrow down your problem. Good luck Hans

Sounds as though your prop texture has no, or a not correctly working, alpha channel. What I usually do in such cases is to copy/paste a prop texture in it's place from a correctly working similar plane and if it's name is different, I rename it to that of my original incorrect one. Hope this helps. Hans

Yes, it's bumpy for all aircraft types, even for some (test) heavies but these are far heavier and can therfore make more use of their suspension properties specified in their aircraft.cfg files. However, experimenting with these same suspension properties for the light aircraft, does have some effect but not nearly enough to make it "As Real as it Gets". This bumpyness is somehow directly related to the runway texture being specified, even when it gets (test) used in the default APnnnnnn.bgl file and together with the related addon scenery being in a de-activated state. When I create a very wide "concrete" apron polygon in the airfield's Afcad file and which then becomes visible along both sides of my bumpy runway, I can then (test) taxi my plane from the runway onto this concrete polygon and the bumbyness will immediately disappear. Taxiing back onto the runway and the bumps are there again, even although the concrete polygon lies at exactly the same elevation. Normally the default APnnnnnn.bgl concrete runway is aotomatically de-activated by the standard coding within the related Afcad file but even if this coding is removed the bumpyness remains as the result of the runway texture being specified via the word "GRAVEL" further down the code listing. I can therefore only conclude that something within FS9 itself automatically creates these bumps whenever it even smells a runway which is non concrete or non asphalt. The mechanism itself seems to be steered by so called "reserved words", e.g. "CONCRETE", "ASPHALT" or "GRAVEL" (and some others), which can be specified as such either in the APnnnnnn.bgl or in the Afcad file. Regards Hans

Normally on most of these small tropical airfields, I use propeller driven single engined light aircraft. Hans

I'm sorry Guys if I wasn't clear enough but Tim's concrete apron polygon method in the related Afcad file was the first thing I tried but sadly that didn't work as hoped. I firstly tried a narrow invisible one under my gravel runway and then a wider visible one just for testing purposes but to no avail. I even tried a very large apron polygon, which covered the whole airfield but the bumps on my gravel runway remained. The test airfield surface elevation is exactly the same as that of the default airfield and that specified in the Afcad file. I took another good look at the Afcad instructions under "Runway properties" and "Surface" where it said in a for me rather cryptic manner:- "This sets the visible surface texture and the smoothness of the surface. There does not appear to be any provisions for custom textures". How I should interpret "custom textures" and if any of these would include my bumps causing gravel texture, remains unclear. I've now arrived at the stage of giving up un this one and just accepting the smooth concrete or asphalt runways for my tropical/bush airfields, which incidently are all situated "on top of" their existing default concrete or asphalt versions. Thanks again guys for your reactions. Hans

Alas Tim, your suggestion sounded to good and too simple to be true but please just forget about my dirt taxiways being bumpy because these were not really the biggest problem ...... but ...... After a lot of testing it seems that the bumpy runways are somehow directly related to the textures being used on them. Anything which deviates from concrete or asphalt causes the bumpiness, no matter if these are drawn by the related Afcad (or ADE) file, by the original APnnnnnn.bgl file or even by both. E.g. when I de-activate my new addon tropical airfield in my scenery library, together with it's "gravel" runwayed Afcad (or ADE) file and I edit the default APnnnnnn.bgl file's "concrete" into "gravel", the bumps are there. After restoring the "concrete" back into the APnnnnnn.bgl file, the bumps are gone. When I then re-activate the gravel runwayed Afcad (or ADE) file, the bumps are back. I'm now convinced that concrete and/or asphalt runway textures remain the only non-bumpy ones, independant of where they come from. Sigh !! Regards and thanks for your reaction. Hans

Sounds good Tim. I'll give it a go tomorrow and will report back on the results. Hans

Hi Guys, I'm in the process of giving many of my small tropical airfields the real steamy tropical feel and look, mostly via the Abacus EZ object placement program. Works great and the obviously not so accurate looking airfields, are now beginning to look very steamy indeed with their surrounding tropical forests, tropical buildings, etc. but the dirt taxiways and gravel runways remain very bumpy, so much so that especially the takeoffs, are extremely hazardous, with my plane bouncing around all over the place and difficult to control. I've searched for and have read most of the older forum posts on this subject but as yet nobody seems to have come up with a real solution, other than changing all the Afcad taxi- and runways to, e.g the very unrealistic but hard concrete, asphalt, etc. I've understood that the dirt and gravel taxiways/runways, drawn via the Afcad program and directly on top of the default concrete/asphalt runways, are somehow structurally soft and will therefore always remain bumpy. Very strange indeed because, e.g. my Afcad gravel runway textures, are drawn directly on top of the "hard" underlying default textures. Has anybody ever found a better solution ? Regards Hans

Thanks guys, problem solved. As you pointed out the solution came from the instructions in my autower.ini file, a place I would never have thought of looking into myself. Strange though because I've been using this autower module for many years and without any problems whatsoever. Anyway guys, thanks again. Hans

Hi Guys, Whenever I begin a flight anywhere in the world, a green band appears across the top of my screen with the name of the airport/airfield and it's ICAO code. This band also appears whenever I fly near or across any other airports/airfields along the route to my destination. How can I get rid of this ever more irritating and unrealistic green band ? Regards Hans

When you have used an installer (.exe) program to install your aircraft you cannot just delete any of the thus created files/folders but you must then always un-install them, preferably via the Windows un-install process or via the (usually) supplied un-installer, provided that you have not moved any of the files or folders before actually doing that. By just deleting any of those created files/folders you are in fact just asking for all kinds of unpredictable problems. I believe that the best thing you can now try to do is to un-install your evidently re-installed aircraft and hopefully in doing so, will automatically clear any of the now problematic registry entries. After that you could try to re-install the aircraft, after shutting down your machine, completely switching it off, waiting a few minutes and then switching it on again. Good luck. Hans P.S. Why did you "delete" the aircraft in the first place ?

Myrone, I would like to add my little bit to Tim's reaction in advising that you should in general never use flyable aircraft as AI because their external textures are far too large, too many, too detailed and always unmipped, giving your graphics system a hard time in trying to render them every time such "AI" aircraft come into view. Stuttering and frame rate loss is almost always the result and is especially true when you have more of these "AIs" flying or taxiing around your flyable aircraft. Hans

I've experienced this problem as well in my Win7 setup. Turned out to be caused by the FS9.cfg file unexpectedly being re-created. Why or how, I have no idea but a copy/paste from the backup solved the problem ...... untill the next time. Hans

Neil, This double startup process was certainly negatively effecting my FS9 and I can now clearly see this after Tim's registry edit and my very first Win7/FS9 restart. My frame rates have increased, there's less stuttering and the (first time) startup is noticeably faster than I had become used to. Just one nagging question remains though and that is, although the problematic (pre-FS9 startup) internet access is now structurally being blocked, what sly process could possibly be trying to access the internet and for what purpose ? I'm directing this question towards any Win7/FS9 and structurally internet connected simmer, who might have some experience on this very specific question. Regards Hans

Napamule2, You are absolutely correct in that FS9 should never be installed in it's default folder because that will cause a multitude of unpredictable problems at unpredictable moments. The reason is that a strongly dynamic system like FS9, will then constantly be scrutinized for (normal) internal behavior but which Windows sees as "attacks" on it's security. I therefore learnt many years ago that it's of paramount importance that FS9 always be installed in any partition OTHER than the one in which Windows itself lives. In my setup I even have a completely separate physical SSD which remains solely reserved for my FS9 and all it's supporting software, e.g. Afcad, ADE, S-Builder, EZ-Object placement, etc. etc. It's my main FS9 folder only which is a bare 129 Gb in size, "bare" meaning that it has been stripped of all unnessesary "ballast". Sorry for my inacuracy. Hans

Tim, you're my hero !! Removing the registry entry and another very similar one further down, certainly did the trick but only after I had backed up just about everything I could find and making several restore points. Messing with the registry and running the risk that my system no longer boots, is normally not something I enjoy doing and this was most certainly a first for me. Thanks very much for your help and I learned a lot from it. Hans

Thanks for your suggestions Tim. I disabled my Windows Defender but sadly this didn't help in any way. Scans via the "MS Security Essentials" system did not find anything either nor did Malwarebytes scans. After even more extensive Google searches, it now turns out that there are a number of 6/7 year old forum threads on exactly this subject but, and as far as I can make out, no real solutions were found. The only problem solving exception was evidently to connect to the internet, as experienced by one of the posters. However, because the problem only manifested itself a number of years after Win7 was first introduced, this seems to be a rather dangerous solution because under such circumstances, you never know which possibly "shady" sites will be visited without you knowing about it and for what purpose(s). Moreover, I expect that the problem will immediatly be back as soon as the internet is then disconnected again. It also seems and I repeat the word "seems", that the problem or even the possible Win7 bug, has since then been solved, possibly via a MS update, because new posts on the subject quite suddenly ceased. Could my "host" rundll32.exe file somehow have become corrupted so that it opens an unwanted process even before my FS9 initially starts up ? I'm stumped on this one but for safety reasons prefer to remain disconnected from the internet. Ideas, anyone. Hans