Server/Client Updates

[Radulfr]

Yes, it ain't perfect yet. Deal with it. It's also far from a disaster. Reading your posts, you'd think someone killed your kitten.
And nope, you don't get to talk for the "community as a whole", unless you make a survey. They can talk for themselves.

[qqmwoarplox]

Do whatever the hell you want then

[Imago]

https://github.com/AllegianceZone/Alleg ... e.cpp#L447

[Archangelus]

QUOTE ( Saudade @ Jan 28 2018, 04:09 PM) Don't you ever talk to me like this again by the way

Oh quit your whining.

[_xJammer_]

QUOTE ( Saudade @ Jan 28 2018, 02:04 PM) this game ultimately belongs to the community

This game belongs to Microsoft. And MIT license allows anyone to take it and do w/e they want with it. Servers belong to specific different people who are free to set whichever rules they like. Community does not own the goodwill of people spending their time and money to keep it going on life support.


Anyhow, the update $#@!ed up a lot of things - for the first time in playing alleg I get inconsistent repetitive crashes at completely random times. One game ripping to carrier caused a persistent "object stuck in another object" bouncing sound that would only go away when docking. And ripping to the same carrier would cause it to start again.

Whoever made the new ridiculous forced loadouts that do not even remember my previously chosen and saved one (or even just the Ctrl+1 one).... was not a very smart person.Annoying as hell to have to remember to re-arm the craft every launch. (and no I DO NOT always need a nan in my scout)

Honestly while before the issues were with patches not going through (Djole made a few tested fixes that are still not accepted), this update just shows to me that the development took a deep dive.

[TheRock]

The current game as it is on steam, the servers and the dev team belong to the community, that should be obvious. Playing the game, with you, is the biggest incentive.

It's unfortunate that the update seems to be causing you issues. I was not expecting big issues to appear with the client release, as that has been in beta for a while now. There have been very little changes to the beta in the past three weeks.
With those crashes, have any .dump or .mdump files been created next to the Allegiance.exe? (Probably not... Imago, I know you are reading the forums, do you have any idea how we could improve that?)

I'm not using the fancy ctrl+1 loadout shortcuts, so I don't know what is going on. I'll forward your comments to someone who might, but maybe without the "not a very smart person".

Djole's patch not having been applied is my fault, as I said I would take a look at it a while ago. I'll go through it this weekend.

[Radulfr]

QUOTE (_xJammer_ @ Jan 29 2018, 05:02 AM) Anyhow, the update $#@!ed up a lot of things - for the first time in playing alleg I get inconsistent repetitive crashes at completely random times.

Yep, I'm responsible for at least one new client crash. Fix on GitHub, sorry. It's rather hard to trigger though, which is why I missed it in beta.

QUOTE (_xJammer_ @ Jan 29 2018, 05:02 AM) One game ripping to carrier caused a persistent "object stuck in another object" bouncing sound that would only go away when docking. And ripping to the same carrier would cause it to start again.

That sounds bad, can you reproduce it? and how? What faction, what ship, how did you rip and so on.

QUOTE (_xJammer_ @ Jan 29 2018, 05:02 AM) Whoever made the new ridiculous forced loadouts that do not even remember my previously chosen and saved one (or even just the Ctrl+1 one).... was not a very smart person.Annoying as hell to have to remember to re-arm the craft every launch. (and no I DO NOT always need a nan in my scout)

Contrary to popular perception, nothing about the Ctrl+# system has been changed recently. If it once worked differently, that must have been quite a while ago. It is a bit quirky in that there is a different loadout to save for every ship (figher, enh. fighter, adv. fighter, ..) and every faction.
The only thing I changed is the CARGO you get by default. Not even the ship's equipment. There's also not much different about how the loadouts are stored/remembered. Only on upgrading the ship, it should behave better.

Funny you complain about the nan. For months if not years people complained about not having a nan or enough probes in cargo. Now that it's done, I don't hear much from them. Instead people complain about too many probes and having a nan..
We may need a poll for the scout default loadout. I don't want to make the default loadout changeable, because then there would have to be a "change default loadout to default" button, in case a newb messes it up. However starting with loadout 1 (if it exists) is an idea.

[zombywoof]

QUOTE (Radulfr @ Jan 29 2018, 06:23 AM) Yep, I'm responsible for at least one new client crash. Fix on GitHub, sorry. It's rather hard to trigger though, which is why I missed it in beta.

You know, the most annoying part about this trio of sentences is that when someone tried to point out that all this $#@!ing with the code base seems to be making the game less stable, there was someone who went off and raged at me about how "there's no way my changes could cause the game to be less stable."

[_xJammer_]

QUOTE (Radulfr @ Jan 29 2018, 09:23 AM) Yep, I'm responsible for at least one new client crash. Fix on GitHub, sorry. It's rather hard to trigger though, which is why I missed it in beta.


That sounds bad, can you reproduce it? and how? What faction, what ship, how did you rip and so on.


Contrary to popular perception, nothing about the Ctrl+# system has been changed recently. If it once worked differently, that must have been quite a while ago. It is a bit quirky in that there is a different loadout to save for every ship (figher, enh. fighter, adv. fighter, ..) and every faction.
The only thing I changed is the CARGO you get by default. Not even the ship's equipment. There's also not much different about how the loadouts are stored/remembered. Only on upgrading the ship, it should behave better.

Funny you complain about the nan. For months if not years people complained about not having a nan or enough probes in cargo. Now that it's done, I don't hear much from them. Instead people complain about too many probes and having a nan..
We may need a poll for the scout default loadout. I don't want to make the default loadout changeable, because then there would have to be a "change default loadout to default" button, in case a newb messes it up. However starting with loadout 1 (if it exists) is an idea.

Belter carrier parked next to aleph. Do not know how to reproduce.

Loadouts - just save the last loadout used along with Ctrl + w/e. Do not reset the loadout upon docking or restarting the game. (Like literally default loadout chosen = last launched loadout)

I barely use forums. I never complained about people not having nans by default. Now I have to repeatedly either Ctrl+1 every launch, or launch with useless cargo. Don't worry though, just a cranky voob rant.

P32 was having issues with camera being off-set by 10-20 degrees to the right ( his bullets were firing basically sideways). Not sure if he posted the report yet.


Allegiance is spaghetti code. Someone grab unity + w/e networking engine and slap something together, will take nearly as long as fixing alleg bugs. Myself and Dj unfortunately kind of gave up on it atm.

[MagisterXF94]

PQUOTE 32 was having issues with camera being off-set by 10-20 degrees to the right ( his bullets were firing basically sideways). Not sure if he posted the report yet.[/quote]

I'll follow up with him