Possibly enough info, putting in queue. Else need feedback on what specific feedback you need.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 21 2017
Quoted from erthparadine:
side-note: that Intel GPU warning is useless for macOS users…at-best its an annoyance that nobody can do anything about. At worst, it suggests SM developers are not aware of the inherent driver integration on the macOS platform, and therefore that nobody can simply “update” drivers on macOS.
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?
Just to be clear, the current block count limit does not prevent you from making something larger than specified. It does exactly what it says it does which is disable systems on a ship not conforming to the set limit.
Fixed with recent fixes to projectiles and beams
Possibly fixed with fixing beams recently. needs retesting.
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 :(
fixed longer ago. Only remaining issue is when spawning into a high load sector (physics wise)
Solved by previous optimization in the group calculation (reusing variable sized threads)
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.
it will only set the player name if the name is compatible and there wasnt previously a name set. Uplink is now automatically set from launcher
sensors need testing on cargo
Intended behavior (to not clutter database with data)
Mar 20 2017
-QA Testing-
-QA Testing-
the server I'm on is having the same problem, its even corrupting the factions because of this issue. we've seen this bug since the faction update with npcs.
-QA Testing-
-QA Testing-
https://phab.starma.de/T382 related ticket
Mar 19 2017
The set-up explained in the original description does not replicate it anymore, however I still do get the error but it is very hard to reproduce it reliably (however when using a missile system that causes it, it happens very reliably), I have only experienced it twice since then, both in multiplayer. I am using a Nvidia card as well. However, another SM player has this issue on AMD cards as well.
Mar 18 2017
I'm pretty sure I have triggered this myself on many different public servers unknowingly. Right now I'm playing on Brierie (running .472) and I attempted to "move" my shop to another physical position on my station. Pretty sure it caused the server to need to hang/be restarted. But post restart things are still acting quite wonky at least in my sector.
-QA Testing-
Mar 17 2017
Update: this issue continues to occur, even after switching away from the professional to a consumer-grade GPU card.
fix should be in 0.199.485
Be finally gone, filthy bug
This is not an issue we can fix.
It is a tribute to the way java is used on client computers and on server environments.