Jump to content

SpeedbirdCanada

Members
  • Content Count

    17
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by SpeedbirdCanada

  1. Thanks for the suggestion Hans. I disabled all scenery except for the Default Terrain, Default Scenery and the Continents. No effect. This is leading me to believe, a file(s) has been overwritten in the default scenery that is causing this anomaly. Might just have to live with it as my sim looks fantastic and hate to resort to a fresh install. I was hoping someone may have some more technical ideas to determine how this is possible (for example, what type of files can override or exclude these polygons on a large scale?) I will play with those settings Jerry but, I do like what they do for my sims appearance with all my mods. Appreciate all the suggestions people. Many thanks.
  2. So I've located a small set of VTPP files from the "Forgotten Airports" package (by Bastian Blinten) found on Flightsim.com that when active, somehow allows autogen to spew across all default airports worldwide. When I remove the files Abidjan_VTPP Bissau_VTPP Cotonou_VTPP Freetwon_VTPP Manzini_VTPP Nouakchott_VTPP, all the default airports now have autogen excluded from appearing on runways and aprons. So I got that going for me but, I still don't visually see that background grass around the default airports (ie city streets, farms, etc are still rendering under the runways just no autogen. Weird.
  3. Not sure I used those..... Investigating.... I have discovered that after disabling ALL addon folders the autogen problem seemed to have disappeared but visually the polygon for the airport backgrounds still don't show (underlining city polygon beneath a nearby airport etc) But it is helpful. Will investigate further. If so, I'll have to figure out how to remove them.
  4. I am at my wits end for diagnosing this anomaly. So I have a question: Is there an enhancement addon released in the last few years that may affect the display/effect of the ABxxxxxx.bgl files (Airport Background) to the extent that the polygons no longer display AND autogen scenery is now all over the aprons and runways? I've been coping with the issue for a while (creating new polygons and exclude files with SBuilder as I encouter them) however, recently I experimented an bounced around the entire globe to various default airports and can see that it is a global problem. I've searched the default scenery folders to confirm that all the AB files are present for the affected airports and through SBuilder can confirm that all the polygons are layered at "7" (for airport background/autogen exclude). Furthermore, I have scanned the terrain.cfg files and all Airport background textures are flagged "autogen exclude =1" which according to documentation is correct. I'm sure I installed something (which may make it impossible to track down) that has configured FS scenery to somehow "hide" this airport background polygons (thus creating autogen trees and buildings on top) but, I'm hoping for some suggestions as to hunting down the issue..... What can cause this? Just recently I have disabled the world texture folder (so autogen is gone), I've disabled various addon scenery folders but before I go through all 1400+ entries, I was hoping someone may have experienced and fixed or my have an inkling as to what type of file/addon/freeware/payware that may be able to essentially disable all the AP background polygons from rendering without deleting or editing the original BGLs. I'm assuming an exclude of some kind but, for all of them? A search on google has turned up only a couple instances reported by others but nothing resolved nor does it seem very likely it is a common issue (only response indicated a landclass file but, worldwide?) If someone out there has experienced this and/or can recall what addon caused this please post. Any other suggestions are very welcome. Thanks
  5. Agreed. Just to add to the mystery. Rather than exit as planned I decided to fly one more leg. Switched from the A320 to the A319 (same SMS Overland brand so even same panel) and voila - the A319 RAAS profile is active and working. I'll just make do. RAAS isnt the most vital immersive product necessary to fly but, it worked beautifully and runs perfectly when it is on. Just hoping to find a workaround since re-loading the sim takes about 15+ minutes (lots of aircraft and scenery haha)
  6. I suppose it would not be accurate to claim it only happened recently. This is the first time in years I've noticed it not working with an aircraft I know is configured with an active profile. Since however I do know I have not made any changes to FS to my knowledge. Windows 10 updates, video driver updates are among activity. Livery installations and panel editing would be the extent of my FS dabbling. Occasional scenery installations (freeware basic stuff). Makerwys works flawlessly to add the airports to RAAS. After I finish this leg (SriLankan flight from VCBI-VECC A320) I will shutdown FS and restart and begin noting all the activity that leads to the next failure of RAAS. It seems to work perfectly for the 1st aircraft for sure. I'll run tests. So this is what is in the RAAS.ini file: [RAASPRO] SceneryID= DEFAULTProfile=GA FS9SceneryID=0 NoAutoUpdatesCheck=0 AudioOutputDevice=0 EnableKeyEventAPI=0 Look normal? The default profile is a GA (General) that I use for aircraft without RAAS capability so all features are unchecked. Thanks Scott
  7. Tried with API off.... no effect. Additionally if I open RAAS menu and make absolutely no changes; click on the close "x" button it always asks if I want to save changes.... Not sure if that is by default or if that is a clue.
  8. After reading the manual and perusing the support forum for solutions I feel I should post this issue as it has only RECENTLY become a factor (within the last month). While flying around in various aircraft I've noticed occasionally RAAS will shut itself off and then I cannot re-activate it without restarting FS9 completely. The latest occurence was related to switching from one A320 model (Project Airbus) to another A320 model (SMS Overland). I also noticed this occuring from switching from the SMS A320 to a Project Opensky 747-200F .... It's really odd. The menu shows the on/off button in the OFF position. When I select ON and click save/exit everything looks normal. If I re-open RAAS menu the button is OFF again. I can't save new profiles, switch profiles either. It's like the program has become locked (OFF) ... If I exit FS9 and restart RAAS seems fine again. I cannot lock down any consistencies other than possibly a conflict with the SMS Overland A320 model (how would this be possible?) Does RAAS interact with gauges from the panels that could cause a conflict? Long time user of RAAS Pro Unlocked and never had this occur before. I also tried (for 1st time) activating the API thing with no effect. Switching aircraft has no effect on RAAS as it still wont turn on. A restart is the only solution at this point. ANY SUGGESTIONS? IDEAS? INSIGHT? Many thanks. Ryan Scott Clifford Windows 10 Pro MS Flight Simulator 9.1 16Gb RAM AMD-FX-6100 Processor NVIDIA GeForce GTX 650 Ti
×
×
  • Create New...