Human eye integration factors aside, which has to do with "flicker" and the minimal refresh rate that a person can detect...

FPS (First Person Shooter) gamers reach for the highest refresh rates possible, while flight simmers shoot for the best frame rates possible. Reason being: Aircraft require fast frame rates and shooters require fast refresh rates due to different "success" criteria.

In shooters the goal is to pull the trigger and
frag the other guy ASAP, so they want faster and
faster refresh rate which increases the "world" speed and hence who gets shot first. Hence refresh rate is key to shooter's survival. These guys want over 150 Hz monitors and vcards.

In flight sims, milisecond timing of shots isnt the issue. Rather in flight sims the main issue
is avoiding shimmer and jitter due to the image
not being able to be drawn faster. Simmers want a fluid picture and hence frame rate is key. Frame rates at least 30 fps and reaching for 60+ at the desired resolution is considered great irregardless of the refresh rate.

Optimally you want both, fast framerate and fast
refresh rate. With the exception of LB2 and other retro sims where slowing down the systems is the goal. So LB2 we want a controlled refresh rate of 60hz to be compatible with other online players, and a fast (>30fps) frame rate at our desired resolution.

Does this help?

[/QB][/QUOTE]I dont see where you are trying to get with the 25 and 30 fps and 60 and 75Hz. [/QB][/QUOTE]

he's probably talking about using v sync, where framerate is limited to a divisor of refresh rate.

30 Hz is standard for several HDTV formats eg. in Europe, because 25fps is seen as too few fps for smooth playback (I also added the 60 Hz formats):

• 1080p60
• 1080p30
• 1080i60 (psf)
• 720p60
• 720p30
• 720i60 (psf)

psf means Progressive Scan with Segmented Frames (aka half-frames or interlaced), so 60 Hz interlaced are effectively 30 Hz full frame.

The NTSC color format, eg. used in the US runs at 30/1,001 = ca. 29,97003 Hz ~ 30Hz
NTSC b/w runs at exactly 30 Hz.

Sorry, I forgot about the NTSC system.
btw regular NTSC requires a little more bandwidth than 29.9KHz actually. Closer to 31.something KHz (my old CRT projector support up to 30.5KHz and it isnt enough). Some bandwidth is also used for refreshing horizontal too. But close enough.
Anyway, the LCD monitors can change refreshrates, they just cant change resolution.
So by having a 75Hz LCD monitor you can just as well use 60Hz on it.
So by tying this into the wrapper-side of things, all LCDs can use 60Hz with vsync on in the wrapper.

Shadow said:
"So by tying this into the wrapper-side of things, all LCDs can use 60Hz with vsync on in the wrapper."

The dgVoodoo wrapper effectively allowed us to
synch the game world speed across all kinds of
computer speeds and configurations via the refresh rate synching option.

The manual "throttling" CPU methods are no longer
needed as the only means to control refresh rates of all players is the same world or in solo play.

When all players are in a consistant world speed and a/c behavior environment;
then we have what we see today in our ability to
have very good multiplayer and even shared
cockpits in LB2.

All players having about the same refresh rate
is the key to the puzzle.
Some being higher or lower than others, Ive seen
results in momentary blanking (winking out)
of the other playrs the closer you get to them.

You're talking about horizontal refresh rate (usually in kHz), we were talking about vertical refresh rate (usually in Hz).

The NTSC frame rate is 29.97 interlaced frames per second! This yields an effective framereate of 59.94 Hz (meaning 59.94 full frames per second)

This is the so-called vertical refresh rate and tells how often the cathode ray is moved from the top to the bottom of the screen, thus telling how many pictures per second are generated.
The vertical refresh rate tells how often the cathode ray moves across the screen from left to right.

If you know the horizontal refresh rate you can calculate the vertical refresh rate easily.

Your example:

30.5 KHz horizontal refresh rate.
If your projector could display 1024x768 pixels, then the maximum framerate possible would be:

Horiz. rate/horiz. lines x 0.95 (because the ray needs about 5% of the time to travel back to the opposite side of the screen in the next line to display.

30500/768x0.95= 37.728 Hz

But your projector is a "near" NTSC projector, I think
Take the 480 lines of an NTSC frame:
30500/480x.95= 60.365 Hz Voilá!
A complete NTSC frame has 525 lines, the difference is used for synch, captioning etc. So your projector can't obviously show NTSC frames but maybe computer frames (640x480) at 60 Hz

Now you know why good CRT monitors have a horizontal refresh rate of more than 100 kHz.
You need this especially for higher resolutions.

Speaking of TFT's changing the refresh rate:

My TFT supports 59-61 Hz only.

TFT's that can show both refresh rates usually can't display refresh rates other than 60 Hz and 75 Hz, with a small margin of course.

Apart from that TFT's neither change the refresh rate nor the physical! resolution. CRT'S can change both, refresh rate and resolution (actually the aperture mask is not changeable too).

You were talking about bandwidth (meaning horizontal refresh rate actually), that's something different from both vertical and horizontal refresh rate.
The NTSC tv channel bandwidth lies at 6 MHz. More information about tv signal bandwidth, sidebands etc. is available at wikipedia.

Hi Fellow Pilots,

I want to Express my thankfulness for giving us again this great title Longbow 2,

I've installed it as it appears in the speichts guide and it came to life, but a problem has developed with it,

My hardware is not a gaming rig but it can handle Longbow 2 easily, my video board is A nVidia FX 5700LE (latest drivers installed) and the problem I have is that when you switch to an external view, The "transparency" of the crew's glass windshield panels has gone out, instead It looks like a mirror, "reflecting" everything outside the helicopter, but the most annoying is that both, the main Rotor and the tail rotor appear like opaque black disks, the fuzzy rotational illusion is not Shown anymore.

I've set all the features of the video card almost to the ground (no anti aliasing, no mipmapping, No everything, nothing at all) and the problem persists.

I've downloaded and executed the useful Glide Wrapper, but making every sort of changes Did not resolved anything.

Please, let me know if you have a solution for this near apparently unresolvable error.

SAGU,

Make sure youre running 3DFX and not D3D mode
if you have installed the D3D update patch.

This may be the cause of your mirrored windows on the cockpit.

First, got LB2 working fine, all I had to do was patch it, install the XP Compatibility Kit, and set up the Glide wrapper. It has not crashed yet, all the choppers work.

But two things...
(1) The different parts of the cockpit are not connected, there are little lines spaceing them apart, its not a big problem is there anything I can do to fix it?

(2) Is there any thing in the ca.ini I can modify to make the visuals better...
[GRAPHICS]
XResVideoMode=640
YResVideoMode=480
GammaCorrection=6
FarClip=7890
MeshDetail=2
TerrainLighting=1
Shadows=1
ObjectDetail=2
DetailedHelicopters=1
ObjectLighting=1
CockpitRotorFx=1
LensFlareFx=1
TextureMap=1
Perspective=1
DrawSky=1
Dither=1
SmokeDensity=2
SmokeEffectFx=2
MaxBitmaps=100
Trees=0
TreeDetail=0
TreeSamples=0

Thank you.

Hello Ryan, try turning antialiasing off. That should get rid of the gaps in the cockpit. However, you will see the "jaggies" in your graphics. I've decided live with the gaps to have better 3d world. I;m running with the dgVoodoo wrapper in 3dfx(glide) mode. My CA.ini settings are as follows and things look great:

[GRAPHICS]
XResVideoMode=640
YResVideoMode=480
GammaCorrection=6
FarClip=15780
MeshDetail=16
TerrainLighting=1
Shadows=1
ObjectDetail=15
DetailedHelicopters=1
ObjectLighting=1
CockpitRotorFx=1
LensFlareFx=1
TextureMap=8
Perspective=1
DrawSky=1
Dither=1
SmokeDensity=2
SmokeEffectFx=2
MaxBitmaps=5000
Trees=1
TreeDetail=9
TreeSamples=80000