Quote:Well, after all the build up and the hassle setting it up, if this is the quality of the genuine software it won't be for me. Not with this rig anyway.
You've seen the quality of my screenies in FS9 and there's no way I'd pay money to get the level of visual quality I've obtained in this sampler. There's no comparison for me. Loads of AA jaggies, blurry textures and water that looks great close up (on max setting only) but plain weird from certain angles on lower settings. Maxing everything last night even crashed my system and this morning I had to turn down the AA on my card.
And even with many sliders lowered quite a bit, a FR in spot view of 2 - 6 just ain't on, not when I get 18 with a target of 18 even with thick cloud in FS9.
So there you go. I haven't tried any of the gamer-gimmics (ie missions in the sampler) - just free flight. I thought the VCs were superb, what I saw of them, but if I can't look outside at all of the graphics features that FSX is all about (land, water, autogen, traffic) what's the point of it?
BTW I didn't have SP2 installed on my freshly installed hard drive but installing it didn't affect my FS2004 FR I'm surprised to say.
So it's an initial thumbs-down from me I'm afraid. And as I can't see me EVER paying for a £300 graphics card I don't see me moving up from FS2004 unless something changes. But then again, that's what I said with FS2002 so have to wait and see. I'll let others do the 'pioneering' - I can see these forums being HEAVING with people complaining about FR and graphics and asking how to get better results. It'll make the change-up to FS2004 look like a pic-nic in comparison, just mark my words
My spec:
AMD 64 3000+ (not o/clocked)
1.0 GB DDR 400 RAM
nVidia GForce 6800LE AGP with unmasking (Rivatuner)
150GB Maxtor ATA 7200RPM h/drive
XP Pro SP2
Looks like someone else who did not read the "README" file.
Introduction
Thank you for trying the Microsoft Flight Simulator X demo. The Flight Simulator X demo version is pre-release software. These Release Notes outline the features of Flight Simulator X. It also discusses known issues and incomplete features.
Major Known Issues
At the time we created this demo version, Microsoft Flight Simulator X was not yet complete and work is ongoing.
Setup
The Flight Simulator X demo version is not compatible with the Flight Simulator X beta versions.
Aircraft
Some aircraft in Flight Simulator X demo may not be finished.
Some of the incomplete items, such as untextured aircraft models and animations that don’t work, are obvious and will be implemented before the product ships.
You may also notice that the “level of detail”, or LOD models are not completed—as an aircraft moves away from you, it will abruptly swap to a low-detail model.
Scenery
Taxiway and apron textures will sometimes exhibit regular patterns of mismatched textures, especially at the intersections of different surface types. Taxiway fillets may appear with texturing different from that of the intersecting surfaces.
Airport boundary fences currently block out views of terrain and buildings behind them.
Autogen content (generic bridges, buildings, trees, etc.) and placement are still in progress.
Autogen exclusion is currently not working properly, so you may see trees and buildings appearing on airport polygons.
Some scenery objects in this pre-release demo version are not complete and may display as black or incomplete shapes. This will be corrected in the final product.
Configuration
The retail version of Flight Simulator X runs on Korean, Japanese, and traditional Chinese Microsoft Windows operating systems. This demonstration version of Flight Simulator X will not run on Korean, Chinese, or Japanese versions of Windows.
After changing time of day or location in the simulation, terrain textures occasionally won’t update, or some textures will change to black or bright colors. To resolve the issue, restart a flight. Cycling views will also occasionally resolve this problem (press S).
Anti-aliasing is not working on RADEON X300/X550 series cards.
Anti-aliasing does not work for the Free-Flight aircraft preview window for any configuration.
Windows in Virtual Cockpit mode may not be transparent in video cards that only support shader 1.1.
CH throttle quadrant's range of motion is currently limited.
If you are using an Xbox 360 controller for Windows with Flight Simulator, make sure you plug it in before starting. Plugging an Xbox controller in while Flight Simulator is running may cause problems with control assignments.
Flight Simulator will not render in windowed mode with Windows Vista Aero/Glass enabled. Disable this feature in order to use windowed mode on Vista.
Bloom effects are not functioning.
TOSHIBA: TECRA M4 users may experience a blue screen when altering screen resolutions.
Shader Model 3.0 card users (GeForce 6100 and ATI Radeon X1300) should update their drivers to see self-shadowing.
The setup repair function is not working properly. If you have problems with your installation, please uninstall and reinstall Flight Simulator.