Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: BlackDove on November 03, 2007, 04:34:32 pm
-
Get the system info out of the way first.
------------------
System Information
------------------
Time of this report: 11/3/2007, 22:21:02
Operating System: Windows Vista™ Ultimate (6.0, Build 6000) (6000.vista_gdr.070627-1500)
Language: Swedish (Regional Setting: Swedish)
System Manufacturer: MSI
System Model: MS-7191
BIOS: Default System BIOS
Processor: AMD Athlon(tm) 64 Processor 3500+, ~2.2GHz
Memory: 2046MB RAM
Page File: 1091MB used, 3221MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 10
DX Setup Parameters: Not found
DxDiag Version: 6.00.6000.16386 32bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: 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 8800 GTS
Manufacturer: NVIDIA
Chip type: GeForce 8800 GTS
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0193&SUBSYS_823C1043&REV_A2
Display Memory: 1052 MB
Dedicated Memory: 284 MB
Shared Memory: 767 MB
Current Mode: 1600 x 1200 (32 bit) (60Hz)
Monitor: SAMTRON 96P/97P(T)
Driver Name: nvd3dum,nvd3dumx.dll,nvwgf2um,nvwgf2umx.dll
Driver Version: 7.15.0011.6901 (English)
DDI Version: 9Ex
Driver Attributes: Final Retail
Driver Date/Size: 10/24/2007 19:20:00, 5259264 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-42D3-11CF-0669-37A202C2CA35}
Vendor ID: 0x10DE
Device ID: 0x0193
SubSys ID: 0x823C1043
Revision ID: 0x00A2
Revision ID: 0x00A2
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_B ModeWMV9_B ModeVC1_A 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_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) 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,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) 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,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{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_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
-------------
Sound Devices
-------------
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0880&SUBSYS_1462E603&REV_1008
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5443 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 7/10/2007 09:00:00, 1104408 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 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
Description: Realtek Digital Output (Realtek High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0880&SUBSYS_1462E603&REV_1008
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5443 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 7/10/2007 09:00:00, 1104408 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 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 (Realtek High Definition Audio)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5443 (English)
Driver Attributes: Final Retail
Date and Size: 7/10/2007 09:00:00, 1104408 bytes
Cap Flags: 0x0
Format Flags: 0x0
Description: Realtek Digital Input (Realtek High Definition Audio)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5443 (English)
Driver Attributes: Final Retail
Date and Size: 7/10/2007 09:00:00, 1104408 bytes
Cap Flags: 0x0
Format Flags: 0x0
-------------------
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
Poll w/ Interrupt: No
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x1002, 0x4375
| Matching Device ID: usb\root_hub
| Service: usbhub
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
|
+ Microsoft PS/2 Mouse
| Matching Device ID: *pnp0f03
| Service: i8042prt
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 56.3 GB
Total Space: 239.4 GB
File System: NTFS
Model: Maxtor 6L250S0 ATA Device
Drive: D:
Model: TSSTcorp CD/DVDW SH-W162C ATA Device
Driver: c:\windows\system32\drivers\cdrom.sys, 6.00.6000.16386 (Swedish), , 0 bytes
Drive: F:
Model: BP4880T ICE726B ATA Device
Driver: c:\windows\system32\drivers\cdrom.sys, 6.00.6000.16386 (Swedish), , 0 bytes
--------------
System Devices
--------------
Name: Realtek RTL8139/810x Family Fast Ethernet NIC #2
Device ID: PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\4&B4B0D3&0&08A4
Driver: n/a
Name: Realtek RTL8139/810x Family Fast Ethernet NIC
Device ID: PCI\VEN_10EC&DEV_8139&SUBSYS_191C1462&REV_10\4&B4B0D3&0&18A4
Driver: n/a
Name: NVIDIA GeForce 8800 GTS
Device ID: PCI\VEN_10DE&DEV_0193&SUBSYS_823C1043&REV_A2\4&3494133B&0&0010
Driver: n/a
Name: AMD Miscellaneous Configuration
Device ID: PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&267A616A&0&C3
Driver: n/a
Name: AMD DRAM and HyperTransport(tm) Trace Mode Configuration
Device ID: PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&267A616A&0&C2
Driver: n/a
Name: AMD Address Map Configuration
Device ID: PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&267A616A&0&C1
Driver: n/a
Name: AMD HyperTransport(tm) Configuration
Device ID: PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&267A616A&0&C0
Driver: n/a
Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_1002&DEV_5A34&SUBSYS_59501002&REV_00\3&267A616A&0&10
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1002&DEV_5950&SUBSYS_59501002&REV_10\3&267A616A&0&00
Driver: n/a
Name: High Definition Audio Controller
Device ID: PCI\VEN_1002&DEV_437B&SUBSYS_71911462&REV_01\3&267A616A&0&A2
Driver: n/a
Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_1002&DEV_437A&SUBSYS_71411462&REV_80\3&267A616A&0&88
Driver: n/a
Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_1002&DEV_4379&SUBSYS_71411462&REV_80\3&267A616A&0&90
Driver: n/a
Name: ATI I/O Communications Processor LPC Controller
Device ID: PCI\VEN_1002&DEV_4377&SUBSYS_00000000&REV_80\3&267A616A&0&A3
Driver: n/a
Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_1002&DEV_4376&SUBSYS_71911462&REV_80\3&267A616A&0&A1
Driver: n/a
Name: ATI I/O Communications Processor USB 1.1 OHCI controller
Device ID: PCI\VEN_1002&DEV_4375&SUBSYS_71911462&REV_80\3&267A616A&0&99
Driver: n/a
Name: ATI I/O Communications Processor USB 1.1 OHCI controller
Device ID: PCI\VEN_1002&DEV_4374&SUBSYS_71911462&REV_80\3&267A616A&0&98
Driver: n/a
Name: ATI I/O Communications Processor USB 2.0 EHCI controller
Device ID: PCI\VEN_1002&DEV_4373&SUBSYS_71911462&REV_80\3&267A616A&0&9A
Driver: n/a
Name: ATI I/O Communications Processor SMBus Controller
Device ID: PCI\VEN_1002&DEV_4372&SUBSYS_71911462&REV_81\3&267A616A&0&A0
Driver: n/a
Name: ATI I/O Communications Processor PCI Bus Controller
Device ID: PCI\VEN_1002&DEV_4371&SUBSYS_00000000&REV_80\3&267A616A&0&A4
Driver: n/a
------------------
DirectShow Filters
------------------
DirectShow Filters:
WMAudio Decoder DMO,0x00800800,1,1,,
WMAPro over S/PDIF DMO,0x00600800,1,1,,
WMSpeech Decoder DMO,0x00600800,1,1,,
MP3 Decoder DMO,0x00600800,1,1,,
Mpeg4s Decoder DMO,0x00800001,1,1,,
WMV Screen decoder DMO,0x00600800,1,1,,
WMVideo Decoder DMO,0x00800001,1,1,,
Mpeg43 Decoder DMO,0x00800001,1,1,,
Mpeg4 Decoder DMO,0x00800001,1,1,,
ffdshow MPEG-4 Video Decoder,0xff800001,2,1,ffdshow.ax,1.00.0002.1997
Full Screen Renderer,0x00200000,1,0,,6.06.6000.16386
ffdshow raw video filter,0x00200000,2,1,ffdshow.ax,1.00.0002.1997
ffdshow Audio Decoder,0x3fffffff,1,1,ffdshow.ax,1.00.0002.1997
DV Muxer,0x00400000,0,0,,6.06.6000.16386
Color Space Converter,0x00400001,1,1,,6.06.6000.16386
WM ASF Reader,0x00400000,0,0,,11.00.6000.6324
Screen Capture filter,0x00200000,0,1,wmpsrcwp.dll,11.00.6000.6324
AVI Splitter,0x00600000,1,1,,6.06.6000.16386
VGA 16 Color Ditherer,0x00400000,1,1,,6.06.6000.16386
Microsoft MPEG-2 Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,11.00.5840.6324
RealVideo Decoder,0x00600000,1,1,RealMediaSplitter.ax,1.00.0001.0002
AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,6.06.6000.16386
StreamBufferSink,0x00200000,0,0,sbe.dll,6.06.6000.16386
MJPEG Decompressor,0x00600000,1,1,,6.06.6000.16386
MPEG-I Stream Splitter,0x00600000,1,2,,6.06.6000.16386
SAMI (CC) Parser,0x00400000,1,1,,6.06.6000.16386
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.6000.16386
MPV Decoder Filter,0x00500001,1,1,Mpeg2DecFilter.ax,1.00.0000.0003
MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,6.06.6000.16386
Microsoft MPEG-2 Video Encoder,0x00200000,2,0,msmpeg2enc.dll,11.00.6000.6324
FLV Splitter,0x00600000,1,1,FLVSplitter.ax,1.00.0000.0001
Internal Script Command Renderer,0x00800001,1,0,,6.06.6000.16386
MPEG Audio Decoder,0x03680001,1,1,,6.06.6000.16386
WavPack Audio Decoder,0x00600000,1,1,WavPackDSDecoder.ax,1.00.0003.0431
DV Splitter,0x00600000,1,2,,6.06.6000.16386
Video Mixing Renderer 9,0x00200000,1,0,,6.06.6000.16386
Haali Media Splitter,0x00800001,0,1,splitter.ax,1.07.0077.0005
Haali Media Splitter (AR),0x00400000,1,1,splitter.ax,1.07.0077.0005
Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,11.00.6000.6324
Xvid MPEG-4 Video Decoder,0x00800000,1,1,xvid.ax,
ACM Wrapper,0x00600000,1,1,,6.06.6000.16386
Video Renderer,0x00800001,1,0,,6.06.6000.16386
MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,6.06.6000.16386
Line 21 Decoder,0x00600000,1,1,,6.06.6000.16386
Video Port Manager,0x00600000,2,1,,6.06.6000.16386
Video Renderer,0x00400000,1,0,,6.06.6000.16386
Haali Video Renderer,0x00200000,1,0,dxr.dll,
RealMedia Source,0x00600000,0,0,RealMediaSplitter.ax,1.00.0001.0002
DivX Decoder Filter,0xff800000,1,1,divxdec.ax,6.06.0001.0004
WM ASF Writer,0x00400000,0,0,,11.00.6000.6324
VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,6.00.6000.16386
File writer,0x00200000,1,0,,6.06.6000.16386
Haali Simple Media Splitter,0x00200000,0,1,splitter.ax,1.07.0077.0005
DirectVobSub,0x00200000,2,1,VSFilter.dll,1.00.0001.0003
RealAudio Decoder,0x00600000,1,1,RealMediaSplitter.ax,1.00.0001.0002
DirectVobSub (auto-loading version),0x00800002,2,1,VSFilter.dll,1.00.0001.0003
DVD Navigator,0x00200000,0,3,,6.06.6000.16386
Overlay Mixer2,0x00200000,1,1,,6.06.6000.16386
Haali Matroska Muxer,0x00200000,1,0,splitter.ax,1.07.0077.0005
AVI Draw,0x00600064,9,1,,6.06.6000.16386
Microsoft MPEG-2 Audio Encoder,0x00200000,2,0,msmpeg2enc.dll,11.00.6000.6324
WST Pager,0x00800000,1,1,WSTPager.ax,6.06.6000.16386
MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,6.06.6000.16386
DV Video Decoder,0x00800000,1,1,,6.06.6000.16386
ffdshow Audio Processor,0x00200000,1,1,ffdshow.ax,1.00.0002.1997
SampleGrabber,0x00200000,1,1,qedit.dll,6.06.6000.16386
Null Renderer,0x00200000,1,0,qedit.dll,6.06.6000.16386
MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,6.06.6000.16386
Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,11.00.6000.6324
FLV Source,0x00600000,0,0,FLVSplitter.ax,1.00.0000.0001
StreamBufferSource,0x00200000,0,0,sbe.dll,6.06.6000.16386
Smart Tee,0x00200000,1,2,,6.06.6000.16386
Overlay Mixer,0x00200000,0,0,,6.06.6000.16386
AVI Decompressor,0x00600000,1,1,,6.06.6000.16386
AVI/WAV File Source,0x00400000,0,2,,6.06.6000.16386
Wave Parser,0x00400000,1,1,,6.06.6000.16386
MIDI Parser,0x00400000,1,1,,6.06.6000.16386
Multi-file Parser,0x00400000,1,1,,6.06.6000.16386
File stream renderer,0x00400000,1,1,,6.06.6000.16386
WavPack Audio Splitter,0x00600000,1,1,WavPackDSSplitter.ax,1.00.0003.0277
Microsoft MPEG-1/DD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,11.00.5840.6324
RealMedia Splitter,0x00600000,1,1,RealMediaSplitter.ax,1.00.0001.0002
AVI Mux,0x00200000,1,0,,6.06.6000.16386
Line 21 Decoder 2,0x00600002,1,1,,6.06.6000.16386
File Source (Async.),0x00400000,0,1,,6.06.6000.16386
File Source (URL),0x00400000,0,1,,6.06.6000.16386
Haali Video Sink,0x00200000,1,0,splitter.ax,1.07.0077.0005
Infinite Pin Tee Filter,0x00200000,1,1,,6.06.6000.16386
Enhanced Video Renderer,0x00200000,1,0,evr.dll,5.00.0001.0001
BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,6.06.6000.16386
MPEG Video Decoder,0x40000001,1,1,,6.06.6000.16386
WDM Streaming Tee/Splitter Devices:
Tee/Sink-to-Sink Converter,0x00200000,1,1,,6.00.6000.16386
WDM Streaming Data Transforms:
Microsoft Kernel DRM Audio Descrambler,0x00200000,1,1,,6.00.6000.16386
Video Compressors:
WMVideo8 Encoder DMO,0x00600800,1,1,,
WMVideo9 Encoder DMO,0x00600800,1,1,,
MSScreen 9 encoder DMO,0x00600800,1,1,,
DV Video Encoder,0x00200000,0,0,,6.06.6000.16386
ffdshow video encoder,0x00100000,1,1,ffdshow.ax,1.00.0002.1997
MJPEG Compressor,0x00200000,0,0,,6.06.6000.16386
Cinepak Codec by Radius,0x00200000,1,1,,6.06.6000.16386
DivX® 6.6.1 Codec (1 Logical CPU),0x00200000,1,1,,6.06.6000.16386
ffdshow Video Codec,0x00200000,1,1,,6.06.6000.16386
Fraps Video Decompressor,0x00200000,1,1,,6.06.6000.16386
Intel IYUV codec,0x00200000,1,1,,6.06.6000.16386
Intel IYUV codec,0x00200000,1,1,,6.06.6000.16386
Microsoft RLE,0x00200000,1,1,,6.06.6000.16386
Microsoft Video 1,0x00200000,1,1,,6.06.6000.16386
Microsoft Windows Media Video 9,0x00200000,1,1,,6.06.6000.16386
Xvid MPEG-4 Codec,0x00200000,1,1,,6.06.6000.16386
DivX® 6.6.1 YV12 Decoder,0x00200000,1,1,,6.06.6000.16386
Audio Compressors:
WM Speech Encoder DMO,0x00600800,1,1,,
WMAudio Encoder DMO,0x00600800,1,1,,
IMA ADPCM,0x00200000,1,1,,6.06.6000.16386
PCM,0x00200000,1,1,,6.06.6000.16386
Microsoft ADPCM,0x00200000,1,1,,6.06.6000.16386
GSM 6.10,0x00200000,1,1,,6.06.6000.16386
CCITT A-Law,0x00200000,1,1,,6.06.6000.16386
CCITT u-Law,0x00200000,1,1,,6.06.6000.16386
MPEG Layer-3,0x00200000,1,1,,6.06.6000.16386
Audio Capture Sources:
Microphone (Realtek High Defini,0x00200000,0,0,,6.06.6000.16386
Realtek Digital Input (Realtek ,0x00200000,0,0,,6.06.6000.16386
Midi Renderers:
Default MidiOut Device,0x00800000,1,0,,6.06.6000.16386
Microsoft GS Wavetable Synth,0x00200000,1,0,,6.06.6000.16386
WDM Streaming Capture Devices:
Realtek HD Digital input,0x00200000,1,1,,6.00.6000.16386
,0x00000000,0,0,,
,0x00000000,0,0,,
,0x00000000,0,0,,
,0x00000000,0,0,,
WDM Streaming Rendering Devices:
Realtek HD Audio output,0x00200000,1,1,,6.00.6000.16386
Realtek HDA SPDIF Out,0x00200000,1,1,,6.00.6000.16386
BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.6000.16386
Multi-Instance Capable VBI Codecs:
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.6000.16386
BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.6000.16386
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.6000.16386
BDA CP/CA Filters:
Decrypt/Tag,0x00600000,1,0,EncDec.dll,6.06.6000.16386
Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.6000.16386
XDS Codec,0x00200000,0,0,EncDec.dll,6.06.6000.16386
WDM Streaming Communication Transforms:
Tee/Sink-to-Sink Converter,0x00200000,1,1,,6.00.6000.16386
Audio Renderers:
Speakers (Realtek High Definiti,0x00200000,1,0,,6.06.6000.16386
Default DirectSound Device,0x00800000,1,0,,6.06.6000.16386
Default WaveOut Device,0x00200000,1,0,,6.06.6000.16386
DirectSound: Realtek Digital Output (Realtek High Definition Audio),0x00200000,1,0,,6.06.6000.16386
DirectSound: Speakers (Realtek High Definition Audio),0x00200000,1,0,,6.06.6000.16386
Realtek Digital Output (Realtek,0x00200000,1,0,,6.06.6000.16386
I took Turey's installer (first time install), tagged the stuff I felt important (everything except the user made campaigns), and let it download.
I set the game up, all features on, and well.....this is what I get.
(http://myimg.info/thumbs/viu1194125864l.jpg) (http://myimg.info/viewer.php?id=viu1194125864l.jpg)
(http://myimg.info/thumbs/cqs1194125864o.jpg) (http://myimg.info/viewer.php?id=cqs1194125864o.jpg)
(http://myimg.info/thumbs/rgh1194125865h.jpg) (http://myimg.info/viewer.php?id=rgh1194125865h.jpg)
Most fighters are like that. Herc 1 isn't as an example, but most others are.
Any thoughts?
-
A similar thing happened to INFA. I restarted my computer and it worked. Try that. It probably won't work, but it's worth a try.
-
It's not that.
-
The only time I've seen something like that is when I tried running the game with textures larger than the maximum size my card could handle. But nothing in the media VPs should be causing that issue.
What happens if you run without media VPs?
-
A guess, you've got an nVidia card, you've played Crysis Demo and you've installed 169.xx ForceWare drivers. ;)
169.xx drivers are defective in OGL (you can find more complaints about Doom3 and other OGL games in several forums). Go back to 163.75 or similar.
Check this post of mine (http://www.hard-light.net/forums/index.php/topic,50258.msg1016001.html#msg1016001) in 28-10-2007 build thread.
-
Now that is likely, yeah, I've got the beta Crysis drivers, but I'm not retarding them just to get the textures to properly display in this game. And yeah, the Herc2 in your post looks exactly like mine.
Kara, when I take the mvp folder out, I get the stock default textures, that work normally as they should.
-
I too had this problem; run the beta 3.6.10 build with the normal map test .vp. It ran excellent with no weird bugs for me.
-
Tried four different builds. Same on all.
-
Try with D3D. If that looks ok its probably just because of the crappy OGL driver.
-
Same thing on D3D, all four builds.
-
You'll get the same thing on d3d since there is no d3d anymore and it just uses OGL.
-
Yeah, I know, I tried it anyway just to settle the need for trying pointless things.
-
When the drivers aren't beta, let us know. After 2 years of chasing driver bugs with Torque just to have the manufacture change the underpinnings, I have found its a pointless endeavor to "fix" something that happens in bleeding edge drivers.
It will break again in a new and different way on the next iteration of those drivers.
-
Sure thing.
-
What happens when you play with different options in the nVidia Control Panel? It might be a certain feature that's buggered with the beta drivers, that will disappear if you turn a certain option on/off.
-
Hmm.. anyone know the last build that supported D3D?
Its not too good for playing, but still useful in troubleshooting some things.
-
3.6.9 final, non-BtRL edition, IIRC
-
Really? I thought there was more recent builds available from the stable branch.
-
Really? I thought there was more recent builds available from the stable branch.
You can always make a build with D3D, it's just left out by default now.
-
Yea? I guess it won't keep compiling for long though.
I don't need that myself, but it would be nice to be able to throw a link for people fighting with stuff.
-
Really? I thought there was more recent builds available from the stable branch.
http://www.freespacefaq.com/Downloads/BtRL/BtRL_D3D_Exes.zip
That's slightly newer. It's the version from BtRL's last patch so it's 3.6.9 plus the glide changes and a few other minor fixes.
-
Thanks Kara :yes:
-
nvidia has just launched 169.09 drivers.
I'm a bit tired about installing and unistalling 169.xx drivers because of being defective. So could any 169.xx driver user test this new release?
Known issues, at least in my system (Vista 32 bit + 8800 GTX):
- A lot of resolutions are missing. As example 1280x960 isn't available anymore. (You can check it in Windows Display Properties or in Launcher > Video > Resolution).
- GLSL doesn't seem to work.
- A lot of ships have a strange chessboard texture effect. Look at the initial screenshots of this same thread (http://www.hard-light.net/forums/index.php/topic,50345.msg1017311.html#msg1017311).
Thanks in advance.
-
the 169.09 drivers work fine in FSO, except for GLSL. I'm sure I'll be able to run this. :)
[EDIT] I wonder if your problem is because you're using Vista? :P
Man, I wish D3D worked. Everything loads wicked fast and the textures are much sharper. Transparencies aren't handled very well though.
-
So, if the GLSL is broken, then they do NOT work fine.
Half a driver is no driver in my opinion, especially not with OGL being a highly used impliment of gaming.
And yeah, DX make look sharp and fast, but it's nothing compared to a properly coded OpenGL.
-
They work fine in everyone else.
-
I've just read the 169.xx release notes > Open issues. It doesn't say anything different from 163.75 which works fine. But nevertheless here you are, in case it's useful for coders:
OpenGL Application Issues
The following are known compatibility issues for OpenGL applications developed
under Windows XP:
• Mixed GDI and OpenGL rendering does not work.
A number of applications use GDI to render UI components and object
highlighting. This is not supported in the Windows Vista driver model.
NVIDIA recommends converting GDI rendering to OpenGL.
The following are some applications that are known to have this issue:
Maya 7.01
OneSpace Designer Modeling
• Applications, Tools, and Benchmarks not Supported Under Windows Vista
GLperf
3ds max 8 (later releases may be supported)
CATIA V5R15 (V5R16 is supported)
PTC’s CDRS 2001
• Front buffered rendering may be slow, especially when DWM is enabled.
Flushing the rendering queue while rendering to the front buffer may cause the
window manager to recomposite. Applications should therefore minimize the
frequency with which they flush the rendering queue.
-
Ooops a double post ;)
I've just installed 169.09 and again it doesn't work fine. It still suffers the three issues I posted above.
-
Blame Vista.
-
It's like that on XP, too. :) And since I won't be playing Crysis any time soon, I'm sticking with the 163.75 drivers for the time being. :p
-
You can still run Crysis with 163.75... I did.. it's just that it runs a bit slower.
-
You can still run Crysis with 163.75... I did.. it's just that it runs a bit slower.
That's what I'm doing ;). As I said in other thread, sorry Crysis but FSOpen rules :pimp:
Offtopic: BTW the difference I get with my setting in the GPU benchmark is from 24.8 fps (169.09) to 21.3 fps (163.75); more or less 15%.
-
Hey everyone, I've got sumthings to ask, since I don't want to make any new thread.
I've make a search for free space system requirement but so far no luck.
Well, my question is:
-Can I play SCP with an old T&L ATI Radeon 7200??? I don't need all of its features, i just need to play with the beautiful model.
-
To be honest, I don't think a 7200 will cut it.
If it somehow does work, it'll just barely scrape by.
-
Hey guys, nvidia has just released 169.21 which:
- It says is WHQL Candidate.
- GLSL and general rendering work again. And no more chess-pattern ships.
BUT
- 1280 x 960 resolution (and many others) is still missing.
So please could any one confirm these issues. And, please, does anyone know a hack to enable 1280 x 960 resolution?
-
Is 169.21 an official driver or another Crysis-esque driver?
-
Is 169.21 an official driver or another Crysis-esque driver?
As I've said, it says it's "WHQL Candidate" recommended for DirectX 9, 10 and OGL games. It's not just a Crysis driver (or at least that's what nvidia says). Go to nvidia beta download and see it by yourself.
-
Uh, ok. But it better not have any OGL problems. :p
-
Oooops, an update about 169.21
Now, OGL rendering ONLY works with GLSL. If you use -no_glsl then you get the chess board misplaced texture effect. (I upload a screenshot)
So it's a bit scary that this driver release is "WHQL Candidate" :nervous: :nervous:
[attachment deleted by admin]
-
Do normal maps work?
-
Do normal maps work?
Yes, normal and height maps work. Only old -no_glsl rendering is broken :confused: :confused:
-
Ok screw it, I'm not downloading it until there's an official release. :P
-
Oooops, an update about 169.21
Now, OGL rendering ONLY works with GLSL. If you use -no_glsl then you get the chess board misplaced texture effect. (I upload a screenshot)
So it's a bit scary that this driver release is "WHQL Candidate" :nervous: :nervous:
WHQL doesn't really mean anything. I think Microsoft just tests if it works in basic Windows programs. It's fairly common for the beta drivers (both official and leaked) to be faster and/or more stable than the release ones. :p
-
ARSPR, I've got the missing resolutions.
(http://img412.imageshack.us/img412/7205/launcherls8.png)
-
Went back to 163.75 since a couple of my games were complaining about not being able to load stuff.
-
ARSPR, I've got the missing resolutions.
(http://img412.imageshack.us/img412/7205/launcherls8.png)
Do you use XP or Vista?
I run Vista and I don't have the resolutions even in Windows Display Properties.
-
I'm on XP. The bug-free OS. :P
-
I'm on XP. The bug-free OS. :P
Could you upload nv_disp.inf from the temporal installation folder, please?
I mean when you execute 169.21_forceware_xxxxWhatever.exe, it firstly decompresses itself to a temporary folder, usually C:\nvidia\WinXP\169.21\IS or similar. Then the setup is really launched from that folder. You can find nv_disp.inf there.
-
I don't seem to have that folder anymore. :wtf:
-
Btw, normals are working on Nvidia's 169.21 beta drivers. Yay. :)
-
Uh, yeah, we just said that. :P
-
Uh, yeah, we just said that. :P
D'oh, totally missed that on the previous page. :(
-
I don't seem to have that folder anymore. :wtf:
Re-execute the 169.21_forceware_xxxxWhatever.exe, then leave setup waiting for your input and use the Windows + E to get Explorer... find the folder, copy it to another location, then cancel setup.
-
nVidia has released 169.25 which only runs fine with GLSL like 169.21.
OTOH I've made a hack to enable a lot of missing resolutions (1280x960 among others). This issue seems to happen in Vista, not in XP:
1. Run the driver exe file, decompress it and then cancel.
2. Go to the decompressed auxiliary folder and edit nv_disp.inf
3. Instead of these lines, which don't include the missing resolutions:
HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 720x480 720x576=1;SHV 1680x1050 2048x1536x32=1;1920x1200x32 1920x1440x8,16=1D;640x480 800x600 1024x768 1280x768 1280x1024 1600x1200 1920x1200x8,16=3D;1920x1440x32=9;1920x1080=C01E;2048x1536x8,16=D;1152x864 1440x900=FFF;{400-42F,600,611}S 1920x1440x64 2048x1536x64=1F;640x480x64 800x600x64=1FC2;848x480x64 960x600x64=1FFF;1920x1200x64=2;{191-19E,400-42F,600-6E4}S 720x480x64 720x576x64 1680x1050x64=1;"
HKR,, NV_Modes, %REG_SZ_APPEND%, "640x480x64 800x600x64 1024x768x64 1280x768x64 1280x1024x64 1600x1200x64=3D;720x576x64=8032;1920x1080x64=C01E;1152x864x64 1440x900x64=FFF;{40-6E4}S 720x576=8032;{40-16A,1D0-611}SHV 2048x1536x8,16=12;1920x1440x32=16;2048x1536x32=1E;1920x1080x32=1F;640x480 800x600 1024x768x8,16=1FC2;848x480 960x600=1FFF;1600x1200x32 1920x1200 1920x1440x8,16=2;1280x768x32 1280x1024x32=3C2;1920x1080x8,16=3F;1280x720x32 1280x800x32 1280x960x32 1360x768x32=3FF;1600x1200x8,16=42;"
HKR,, NV_Modes, %REG_SZ_APPEND%, "1280x768x8,16 1280x1024x8,16=7C2;1280x720x8,16 1280x800x8,16 1280x960x8,16 1360x768x8,16=7FF;1024x768x32=FC2;""I've used the following one obtained from 163.75:
HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 640x480 1280x768 1280x800 1360x768 1920x1200=1;800x600 848x480 960x600 1024x768 1152x864 1280x960 1280x1024 1600x1200 1920x1440 2048x1536=3B;{191-19E,400-42F}S 640x480x64 1280x768x64 1280x800x64 1360x768x64 1680x1050 1920x1200x64=1;800x600x64 848x480x64 960x600x64 1024x768x64 1152x864x64 1280x960x64 1280x1024x64 1600x1200x64 1920x1440x64 2048x1536x64=3B;"
4. Install the driver running the setup.exe in the auxiliary decompressed folder.
And it seems to work fine. I've got 1280x960 again :yes:
-
Texturing is still broken on most models in 169.25.
-
169.21 has gone official in XP (while 163.75 is kept official for Vista).
I suppose these are bad news because now FS2 doesn't work fine with OFFICIAL driver release. (I suppose it's the same as 169.21 beta launched before. Some testing on XP systems would be welcomed) :(
-
169.21 has gone official in XP (while 163.75 is kept official for Vista).
It's official on Vista too:
http://www.nvidia.com/object/winvista_x64_169.25_whql.html (http://www.nvidia.com/object/winvista_x64_169.25_whql.html)
I suppose these are bad news because now FS2 doesn't work fine with OFFICIAL driver release. (I suppose it's the same as 169.21 beta launched before. Some testing on XP systems would be welcomed) :(
So is SCP going to be ATI only now?
-
No one said that.
That would be a foolish move even if they had even considered making it ATi exclusive. Most of us here use nVidia cards.
-
Tried clearing the .IBXs in the data\cache folder?
-
.ibx files are for the models, not the textures.
-
Did a clean install of XP with 169.21. Ran Tureys installer. So, everything clean.
Grabbed latest XT build. Only four ships are screwed-ish up. (This is with normal mapping enabled, but with the nm_test.vp not yet installed):
Herc Mark II
Myrmidon
Serapis
Aten
All four show funcky-fresh texturing even under default settings. Might the problem with the texture more be a fault of models and not necessarily the engine or drivers? Granted, driver revisions always break something, but what if it broke something by fixing something nobody ever knew was broken in the first place?
I've ran both the 169.21 Beta and WHQL with the exact same results. Other than the texturing, it all looks and runs perfectly.
-
I posted in this thread before but ARSPR wanted me to post here instead, I also get the checkerd ships and I use the new 169.25 Official drivers for Vista 32-bit.
Still dosent seem to work, and by the way the "no_glsl" flag you simply input as "no_glsl" in the custom flag field in the launcher right????
-
I posted in this thread before but ARSPR wanted me to post here instead, I also get the checkerd ships and I use the new 169.25 Official drivers for Vista 32-bit.
Still dosent seem to work, and by the way the "no_glsl" flag you simply input as "no_glsl" in the custom flag field in the launcher right????
Several comments:
- GLSL (shaders) rendering is only present in newest beta builds. As example this one (http://www.hard-light.net/forums/index.php/topic,50258.0.html), although it's a bit old and it's not really going to become 3.6.10. Official 3.6.9. doesn't have GLSL so it isn't going to run fine, (it's like disabling GLSL in newest builds).
- 169.21 and 169.25 should work fine with a GLSL capable build and GPU. Or at least you will be the very first one with troubles...
- All the flags are typed with a - before. So it's -no_glsl, not no_glsl. Instead of typing it you can tick it in Troubleshot flag group IIRC. Something like "Disable GLSL". (I'm not in my PC so I don't have FSOpen available right now). BUT you always need a GLSL capable build in order to disable it ;). GLSL >> it should render fine; no GLSL >> chess board, (or maybe zebra stripes), effect.
-
Ok fixed it with the new build everything seems to work now so thank you. maybe you should make an anouncement or a sticky or something it seems to me that this is something that alot of people will ask about.
-
Did a clean install of XP with 169.21. Ran Tureys installer. So, everything clean.
Grabbed latest XT build. Only four ships are screwed-ish up. (This is with normal mapping enabled, but with the nm_test.vp not yet installed):
Herc Mark II
Myrmidon
Serapis
Aten
All four show funcky-fresh texturing even under default settings. Might the problem with the texture more be a fault of models and not necessarily the engine or drivers? Granted, driver revisions always break something, but what if it broke something by fixing something nobody ever knew was broken in the first place?
I've ran both the 169.21 Beta and WHQL with the exact same results. Other than the texturing, it all looks and runs perfectly.
For me, the Herc 2 is fine except in the targeting box. (169.25 and 3.6.10-20071028 on Vista64 and 8800gt)
[attachment deleted by ninja]
-
For me, the Herc 2 is fine except in the targeting box. (169.25 and 3.6.10-20071028 on Vista64 and 8800gt)
Although it's a resource waste, try forcing LOD0 in target window (by default LOD1 is used).
Use the next WhatEverNameYouWant-shp.tbm file placed in MediaVPS\data\tables folder:
#Ship Classes
$Name: GTF Hercules Mark II
+nocreate
$POF target LOD: 0
#End
Nevertheless, I get good rendering even in target window :confused: :confused: (Vista 32 bit + 8800 GTX + 169.25)
EDITED ------
OTOH your screen is distorted because FS2 is designed to work with a 4:3 resolution aspect ratio. I also have a 1680x1050 monitor but I use:
- Standard 1280 x 960.
OR
- I've enabled a custom 1400 x 1050 x 32 bit x 60 Hz through RivaTuner utility >> Custom display modes / refresh rate wizard.
-
For me, the Herc 2 is fine except in the targeting box. (169.25 and 3.6.10-20071028 on Vista64 and 8800gt)
Although it's a resource waste, try forcing LOD0 in target window (by default LOD1 is used).
Use the next WhatEverNameYouWant-shp.tbm file placed in MediaVPS\data\tables folder:
#Ship Classes
$Name: GTF Hercules Mark II
+nocreate
$POF target LOD: 0
#End
Nevertheless, I get good rendering even in target window :confused: :confused: (Vista 32 bit + 8800 GTX + 169.25)
That fixes it. But if I set detail to low, none of the lods in the main view look bad.
Wait a second... I deleted the tbm file and now it's fixed... :wtf:
Ok, I figured it out: I start the mission, Herc2 in targeting box has zebra textures. I set model detail to 3 "lights" (4 and 5 have the zebra textures), and it's ok. I set it back to 5 lights, and it's still fine... And I don't see any change in the targeting box model
EDIT: yeah, i know about the distortion. Doesn't bother me now, since I don't play, just test. Widescreen has a bug though, the targeting boxes and all that stuff is incorrectly placed
EDIT2: I took that with 1680x1050, there shouldn't be any distortion there
-
ForceWare mysteries...
I've got all my detail settings at maximum.
Nx, in case you haven't read it, please check my edited former post comments about your resolution.
Ah, and remember to set your ForceWare settings so NO SCALING is applied when displaying a resolution smaller than your LCD capabilities.
-
ForceWare mysteries...
I've got all my detail settings at maximum.
Nx, in case you haven't read it, please check my edited former post comments about your resolution.
Ah, and remember to set your ForceWare settings so NO SCALING is applied when displaying a resolution smaller than your LCD capabilities.
Try setting them to minimum, going back to the game, then back to maximum. That's what fixes it form me
-
this also happens on Linux, with official 169.07 drivers.
crap on a crutch
-
nVidia has launched 169.28 beta which at least in Vista:
- runs fine in GLSL
- doesn't run fine with -no_glsl
- still miss a lot of resolutions. I'm using RivaTuner to enable useful resolutions as example standard 1280x960 and custom 1400x1050 so this issue doesn't bother me any more.
Till now, nothing new.
But now, the important part of this post starts. ;7 ;7
I've discovered that I can get the models to render fine WITH NO GLSL at least in F3 Lab. Maybe this can be a clue to detect what the hell happens. I'm using XT1207 + shaders from sdr1119.vp + Mediavps 3.6.8. zeta.
- Run the game in GLSL (default, no flag needed). Go to F3 Lab. Tick Render Options > Fixed Render Pipeline (ie. no shaders).
- Then open any model. As example Ulysses LOD 0. I get the expected messed up textures. (See attached 01-Fixed Pipeline is ticked before selecting.jpg)
- Then untick Fixed Render Pipeline. Shaders, and then normal & parallax, are enabled and you get the new and pretty looking. (See attached 02-Fixed Pipeline is unticked - GLSL.jpg)
- Then tick AGAIN Fixed Render Pipeline. Shaders are disabled, but the model looks fine with no messed textures. :wtf: :eek2: :confused: (See attached 03-Fixed Pipeline is ticked AGAIN.jpg)
- This happens with every new model you load. If Fixed Render Pipeline is selected BEFORE you load that model, the textures are FUBAR. But if you load the model with enabled shaders, and then you disable them, the model is rendered fine.
I hope this info can be useful ...
Can anyone confirm this behaviour? (Remember that used shaders need a SM 3.0 capable GPU - so 6xxx or above)
[attachment deleted by ninja]
-
According to ARSPR Ive had a related issue.
Running both Forceware 169.21 & 169.03 and fs2_open_3_6_9.exe I got this:
(http://img522.imageshack.us/img522/7038/fs2bugdn5.th.jpg) (http://img522.imageshack.us/my.php?image=fs2bugdn5.jpg)
The newer build slightly fixed it.
Running 169.21 and either fs2_open_3_6_10-20071028T.exe or fs2_open_3_6_10-20071007T.exe I get something similar. The ship in the middle will now appear 100% correctly (all of them do), but the same ship in the lower left corner where it shows your target still suffers the same bug as before (but not all of them). Iy only happens on the ships which are well lit.
[edit]My bad, in that particular picture both ships are fixed. However the results I explained can still be seen in many other missions, for eg A Lion at the Door.[/edit]
I guess what ever was done to normal ships between those 2 versions needs to happen for target view ships? I have no idea.
Running a 7900GS, AMD 64 X2 4600+ on Windows XP Pro SP2. Want more info/testing, just ask.
Just want to add, everyone involved in updating FS2 does an excellent job. Ive never seen community support for a game like this before.
-
Hmm. I've just gone back and done a clone of a fresh install on three machines. All of the eVGA cards. 8800 GTS 640, 8800 GT and 7600 GTS. Using every foreceware driver since 163.44 to current beta, I can no longer reproduce this issue under 3.6.9 or 3.6.10 provided by Turey's installer (that I cloned to the other machines) or the 1207 XT Build.
Buh? Now _I'm_ confused....and yes, I know these were clean installs of the driver, I used a clean install of the OS.
The only thing I can think of is how I'm doing the OS. Each install is actually being installed and run from a USB Stick with the forceware drivers directly integrated into the install source. (Meaning that the nVidia drivers are installed during the "Setup will complete in 39 Minutes" portion where it's installing new hardware.)
Very curious.
-
Are you using the 3.6.8 Z Media VPs? They're the only ones causing trouble for me, retail and 3.6.10b work fine.
-
Yeap, the render troubles are dependant on the exact model and texture.
Mediavps 3.6.10beta seem to work better than 3.6.8. (there's a completely new set of textures and models), but you can still find some issues.
EDITED ----
As example Herc II is FUBAR in my system
-
Hmm.. maybe we should take a closer look at the H2 maps, to try and see if we can find the critical factor, so to speak.
-
I've just tested nvidia 169.44
And as far as I've seen there's nothing new. -no_glsl still doesn't render fine.
-
Well, as for my SCP builds, I've been getting strange errors lately.
I was playing some modded campaigns, when the scp freezes and crashes.. then it happened in the mission room, and now i can't even 'log' with the pilot.. Previously I had some errors about low virtual momery, but I made the page fiole bigger so it's ok now..This happened in 369 and 3610, I couldn't get any logs out of debug. I have the error.log file though, if it helps.
Any ideas ?
EDIT: Got the debug file now, it's here.
[attachment deleted by ninja]
-
quick question why would you want to use no gsl ?
-
ARSPR: What video card do you have again? I've noticed that just about any 7xxx card (with few exceptions) are having issues with the 169.xx series drivers.
If you have an 8xxx series card, find a version set 171.17. They are WHQL for XP and have been doing phenomenally for me.
I've given up on Crysis "optimized" drivers. Love the game and the patches, but I always come back to the 171.17 (once they released, previously I just stuck with the 163.75). Also, Omega is back on the scene for nVidia drivers, but I cannot recommend them. I had edge blurring and "broadcast" distortion when ever ANY method of anti-aliasing was applied, (with and without Gamma and no matter what transparency option) but other people may have different results.
-
I've got a 8800 GTX + Vista 32 bit and I only use drivers from nVidia WEB. And the latest available driver is 169.44.
quick question why would you want to use no gsl ?
It's just a test. Remember that old GPUs don't support glsl (SM 3.0 required) and that the current OFFICIAL build is still 3.6.9 which doesn't support it either.
My posts here are just general info. Personally, I don't worry much about it
-
nvidia has released 174.74 beta drivers (http://www.nvidia.com/Download/Find.aspx?lang=en-us) for ALL cards, Vista and XP, 32 & 64-bit.
In guru3d forums someone posted that this driver solved "texture corruption with old games".
I'm outside home till monday so could anyone give them a try and check if:
+ GLSL rendering (ie XT builds with normal mapping support enabled) renders fine.
AND
+ old rendering, (official 3.6.9. build, newest 20080321 SVN trunk build (http://www.hard-light.net/forums/index.php/topic,52856.0.html) or -no_glsl within Taylor's XT builds), is fixed again. So chess-board pattern artifacts or white & black lines instead of textures are gone.
(Please remember that mediavp 3.6.8zeta models and textures are more prone to these troubles than mediavp 3.6.10beta ones).
-
I've been running the 171.17 WHQL drivers for XP (http://downloads.guru3d.com/ForceWare-171.17-WHQL-XP-(32-bit)-download-1848.html) since the day of release. They only work on 8xxx series cards, however.
Hopefully these drivers are the same thing but more broad spectrum. I think the broad spectrum part is what is hurting the drivers though. The should have 2 classes of unified drivers: Everything below the 8xxx series in one and 8xxx Above in another.
Hopefully these don't have the same performance impacts of the other 17x.xx drivers on older cards. I will try them on my 7600 GTS and find out.
**Edit: Have confirmed under basic 3.6.9, Stable Trunk and XT (with and withot -no_glsl) that there are no graphical corruptions under 3.6.8Z and 3.6.10B mediavp's.
-
I've just tested with 174.74 and I reconfirm that the graphical corruptions seem fixed.
-
Yay, I should get my new rig put together this week and hope to be able to show off all the new features at a LAN party this weekend, with a bunch of comp sci's around. Maybe I can generate some interest among them too :)
So it sounds like I should be able to find a fairly stable setup using an 8800 GTS 512 using the 17x.xx drivers now.