Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 33

Thread: Unigine Heaven 2.0 Launches For Linux

  1. #11
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,587

    Default

    Quote Originally Posted by Qaridarium View Post
    good point..... i also can just shot a bulled in my head!
    Well it would have the same effectiveness as your rants to get gaming in linux up to the same level as windows.

  2. #12
    Join Date
    Oct 2007
    Location
    Dresden
    Posts
    53

    Default

    mhm, seems to be broken on gf7 , i get a bad white flickering and the following errors:
    GLFrameBuffer::check_status(): unsupported
    OpenGL error: invalid framebuffer operation

  3. #13
    Join Date
    Oct 2007
    Posts
    19

    Default

    I'm not sure where to report bugs, can't find any appropriate links at their site.

    Running both x86_fullscreen_1920x1080.sh and x86_windowed_1024x768.sh under Fedora 11/i386 produces this error:

    Unigine fatal error
    Engine::init(): chdir() failed

    strace shows:
    ....
    readlink("/proc/self/exe", "/home/fff/GAMES/Unigine_Heaven/bin/Heaven_x86"..., 1024) = 46
    chdir("/home/fff/GAMES/Unigine_Heaven/bin/Heaven_x86\277\277\5G/") = -1 ENOENT (No such file or directory)
    write(2, "\nUnigine fatal error\n", 21
    Unigine fatal error
    ) = 21
    Why is it trying to chdir to some mangled path?

  4. #14
    Join Date
    Aug 2007
    Posts
    6,674

    Default

    Well one problem i found with openal yesterday that prevented it from running when openal was installed, it ran (without sound) with 64 bit then in 32 bit mode because there was no openal lib. The solution i found now is really simple.

  5. #15
    Join Date
    Oct 2007
    Location
    Poland
    Posts
    200

    Default

    bah, it kills my HD4850 :/ 1280x1024 aax4 and everything max, and I have like 20-30fps fglrx 10.2 ofc.

  6. #16
    Join Date
    Dec 2008
    Posts
    166

    Default

    Still... no native UT3 for GNU/Linux?


  7. #17
    Join Date
    Jul 2009
    Posts
    416

    Default

    @Bridgman, or anybody

    What would it take to implement GL_ARB_map_buffer_range into the r600 mesa driver? I tried running Unigine Sanctuary, and that's the error I get.

    Code:
    Unigine fatal error
    Engine::init(): clear video settings for "Mesa DRI R600 (RV770 9442) 20090101 x86/MMX+/3DNow!+/SSE2 TCL DRI2 2.0 Mesa 7.9-devel"
    GLRender::GLRender(): Unknown GPU
    GLRender::require_extension(): required extension GL_ARB_map_buffer_range is not supported

  8. #18
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,571

    Default

    Take this with a grain of salt, but it looks like the extension has already been at least partially implemented for the Gallium3D framework (not sure about specific G3D drivers) and Intel DRI. From a quick look at the API spec this seems like one of those things that isn't too bad to implement today (when the drivers only expose video memory up to the BAR limit) but which could get a lot more exciting once the drivers start using memory above the BAR limit.

  9. #19
    Join Date
    Oct 2008
    Location
    Sweden
    Posts
    983

    Default

    Quote Originally Posted by pvtcupcakes View Post
    @Bridgman, or anybody

    What would it take to implement GL_ARB_map_buffer_range into the r600 mesa driver? I tried running Unigine Sanctuary, and that's the error I get.
    Unfortunately, that's not the only extension not implemented in Mesa.

  10. #20
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,571

    Default

    Yeah, that was my concern as well - there's a good chance that implementing that extension would just allow the app to get to the *next* unimplemented extension, and so on...

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •