| View previous topic :: View next topic |
| Author |
Message |
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
 Posted: Mon Oct 13, 2008 7:36 pm Post subject: EVE Premium won't show textures |
 |
|
So, I just got this totally great new video card - and a new PSU because of said card, and its stated power draw of the PSU's total output - and now I have X back up and running. Now here's the problem: I can run EVE-Online normally, but when I turn on the "premium" content, All I see are the lights. No polygons, no ships, nothing. My xorg-conf file is below; note that I've enabled dri, and set its permissions correctly (the latter doesn't appear here, but I set its mode to '0666' in a Module section).
| Code: | Section "Module"
# This loads the DBE extension module.
Load "dbe"
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
Load "glx"
Load "dri"
EndSection
# **********************************************************************
# Server flags section. This contains various server-wide Options.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "DontZoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
# Set the basic blanking screen saver timeout.
Option "blank time" "10" # 10 minutes
# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.
Option "standby time" "120"
Option "suspend time" "130"
Option "off time" "240"
# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.
# Option "EstimateSizesAggresively" "0"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# Set the keyboard auto repeat parameters. Not all platforms implement
# this.
Option "AutoRepeat" "500 5"
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
# Option "XkbLayout" "de"
#
# or:
#
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for xorg
#
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
# The mouse protocol and device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.
# Option "Protocol" "Auto"
Option "Device" "/dev/input/mice"
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
Option "Protocol" "Auto"
# When using mouse connected to a PS/2 port (aka "MousePort"), set the
# the protocol as follows. On some platforms some other settings may
# be available.
# Option "Protocol" "PS/2"
# Baudrate and SampleRate are only for some older Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice, or any
# 3-button mouse where the middle button generates left+right button
# events.
# Option "ChordMiddle"
Option "Emulate3Buttons" "false"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
#Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
#EndSection
# Some examples of extended input devices
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
# The identifier line must be present.
Identifier "Samsung SyncMaster 244T (Analog)"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 31.5 # typical for a single frequency fixed-sync monitor
HorizSync 30-94 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# VertRefresh 60 # typical for a single frequency fixed-sync monitor
VertRefresh 56-75 # multisync
# VertRefresh 60, 65 # multiple fixed sync frequencies
# VertRefresh 40-50, 80-100 # multiple ranges of sync frequencies
# Modes can be specified in two formats. A compact one-line format, or
# a multi-line format.
# A generic VGA 640x480 mode (hsync = 31.5kHz, refresh = 60Hz)
# These two are equivalent
# ModeLine "640x480" 25.175 640 664 760 800 480 491 493 525
# Mode "640x480"
# DotClock 25.175
# HTimings 640 664 760 800
# VTimings 480 491 493 525
# EndMode
# These two are equivalent
# ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace
# Mode "1024x768i"
# DotClock 45
# HTimings 1024 1048 1208 1264
# VTimings 768 776 784 817
# Flags "Interlace"
# EndMode
ModeLine "1920x1200@75" 246.6 1920 2064 2272 2624 1200 1201 1204 1253 -hsync +vsync
# If a monitor has DPMS support, that can be indicated here. This will
# enable DPMS when the monitor is used with drivers that support it.
Option "dpms"
# If a monitor requires that the sync signals be superimposed on the
# green signal, the following option will enable this when used with
# drivers that support it. Only a relatively small range of hardware
# (and drivers) actually support this.
# Option "sync on green"
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
Section "Device"
# The Identifier must be present.
Identifier "EAH4870X2"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "fglrx"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# Various other lines can be specified to override the driver's automatic
# detection code. In most cases they are not needed.
# VideoRam 256
# Clocks 25.2 28.3
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# Various option lines can be added here as required. Some options
# are more appropriate in Screen sections, Display subsections or even
# Monitor sections.
Option "hw cursor" "off"
Option "AddARGBGLXVisuals" "true"
Option "UseEvents" "false"
Option "RenderAccel" "true"
Option "RandRRotation" "true"
EndSection
Section "Extensions"
Option "Composite" "enable"
EndSection
# **********************************************************************
# Screen sections.
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
# The Identifier, Device and Monitor lines must be present
Identifier "Default Screen"
Device "EAH4870X2"
Monitor "Samsung SyncMaster 244T (Analog)"
DefaultDepth 24
SubSection "Display"
Virtual 1920 1200
Depth 24
Modes "1920x1200@75"
EndSubSection
EndSection
|
Let me know if I need to give more detail.
Thanks!
EE |
|
| Back to top |
|
 |
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5934
|
| Posted: Mon Oct 13, 2008 10:21 pm Post subject: |
|
|
how are you playing it, via wine, or via their cedega build?
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Mon Oct 13, 2008 10:37 pm Post subject: |
|
|
I'm playing via wine. The cedega version doesn't properly identify my audio hardware, and generally sucks (not the least because it lacks the premium version). So I run it under wine, whichever is the most recent build.
Thanks,
EE |
|
| Back to top |
|
|
nutbar21
Apprentice
Joined: 05 Dec 2004
Posts: 205
Location: USA
|
| Posted: Wed Oct 22, 2008 2:05 am Post subject: |
|
|
I recently got EVE working with premium graphics. I had to load it up, toggle the HDR settings on and then off again, then restart the game. It's weird but it worked for me and I had what sounds like the same problem you are having. I found this solution at the official EVE forums in this thread. I know it's a monster thread at 75 pages but I assure you the answer is in there somewhere (I would point you to the exact post but their search feature is offline right now for some reason).
_________________
"Your voice is like the sound of sirens to a house on fire..." -The Alkaline Trio |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Wed Oct 22, 2008 11:18 pm Post subject: |
|
|
Thanks for the suggestion. I have other issues right now (X won't even start  ) , but I'll give that a shot when (if?) I get it working.
Thanks,
EE |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Wed Nov 12, 2008 9:08 am Post subject: |
|
|
Well, after several wine upgrades, and now the new EVE upgrade, EVE remains where it has been for a while: stuck. I start it, and it won't start. As a regular user, I get no terminal output. However, as root, I get this:
| Code: | wine Program\ Files/CCP/EVE/eve.exe
err:ole:CoGetClassObject class {9a5ea990-3034-4d6f-9128-01f3c61022bc} not registered
err:ole:CoGetClassObject no class object {9a5ea990-3034-4d6f-9128-01f3c61022bc} could be created for context 0x1
fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling mixer
err:module:find_forwarded_export function not found for forward 'd3dx8.D3DXGetImageInfoFromFileInMemory' used by L"C:\\windows\\system32\\d3dx9_36.dll". If you are using builtin L"d3dx9_36.dll", try using the native one instead.
err:module:find_forwarded_export function not found for forward 'd3dx9_36.D3DXGetImageInfoFromFileInMemory' used by L"C:\\windows\\system32\\d3dx9_35.dll". If you are using builtin L"d3dx9_35.dll", try using the native one instead.
err:module:find_forwarded_export function not found for forward 'd3dx8.D3DXIntersectTri' used by L"C:\\windows\\system32\\d3dx9_36.dll". If you are using builtin L"d3dx9_36.dll", try using the native one instead.
err:module:find_forwarded_export function not found for forward 'd3dx9_36.D3DXIntersectTri' used by L"C:\\windows\\system32\\d3dx9_35.dll". If you are using builtin L"d3dx9_35.dll", try using the native one instead.
err:module:find_forwarded_export function not found for forward 'd3dx8.D3DXQuaternionSquadSetup' used by L"C:\\windows\\system32\\d3dx9_36.dll". If you are using builtin L"d3dx9_36.dll", try using the native one instead.
err:module:find_forwarded_export function not found for forward 'd3dx9_36.D3DXQuaternionSquadSetup' used by L"C:\\windows\\system32\\d3dx9_35.dll". If you are using builtin L"d3dx9_35.dll", try using the native one instead.
fixme:d3d:IWineD3DImpl_FillGLCaps OpenGL implementation supports 16 vertex samplers and 16 total samplers
fixme:d3d:IWineD3DImpl_FillGLCaps Expected vertex samplers + MAX_TEXTURES(=8) > combined_samplers
fixme:win:EnumDisplayDevicesW ((null),0,0x33af94,0x00000000), stub!
fixme:d3d:test_pbo_functionality >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from Loading the PBO test texture
@ directx.c / 3795
fixme:d3dx8:ID3DXMatrixStackImpl_LoadIdentity (0x1422d0) : stub
fixme:d3dx8:ID3DXMatrixStackImpl_LoadIdentity (0x1422e8) : stub
fixme:d3dx8:ID3DXMatrixStackImpl_LoadIdentity (0x142300) : stub
fixme:d3dx8:ID3DXMatrixStackImpl_LoadIdentity (0x1417c8) : stub
domo-kun drive_c # fixme:d3dx8:ID3DXMatrixStackImpl_LoadIdentity (0x1422d0) : stub
fixme:d3dx8:ID3DXMatrixStackImpl_GetTop (0x1422d0) : stub
wine: Unhandled page fault on read access to 0x00000000 at address 0x2b40949 (thread 0019), starting debugger...
err:seh:setup_exception_record nested exception on signal stack in thread 0019 eip 7efc0750 esp 7ffdbc7c stack 0x242000-0x340000 |
So, something with these two d3dx9 drivers is wrong. I don't have them at that location. Is there a file somewhere that's referencing them erroneously?
Thanks,
EE |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gamers & Players
