Rendering problems on maps with multiple systems

When I play on maps with multiple systems, the planets in one system end up very close to the sun of another system. This results in problems rendering models at those planets due to "glare" of the adjacent sun! I usually only see the planet, the mineral asteroids, and the little cities on the planet and nothing else. This only affects systems adjacent to other suns on the map. Systems opposite of the other suns are fine.

Here is my system information. I'm running v5.1.

------------------
System Information
------------------
Time of this report: 1/12/2008, 13:10:09
Machine name: TORNADO
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
Language: English (Regional Setting: English)
System Manufacturer: VIAK8T
System Model: AWRDACPI
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 Processor 3400+, MMX, 3DNow, ~2.2GHz
Memory: 2048MB RAM
Page File: 250MB used, 3689MB 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

------------
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 7800 GS
Manufacturer: NVIDIA
Chip type: GeForce 7800 GS
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_00F5&SUBSYS_1FA419F1&REV_A2
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (70Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.6371 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 9/17/2007 00:07:00, 5783040 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 9/17/2007 00:07:00, 6853088 bytes
Device Identifier: {D7B71E3E-43B5-11CF-A262-AF3F03C2CB35}
Vendor ID: 0x10DE
Device ID: 0x00F5
SubSys ID: 0x1FA419F1
Revision ID: 0x00A2
Revision ID: 0x00A2
Video Accel: ModeMPEG2_A ModeMPEG2_B 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_BOBVerticalStretch
{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_BOBVerticalStretch
{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_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
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: Realtek AC97 Audio
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1106&DEV_3059&SUBSYS_1415147B&REV_60
Manufacturer ID: 65535
Product ID: 65535
Type: WDM
Driver Name: ALCXWDM.SYS
Driver Version: 5.10.0000.5580 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 5/14/2004 10:24:10, 622172 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 192000
Static/Strm HW Mix Bufs: 33, 32
Static/Strm HW 3D Bufs: 33, 32
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: Realtek AC97 Audio
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: ALCXWDM.SYS
Driver Version: 5.10.0000.5580 (English)
Driver Attributes: Final Retail
Date and Size: 5/14/2004 10:24:10, 622172 bytes
Cap Flags: 0x41
Format Flags: 0xFFF

-----------
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
Realtek AC97 Audio, Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [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: Nostromo n52 Speedpad2
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x050D, 0x0815
FF Driver: n/a

Poll w/ Interrupt: No
Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x1106, 0x3038
| Matching Device ID: usb\root_hub
| Lower Filters: vulfntrs
| Service: usbhub
| Driver: usbhub.sys, 8/4/2004 07:00:00, 57600 bytes
| Driver: usbd.sys, 8/4/2004 07:00:00, 4736 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 8/4/2004 07:00:00, 52736 bytes
| Driver: kbdclass.sys, 8/4/2004 07:00:00, 24576 bytes
|
+ HID Keyboard Device
| Vendor/Product ID: 0x050D, 0x0815
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| OEMData: 03 00 88 11 18 00 00 00
| Flags 1: 04000000
| Driver: kbdhid.sys, 8/3/2004 21:58:36, 14848 bytes
| Driver: kbdclass.sys, 8/4/2004 07:00:00, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 00:01:08, 40840 bytes
| Driver: kbdclass.sys, 8/4/2004 07:00:00, 24576 bytes
|
+ Microsoft USB Wheel Mouse Optical
| Vendor/Product ID: 0x045E, 0x0040
| Matching Device ID: hid\vid_045e&pid_0040
| Service: mouhid
| Driver: mouclass.sys, 8/4/2004 07:00:00, 23040 bytes
| Driver: mouhid.sys, 8/4/2004 07:00:00, 12160 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x050D, 0x0815
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| OEMData: 03 00 88 11 18 00 00 00
| Flags 1: 04000000
| Driver: mouclass.sys, 8/4/2004 07:00:00, 23040 bytes
| Driver: mouhid.sys, 8/4/2004 07:00:00, 12160 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x050D, 0x0815
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| OEMData: 03 00 88 11 18 00 00 00
| Flags 1: 04000000
| Driver: mouclass.sys, 8/4/2004 07:00:00, 23040 bytes
| Driver: mouhid.sys, 8/4/2004 07:00:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 00:01:08, 40840 bytes
| Driver: mouclass.sys, 8/4/2004 07:00:00, 23040 bytes

----------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)

DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK

-------------------
DirectPlay Adapters
-------------------
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -

-----------------------
DirectPlay Voice Codecs
-----------------------
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
2,443 views 10 replies
Reply #1 Top
Yep, long since fixed internally. Thanks anyways though :)
Reply #2 Top

Yep, long since fixed internally. Thanks anyways though

End of quote


Thank goodness. It really made it difficult for me to try bigger maps. When can we hope to see this fix go live?
Reply #3 Top
At release.
Reply #4 Top
When can we hope to see this fix go live?
End of quote


in 23 days, 5 hours, and some odd minutes... for me, anyway. There is a countdown at the top of the page until release :D
Reply #5 Top
At the end of the countdown clock is when yarlen will tell us all they need another 10 minutes... :LOL:
Reply #6 Top
and another and another and another ;p
Reply #7 Top
Then I muat be imaging the fact that no matter what type of game I play, if it has multible galaxies, I cannot see any ships, or structures. I have saved games, that at least on my system do it everytime now.

System Specs:
P4 D935 3.2x2 L1 2x2mb
Biostar G965 Micro 775 Bios Ver 3.19
2 gig OCZ SOE DDR2 PC667
Asus 8600GT 256MB DDR3 PCIex16 Driver version (64Bit) 129.25
Creative SB X-Fi Fatal1ty XtremeGamer w/64mb X-ram
Maxtor SATA 100 Gig ver 1.5
Seagate ATA 125 Gig
Asus 1814BLT SATA ver 3.0

All Drivers are Updated to latest web builds. Vista 64bit w/SP1 RC1

The problem has happened in the WHQL driver version of 129.25 as well. I have 2 saved games, one that it happened on the second save, and one that it happened as soon as I started a new game.
I could not find the how to report a bug post, so please bear with me here. What files and where would you like them sent or displayed.
And honestly I cannot play the game the way it displays itself now, how can I as a paying tester here be convinced the bug is fixed if nothing is said or done about it before release.

Glenn A Nicholson
Reply #8 Top
As was said, the fix has not been released. Beta 4 has not been updated aside from one small patch before this issue was fixed and will not be (the codebase as it was in Beta 4 no longer exists, and hasn't for some time, making a patch impossible).

It is fixed in the final version of the game.
Reply #9 Top
how can I as a paying tester here be convinced the bug is fixed if nothing is said or done about it before release
End of quote


It's been mentioned many times prior to this, discussed, and reported nearly as many times as having been fixed internally (as many times as it's been reported since it was fixed...).

The public beta ended more than a month ago; the internal versions are so far removed from what is generally available that there's really not any more useful testing that can be done on it.... It remains mostly just to sate those who want to play now rather than waiting for release in two weeks.
Reply #10 Top
Thanks for the update, I have not been able to play the game since last year, due to new job and hours involved. I did not see the posts anouching this so I aploigize for the rough wording. To be quite honest I did not anticapte the release being this soon. I can wait until the final is released, again thanks for the update

Sincerely
Glenn A Nicholson