I'd look at your setup carefully. I'm not seeing any of that on a 1.83 GHz Pentium M, 1GB mem, 64 MB ATI X300 mobility graphics. Look for background programs and stuff like that. You should have much better performance.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

>So you and the others here mentioning a decrease in FPS are>just seeing the effects of CPU cycles that used to go to FPS>now going to texture rendering. This also explains why people>are saying the blurries are much better with demo2 compared to>demo1.>>BruceThanks Bruce...that DOES seem to be the case. The blurries are better. However, after cutting back on some sliders I was able to get all of my FPS back, and then some! (See my Post # 105) I am almost ecstatic that I can run Demo 2 so well on this old machine. I will now be able to enjoy FSX and the missions and wait til later to build a new machine. I was almost certain I was going to have to spend a fair amount on hardware just to get started.

>Haven't tried the CRJ yet, but the Learjet definitely has the>glass reflections, and they look oh so sweet!>>The reflections in general look light-years ahead of what's in>FS9, especially from the metallic surfaces.>>The light bloom effect combined with the self-shadowing is>also incredible, and really adds another dimension to the look>of the sim.>>I did however find some strange graphic clitches such as the>ground shadow occassionally flashing red and also being able>to see the nav lights etc through the aircraft.>>JamesThx, James.What I meant, though, was the cockpit glass when viewed from the outside (sorry, I should have been more clear).I just dl'd and tried both and niether have the outside-cockpit glass reflections. The CRJ had them in the first demo, and they looked GREAT. Now thye have seemingly been removed. Check out how the outside-cockpit glass looks on the R-22 and the Barn to get a better idea of what I mean. It looks GREAT when it is done right. IMO, it adds that little extra touch of realism to the models. It looks sort of wack when a model has no outside-cockpit glass reflections. It sort of looks like the pilot are sitting in a cockpit with no windshield. lol I hope I can add the CRJs glass textures so they are back to how they were in the first demo, and add some glass textures to the Lear. On a side note, the self-shadowing looks great! I only wish the bloom and fsaa worked together. :(I noticed how I seem to be having issues with FSAA in the demo no matter what settings I use.

I think that this post would be quite usefull as the template for all the folks that will start posting when they get their hands on the release version of FSX. It's in text and covers every specific that I can see so that folks can see exact settings when trying to compare apples to apples. The only things I would change is instead of putting the phrase "latest drivers" I would suggest that one put the exact driver version. One other thing would be to use a specific airport eg: Seattle for recording the informaton. Lastly a high and low framerate using a specific aircraft flying a specific heading from takeoff to perhaps 5000 ft. A good post; something that was specific and measurable. I'm copying and pasting this to Word for future use. Craig

What's up with that beacon relection on the engine of the R22? Seems the flash on the engine is a half second after the beacon flash on the tailboom. Is that an artifact of recording the video or is that how it's shown realtime in the sim?

Tried it first with nvidia control panel and then with it checked. Seemed not to make much of a difference perfomance wise.Ian.

I have now found that Demo 2 does not in fact have the FIBER_FRAME_TIME_FRACTION=0.33 setting by default, and that changing this setting has no perceptible effect on frame rates or dynamic blurred textures. In addition, after more testing, I have come to the conclusion that the blurries are no better compared to Demo 1. This is a key feature revealed by the team many weeks ago. As this feature does not appear to be implemented then it does tend to suggest that Demo 2 does not represent the final release build. It would be great if one of the Microsoft team could comment on this. Demo 2 was still worth releasing because it does contain many fixes for outstanding problems.The other possibility is that this feature has been dropped, in which case the blurries will be no better in the final release. I certainly hope that's not the case.But, anyway, we'll know for sure in another couple of weeks!Best regards, Chris

Howard, I did some more tests last night and it confirms what you found. Even with the value set to 0.95 there was no perceptible change in the blurries or frame rates (I used four standard benchmark views for reasonable consistency). I also ran Demo 1 for about half an hour for a better comparison. I now feel that the blurries are about the same in both demos. However, my benchmark tests indicated that Demo 2 does in fact run a bit faster (my initial impressions were the opposite).I spotted one nice improvement in Demo 2. It now has waves breaking on the shore (standard in FS9 but not in Demo 1). And it gets better. Sometimes similar breaking waves can be seen out in deep water away from the beaches. That's a nice touch. That's with one of the lowest water settings.Overall, despite the blurries, my impressions of the second demo are very positive. I have a sneaking feeling that we'll see yet more improvements in the final release. After all, tdragger did say they were leaving the best to the last! Best regards, Chris

Some people are still clinging onto DX10!?!?!? :-lolUhhh ... here's a quote from Tdragger:".... the issue has caused so much confusion over the past few months I wince when I see DX10 used. Wink Truth is we designed FSX for DX9 'cause that's all we had to work with. When DX10 cards are ready only then will be *start* thinking about what to do with them."FSX was designed for DX9. Unless they release a major patch there will be no significant improvements. BTW, those screenshots of FSX in DX10 were "artist impressions".

Are you sure that FIBER_FRAME_TIME_FRACTION=0.33 is in your demo .cfg. I did a search and could not find it so I added it in. When tweaked it does not seem to have a significant effect on frames for me.____________________________________________________________________I think it has to into the main area like this.[Main]User Objects=Airplane, HelicopterSimObjectPaths.0=SimObjectsAirplanesSimObjectPaths.1=SimObjectsRotorcraftSimObjectPaths.2=SimObjectsGroundVehiclesSimObjectPaths.3=SimObjectsBoatsSimObjectPaths.4=SimObjectsAnimalsSimObjectPaths.5=SimObjectsMiscLocation=60,30,1092,796,.DISPLAY1FIBER_FRAME_TIME_FRACTION=0.15Maximized=1HideMenuNormal=0HideMenuFullscreen=1Changing it from 0.10 to 0.90 makes a huge impact on frame rates.John

> ".... the issue has caused so much confusion over the past few months I wince when I see DX10 used. Wink Truth > is we designed FSX for DX9 'cause that's all we had to work with. When DX10 cards are ready only then > will be *start* thinking about what to do with them."Thats pretty gullible to believe that. This is Microsoft dude, you know the same guys who are developing the next version of Windows which will feature dx10. Of course they have test dx10 cards. Even one of the flightsim.com readers had one back in May :-lol

Oops! Sorry Craig....I agree that info should have been posted.The Nvidia Driver is version 91.47The settings were in Demo 2, Princess Juliana airport in the ultra-light. I took off and was orbiting the airport. I would make a full orbit before making a change...to get a full range of scenery. It was hard for me to get an exact high-low FPS as the number never held constant, even if I paused the sim. I'm sure that different machines will show different results, so would be glad to see others post their results. The main point being to start with all sliders full left and then adjust them one at a time.Wouldn't it be cool if someone comes up with a little utility that would switch the settings configuration "on the fly"! Then, on final approach a simple keystroke would put you into "performance mode".

It's refreshing to see "the glass is half full" approach here for a change. I get really tired of seeing the naysayers and the people with their brand new core duo machines saying it won't work. Thanks for the driver info and yes a utility to switch settings on the fly would be great. Craig

I get tired of people who get tired of other people posting their views in this forum.Manny

Manny, I didn't say anything about others posting their views and your most welcome to yours. All I said was I get tired of people saying FSX won't work when in fact it will work even on a midrange machine and that it is refreshing to see someone who has made it work to their liking as well as posting detailed settings. Craig