Its easier to just use a mat trader.
It's easier to use an exploit like this to grind imperial shielding and use a mat trader than to look for a mythical pharmaceutical isolators HGE.
Its easier to just use a mat trader.
It's easier to use an exploit like this to grind imperial shielding and use a mat trader than to look for a mythical pharmaceutical isolators HGE.
It's not a desynchronization issue. It's an issue that almost everything you see in Elite, other than mission boards and BGS data, is actually generated by your client. If you look at the in-game bandwith monitor you'll find that very little data is transferred to FD's servers while you are playing the game. The reason these types of loopholes exist is because Elite uses a P2P architecture instead of a client-server model. FD's servers aren't generating the USS, your client is, and that is why it repopulates the USS in that manner.
That is also why there is no actual "fix" for combat logging. FD knew this when they decided to use a much cheaper P2P architecture instead of a client-server model and that is not going to change. The best the FD can do is try to "monitor" combat logging but with the game being so unstable FD can't reliably determine if someone's client has crashed, if there was a problem with someone's internet connection or if they have intentionally task-killed the client. That is why FD has not yet implemented any "consequences" for suspected combat logging, they don't have the time or resources to properly investigate each case to be certain that combat logging was, in fact, involved rather than a game crash or other issue.
Sad but reasonable.
It's not a desynchronization issue. It's an issue that almost everything you see in Elite, other than mission boards and BGS data, is actually generated by your client. If you look at the in-game bandwith monitor you'll find that very little data is transferred to FD's servers while you are playing the game. The reason these types of loopholes exist is because Elite uses a P2P architecture instead of a client-server model. FD's servers aren't generating the USS, your client is, and that is why it repopulates the USS in that manner.
That is also why there is no actual "fix" for combat logging. FD knew this when they decided to use a much cheaper P2P architecture instead of a client-server model and that is not going to change. The best the FD can do is try to "monitor" combat logging but with the game being so unstable FD can't reliably determine if someone's client has crashed, if there was a problem with someone's internet connection or if they have intentionally task-killed the client. That is why FD has not yet implemented any "consequences" for suspected combat logging, they don't have the time or resources to properly investigate each case to be certain that combat logging was, in fact, involved rather than a game crash or other issue.
P2P and cosmetics sales were the alternative to a subscription IIRC.
For someone with tunnel vision, yes, subscription is the only alternative.
It was a cheap move from people who otherwise did great.
It's not a desynchronization issue. It's an issue that almost everything you see in Elite, other than mission boards and BGS data, is actually generated by your client. If you look at the in-game bandwith monitor you'll find that very little data is transferred to FD's servers while you are playing the game. The reason these types of loopholes exist is because Elite uses a P2P architecture instead of a client-server model. FD's servers aren't generating the USS, your client is, and that is why it repopulates the USS in that manner.
That is also why there is no actual "fix" for combat logging. FD knew this when they decided to use a much cheaper P2P architecture instead of a client-server model and that is not going to change. The best the FD can do is try to "monitor" combat logging but with the game being so unstable FD can't reliably determine if someone's client has crashed, if there was a problem with someone's internet connection or if they have intentionally task-killed the client. That is why FD has not yet implemented any "consequences" for suspected combat logging, they don't have the time or resources to properly investigate each case to be certain that combat logging was, in fact, involved rather than a game crash or other issue.
If you don't like P2P you should do better pre purchase research, I did and its why I've no issues with it at all. Buyer beware.
Try to tell your father what he Should do, I didn’t ask for your advice. I was commenting on your tunnel vision.
I mean, the game mechanic must be engaging and trail-blazing if people are willing to pull their network cable or sit and watch the entire loading sequence rather than play the game as intended.
You're the one annoyed by being blindsided about a pre existing widely discussed well known feature in the video game you chose to buy. Maybe if you took your blinkers off to other better approaches to buying video games you'd be a happier gamer, just like me.
Since this is already public to my community, I'm gonna be that guy and spoil it for everyone.
HGEs (and other USSs of materials) won't expire as fixed if you scoop the materials and then exit to desktop or task-kill, which ever is faster.
Not only chose to buy, I bought 2 copies back @ game launch. You know, you seem a strange fella - you feel I need your advices, then, when your unasked advices are ignored you feel that I am annoyed.. (I’m not) Then you want to enlighten me about approaches (!) to buying video games. And if that wouldn’ be enough - you want to make me a happier gamer? Did I already tell you who to consult about advices?
Anyway, it all began with you making stupid remark about game design few posts back, just so you won’t forget in whiteknighting rush. Now you have my permission to type words about me being “annoyed“ cause I gotta go.