Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mikochu]

Have you installed the very latest Intel HD drivers on it? We tested the last build on Intel (though on HD 4400) and it worked ok.

Yeah, I downloaded the latest Intel HD/Iris driver (April 2015).  I'll have to try it again, but I remember the eng.log being very short.  Looking at other eng.log files in this thread, I think it cuts off right before "Using OpenAL device (OpenAL Soft)"...I wonder if there's an issue with OpenAL.

Update: It seems like there are a couple of issues.  Outerra crashes after running the first time.  After initial launch, I try to log in, then it updates.  However, after it installs the update, it crashes.  If I reboot after an update is applied, it works, but I did get the following error:

ERROR: OpenGL error: shader compilation failed (: matbaked2)

[cameni]

What OT build number is it? The info should be in first few lines of eng.log.

[mikochu]

What OT build number is it? The info should be in first few lines of eng.log.

INFO: Outerra 0.8.4, build 5525 from Mon, 25 May 2015 07:42:42 GMT

Attached is my eng.log.  It ends abruptly.  Not sure what's causing my issue.

[balfourcraig]

I am having the same (: matbaked2) issue. I only just reinstalled Outerra after having had it uninstalled for a few months. It used to work, not it doesn't.

Graphics card is nVidia EVGA GT240.

[cameni]

I am having the same (: matbaked2) issue. I only just reinstalled Outerra after having had it uninstalled for a few months. It used to work, not it doesn't.

Graphics card is nVidia EVGA GT240.

It's a problem with old Nvidia cards with drivers that are no longer being fixed. Workaround will be in the next patch.

[mouser98]

hi,

i am running windows XP on an AMD Phenom II CPU and a HD 5830 video card.  I have uninstalled and installed the latest drivers 4 times now, the last two times using the DDU utility.  When I try to run Outerra I get the error message saying that my graphics drivers are outdated, then when I hit okay, after a few seconds it pops up again and says my graphics drivers have crashed. 

eng.log:

INFO: starting io_man...
DEBUG: program directory: F:\Program Files\Outerra\Anteworld\
INFO: Outerra 0.8.4, build 5372 from Thu, 26 Mar 2015 17:47:04 GMT
DEBUG: Initializing engine...
DEBUG: data root directory: F:\Documents and Settings\Chip\Outerra\
DEBUG: Windows version: 5.1.2600
DEBUG: CPU info:
   CPU string: AuthenticAMD
   CPU brand string: AMD Phenom(tm) II X4 965 Processor
   Stepping ID: 3
   Model: 4
   Family: 15
   Processor type: 0
   Extended model: 0
   Extended family: 1
   Brand Index: 0
   CLFLUSH cache line size: 64
   APIC Physical ID: 3

DEBUG: Reading F:\Documents and Settings\Chip\Outerra\eng.cfg
DEBUG: GPU Vendor: ATI Technologies Inc.
DEBUG: GL Renderer: AMD Radeon HD 5800 Series
DEBUG: GL Version: (420) 4.2.11927 Compatibility Profile Context
DEBUG: OpenGL context defaults to: AMD, detected version: 420 build 11927
DEBUG: Display devices attached to desktop:
\\.\DISPLAY1                     1002 689e AMD Radeon HD 5800 Series, Display: Plug and Play Monitor
\\.\DISPLAY2                     1002 689e AMD Radeon HD 5800 Series, Display: Plug and Play Monitor
\\.\DISPLAYV1                    0000 0000 NetMeeting driver
\\.\DISPLAYV2                    0000 0000 RDPDD Chained DD
DEBUG: GPU System info
    Graphics card: AMD Radeon HD 5800 Series
    GPU vendor ID: 1002 (ATI Technologies Inc.)
    GPU device ID: 689e
    OpenGL driver version: 6.14.10.11927 (atioglxx.dll)
    OpenGL driver build number: 11927


DEBUG: Your AMD graphics drivers are outdated, with known issues in Outerra. Please update your graphics card drivers to the latest available version (Catalyst 14.12 and newer).

Known issues of these drivers in Outerra:
- no MSAA
- no shadows
- no objects
- bad terrain lighting
WARNING: Outdated drivers, shadows have been disabled because of an OpenGL driver bug
WARNING: Outdated drivers, objects have been disabled because of an OpenGL driver bug
INFO: FT tracker initialized
DEBUG:   init timer to 1ms
DEBUG: Outerra window created size 1280x720
DEBUG: Starting JobMaster...
DEBUG: Creating JobMaster thread 0
DEBUG: Creating JobMaster thread 1
DEBUG: Creating JobMaster thread 2
DEBUG: Creating JobMaster thread 3
DEBUG: Creating JobMaster thread 4
DEBUG: Creating JobMaster thread 5
DEBUG: Creating JobMaster thread 6
DEBUG: Creating JobMaster thread 7
DEBUG: Event "vertical_speed" already defined, overriding with latest definition.
DEBUG: Event "heading" already defined, overriding with latest definition.
DEBUG: (io_man) event group "player" has been activated...
DEBUG: Available display modes:
    640x480@60
    640x480@67
    640x480@72
    640x480@75
    640x480@60
    640x480@67
    640x480@72
    640x480@75
    800x600@56
    800x600@60
    800x600@72
    800x600@75
    800x600@56
    800x600@60
    800x600@72
    800x600@75
    1024x768@60
    1024x768@70
    1024x768@75
    1024x768@60
    1024x768@70
    1024x768@75
    1152x864@60
    1152x864@75
    1152x864@60
    1152x864@75
    1280x720@60
    1280x768@60
    1280x800@60
    1280x960@60
    1280x1024@60
    1280x1024@75
    1280x1024@60
    1280x1024@75
    1360x768@60
    1360x1024@60
    1366x768@60
    1400x1050@60
    1440x900@60
    1600x900@60
    1680x1050@60
    1920x1080@60
    1920x1080@60

DEBUG:
Available Capture Devices are:-
Realtek HD Audio Input

DEBUG:
Sound system information:
    Using OpenAL device (OpenAL Soft)
    ALC Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFT_loopback
    Using OpenAL capture device (OpenAL Soft)
    ALC_FREQUENCY: 44100
    ALC_REFRESH: 43
    ALC_SYNC: 0
    ALC_MONO_SOURCES: 255
    ALC_STEREO_SOURCES: 1

OpenAL info:
    Vendor: OpenAL Community
    Version: 1.1 ALSOFT 1.15.1
    Renderer: OpenAL Soft
    Extensions: AL_EXT_ALAW AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_LOKI_quadriphonic AL_SOFT_buffer_samples AL_SOFT_buffer_sub_data AL_SOFTX_deferred_updates AL_SOFT_direct_channels AL_SOFT_loop_points AL_SOFT_source_latency

DEBUG: renderer: thread started...
DEBUG: Searching suitable pixel format...
INFO: Pixel format description:
    WGL_SUPPORT_OPENGL_ARB=1
    WGL_DOUBLE_BUFFER_ARB=1
    WGL_SWAP_METHOD_ARB=WGL_SWAP_UNDEFINED_ARB
    WGL_SAMPLES_ARB=0
    WGL_SAMPLE_BUFFERS_ARB=0
    WGL_AUX_BUFFERS_ARB=0
    WGL_ACCUM_BITS_ARB=0
DEBUG: Pixel format has been found: 2
DEBUG: Setting pixel format
DEBUG: Creating temporary OpenGL rendering context
DEBUG: Setting temporary rendering context as current
DEBUG: Creating OpenGL 4.x rendering context

[cameni]

Windows XP is not officially supported, it has a severely limited memory for communication with the GPU.
Also those AMD drivers are old (4.2.11927), 14.12 drivers should have the last number 13283, but it may be again an issue with Windows XP and version detection (unless you installed wrong drivers, or the new ones aren't supported on Windows XP)

But even if you get the drivers working, Windows XP will have problems running it, you'll have to close browser windows to free some of the limited shared memory.

[mouser98]

Okay, thanks.  I guess it is time to move to Windows 7

[Khanromi]

Hello,
I'm trying to run the Anteworld demo on my PC (Windows 7 Ultimate 64-bit) (CPU: AMD FX-8350 Eight-core, 4 GHz) (GPU: 2x AMD R9 285X, 2gb GPU Mem each, crossfire capable) (2x8gb DDR3 RAM). Every time I try to run it, I can load the world, but after a short time the screen blacks out, then returns, saying the graphics driver stopped responding and successfully recovered. The game no longer renders after this point, though it does not terminate.
It is often preceded by significant visual artifacting: flickering trees, flashes of massive black polygons. It seems to happen regardless of the state of my computer fan, so I don't believe my cards are overheating.
I looked up some of the usual answers to these sorts of problems. I've reinstalled the game completely, deleted the config file, run it with and without crossfire, uninstalled and reinstalled the drivers for both graphics cards using the device manager, and the problem does not stop.
By all accounts, my computer should be capable of running this game.

Here is the eng.log for my last run of the game.
http://pastebin.com/LF64KHkF

I would greatly appreciate any help you guys can give on this matter.

[Levi]

Khanromi, make sure you're running the latest version of your graphics card driver: Omega (14.12)

[Khanromi]

Khanromi, make sure you're running the latest version of your graphics card driver: Omega (14.12)

Downloaded and installed the drivers you recommended. The issue then happened more or less immediately after world loading.
I have turned off Crossfire now, and the game worked until I spun the camera around, whereupon it had the issue again.

[cameni]

There is some kind of problem with AMD cards and drivers, the driver crash seems to happen from time to time on all their card series, though the frequency is much lower. On our test machine the driver crash occurs in roughly 5% of runs, but the reason is unknown and it doesn't seem to be linked to any particular thing.

Driver cleanup (with DDU) usually helps with the problem, though it doesn't eliminate it completely: just recently my main computer got into a state when 4 of 5 runs would crash the drivers shortly before the world was going to get displayed. I used DDU to clean up the drivers and reinstall them, and now the issue is rare, like 1 out of 20 runs. I have no idea why it works this way, and unless we can reliably crash the drivers, AMD devs aren't able to debug it ...

Actually, if your computer is crashing this reliably, it would be great to check what the state of the drivers on your computer is before cleanup.
Could you download this tool: https://technet.microsoft.com/en-us/sysinternals/bb897441
and run the following command:

Code: [Select]

sigcheck.exe -q -c C:\Windows\SysWOW64\ati* >ati.txt

And then upload the generated ati.txt file with file versions?

[Acetone]

There is some kind of problem with AMD cards and drivers, the driver crash seems to happen from time to time on all their card series, though the frequency is much lower. On our test machine the driver crash occurs in roughly 5% of runs, but the reason is unknown and it doesn't seem to be linked to any particular thing.

Driver cleanup (with DDU) usually helps with the problem, though it doesn't eliminate it completely: just recently my main computer got into a state when 4 of 5 runs would crash the drivers shortly before the world was going to get displayed. I used DDU to clean up the drivers and reinstall them, and now the issue is rare, like 1 out of 20 runs. I have no idea why it works this way, and unless we can reliably crash the drivers, AMD devs aren't able to debug it ...

Actually, if your computer is crashing this reliably, it would be great to check what the state of the drivers on your computer is before cleanup.
Could you download this tool: https://technet.microsoft.com/en-us/sysinternals/bb897441
and run the following command:

Code: [Select]

sigcheck.exe -q -c C:\Windows\SysWOW64\ati* >ati.txt

And then upload the generated ati.txt file with file versions?

Yep, random crashes too.
I'm going to test the latest 15.6 Beta drivers (after a DDU clean). I'll post here if I see any improvements.

Edit:
It needs more testing, but it seems like the beta driver is way more stable. I think I also have an higher/more stable framerate in general

[Khanromi]

...

Actually, if your computer is crashing this reliably, it would be great to check what the state of the drivers on your computer is before cleanup.
Could you download this tool: https://technet.microsoft.com/en-us/sysinternals/bb897441
and run the following command:

Code: [Select]

sigcheck.exe -q -c C:\Windows\SysWOW64\ati* >ati.txt

And then upload the generated ati.txt file with file versions?

Done, here you go:
http://pastebin.com/G1KbesLf
Edit: Would you recommend using DDU to uninstall/reinstall drivers, since I've made a snapshot of what I had?

[cameni]

Done, here you go:
http://pastebin.com/G1KbesLf
Edit: Would you recommend using DDU to uninstall/reinstall drivers, since I've made a snapshot of what I had?

Thanks. Yes, please use DDU now, and you could also run the script again so we can compare if any drivers changed, assuming you install the same drivers that you had before the cleanup.