Can anyone recommend me a basic joystick that will work with X-Plane and Macs? Also, would X-Plane run better on a 2.0GHz G5 iMac (rev. B) with 512 RAM, or a 2.0GHz C2D MacBook with 1.0GB RAM?
Thanks!
That's a tough one.
The iMac with it's 128MB ATI X600 XT has a faster video card than the MacBook's 64MB Intel GMA 950 GPU.
X-Plane is CPU intensive as well as GPU intensive.
That 1GB of memory in the MacBook will work much better than the 512MB of memory in the iMac.
The 2-cores of the MacBook will probably help it run X-Plane better also.
Consider that I run X-Plane frequently...If it were me, I'd take the iMac but I would want to put 2 to 4GB of memory inside same.
Joystick? I use Saitek but I don't think the joystick I use is made any longer.
And you should take note of the many ways of getting higher frame rates with what you've got.
For example, the following effect X-Plane's frame rate:
* Visibility (in Settings -> Weather Atmosphere). The farther you can see, the more terrain and stuff X-Plane needs to render.
* Field of view (in Settings -> Rendering Options). Same deal: a wider field of view lets you see more and makes X-Plane do more work.
* Clouds (in Settings -> Weather Atmosphere). The scattered and broken clouds in V6 have a modest frame rate cost. The V7+ 3D clouds (what you get with scattered or broken clouds) are build up out of a great many texture objects and cause a major frame rate hit.
* Cloud shadows and reflections (V7+) have a substantial frame rate cost.
* Textured lights have a modest frame rate cost.
* Resolution (in Settings -> Rendering Options). Higher resolution means more data for your graphics card to handle for each frame. This covers both screen size and texture detail. Note higher resolution also requires more VRAM in your graphics card. When you're close to running out of VRAM there is an abrupt drop in frame rate, typically going to zero in short order.
* Objects (in Settings -> Rendering Options). All the scenery and eye candy goodies cost frame rate. This means trees, air traffic, objects, plane exterior, and forest fires. Autogen and object density and visibility distance translate directly into rendering load.
* Instrument panel. The glass cockpit instruments, especially the EFIS map, cost frame rate.
* 3D panels substantially increase the graphics load and consume more VRAM. because of implementation issues they cause an especially bad hit if you're running in 16 bit mode.
* Same goes for externally visible cockpit objects.
* Location. For better frame rate, stay away from areas with lots of buildings and complex airports. LAX is a good example.