ohanmer

I would just like to pubicly thank Brian for all his excellent support via email. Problem has now been resolved (needed to install FS2Crew into the root folder for FS9, ensure the latest NET Framework was installed and setting the Speech Recognition to English). He really sets the standard that others should emulate.One very satisfied customer.Cheers Brian and keep up the great work.All the bestOwen

Hi folksJust purchased FS2Crew for the Maddog and I'm afraid I am stuck already.Running FS9.1 on Win XP 32bit Home Edition. First time I installed, FS2Crew incured the FS registry problem, Ran the Registry Repair Tool, reinstalled FS2Crew and SP1. When I click on the blue desktop icon, the initial screen opens (with the options to start FS9, FSX, Restore Original Mad Dog Panel CFGs etc). If I click FS9 Registry Integrity Test button, I get "FS9 Installation Folder found on Local Machine". I've run the Maddog Manager & Setup, unchecked "Enable first officer calls" and clicked OK....however, I do not get a promt to select "COLD and DARK" for the Panel State as indicated in your Readme First PDF. I have checked my Panels folder for the Maddog, and panel.novc.fs2crew_backup and panel.vc.fs2crew_backup are both present. If I open panel.cfg, I seem to have all the necessary FS2Crew entries (see selection below):[Window Titles]window00=Systems - Never close!window01=Left Main Panelwindow02=Right Main Panelwindow03=Pedestal Panelwindow04=Overhead Panelwindow05=Startup Overhead Panelwindow06=AFT Overhead Panelwindow07=FMSwindow08=Left Light Panelwindow09=Right Light Panelwindow10=Speed chartwindow11=Ground/Crew Communicationwindow12=Flight Documentswindow13=PFD & ND zoomWindow14=FS2Crew Main PanelWindow15=FS2Crew Configuration Panel...[Window14]size_mm=681, 57pixel_size=681, 57position=3visible=0ident=1000zorder=100gauge00=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_MainPanel, 0,0,681,57gauge01=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_VoiceMain, 10,10,5,5gauge02=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_Audio, 20,20,5,5gauge03=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_Input, 30,30,5,5[Window15]size_mm=866, 248pixel_size=866, 248position=4visible=0ident=1001zorder=101gauge00=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_AudioSetup, 0,0,866,62gauge01=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_PreFlight, 0,62,866,62gauge02=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_Pushback, 0,124,866,62gauge03=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_FlightData, 0,186,866,62...gauge31=FS2Crew2010\Versions\MadDog\Gauges\FS2CrewMadDog!FS2Crew_Icon, 5,31,285,221When I start FS9 with default Cessna, then change to the Maddog, it loads fine with no errors reported from FS2Crew. However, everytime I click the Captain's Primary Flight Display, I get nothing with the left click of the mouse and right clicking it simply brings up the traditional right click mini menu (ie options to close this window etc). Same applies in VC and it doesn't make any difference if I change livery models or airport.So now I am completely stuck and would greatly appreciate any help you good people might be able to provide.Thanks in anticipationOwen

Thanks for all your help guys.Clum...you are right about the level of buildings...they do seem about the same...it's the base textures that seem to be completely missing in my setup compared to your screen grab. So now maybe worth looking in that direction for an answer....Gus...Thanks for the link...a few more interesting parameters that I wasn't even aware of...so I will have a tweak and see if that does anything.Alex...although I removed UT after the problem occured...you still might be onto to something. So I will have a go at re-installing UT and see what happens.Oh well...If at first you don't succeed etc etc.....Onwards and upwards.Will keep you posted.Cheers everyoneOwen

Hi ClumTried with the AUTO_LOD set both ways with no joy I'm afraid (it was already set to 0). I'm intrigued by your observation that you think my screen shots look normal. Have I been missing something for the four years that I have been using FS9?...I certainly cannot remember such a barren wasteland as depicted in my first image (Problems with Autogen) viewing downtown New York from KJFK (and this is repeated for so many other 'urban' areas). I would be really interested to make a comparison with screen shots from other users (just slew up to around 1300ft above KJFK and point the aircraft at the Manhattan skyline). And remember, as stated in my original post, I have removed UT USA completely, so that isn't an issue any more. Really appreciate your input and ideas. All the bestOwen

Hi JoshYes, I do have nHancer installed. Settings are as follows:AA Combined 8xSEnhanced in game settings - OFFGamma Correction - ONTransparency - MULTIAnisotropic Filtering - APPLICATIONVert Sync - ONTexture Filtering - HIGH QUALITYTrilenear - OFFNegative LOD Bias - CLAMPClum...where would I find AUTO-LOD?Thanks again for your inputs guys.Owen

Hi JoshThanks for the suggestion. I tried your settings but, unfortunately, I've still got the same problem. I don't know enough about how autogen buildings are created but I'm wondering if there are different BGL files for bringing up autogen buildings at different ranges and somehow the one drawing out buildings beyond the 1nm range has been corrupted or overwritten (probably talking out of the back of my head). As I have said already, the autogen is there, but only when I get within close range. Any more suggestions would be really appreciated.All the bestOwen

Hi LuisThanks for responding so quickly. I have already created a fresh FS9.CFG file, but unfortunately that did not cure the problem (please see the link to my original post above for all the things I have tried so far). My [TERRAIN] settings in the FS9.CFG are as follows:[TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=19TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=3.500000TERRAIN_EXTENDED_RADIUS=3.500000TERRAIN_EXTENDED_LEVELS=4Any suggestions gratefully received.CheersOwen

Hi folksI posted a request for help early in January (Problems with Autogen) but have had little response so far (many thanks to those that did). Sorry to ressurect this problem, but if I cannot get it fixed I will have to re-install FS9 (again) which I am loathe to do.In essence, it seems like my autogen is only appearing at very short range (approximately 1nm). Other scenery objects (landmark buildings such as New York, airport scenery addons and custom-built scenery objects) seem to appear at normal distances, just the generic buildings etc are missing beyond this short-range perimeter. All the autogen is there, because it will eventually appear when I get close enough. Am I missing a setting that controls this autogen drawing distance? Could a stray .BGL cause this to happen? All my machine specs, configuration settings and some example images can be found on the original posting Problems with Autogen as well as some of the steps that I have taken so far.If anyone can help, I would be very grateful.Thanks in anticipation.Owen

Thanks for the few suggestions made so far guys...unfortunately the problem still persists.The key thing is that all the scenery objects are there (autogen buildings, landmark city buildings, add-on airport scenery and custom objects created with EZ-Scenery) and eventually they all come into view. It's just the Autogen objects that don't appear until they are within approx 1nm distance from my viewpoint. All other objects appear according to their inherent sight range. Surely there is a setting that controls the maximum range for autogen to start appearing (but I certainly can't find it). Really could do with some more help here please......CheersOwen

Many thanks for the additional suggestions guys. Tried them all...unfortunately with no success. I would be really grateful for any other input as I am completely stumped!CheersOwen

Thanks for the quick response Mel.Tried your suggested amendments for the FS9.cfg - unfortunately still no improvement. I have been using UT for years (I only removed it as a last resort in trying to eliminate the source of the problem).Does anyone else out there have any ideas to help me on this one? (Opa....where are you in my time or need?)CheersOwen

Hi folksI wonder if any of you scenery gurus can shed some light on a recent problem I have encoutered with my autogen.I have recently re-installed FS9.1 and everything seemed to be fine after adding Genesis Mesh, Ground Environment (not Pro), Flight Environment, UT USA, various add-on aircraft, add-on sceneries and a whole host of WOAI and MAIW AI aircraft. Suddenly became aware that my Autogen was only drawing out detailed buildings at very short range (please see accompanying series of five pictures taken at KJFK). Browsed through related topics on this forum and I have tried the following remedies so far:1) Reinstalled an original default.xml file into the Autogen Folder2) Deselected all my add-on sceneries using the FS Library manager (made no difference)3) Removed UT USA plus the Sandwich fix for using Genesis US Landclass4) Copied over contents of original Sceneries and Texture folders for Scenery\World, Scenery\Base\, Scenery Generic\, Scenery Cities and Scenery Name5) Deleted all the Scenery.Dat files in all the folders in FS9\Scenery and allowed FS9 to regenerate new ones6) Loaded FS9 with the original FS9.cfgNow I've completely run out of ideas.System spec is as follows:Athlon 64 38000+ processor, nForce A939 MOBO, 2GB DDR RAM, nVidia 7600GS (256Mb) graphics cardFS9 Display Sliders as follows:SCENERY - All maxed except Water Effects set to LowWEATHER - Sight Distance 60m, Cloud Draw Distance 40m, 3D Cloud Percentage 100%, Cloud Coverage Density MAXHARDWARE - Target Frame Rate 30, Render to Texture ON, Transform & Lighting ON, AA OFF, Filtering TRILINEAR, MIP Mapping Quality 4, H/ware Rendered Lights 8, Global Max Texture Size MASSIVE Relevant settings in FS9.cfg as follows:[DISPLAY.Device.NVIDIA GeForce 7600 GS .0]Mode=1280x1024x32TriLinear=1[DISPLAY]UPPER_FRAMERATE_LIMIT=30TEXTURE_BANDWIDTH_MULT=600TextureMaxLoad=6[TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=19TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=3.500000TERRAIN_EXTENDED_RADIUS=3.500000TERRAIN_EXTENDED_LEVELS=4[sCENERY]IMAGE_COMPLEXITY=5DYNAMIC_SCENERY=1DYN_SCN_DENSITY=5DAWN_DUSK_SMOOTHING=1SUNGLARE=1LENSFLARE=1nHancer settings for video card as follows:AA Combined 8xSEnhanced in game settings - OFFGamma Correction - ONTransparency - MULTIAnisotropic Filtering - APPLICATIONVert Sync - ONTexture Filtering - HIGH QUALITYTrilenear - OFFNegative LOD Bias - CLAMPNow I'm completely stuck! Any guidance or assistance would be gratefully received.Thanks in anticipationOwen

Oops! Sorry about that! Senior moment!!Oscar

Hi DaveHaven't visited the forum for a while. Recently been getting into helicopters with FS9. Purchased the Nemeth Design Sikorsky S-76A and I thought, wouldn't it be great to operate this wonderful bird multi-crew with FDC (I'm a fan and have used it really successfully with the Aeroworx B200 and the DF 727). Oooops...no flaps! Just as I was about to put your great product on the shelf to gather dust, I decided to try the following:I copied the following section from the default 172 aircraft.cfg file to my S-76 aircraft.cfg file and created a new performance file in FDC for the S-76 specifying one flap position. [flaps.0] //Trailing Edge Flapstype = 1 // 1 - tail, 2 - leadspan-outboard = 0.5 // 0.0 .. 1.0extending-time = 7 // secondsflaps-position.0 = 0 // degreesflaps-position.1 = 12.7 // degreesdamaging-speed = 120 // KIASblowout-speed = 150 // KIASlift_scalar = 1.0 drag_scalar = 1.0pitch_scalar= 1.0system_type = 0 //0=Electric, 1=Hydraulic, 2=Pneumatic, 3=Manual, 4=NoneI now have FDC running with the Sikorsky. Admittedly, I have to be a bit creative with some of the checklist calls (no collective, no cyclic, no hover thrust etc), but it seems to be working fine. One very happy helo aviator now that I can keep using one of my favourite add-ons.Just thought I would let you know.Keep up the good work Dave.Best regards.Oscar

I think your problem is Ultimate Terrain. If you have residential roads turned on, FS9 will not be able to place any autogen objects where these (numerous) roads are placed. Likewise, if you have enhanced lighting turned on, autogen objects cannot be placed where these lights are placed, even during the day when you cannot see the lights themselves. If you read the UT manual, they do raise this problem and therefore recommend that you leave residential roads off and only opt for Enhanced Lights (Except for Residential). This is the best compromise unless you know that you are going to be doing most of your flying at night. I hope this helps. Oscar