Jump to content

Postie

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by Postie

  1. Good evening Leti, Tried tinkering with the monitors per your suggestions. Still had the same crash error occur with whichever one was plugged in, and both times the crash log said whichever monitor was plugged in at the time was "x: 0, y:0. w: 0" For lack of any further ideas, I tried running the game off of the built in Intel GPU again, and the game now seems to be loading properly, with the cautionary alert that it's using the Intel GPU, rather than the Radeon GPU. If I try switching back to the Radeon GPU, it crashes again. Not sure what you can make of that, given all drivers are up-to-date.
  2. Good afternoon Leti, Thanks for the response, unfortunately this hasn't resolved the issue. Firstly, I think the FAQ needs to be updated for AMD users using the Adrenaline system, as there's no way to switch between the internal and the dedicated graphics card with the current version of AMD Adrenaline. I've managed to assign Avorion to use the dedicated GPU via an alternate method, but still experience the same crash at launch. Attached is the most recent crash log. clientlog 2023-08-08 13-11-22.txt
  3. My PC has a Radeon RX 580 graphics card. That said I've never been able to get Avorion to recognise it and run off it, it always ran off of the built in Intel GPU. Was never an issue until late last year, worked properly on an old laptop with no dedicated GPU, and on my current PC. Looking through the crash log, the only thing that seems out of place is OpenGL, but I can't see how that's a problem as all drivers for both GPUs have been updated numerous times, yet the game still crashes on launch.
  4. Unfortunately still no joy, backed up the folder, deleted everything, still the same problem. Tries launching, crashes, and the crash detection file is created again. clientlog 2023-06-30 20-57-35.txt
  5. Don't suppose you have any other suggestions or insight on what might be causing this problem?
  6. Evening TheMgt, Thanks for the suggestion, unfortunately still no joy. Delete that file in the roaming data folder, try launching the game, it tries opening a window, closes/crashes a second later, and the .startupCrashDetection is recreated in the roaming data folder. I've updated my graphics drivers numerous times since I first started getting this error last year, so I can't see how that's the issue. Kind of becoming infuriating that none of the game devs seem to be paying attention to the troubleshooting forum. Given I've been able to play Avorion on this PC for at least 2-3 years on this PC with no issue, I can only attribute it to something in the latest patch for the game has made it unplayable for players like myself and Pandize (and presumably plenty more), and they seem to be willfully ignorant of the issue.
  7. Is there any actual tech support or game staff able to assist in trouble shooting problems with the game, or is this board completely pointless?
  8. Is there anyone that can assist, or a more direct way to get troubleshooting, as this issue still persists.
  9. Thanks for the response. Thing is until one of the most recent updates, it was running fine on the integrated Intel GPU... Other games and programs I have run based off the dedicated graphics card, but I've never been able to get Avorion to run off of it.
  10. Anyone able to offer suggestions on how to fix this?
  11. Have been playing since 2017. For the past couple of months I now get this error when trying to start the game; "We detected a crash during game startup Pleas make sure that you are using the latest drivers for your graphics card. This problem can also be caused by mods. In an attempt to fix this problem, the graphics settings have been reduced to an absolute minimum and your mods have been disabled" I've already made sure my graphics drivers are up to date, and have fully uninstalled and reinstalled Avorion and deleted everything from the AppData Roaming folder, yet the issue persists. Any other troubleshooting I can do to resolve this? clientlog 2022-11-26 14-42-29.txt
×
×
  • Create New...