New Sound settings in AH (respectful)

[TwinBoom]

audigy 2 zs here and I cant hear half my sounds and when i make/modify them i have them at all the same decibel level 

[SlapShot]

My FPS went down from 180+ to about 120. That's a big difference for just a few new buildings... bug?

What is the screen refresh rate of your monitor? ... do you have VSync on or off ?

I am guessing you have VSync off ... unless your monitor can handle a refresh rate of 180 or 120, that is not the real FPS.

My monitor has a 60 Hertz refresh rate ... I have VSync on and I never get FPS any higher than 60 ... it is usually always 59 FPS.

You can never really get any more FPS than what your monitor refresh rate can handle ... unless VSync is off ... and then you really aren't getting a reading on the true FPS.

[MORAY37]

My FPS went down from 180+ to about 120. That's a big difference for just a few new buildings... bug?

Considering your eyes see at an average of 20-24 FPS in real life......when "applied" to the format of FPS.  Or to be more technical, 50 cycles per degree is the upper limit of an exceptionally good, healthy human eye. (1.2 arcminute per line pair, or a 0.35 mm line pair, at 1 m)

As someone else said, worry about it if it goes to 30 FPS.  Your eye just can't see any difference past between 60 and 80 FPS (depending on many factors), and your brain is honestly more than likely only interpreting 5 frames out of every 10 at 180 FPS.  There's just more information than the visual cortex can process and deliver, so it "shortens the film" at such a high frame rate, and starts throwing out frames.

Unless your frame rate is a bragging point for you, I wouldn't worry.

Also, as slapshot said, make sure your Vsynch is on.  If it's off, you'll get a lot more rubber bullets, and have an amazingly high FPS rate at the same time.

[Ghastly]

Considering your eyes see at an average of 20-24 FPS in real life......when "applied" to the format of FPS.  Or to be more technical, 50 cycles per degree is the upper limit of an exceptionally good, healthy human eye. (1.2 arcminute per line pair, or a 0.35 mm line pair, at 1 m)

Most of that made no sense, but the 24 FPS is wrong - 24 frames per second of motion blurred film (each typically shown twice, for an actual FPS of 48, since "light trumps darkness" to the human eye) was considered to be the minimum that seemed plausible to the early developers of film technology.  Eyes don't "see" FPS, anyway, so there isn't a direct comparison.

A good synopsis can be found here:
http://www.100fps.com/how_many_frames_can_humans_see.htm

In no way does that 24 FPS translate to the display of "frozen frames" such as that generated by 3D computer games.  Arguing that 24 FPS is "all a person needs" - based on a completely different technology - is like saying that anything over 40 octane gas is a waste because that's what cars ran on in the 20's.

<S>

[sluggish]

I can finally output vox to my headset while having the game sounds output to my speakers!  And it sounds fantastic!  WTG HTC!

[SPKmes]

My GV sounds are awesome...I'm loving them...I can't wait for a good sized GV battle in one of these new towns....My planes...well they are another story...I am having to re learn my SA....It is amazing how dependent I became on my sounds...I always knew I used them to much...especially in multi con engagements...It will take me a tour or two to be comfortable again I think.. After a couple of days I am finally coming to grips with my stalls....

[Money]

I can finally output vox to my headset while having the game sounds output to my speakers!  And it sounds fantastic!  WTG HTC!

this would be fantastic and I hope it is true!  Going to arena now to find out

[MORAY37]

Most of that made no sense, but the 24 FPS is wrong - 24 frames per second of motion blurred film (each typically shown twice, for an actual FPS of 48, since "light trumps darkness" to the human eye) was considered to be the minimum that seemed plausible to the early developers of film technology.  Eyes don't "see" FPS, anyway, so there isn't a direct comparison.


<S>

It made perfect sense.

I averaged it to FPS...there is an average comparison, not a direct one.  Visual acuity is tied to the latter, at 50 cycles per second (1.2 arcminute per line pair).  You are correct, the eye does not see in FPS.  The fact remains, your eye won't be able to tell the difference past 60 FPS in a game, and at over 100 you are actually not even registering the frames passing on the visual cortex.

Your average everyday eye sees at a comparable 24 frames per second walking down the street.

Basic biology.

<S>

[Ghastly]

It made perfect sense.

I averaged it to FPS...there is an average comparison, not a direct one.  Visual acuity is tied to the latter, at 50 cycles per second (1.2 arcminute per line pair).  You are correct, the eye does not see in FPS.  The fact remains, your eye won't be able to tell the difference past 60 FPS in a game, and at over 100 you are actually not even registering the frames passing on the visual cortex.

Your average everyday eye sees at a comparable 24 frames per second walking down the street.

Basic biology.

<S>

Basic Biology, you mean like "Bumblebees are too heavy to fly", etc?

HorsePucky. I know what I see, even when I'm told I can't. Even at 60 FPS, there is very noticeable "stuttering" when viewing game generated frames, especially when the entire scene rotates, like when you roll an aircraft - which translates (for me) into eyestrain and fatigue.   

Speaking solely for myself, the stuttering that I supposedly can't see because, you know, my eyes don't register anything more than 24 FPS - everyone keeps repeating it, so it must be true - is distracting and fatiguing up until about 75 FPS, and doesn't diminish to where I don't notice it as an intrusion until somewhere between 85 and 100 FPS.  I've read that some people still register it as the FPS approaches 200.

But if anything above 24 FPS is undetectable to you, then by all means, I'm happy for you.

<S>

[perdue3]

No offense, but you are kind of turning into a forum snob.

Forum snob, thats rich 


perdweeb

[sluggish]

Basic Biology, you mean like "Bumblebees are too heavy to fly", etc?

HorsePucky. I know what I see, even when I'm told I can't. Even at 60 FPS, there is very noticeable "stuttering" when viewing game generated frames, especially when the entire scene rotates, like when you roll an aircraft - which translates (for me) into eyestrain and fatigue.   

Speaking solely for myself, the stuttering that I supposedly can't see because, you know, my eyes don't register anything more than 24 FPS - everyone keeps repeating it, so it must be true - is distracting and fatiguing up until about 75 FPS, and doesn't diminish to where I don't notice it as an intrusion until somewhere between 85 and 100 FPS.  I've read that some people still register it as the FPS approaches 200.

But if anything above 24 FPS is undetectable to you, then by all means, I'm happy for you.

<S>

It must be hell to go through life literally unable to watch a motion picture...

[usvi]

It must be hell to go through life literally unable to watch a motion picture...

Not if you never have to see a Will Ferrell movie.That sounds like my idea of heaven.

[Ghastly]

It must be hell to go through life literally unable to watch a motion picture...

No, the difference is motion blurred frames versus static snapshot images.  Movies are no problem.  Movie film captures motion as a blur, so your mind perceives a continuous smooth movement from the disjointed frames.

The problem is that people continue to propagate the myth that because 24 frames of motion blurred film (completely ignoring that each is actually shown twice) is enough to appear smooth to (most) people,  that somehow means that 24 frames per second is all you need to perceive smooth motion during gaming.

If I've seen this posted once over the last decade, I've seen it 50 times.  And each time I see it, I grit my teeth imagining how unhappy someone who takes that on faith is likely to be when they settle for hardware/software that will only perform to that level.   And it's not just players - I once had the lead designer for a sim I was beta testing tell me that because 24 FPS was all anyone could detect, he was designing the sim to never go above 30 FPS no matter what hardware the players had.   

Dunno bout you, but I can't fly at 30 FPS or less  = or at least, enjoy it very much for very long. 

<S>

[USRanger]

I thought this thread was about sounds.

[Ghastly]

I thought this thread was about sounds.

We started with one type of human input, and are spreading out to the others, I guess.   And I'm sure we'll end up landing on "output" eventually ...  {grin}

<S>