Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Important Important
    • Resolution: Unresolved
    • Affects Version/s: 3.00 Beta 1
    • Fix Version/s: None
    • Labels:

      Description

      You landed on this page because the game detected an error to start the game.

      We are currently investigating the exact conditions which can trigger this startup error. If you wanna help us to identify the exact conditions (and determine a possible workaround), please follow the steps in the section: "Further support".

      Further support

      If you want to help us to speed up the investigation, please send a mail to: prioritysupport@egosoft.com with the subject set to: "X4-371 - Exitcode 235" and attach the following details:

      • a screenshot of the popup the game presented to you
      • the dxdiag and vulkaninfo (see this wiki page for details on how to retrieve this data)
      • state whether you always get the Exitcode 235 issue at startup or whether it just happens occasionally (or maybe even just happened once)

      Issue history

      This compatibility check was introduced in 3.00 Beta 1.
      During the 3.00 Beta phase it mainly occurred for Intel graphics cards. We improved the handling for these type of graphics devices in 3.00 Beta 5 and provided a workaround to prevent running into this startup issue. This heavily reduced the chance of triggering this startup error.

        Activity

        Hide
        added a comment -

        Error: "Couldn't find acceptable transfer- queue"

        2.6 works without problems, however.

        From vulkaninfo, regarding queue families:

        VkQueueFamilyProperties[0]:
        ===========================
                queueFlags         = GRAPHICS | COMPUTE | TRANSFER | SPARSE
                queueCount         = 1
                timestampValidBits = 36
                minImageTransferGranularity = (1, 1, 1)
                present support    = true
        

        Seems about right to me. It fullfills all Vulkan specifications.
        Just an educated guess: I suspect the game (in version 3.0) is searching for dedicated transfer-only queues or something like that, but doesn't fall back to other suitable queues if it can't find one.

        Show
        added a comment - Error: "Couldn't find acceptable transfer- queue" 2.6 works without problems, however. From vulkaninfo, regarding queue families: VkQueueFamilyProperties[0]: =========================== queueFlags = GRAPHICS | COMPUTE | TRANSFER | SPARSE queueCount = 1 timestampValidBits = 36 minImageTransferGranularity = (1, 1, 1) present support = true Seems about right to me. It fullfills all Vulkan specifications. Just an educated guess: I suspect the game (in version 3.0) is searching for dedicated transfer-only queues or something like that, but doesn't fall back to other suitable queues if it can't find one.
        Hide
        Stefan Hett added a comment -

        It would be helpful to receive the full details as mentioned in the description. Would be much appreciated, if you could send us the details by mail.

        Show
        Stefan Hett added a comment - It would be helpful to receive the full details as mentioned in the description. Would be much appreciated, if you could send us the details by mail.
        Hide
        added a comment -

        Hello,

        I have the same problem with 3.0 but I am playing on an Intel chip*. I know this is technically not "supported" hardware** on your end, are you interested in the data, nevertheless?

        • thanks to the shared memory option of iGPUs this is not a problem
          • but if it works, it works
        Show
        added a comment - Hello, I have the same problem with 3.0 but I am playing on an Intel chip*. I know this is technically not "supported" hardware** on your end, are you interested in the data, nevertheless? thanks to the shared memory option of iGPUs this is not a problem but if it works, it works
        Hide
        Stefan Hett added a comment -

        Yes, we'd like to receive the data also for these cases, even if it will just help us to fine tune the hardware detection to point out unsupported HW setups.

        Show
        Stefan Hett added a comment - Yes, we'd like to receive the data also for these cases, even if it will just help us to fine tune the hardware detection to point out unsupported HW setups.
        Hide
        Stefan Hett added a comment -

        Thanks for all your input we were able to identify an issue in 3.0 Beta 1 to Beta 4 (Hotfix 2) and are working on a fix for the next beta version (at the time of writing this, this is likely going to be 3.0 Beta 5).

        Show
        Stefan Hett added a comment - Thanks for all your input we were able to identify an issue in 3.0 Beta 1 to Beta 4 (Hotfix 2) and are working on a fix for the next beta version (at the time of writing this, this is likely going to be 3.0 Beta 5).

          People

          • Assignee:
            Stefan Hett
            Reporter:
            Stefan Hett
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: