Forums » Bugs

New Linux64 update

Oct 22, 2012 raybondo link
A new linux64 update has been released that implements screenshots and pasting from the clipboard should no longer crash.
Most of the game crashes should also be fixed but whenever a crash happens and the bug reporter doesn't show up, please post or send me your errors.log file.
I added more debugging info into there to help track down some of the uncommon crashes.

I also added the ability to disable multithreading by editing the game's config.ini file and adding multithreaded=0 to the [Vendetta] section.
Oct 22, 2012 abortretryfail link
Sweet. /dump works now!

Have a screenshot with some rendering goofballs :)
Oct 22, 2012 abortretryfail link
Oct 23, 2012 Pizzasgood link
It would, but the capship station tends to make everything in proximity look tiny, so you're okay.
Oct 23, 2012 abortretryfail link
Oh the power of contrast!
Oct 23, 2012 Lisa50469 link
I never had issues using /dump. I often take screenshots.

The crashes I was seeing never left anything in the errors.log file, but since I launch vendetta from a terminal window, the following error was shown:

XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 46213 requests (46213 known processed) with 1 events remaining.

I did have to add the multithreaded=0 to the [Vendetta] section.
Then these errors stopped and VO is solid again.
Oct 23, 2012 raybondo link
Thanks for the reports, keep 'em coming.
Oct 24, 2012 abortretryfail link
So far nothing new to report except for more similar rendering errors on other ships, including vultures, revenants, prometheus, etc.
Oct 28, 2012 mr_spuck link
Today I crashed three times with an error similar to lisa's. It always happened when jumping. When I logged back on I was in the next sector.

Don't know if it means that I was flying around in a trident.
Oct 29, 2012 mr_spuck link
..and now it happened while undocking
Oct 29, 2012 incarnate link
Please keep the reports coming. I think we know "what" is causing these issues, but we're still not sure "why". Debugging is ongoing.