Server details ... Unknown player
Balmark
Join Date: 2002-11-01 Member: 3476Members, Constellation, Reinforced - Silver, Reinforced - Shadow, WC 2013 - Shadow
Cmon .. fix this ..
I'm dumbfounded it didn't make it into last 2 patches .. seriously ..
Reminds me of an ad I saw for vans .. 'what does your van say about your company? *guy mimmicing a van starting up*cow cow cow cow cowboy! brummm bruuumm'
http://www.asai.ie/complaint_view.asp?CID=1079&BID=54
I'm dumbfounded it didn't make it into last 2 patches .. seriously ..
Reminds me of an ad I saw for vans .. 'what does your van say about your company? *guy mimmicing a van starting up*cow cow cow cow cowboy! brummm bruuumm'
http://www.asai.ie/complaint_view.asp?CID=1079&BID=54
Comments
Just so you know, this is an engine but, and one that's not likely to be fixed any time soon as they're not sure of the exact cause, and any devs with access to engine code are extremely busy with Subnautica.
As for the gun jam, I know that having a reliable repro is great for fixing a bug, but for bugs like this that appear to happen at random and haven't gotten reliable repro steps in at least a year, it's just not going to happen. Since it seems to be just limited to the LMG, rewriting relevant LMG code may be the way to go to try to avoid writing the same bug in again, assuming it's not a ton of complicated code. And if it is a ton of complicated code, that's probably the issue, anyway.
PS - SamusDroid, huge props for your work on the game. Massively appreciated.
unfortunately this will never happen until UWE decides that the spark engine doesn't have any real further value to offer their company and open sources it (read: years if ever). only UWE devs are given access to engine code because it's the entire intellectual property of the game, it's the real product of the time they spent developing it. functionally, you would have to get every person you give it access to fully vetted and have them sign onerous non-disclosure agreements, effectively bringing them on as a contractor, and even then if they went and uploaded the engine codebase to thepiratebay there would never be any way to prove who it was and sue them.
They totally could give access to the engine to someone outside of UWE.
Never say never
It's written the same way as all other weapons are written. If the problem was in the lua file for the weapon, it would occur with all other weapons too. From what we can tell it seems to be something relating to animations.
I'm confused...
To clarify for you:
The devs are busy.
The devs still care about ns2.
I think you missed the news! We released a patch with lots of fixes to faults with the game recently. The unknown player bug is annoying I know - it's enemy number one in my book right now and hopefully we can get it fixed up in the future.
Best would be to also give him access to the code version of 3 builds ago ( as this issue was introduced 3 builds ago anyone with abit coding skills could track down the source of that issue by just looking at the changes ... )
//NS2.working = true;
I could fix that...
Wait... it's LUA, right?
would be
then.
In build 263, the function NS2Gamerules:UpdateScores() was removed when the scoreboard networking was overhauled. That function was responsible for updating the Steam browser data as well as the scoreboard. This functionality was never replaced elsewhere, hence no more player info in Steam.
I just set up a listen server which calls Server.UpdatePlayerInfo() every second and sure enough I show up in the player list and there's no unknowns in sight.
Shine will be updated in the mean time to run this fix, which unless I've missed something, is all that was wrong.