Jump to content

flynman33

Members
  • Content Count

    304
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by flynman33


  1. Randy,Is your default flight a saved flight or the out-of-the-box default (C172@KSEA)?If it is a saved flight, look in your FS9.cfg for...Situation= and delete everything on that line after the = sign.Then try to start FS9.regards,Joe
    I'm afraid that didn't work.....Randy

  2. You've presented a very open ended question.What's your budget? How likely are you to use FSX on this new computer? What are your flying styles? Any significant addons that you are using or wish to use? What are your preferences - framerate speed, image quality, or both?Most modern computers with a half-decent graphics adapter will run W7 and FS9 with zero problems. If you have the budget for an i7-class machine, you will be in absolutely fine shape for FS9. Stay away from the true cheap-o budget computers and processors, and stay in Core2Duo and i5/i7 class of Intel machines - FS9 will appreciate it. Obviously, the faster the computer, the better it will run FSX too. I run it on my system (specs below) with no qualms or concerns. -Greg
    I will build it my self....$500 to $800.....I already have dvd roms,case,monitorI run PMDG panels Just Flight 777 and Wilco E170 and third party scenerys from Blue Print,Fly Tampa and Imagine Sim.Thanks

  3. It would be nice to see some nice paywares of the following airports.STL......SLC....RNO.....STL....LIT.....SMF.....GEG......CHS......CRW.......BGR.......PWM.......BDL.........BTV........PANC.....BUF.....ALB...And perhaps a better frame rate DEN....the Imaginesim package eats up my system like a kid and ice cream in the summer.Can you think of more.


  4. Last night I loaded up a demo of Abacus EZ Scenery and after that loaded up a small airfield around the Seattle area to see if the demo worked good enough for me...well while loading it up after the field got to 19% terrain it stopped and a few seconds later I got an error stating that it was the Terrain.dll that caused the error so I tried another field and got the same thing. Iuninstalled ez scenery and tried it again and the same thing happened again.....the strange thing is this is only happening to areas from SFO North to YVR and BOI to the W-coast all other fields work fine...I have tried recycling the fs9.cfg and swaped out the Terrain.dll file as well with no positive results and looked through the files to see if any EZ files were still in there......Any clues or ideas..ThanksRandy

×
×
  • Create New...