I may have a clue as to why logos disappear...

[HRBaker]

Like many of you, I had to reload some of my logos many times before they finally "stuck". The past month or so, however, they finally seemed to be ok.

I left town last week, bringing my trusty laptop with me, and checked into a studio apartment for a 10 day stay. Turns out the network is terrible. Too many people get on and it's almost useless.

Sunday night, I made some team changes and submitted before I went to bed. Monday morning, my changes were only half correct, and all 3 of my custom logos were gone.

Conclusion?

It could very possibly be that IF you have a questionable network connection, whatever the coding has to do to save your logos and/or make team changes will hic-cup in the process.

This would explain why OOTP hasn't fixed it - because they can't... it's due to your network stability.

[Will_L]

I think you're onto something with this since I've noticed that it never happens when I'm using my laptop with a wired connection in the bedroom but when I'm in the living room using the wifi it happens occasionally.

[cmcgill]

Not sure that's entirely the issue. This happens from my desktop which is hard-wired to the router, and my service is excellent. Very few houses out where we live.

[neugey]

Hmmm could be something along those lines. This last time my logo stayed intact, but many recent other times it has not. I'm going to pay attention to what exact screen I leave OOTP on when the Sunday overnight transition happens - wonder if that is a factor.

[brotherblues]

I think it's way more likely that logos only work for people who have dirt on the devs, possibly naughty pics and the like. But that's just me. Most definitely probably just me.

[Syd Thrift]

So... if what's happening is that the game tries to upload a giant packet that includes logo/etc. information every time you save, that is a big, big opportunity for improvement. Speaking as a web developer myself, with a thin client app like this even if you're not having actual logo/etc. issues, you should only be sending images up if they've changed. In fact, if OOTPDev is sending up images *every single time* you update your rotation, etc., I could very easily see where all of the increased bandwidth on the servers could cause an issue where timeouts are plentiful and as a result logo data keeps getting reset.

Even if it's not a literal "every time" thing, even if the thin client is just a little bit too aggressive in sending up images, that could be a massive increase in bandwidth: imagine that instead of pushing up a 5k file (probably way more than you need for simple roster changes in an XML type format), you push up 1 meg worth of data. Now multiply that by thousands of users, thousands of times a day. This might be decried as a bad UX thing but I might go so far as to say that maybe there should be a separate button to upload images, and the only time you ever send them is when that separate button is clicked (and on top of that, the client needs to track changes as well so that jamming on the button would have no effect).

I have not set up Fiddler on my machine to track this because, well, I do this in my free time, but hey, someone feel free to do that...