-QA Testing-
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 24 2017
Mar 22 2017
-QA Testing-
-QA Testing-
Mar 21 2017
-QA Testing-
Made a sample video on the test server to show the effect.
https://youtu.be/XdW5S0RFCi8
I'm trying to get it to work by using new ContextAttribs(3, 2).withForwardCompatible(true).withProfileCompatibility(true)
yes I read the stackoverlow thread and I used
Display.create(new PixelFormat(), new ContextAttribs(3, 2).withForwardCompatible(true).withProfileCore(true));
While the "Creating MAC OS context for OpenGL 4.1 if possible" entry does appear, the game crashes on launch.
-QA Testing-
version 0.199.489 or higher
you should see
The thing was that i used a check for capabilities beforehand. I'll try to create a context that way if macOS is used. Hopefully that wont affect other users
calm down. we are definitely not dropping macOS support. No reason to get angry. I misunderstood the comment above
The problem is that the driver DOES support it, STARMADE IS MAKING THE WRONG API CALLS and therefore not detecting relevant support. Please see my extensive commentary this topic in-ticket. Since performance is so abysmal on macOS without framebuffer support, should we assume the wrontfix is an indication of plans to drop macOS support?
Fixed with recent fixes to projectiles and beams
If the driver reports to the game that it doesn't support it but still support it, it is a driver issue which can't really be fixed ingame. Trying to turn on framebuffer as a check would have bad consequences on graphics cards that dont support it.
I can't reproduce :(
Related to other issue with similar NullPointer (probably not needed though). Shutdown error is possibly fixed already
Uplink now provided with launcher, so it should be fixed with that
sidenote: this only happens if you try to dock on a ship that already has a docked ship elesewhere on it
You can only dock a ship that isn't already docked.
sensors need testing on cargo
Mar 20 2017
-QA Testing-
-QA Testing-
Mar 18 2017
Mar 17 2017
fix should be in 0.199.485
Be finally gone, filthy bug
Mar 16 2017
-QA Testing-