I>tick only 2 things-Auto-Coordination and timeof day (dusk). In FlightGear, res is minimum>(640x480- it reduces the lag time, but doesnt eliminate it). >Man, my computer runs google earth pretty fast, I can play>quake 3, HL1, and even NFS High Stakes well and good. Newayz, has anybody seen the x-15 plane and its bugs? There is one trouble-i dunno any sort of coding (except html), and i wanna make landmarks for flightgear, and possibly planes too (how about a x-wing and tie-fighter, guys? a space shuttle would do well too!) Some are still missing (do they think that India is still in the colonial days?-wake up!)->taj mahal (agra)>india gate (delhi)>gateway of india (mumbai)>qutab minar (delhi)Planes->The 2 Antonovs>f22>c-5 galaxia>a space shuttle>learjet>geebee racerthere are millions more, dude! In the features-Splash screen, intro music,mouse pointer,panel, sound, hud, hud 3d, and auto coordination are ticked.In rendering- clouds, sky blend and tetures are enabled. I tick only 2 things-Auto-Coordination and timeof day (dusk). In FlightGear, res is minimum (640x480- it reduces the lag time, but doesnt eliminate it). Man, my computer runs google earth pretty fast, I can play quake 3, HL1, and even NFS High Stakes well and good. You may be able to get an impression of the usually required data by checking out some of the recent threads. But again, we cannot provide much help if you do not provide relevant information such as the aforementioned items. Thus, even if you had a fully OpenGL (preferably NVIDIA/ATI) capable hardware accelerator board with dedicated 256MB RAM, it would still be possible to start FlightGear with ridiculous startup settings, so that even a decent system would no longer be able to provide decent performance for such settings. your startup settings (resolution,airport,aircraft,scenery complexity (3D clouds/shadows?), AI scenarios etc.) All of these things may have a varying degree of impact on the overall performance. As of now there is still plenty of information lacking, i.e. Apart from that you need to realize that there is a variety of possible reasons for the behaviour you are experiencing, many of which can only be ruled out if you provide complete data for your system and FlightGear itself properly. So you may first want to make sure that other OpenGL apps work properly for your system, before looking into FlightGear specifically. However, on the other hand you do not even have all that much RAM in the first place, 256MB can probably be considered to be the minimum amount of RAM recommended for use with FlightGear. So you may first want to really make sure that your mainboard's OpenGL chipset has full OpenGL support and what sort/amount of RAM it has, then it would be crucial to make sure your drivers actually make use of your hardware's capabilities.Also, you MAY be able to get some more performance out of it by using some more RAM for your 3D chipset (from your main RAM). Butthe ame runs too slow and goes all>block-block-block.(I dunno y-Intel P4 1.72 Ghz, 256 MB RAM,>onboard 3d accelerator-whats the matter?)Probably, it's your ON BOARD 3D accelerator, only rarely are these on board chipsets fully OpenGL capable (or manufacturers do not provide proper drivers), often they do not have their own RAM either, rather they use shared memory from the main RAM. I'm>currently downloading scenery 4 India, so I practice on my>take-offs. >Hmmm.I like to roam the kies in my f16 or x-15 (its got sum>bug-appears red in the selection menu) or my a10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |