FSX & SLI

[Black ZR-1]

Mesh Resolution to 19 unless you run 10m mesh from FSGensis,... heres the deal, running any higher than 19m is useless because the default mesh is 38m (19) and 76m. 10m mesh means the slider gets set to 10m... you dont have 1m mesh installed so I think you may be wasting resources.

Texture Resulution to 1m,... You will probably find very little difference between 1m and 7cm and what you save between those two may give you what you need to raise Water to 2x Low (4 in the config file)

Mesh Complexity to 100%.. not sure why you have it at 99%


FSX was designed for add-on partners to develop mesh and textures that will make full use of the sim sliders. Setting the MR and TR to max may not really be giving you as much as you may think and backing them down might provide more where you need it.



It is good you know about clocking.. that is going to give the system that last boost it needs


I assume you use the WideViewAspect=True switch in the FSX.cfg file



You are also pulling resources by running FRAPS at the same time even if it is not encoding

I must of missed the Mesh Complexity when I was messing around with the sliders. I have it at 100%.

Also, with WideViewAspect=True, I lose about 8 - 9 frames. What could cause this? I've always had it off.

[justpassingthrough]

Mesh Resolution to 19 unless you run 10m mesh from FSGensis,... heres the deal, running any higher than 19m is useless because the default mesh is 38m (19) and 76m. 10m mesh means the slider gets set to 10m... you dont have 1m mesh installed so I think you may be wasting resources.

Texture Resulution to 1m,... You will probably find very little difference between 1m and 7cm and what you save between those two may give you what you need to raise Water to 2x Low (4 in the config file)

Mesh Complexity to 100%.. not sure why you have it at 99%


FSX was designed for add-on partners to develop mesh and textures that will make full use of the sim sliders. Setting the MR and TR to max may not really be giving you as much as you may think and backing them down might provide more where you need it.



It is good you know about clocking.. that is going to give the system that last boost it needs


I assume you use the WideViewAspect=True switch in the FSX.cfg file



You are also pulling resources by running FRAPS at the same time even if it is not encoding

I must of missed the Mesh Complexity when I was messing around with the sliders. I have it at 100%.

Also, with WideViewAspect=True, I lose about 8 - 9 frames. What could cause this? I've always had it off.

Not sure. I run 1920x1200 with a new 24inch TFT from BenQ and have no loss or change in performance when I switched WideViewAspect from FALSE to TRUE. The screen when set to TRUE displays FSX zoom and view correct as compared to FALSE where it is distored somewhat.

I assume you have your video driver set to: SINGLE DISPLAY PERFORMANCE MODE and also have the LCD FLAT PANEL SCALING set to: USE BUILT IN SCALING or MONITOR SCALING?

If all the above are in order, perhaps it is some type of driver rendering issue with respect to the aspect ratio involved @ 1680x1050x32

Both are a 1.6:1 widescreen ratio so I do not see where that would make a difference. There is a bit more to that and it is based on the size of the screen itself (L - W and Diagonal) The unit itself could be forcing some type of strange internal number because of the screen geometry.

I assume you checked the Hz frequency refresh setting too. Most TFT's run at 60 but there are some that want to see

[Black ZR-1]

Ok, here are some screenshots with max Texture & Mesh resolution compared to 19m & 1m.

[Black ZR-1]

Mesh Resolution to 19 unless you run 10m mesh from FSGensis,... heres the deal, running any higher than 19m is useless because the default mesh is 38m (19) and 76m. 10m mesh means the slider gets set to 10m... you dont have 1m mesh installed so I think you may be wasting resources.

Texture Resulution to 1m,... You will probably find very little difference between 1m and 7cm and what you save between those two may give you what you need to raise Water to 2x Low (4 in the config file)

Mesh Complexity to 100%.. not sure why you have it at 99%


FSX was designed for add-on partners to develop mesh and textures that will make full use of the sim sliders. Setting the MR and TR to max may not really be giving you as much as you may think and backing them down might provide more where you need it.



It is good you know about clocking.. that is going to give the system that last boost it needs


I assume you use the WideViewAspect=True switch in the FSX.cfg file



You are also pulling resources by running FRAPS at the same time even if it is not encoding

I must of missed the Mesh Complexity when I was messing around with the sliders. I have it at 100%.

Also, with WideViewAspect=True, I lose about 8 - 9 frames. What could cause this? I've always had it off.

Not sure. I run 1920x1200 with a new 24inch TFT from BenQ and have no loss or change in performance when I switched WideViewAspect from FALSE to TRUE. The screen when set to TRUE displays FSX zoom and view correct as compared to FALSE where it is distored somewhat.

I assume you have your video driver set to: SINGLE DISPLAY PERFORMANCE MODE and also have the LCD FLAT PANEL SCALING set to: USE BUILT IN SCALING or MONITOR SCALING?

If all the above are in order, perhaps it is some type of driver rendering issue with respect to the aspect ratio involved @ 1680x1050x32

Both are a 1.6:1 widescreen ratio so I do not see where that would make a difference. There is a bit more to that and it is based on the size of the screen itself (L - W and Diagonal) The unit itself could be forcing some type of strange internal number because of the screen geometry.

I assume you checked the Hz frequency refresh setting too. Most TFT's run at 60 but there are some that want to see

[justpassingthrough]

[quote]Ok, here are some screenshots with max Texture & Mesh resolution compared to 19m & 1m.

[justpassingthrough]

Mesh Resolution to 19 unless you run 10m mesh from FSGensis,... heres the deal, running any higher than 19m is useless because the default mesh is 38m (19) and 76m. 10m mesh means the slider gets set to 10m... you dont have 1m mesh installed so I think you may be wasting resources.

Texture Resulution to 1m,... You will probably find very little difference between 1m and 7cm and what you save between those two may give you what you need to raise Water to 2x Low (4 in the config file)

Mesh Complexity to 100%.. not sure why you have it at 99%


FSX was designed for add-on partners to develop mesh and textures that will make full use of the sim sliders. Setting the MR and TR to max may not really be giving you as much as you may think and backing them down might provide more where you need it.



It is good you know about clocking.. that is going to give the system that last boost it needs


I assume you use the WideViewAspect=True switch in the FSX.cfg file



You are also pulling resources by running FRAPS at the same time even if it is not encoding

I must of missed the Mesh Complexity when I was messing around with the sliders. I have it at 100%.

Also, with WideViewAspect=True, I lose about 8 - 9 frames. What could cause this? I've always had it off.

Not sure. I run 1920x1200 with a new 24inch TFT from BenQ and have no loss or change in performance when I switched WideViewAspect from FALSE to TRUE. The screen when set to TRUE displays FSX zoom and view correct as compared to FALSE where it is distored somewhat.

I assume you have your video driver set to: SINGLE DISPLAY PERFORMANCE MODE and also have the LCD FLAT PANEL SCALING set to: USE BUILT IN SCALING or MONITOR SCALING?

If all the above are in order, perhaps it is some type of driver rendering issue with respect to the aspect ratio involved @ 1680x1050x32

Both are a 1.6:1 widescreen ratio so I do not see where that would make a difference. There is a bit more to that and it is based on the size of the screen itself (L - W and Diagonal) The unit itself could be forcing some type of strange internal number because of the screen geometry.

I assume you checked the Hz frequency refresh setting too. Most TFT's run at 60 but there are some that want to see

[Black ZR-1]

I see absoluetly no difference and in some respects the lower res settings display sharper in some areas, probably because of the increased processor and GPU time available but as for how well they POP in comparison.. no difference

Its not worth the higher slider values past 19m/1m unless you are running 10m mesh from FSGenesis or other add on dev.. and until a developer comes out with textures for 1m, its a waste to run that too for flight.


I dont know if you did all those texture hacks but I can tell you that if you did, you reduced the 'true' clarity of them to get performance

I see no difference either. No, I haven't done the hacks yet on these screenshots. I will be doing them later with comparison shots since I'm going back and forth.

[quote]
Go to the driver panel and look for: DIGITAL FLAT PANEL SETTINGS

however, you are using a converter and and old cable it is very possible that old cable and converter are NOT allowing the correct TFT Digital access to the system.

Yes, that may be your problem. A good TFT MUST have the right cables going to it. That goes for all its functions. The BenQ allows for HDMI and full 1080p resolutions from BlueRay and other devices along with PIP signals so the cables MUST be correct or those signals will not be processed correctly and dispayed right.

Also verify if there are monitor drivers for the unit. The BenQ has drivers and in combination with the Nivida Drivers, allows access the BenQ OSD

[justpassingthrough]

I see you have a frame lock of 30. I would reduce that to 25 and work the other settings but if you feel 30 is where you want it, then leave it. As Ptaylor and other devs said, the higer the frame lock, the less time goes to the fiber frame.

I noticed you paused the sim for the MAX images (unless you cropped that on the low settings) pasuing the sim allows screenshots to sharpen.. just and FYI


At what value are you running the FIBER_FRAME_TIME_FRACTION=?

If you are currently set to .33... try raising it to .40 and see what happens both visually to the ground textures and performance

Some said the 8800 and the Core 2 like increasing that value.. see if it makes a difference.

[Black ZR-1]

I see you have a frame lock of 30. I would reduce that to 25 and work the other settings but if you feel 30 is where you want it, then leave it. As Ptaylor and other devs said, the higer the frame lock, the less time goes to the fiber frame.

I noticed you paused the sim for the MAX images (unless you cropped that on the low settings) pasuing the sim allows screenshots to sharpen.. just and FYI


At what value are you running the FIBER_FRAME_TIME_FRACTION=?

If you are currently set to .33... try raising it to .40 and see what happens both visually to the ground textures and performance

Some said the 8800 and the Core 2 like increasing that value.. see if it makes a difference.

I have dropped the lock down to 28 since I've posed the screenshots. I paused it for my own preferences so I can tell the difference between the screenshots while I was setting them up in photoshop, but I understand what you're saying. I have the time_fraction at 33. I will try bumping it.

[justpassingthrough]

I see you have a frame lock of 30. I would reduce that to 25 and work the other settings but if you feel 30 is where you want it, then leave it. As Ptaylor and other devs said, the higer the frame lock, the less time goes to the fiber frame.

I noticed you paused the sim for the MAX images (unless you cropped that on the low settings) pasuing the sim allows screenshots to sharpen.. just and FYI


At what value are you running the FIBER_FRAME_TIME_FRACTION=?

If you are currently set to .33... try raising it to .40 and see what happens both visually to the ground textures and performance

Some said the 8800 and the Core 2 like increasing that value.. see if it makes a difference.

I have dropped the lock down to 28 since I've posed the screenshots. I paused it for my own preferences so I can tell the difference between the screenshots while I was setting them up in photoshop, but I understand what you're saying. I have the time_fraction at 33. I will try bumping it.

Definitely get the right cable for your monitor. I would think that would have come with the unit

I do not know for sure getting the right one will have a positive impact on the system however if your drivers are not seeing a digital flat panel it could very be a reason for aspect ratio problems.

[Black ZR-1]

Ok. I digged around my apartment and found the correct cables that came with my monitor. Right away I noticed a difference in quality between my older cables and newer ones. Everything looks sharper and better. But When I tried changing the scaling to 'Use NVIDIA scaling with fixed-aspect ratio', everything got blurry. I switched it to 'Display built-in scaling' and everything is smooth.



However, I went back to my FSX config file, switched it to Use WideViewAspect=True, and I still lost 6 - 8 FPS. Im still confused...

[justpassingthrough]

Ok. I digged around my apartment and found the correct cables that came with my monitor. Right away I noticed a difference in quality between my older cables and newer ones. Everything looks sharper and better. But When I tried changing the scaling to 'Use NVIDIA scaling with fixed-aspect ratio', everything got blurry. I switched it to 'Display built-in scaling' and everything is smooth.



However, I went back to my FSX config file, switched it to Use WideViewAspect=True, and I still lost 6 - 8 FPS. Im still confused...

It's suppose to be set to "Use My Monitors built in scaling" so what you have is correct. I figured once you hooked up the correct cable your video image would change for the better.




Strange that you are loosing performance on wide screen aspect.

Question: When you do use the widescreen switch, does the screen appear better in terms of the zoom levels and how things look? Or does it look the same with or without the switch enabled?

Does the image appear stretched with widescreen set to FALSE?


I guess it is possible that resolution is one that FSX does not like.

[Black ZR-1]

I see a difference now comparing the 2 screenshots.

Screenshot 1 is True widescreen. Notice the zoom: 1.50 and how far away the plane is.



Screenshot 2 is False widescreen. Same angle. Notice the zoom: 1.50 (the same as shot 1) but this time notice how close the plane is with the same zoom rate. Also notice my FPS.



With wideview false, my screenshots are clipped. With wideview true, my FPS get cut. What to do....

EDIT: 2 more





Zoom rate untouched on these 2

[ATI_7500]

Some said the 8800 and the Core 2 like increasing that value.. see if it makes a difference.

Mine don't.

I'm still playing around with those, but from what I've seen so far, it's like this:

High FFTF (0.66), no frame lock: Good frames with blurries.
High FFTF, frame lock: Bad frame rates.
Low FFTF (0.33), no frame lock: Good frames with blurries.
Low FFTF, frame lock: Working fine (so far...)

Apparently, my system doesn't like FFTF.

Or I did something wrong with some drivers and settings.

I'll keep on investigating.

[justpassingthrough]

Some said the 8800 and the Core 2 like increasing that value.. see if it makes a difference.

Mine don't.

I'm still playing around with those, but from what I've seen so far, it's like this:

High FFTF (0.66), no frame lock: Good frames with blurries.
High FFTF, frame lock: Bad frame rates.
Low FFTF (0.33), no frame lock: Good frames with blurries.
Low FFTF, frame lock: Working fine (so far...)

Apparently, my system doesn't like FFTF.

Or I did something wrong with some drivers and settings.

I'll keep on investigating.

Well that stands to reason. The developers said that raising the value and running the frame lock up would create blurries and other issues. Thats is why I was surprised when you mentioned a few weeks ago a higher FFTF was working better for you.