Aces High Bulletin Board
Help and Support Forums => Aces High Bug Reports => Topic started by: Dustoff2 on March 10, 2010, 09:56:25 PM
-
When I lower my Rpm's, I lose at least 20 inches man. before I even get 1 rpm lower indicated on the gauge and then the rpms are very slow to respond when I try to keep lowering them.
-
if you bump the rpms down just once, the rpms move about 3-4 rpms and before stoping. They are very slow to respond.
-
I find this new version horrible. I cant believe that nobody else is experiencing the sluggish response in the rpm gauge needle while trying to change the rpm's in the hog or any other plane. I find it hard to set a cruise setting. There is definitely something wrong.
-
How are you trying to lower your RPM? Are you using the keyboard? If you are using a joystick is RPM mapped to buttons, or are you mapping it to a slider. If you're using a slider or something similar it may be that you need to calibrate it.
-
I use a CH Pro throttle. Before this latest update. The RPM needle moved fast. As fast as the manifold pressure needle does now. Now the RPM needle moves very slow, and runs past the setting that you want ie. reducing from 2700 to 2200 rpm for best cruise, then you toggle it up and it starts to slow down from moving down to moving up but then goes past the setting that you want. Its a constant battle to get it where you want it. It was not like that before. It moved fast. Stopped where you wanted it to when you stopped toggling. It does this regardless if you are using the toggle button or the plus/minus keys. Very annoying to those of us that adjust use that feature. But to those that fly balls to the wall.......I guess it doesn't matter and is not a problem.
-
System Information
------------------
Time of this report: 3/11/2010, 07:59:40
Machine name: HELLCAT
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp.080413-2111)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: P5K/EPU
BIOS: BIOS Date: 03/06/08 10:24:46 Ver: 08.00.12
Processor: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (2 CPUs)
Memory: 2048MB RAM
Page File: 171MB used, 3768MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 260
Manufacturer: NVIDIA
Chip type: GeForce GTX 260
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_05E2&SUBSYS_0FA919F1&REV_A1
Display Memory: 896.0 MB
Current Mode: 1024 x 768 (32 bit) (75Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.8242 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 3/18/2009 14:56:00, 6185344 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 3/18/2009 14:56:01, 6288672 bytes
Device Identifier: {D7B71E3E-46A2-11CF-735A-A22F00C2CB35}
Vendor ID: 0x10DE
Device ID: 0x05E2
SubSys ID: 0x0FA919F1
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
-------------
Sound Devices
-------------
Description: Sound Blaster X-Fi Xtreme Audio
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_1102&DEV_000A&SUBSYS_11021006&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: t3.sys
Driver Version: 5.10.0000.0200 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 6/18/2007 23:38:52, 735744 bytes
Other Files:
Driver Provider: CREATIVE
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 192000
Static/Strm HW Mix Bufs: 65, 64
Static/Strm HW 3D Bufs: 65, 64
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: Sound Blaster X-Fi Xtreme Audio
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: t3.sys
Driver Version: 5.10.0000.0200 (English)
Driver Attributes: Final Retail
Date and Size: 6/18/2007 23:38:52, 735744 bytes
Cap Flags: 0x41
Format Flags: 0xCC0
-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Creative SoundFont Synthesizer [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: CH PRO THROTTLE USB
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x068E, 0x00F1
FF Driver: n/a
Device Name: CH PRO PEDALS USB
Attached: 1
Controller ID: 0x1
Vendor/Product ID: 0x068E, 0x00F2
FF Driver: n/a
Device Name: CH FIGHTERSTICK USB
Attached: 1
Controller ID: 0x2
Vendor/Product ID: 0x068E, 0x00F3
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-
I don't think its a bug, but if it is I'm also experiencing it. I don't really see it as a problem though. If you are having a hard time adjusting for the delay, use the "-" "+" keys for more precise adjustments. It is quite possible to notch it down only 1 with a single tap.
Edit: Also, it's not just the F4U...all rides as far as I can tell. Hence why I don't think its a bug. :aok
-
so we can agree that before Version 2.18 Patch 0 Released, the prop pitch control acted, behaved, operated whatever you want to call it, differently than after this current release. Or I guess you can say it operates differently now after this release.
Either way,I don't like it. Here's what the current release information said "Fixed prop pitch in 3d models of the P39s and A6Ms."
But I feel they totally screwed up all the other planes if this is what they are referring to when they fixed the prop pitch.
-
yeah!!!!!!!!!!!! :banana:
patch 1 fixed it. I have my beloved plane back to normal again. Thanks guys :x