@redrum I have access to a mac on Tuesday, what exactly do you want me to check?
I haven't followed the whole conversation

The biggest problem with using a "global email" is that if we did that without any authentication, one could use our service to spam another ones email account and create something like a dos attack.
So in any case we'd need authentication, which might defeat its purpose already.

@Raville
I get what you're asking for, but I don't think there exists an old version not requiring a password, at least for the 3 years since I joined the project.

@Raville
You shouldn't trust some random application to handle your password, however because triplea is open source you could check the source code on your own and notice that we don't use the passwords for anything else than authentication.
And if your email provider requires a password we can't just simply not require one and expect it to work, so I don't really get your point.

@CrazyIvan
This Thread was mainly focused on client side changes to PbF/PbEM, not changes to the whole system in general, but I'll try to respond to your ideas anyways.

Note that the biggest Problem for most of your suggestions is probably that it's not worth the time for us. See, we're currently 4 Developers with write access to the repository, 2 of which are currently not available for coding tasks and I myself currently don't have a lot of free time either, except for the weekends. So it's important to keep that in mind and the fact that we don't get paid for this in case the answers are somewhat disappointing.

1. Well I don't really see the benefit of making clear which game a certain thread is about. As far as I can tell players usually start a game with someone else (or more people) and then those players know which game the Thread is about. The Thread isn't really interesting for other people either, except maybe if you want to analyze certain strategies or something.
2. While the stats would be nice to have, I don't think enough players are using this feature to create meaningful ones. Also there's the Problem of determining if a game is still in progress, the forums is unable to track that. However if someone with the necessary skills wants to code a NodeBB Plugin for this, I'd be happy to install it, but I currently don't have the resources to create something in that regard.
3. It wasn't a joke, but it wasn't a realistic thing either. We simply don't have the money to pay someone else to do it, and don't have the time to do it on our own. The Forum here is probably the closest thing to a helpdesk we can afford.
4. I mean we don't have any rules forbidding that someone of the community offers such a service, but ideally the whole process would be more or less self-explanatory, but this isn't an easy thing to do either.
5. See 4.
6. Maybe not for PbF/PbEM as it's hard to track those games because they're more or less offline, but for lobby gameplay this is a thing for the future. The main Problem we have is that the current state of the engine is not really extensible in a backwards-compatible way. There are some efforts by @LaFayette to redo a lot of the networking code for the lobby that would allow us to implement such features faster but as long as this isn't a production-ready system it would be fairly time-consuming to implement such a feature.
7. Lobby-Feature, see 6.
8. Yeah, you're probably right about that. Sometimes it's frustrating that we are so few people actively developing TripleA, because so many people have really good suggestions that are just not feasible for us to implement in a reasonable amount of time because the codebase didn't age too well (Originally created almost 19 years ago). Volunteers for such things are always welcome, so in case you wan't to teach yourself Java and start experimenting with the engine on your own and implement all your dreamfeatures yourself there's nothing stopping you from our side

Could be a number of things, any chance your opponent turned off "allow access of less secure apps"?
In any case it's probably not us. The SMTP protocol is so old that every provider has their own way of securing it.

Props to you @Panther you're getting really good at troubleshooting common issues
Couldn't have done it any better

@avshar Interesting, definitely very odd. I need you to check a couple of things to find the root cause of this since as @Panther pointed out the other issue has already been fixed.

1. Try out the latest pre-release. You can find a list of all versions here. Maybe your issue got fixed unintentionally already. Note that 1.10 versions are heavily incompatible with 1.9
2. If the issue still isn't fixed I'd kindly ask you to try to identify the version introducing this issue has been introduced. It will be a tedious process, but it will make identifying the problem so much easier for us than just random guessing.
3. My current guess is that the game simply gets a little bit resource hungry on your system even though 6GB of ram should be sufficient. Could you check if this is actually the case? Try opening Task Manager just before you start the game and keep an eye on the memory consumption and CPU usage. When the game decides to throw an exception try creating a Screenshot (or create a photo of the screen using any camera if this doesn't work) and post it here. Maybe terminating a couple of processes before launching helps already.

Ok, let's try the easiest things first:

1. Make sure you have the latest Nvidia graphics driver. Since you're on a laptop and I'm assuming that it has an Intel graphics unit as well, also make sure your Intel graphic drivers are up-to-date.
2. Check your Nvidia driver settings: Follow the steps as described here
3. Navigate to your TripleA installation folder. You'll find a TripleA.vmoptions file there. Edit this file with a text editor of your choice and add the following line to the end of the file: -Dsun.java2d.d3d=false

One of the steps should hopefully help. Let me know if that works for you.

Well great to hear that you got your problem fixed although the settings you mentioned shouldn't have any effect whatsoever.
It looks like there are a lot of potential fixes for this kind of issue.
If you want to find the real issue you might want to try one of the solutions described here:
https://stackoverflow.com/questions/22737535/swing-rendering-appears-broken-in-jdk-1-8-correct-in-jdk-1-7
https://github.com/magefree/mage/issues/1514#issuecomment-368220596

I can help you with those settings if you're interested

ianelletson created this issue in magefree/mage

closed Screen elements jump and draw randomly over game screen (graphic card driver issue) #1514