Aces High Bulletin Board
Help and Support Forums => Aces High Bug Reports => Topic started by: lyric1 on May 18, 2011, 04:06:07 PM
-
For me the same issue every one sounds as if they have head colds or talking inside of a box. No other issues though.
-
just out on AP - "massive head cold pandemic sweeps the nation!" The only protection for the unaffected - crawl inside of a cardboard box!
There's the problem right there.
-
between barely readable and boxy, I'll take boxy...
-
I'm pretty sure this patch added dynamic gain control meaning it is a compressor/limiter and the "boxy sound" most are hearing is the mic now picking up the natural reverb of the room........which varys from person to person depending on room size and furnishings.
-
For me the same issue every one sounds as if they have head colds or talking inside of a box. No other issues though.
same here, sounds dreadful.
-
Not dreadful, just different. Adds a more "tin" sound, more realistic to the radio communication sounds of WWII. :D
-
Could it be that due to the hiigher quality sound, it's more affected by other sound in the room your in. The other day I could ear someone engine sound trough his vox and just yesterday the music playing in the background of someone in AVA. Could it be that those that use a standalone desktop mic might be more prone to voice being distant and/or boxy because of the distance of the mic. What do you think??
-
i have been hearing a variety of vox transmission quality...floatsup sounded like he was sitting right next to me...a couple of other people sounded like they were talking into tin cans...and yet others sounded like cb radios...did a vox text to myself and i can't get the mic to transmit any louder than a whisper even though i all my other voice programs transmit very loud...it's a real :headscratch:
-
Yesterday mine was working well but today I logged on and my vox was all scratchy.. kind of like a loud static in the background. I alt-tabbed to windows and in my Turtle Beach control panel raised the mic volume which fixed things.
Then I switched to SEA for FSO tonight and it was scratchy again. I simply alt-tabbed out and came back and it cleared up.
After FSO went back to Orange and was scratchy once again. Once again I alt-tabbed out and back in and it cleared up.
Might be due to my AKR8 headset (It's the USB interface version of the HPA2 headphones) but who knows.. definitely worth mentioning. I do have my right speaker starting to go. I'll be replacing them with the HPA2 in the near future...
-
Had a squadee with vox problems no vox at all at first. We experimented and eventually got loud clear sounding vox. This is what we did.
1- Preferences > Game Sounds (Tab).. Found more than one option in the drop down box for microphone..... tried each option until we found one that produced vox sound (initially sound was low volume) clicked apply and then okay.
2- Preferences > Game Sounds (Tab).. Tried to move the mic dB boost slider and found it did not respond. Neither could he uncheck the box that says "Enable mic dB Boost". Next step fixed all vox issues.
3- Quit game and relaunched the game. When returned the mic dB boost slider worked properly, and vox was easily adjusted.
I hope this will help some of you. It seems that the changes to the microphone systems don't take effect until you re launch the game.
-
New VOX sounds wierd.
New GV Reticule isn't as easy to use.
Since Patch 4 I've had reduced bullet damage.
-
New VOX sounds wierd.
New GV Reticule isn't as easy to use.
Since Patch 4 I've had reduced bullet damage.
I really would like for someone from HTC to seriously consider this damage question. I have a good friend who has been working with me on my computer settings and he suspects computer memory as being a culprit of the nerf bug. Without going into great detail or sounding off the whine alarm, there is some merit to this complaint. I just can't say that it is tied to this patch.
-
I had trouble getting vox to work. Once I did the .resetv and relogged vox works better than ever. Crystal clear.
I can see better in GVs now and can get hits before I die which I couldn't do before.
My hit % has gone up a couple points since the update.
The point is I don't think the game has a problem. Too many people play this game with laptops or don't realize that their computer is at the edge of it's ability to run the game smoothly. Then an update comes along and pushes their equipment over edge because of the new demands and it's all the games fault.
Just because you can run COD with eveything maxed doesn't mean you can do the same with this game. Aces is built different. Everything is run on your computer. COD is run on a server that you log into, so some of the computing load is on the server. Here it all you. So if your computer is just hanging on, an updae can push it over the edge.
-
I had trouble getting vox to work. Once I did the .resetv and relogged vox works better than ever. Crystal clear.
I can see better in GVs now and can get hits before I die which I couldn't do before.
My hit % has gone up a couple points since the update.
The point is I don't think the game has a problem. Too many people play this game with laptops or don't realize that their computer is at the edge of it's ability to run the game smoothly. Then an update comes along and pushes their equipment over edge because of the new demands and it's all the games fault.
Just because you can run COD with eveything maxed doesn't mean you can do the same with this game. Aces is built different. Everything is run on your computer. COD is run on a server that you log into, so some of the computing load is on the server. Here it all you. So if your computer is just hanging on, an updae can push it over the edge.
Not the case in my situation should have enough of everything.
-----------------
System Information
------------------
Time of this report: 5/23/2011, 16:40:19
Machine name: RODNEY-PC
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.110408-1633)
Language: English (Regional Setting: English)
System Manufacturer: DELL Inc.
System Model: Studio XPS 435T/9000
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (8 CPUs), ~3.1GHz
Memory: 12288MB RAM
Available OS Memory: 8182MB RAM
Page File: 2163MB used, 14200MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Input Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 480
Manufacturer: NVIDIA
Chip type: GeForce GTX 480
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_06C0&SUBSYS_14823842&REV_A3
Display Memory: 4063 MB
Dedicated Memory: 1503 MB
Shared Memory: 2559 MB
Current Mode: 1920 x 1200 (32 bit) (59Hz)
Monitor Name: Dell 2407WFP (Digital)
Monitor Model: DELL 2407WFP
Monitor Id: DELA017
Native Mode: 1920 x 1200(p) (59.950Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.7061 (English)
Driver Version: 8.17.12.7061
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 4/8/2011 01:14:00, 12934248 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-4580-11CF-6740-8E341DC2C535}
Vendor ID: 0x10DE
Device ID: 0x06C0
SubSys ID: 0x14823842
Revision ID: 0x00A3
-
How much stuff do you have running in the background on that thing?
Is it a USB that is the setup for your sound/vox?
Maybe you should post the sound part of your Dxdiag too.
-
I really would like for someone from HTC to seriously consider this damage question. I have a good friend who has been working with me on my computer settings and he suspects computer memory as being a culprit of the nerf bug. Without going into great detail or sounding off the whine alarm, there is some merit to this complaint. I just can't say that it is tied to this patch.
When you say memory, in what context? RAM, Hard Drive or Graphics Card?
-
How much stuff do you have running in the background on that thing?
Is it a USB that is the setup for your sound/vox?
Maybe you should post the sound part of your Dxdiag too.
Here it is. I don't think I have any USB on the sound card at all. I have a bunch in the back ground I shut as much as I can down when playing AHII.
-------------
Sound Devices
-------------
Description: Speakers (HTO STRIKER 7.1)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_13F6&DEV_0111&SUBSYS_83847284&REV_10
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: cmudax3.sys
Driver Version: 5.12.0001.0008 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 3/3/2008 05:25:46, 846848 bytes
Other Files:
Driver Provider: HT OMEGA Inc.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
---------------------
Sound Capture Devices
---------------------
Description: Microphone (HTO STRIKER 7.1)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: cmudax3.sys
Driver Version: 5.12.0001.0008 (English)
Driver Attributes: Final Retail
Date and Size: 3/3/2008 05:25:46, 846848 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
Description: Stereo Mix (HTO STRIKER 7.1)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: cmudax3.sys
Driver Version: 5.12.0001.0008 (English)
Driver Attributes: Final Retail
Date and Size: 3/3/2008 05:25:46, 846848 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
Description: SPDIF In (HTO STRIKER 7.1)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: cmudax3.sys
Driver Version: 5.12.0001.0008 (English)
Driver Attributes: Final Retail
Date and Size: 3/3/2008 05:25:46, 846848 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
Description: Aux (HTO STRIKER 7.1)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: cmudax3.sys
Driver Version: 5.12.0001.0008 (English)
Driver Attributes: Final Retail
Date and Size: 3/3/2008 05:25:46, 846848 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
Description: Line In (HTO STRIKER 7.1)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: cmudax3.sys
Driver Version: 5.12.0001.0008 (English)
Driver Attributes: Final Retail
Date and Size: 3/3/2008 05:25:46, 846848 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
-
When you say memory, in what context? RAM, Hard Drive or Graphics Card?
he's talking about a possible memory leak...if there is one, findiing it would not be easy and the symptoms could be all over the place.
-
Thanks Gyrene,
Yes, I was wondering if there were leaks. But the simple fact that I haven't a clue what a memory leak is, lets you know that I am relying on second hand information and trial and error, to defeat the "nerf".
What I have been told to do was to increase my windows memory access (virtual memory). I can't say one way or the other as a result yet. I do have one other test to run to see if there is any merit to need for additional virtual memory for my machine.
I was hoping that reports from other players might help in locating a source when it came to nerf rounds.
-
I really would like for someone from HTC to seriously consider this damage question. I have a good friend who has been working with me on my computer settings and he suspects computer memory as being a culprit of the nerf bug. Without going into great detail or sounding off the whine alarm, there is some merit to this complaint. I just can't say that it is tied to this patch.
There is no merit to the idea of a memory leak causing reduced damage.
Although a mem leak is always possible, and you can see if there is one by opening your task manager and watch performance mem usage over a few hours of play. If it is continually increasing over a long period, there may be a leak. In our last testing, (was this version) we havn't seen any.
HiTech
-
Thanks for the response. I am fortunate enough to understand how to test memory usage with task manager and other utilities and am willing to run any tests that may be helpful.
Now, back to the reason that I even went in this direction in the first place with my limited understanding. I have been experiencing what I am from here on out calling, "nerf rounds". These rounds either, never hit their target (even at point blank) or they do not record damage.
Why I am not talking out of my rear end: On bombing runs I increase my graphic range sliders. Sometimes forgetting to return the settings to the performance setting. Sometimes a sortee or two may go by before I have realized that even when I see hit sprites all over my opponent, or am right in perfect range of him and giving no damage, that something is not normal. I immediately check my detail settings and adjust them and presto, I am back to shooting stuff down again.
I must add that if I am using Ground Detail (only use it when hunting GVs from the air or on the ground) I get the same result with nerf rounds.
I tried doing a test using the target and shooting the same approximate rounds. Although I could see a possible difference, it was not big enough to dispell any bias on my part either in # of rounds or perceived result.
I believe that I may have the ability to record memory usage with a utility on my computer while AH2 is running. But it is a no brainer that the usage will go up with higher settings. I think this is evident in the FPS count that I watch from the in game utility. Ground vis or increased detail range generally shoot frame rates down considerably.
Now, do I sound like a babbling idiot that should be ignored, or do I have legitimate issues that could be solved by tweaking virtual memory or some other hardware or software adjustment?
------------------
System Information
------------------
Time of this report: 5/25/2011, 04:00:26
Machine name: MERCURY
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_rtm.040803-2158)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dimension 5100
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz (2 CPUs)
Memory: 3326MB RAM
Page File: 383MB used, 10280MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
---------------
Display Devices
---------------
Card name: NVIDIA GeForce 210
Manufacturer: NVIDIA
Chip type: GeForce 210
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0A65&SUBSYS_12123842&REV_A2
Display Memory: 1024.0 MB
Current Mode: 1600 x 900 (32 bit) (60Hz)
Monitor: HP S2031 Series Wide LCD Monitor
Monitor Max Res: 1600,900
Driver Name: nv4_disp.dll
Driver Version: 6.14.0012.7061 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 4/8/2011 01:14:00, 4111232 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 4/8/2011 01:14:00, 12501600 bytes
Device Identifier: {D7B71E3E-4925-11CF-6740-1E3203C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0A65
SubSys ID: 0x12123842
Revision ID: 0x00A2
Revision ID: 0x00A2
Video Accel: ModeMPEG2_C ModeMPEG2_D
-------------
Sound Devices
-------------
Description: Rocketfish 5.1
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_10011102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: P17.sys
Driver Version: 5.12.0001.0522 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 2/26/2009 02:29:58, 1142272 bytes
Other Files:
Driver Provider: Rocketfish
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 4000, 96000
Static/Strm HW Mix Bufs: 64, 63
Static/Strm HW 3D Bufs: 64, 63
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: Rocketfish 5.1
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: P17.sys
Driver Version: 5.12.0001.0522 (English)
Driver Attributes: Final Retail
Date and Size: 2/26/2009 02:29:58, 1142272 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
------------------------
Drive: C:
Free Space: 131.9 GB
Total Space: 152.6 GB
File System: NTFS
Model: WDC WD1600AAJS-00YZCA0
Drive: D:
Model: TOSHIBA DVD-ROM SD-M1612
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/3/2004 23:59:54, 49536 bytes
Drive: E:
Model: HL-DT-ST CD-RW GCE-8400B
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/3/2004 23:59:54, 49536 bytes
-
Send us a film of this happening and we'll analyze it.
-
Thanks again fellas. :aok I will do that and hope this will lead to a better understanding on what to look for in order to tweak my settings properly. :salute