Jump to content

historic_bruno

WFG Retired
  • Posts

    2.755
  • Joined

  • Last visited

  • Days Won

    47

Posts posted by historic_bruno

  1. AFAIK you couldn't view Chinese characters without the East Asian locale mod applied, or at least some modification of SVN :) They all appear as <?> in SVN, this is relevant information.

    The error is that it's out of memory:

    "Unhandled exception at 0x5e340a4a in crashlog.dmp: 0xC0000005: Access violation writing location 0x00000000.*D:\16009\binaries\system\msvcr100.dll: Out of memory.*C:\Windows\System32\ntdll.dll: Out of memory."
    How long had the game been running when this error occurred?

    The call stack shows the crash in texture converter, but it could occur almost anywhere in an OOM condition:

    >	msvcr100.dll!__VEC_memcpy()  + 0x51 bytes	 	pyrogenesis.exe!CTextureConverter::ConvertTexture(const boost::shared_ptr<CTexture> & texture={...}, const Path & src={...}, const Path & dest={...}, const CTextureConverter::Settings & settings={...})  Line 460	C++ 	pyrogenesis.exe!CTextureManagerImpl::ConvertTexture(const boost::shared_ptr<CTexture> & texture={...})  Line 307	C++ 	pyrogenesis.exe!CTextureManagerImpl::MakeProgress()  Line 372	C++ 	pyrogenesis.exe!RendererIncrementalLoad()  Line 261	C++ 	pyrogenesis.exe!Frame()  Line 321	C++ 	pyrogenesis.exe!RunGameOrAtlas(int argc=1, const char * * argv=0x0204e160)  Line 511 + 0x5 bytes	C++ 	pyrogenesis.exe!SDL_main(int argc=1, char * * argv=0x0204e160)  Line 555 + 0xd bytes	C++ 	pyrogenesis.exe!main(int argc=1, char * * argv=0x0204e160)  Line 140 + 0xd bytes	C 	pyrogenesis.exe!wmain(int argc=1, wchar_t * * argv=0x0204eb78)  Line 380 + 0xa bytes	C++ 	pyrogenesis.exe!__tmainCRTStartup()  Line 583 + 0x17 bytes	C 	pyrogenesis.exe!CallStartupWithinTryBlock()  Line 397	C++ 	kernel32.dll!@BaseThreadInitThunk@12()  + 0x12 bytes	 	ntdll.dll!___RtlUserThreadStart@8()  + 0x27 bytes	 	ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes	
    Possibly it was converting a huge East Asian font texture and it ran out of memory (due to fragmentation or leaks).
  2. Here is the call stack:

     	ig75icd32.dll!631e6258() 	 	[Frames below may be incorrect and/or missing, no symbols loaded for ig75icd32.dll]	>	pyrogenesis.exe!CPostprocManager::ReleaseRenderOutput()  Line 391	C++ 	pyrogenesis.exe!CRenderer::RenderSubmissions(const CBoundingBoxAligned & waterScissor={...})  Line 1567	C++ 	pyrogenesis.exe!CRenderer::RenderScene(Scene & scene={...})  Line 1870	C++ 	pyrogenesis.exe!CGameView::Render()  Line 489 + 0x3c bytes	C++ 	pyrogenesis.exe!Render()  Line 229	C++ 	pyrogenesis.exe!Frame()  Line 369	C++ 	pyrogenesis.exe!RunGameOrAtlas(int argc=1, const char * * argv=0x027115e8)  Line 511 + 0x5 bytes	C++ 	pyrogenesis.exe!SDL_main(int argc=1, char * * argv=0x027115e8)  Line 555 + 0xd bytes	C++ 	pyrogenesis.exe!main(int argc=1, char * * argv=0x027115e8)  Line 140 + 0xd bytes	C 	pyrogenesis.exe!wmain(int argc=1, wchar_t * * argv=0x02716c18)  Line 380 + 0xa bytes	C++ 	pyrogenesis.exe!__tmainCRTStartup()  Line 583 + 0x17 bytes	C 	pyrogenesis.exe!CallStartupWithinTryBlock()  Line 397	C++ 	kernel32.dll!@BaseThreadInitThunk@12()  + 0xe bytes	 	ntdll.dll!__RtlUserThreadStart()  + 0x24 bytes	 	ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes	
    It could be an issue with post processing initialization that is fixed for A18, though your GPU is definitely new enough that it supports FBOs. At least in the crash dump, pglBindFramebufferEXT is a null pointer, though it indicates the crash is occurring inside the driver itself. If enabling GLSL per Loki1950's suggestion doesn't help, then I would try updating your drivers.
  3. Any updates?

    It's annoying to update most library binaries on Windows and just not much of a priority for our Windows devs. That said, you should create a new Trac ticket for it. There was an old one, but it was fixed, I would just create a new one with your list. Also, if we're going to start requiring VS 2013 in the future, they should be rebuilt for that, which can be mentioned in your ticket. It took years to bring things up to date before, just a warning :P

    What we really need to streamline the process is a build script for all the Windows binaries, so we can update the versions or compiler, and kick off the script. It's a lot of manual work now, and in many cases, you have to research the exact procedure and fix bugs to even get them to build. Sometimes you need CMake, sometimes you need the MSVC command line, sometimes it has its own bootstrapping, sometimes you need to build a bunch of dependencies first, sometimes you need to alter the project build settings (almost always, to get them to end up the way we want).

  4. That's strange, you're using A17? It runs perfectly for me on XP SP3, so I wonder if it only happens on some other error condition? We never call that function in our source code, so it must be some other library, but we need more information to debug this. Is there anything else mentioned in the error message? Is it reproducible on every attempt to start the game? Do you have user feedback enabled in-game?

    There are no crashlogs in your logs.zip, it would be helpful to run the game in a debugger, either Visual Studio or WinDbg as described here.

    • Like 1
  5. The crash is definitely related to graphics card/driver described here, but it's already fixed for the next release.

    Edit: should mention that you can use the SVN dev version of the game until A18 is released, if you want to play the game in the latest state, though it won't be compatible w/ A17 in multiplayer.

    • Like 1
  6. If it's installed into User1's home directory, you should only run it from User1's account. Otherwise, there is a good chance that permissions will be incorrect. If you want both User1 and User2 to play the same install, you should install it somewhere that both can access. I don't know why that would cause a problem with cursors though, or if it would.

  7. What would you suggest replacing it with? There will always be an artificial point at which the "land meets the sky" or the game world ends, and having a visible sky complicates this (besides not really enhancing gameplay or visual quality). There's a reason it's hidden by default.

    In some 3D environments, I've seen them reflect the terrain, trees, etc. out to infinity with filters in place. That's probably a better solution for a first-person view, not a top-down RTS like 0 A.D. The issue is the diversity of maps we have and the possible camera angles, so no one solution seems like it would work.

    • Like 1
×
×
  • Create New...