Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I wouldn't think that sounds are doing much, as they are still there just not audible? I could be wrong.I appreciate the detailed response. I'm going to try it out right now. I was also advised in-game that I should turn off sound effects and music as well.
yes!!!!!! im on right now and trying to sail. everything looks great and smooth sailing.i fill my cargo and go to land then crash.its happen 4 time in 1 hour.other then that the game is coming along very nice.thanks for the hard work!I crash doing just about anything, sailing especially makes me crash multiple times per voyage. does anyone else have the same experience? is there anything i can do to prevent crashes?
I believe when you disable something, the game no longer tries to make a call routine to that item that is disabled. So, if you turn something off it would /could/should be ignored for the rest of your session? Thus, if some code routine call is causing a conflict, disabling that call will stop the asking for it?I wouldn't think that sounds are doing much, as they are still there just not audible? I could be wrong.
Also 1.08 has made the game crash again for me.
now im more confused. anyway bottom line no one can sail right now..bummer.I believe when you disable something, the game no longer tries to make a call routine to that item that is disabled. So, if you turn something off it would /could/should be ignored for the rest of your session? Thus, if some code routine call is causing a conflict, disabling that call will stop the asking for it?
Those comments really don't seem fair at all. To any developer. You code your game for as many system profiles within reason and they do not have control over what people are running. I still submit that the issues will/are mostly with our systems and compatibility problems.I'm crashing repeatedly too; not even doing much of anything and abending out to the launcher. They talk about all the "testing" they do, but there's something seriously wrong with how they manage testing since they introduce new bugs with every patch. I'm convinced one or more of the TLOPO folks came from POTCO because this entire syndrome is how it was in POTCO.
Sorry. My comments are not vetted by developers, but they are only suggestions and theories based on older limited experiences.now im more confused. anyway bottom line no one can sail right now..bummer.
Those comments really don't seem fair at all. To any developer. You code your game for as many system profiles within reason and they do not have control over what people are running. I still submit that the issues will/are mostly with our systems and compatibility problems.
I wonder if a direct x version would have run any smoother or solidly, but tlopo may not be able to utilize that api any more.
My reactions were about the reference to potco and it seemed to be a slight against the staff in a way. I do remember they have done a roll back.I have been in IT since 1983 (37 years), including stints as a programmer in 3 different industries using very different platforms and technologies. I spent years managing programmers in a highly regulated industry. Today I am helping my largest client to gain control over their own software vendor (programmers) (now my 4th industry) because that vendor isn't wielding good testing methodologies and keeps introducing new bugs.
Sound familiar?
I am a [very] senior consultant and expert. My comments are not only completely fair and objective, they are accurate.
There are a lot more problems here than just user system profiles. When you deploy a new version and there are substantial problems, you should roll it back to a version that was working. You should not leave your customers wallowing in your new problems. These guys have never rolled anything back. They just expect everyone to deal with the new pain they caused until it's fixed-- but as I pointed out, each next "fix" just presents new problems. This is a conglomeration of cultural and process problems. Sadly it doesn't seem like they are interested in evolving.
I believe you do have expertise. Maybe if you offered to help them some progress could be made quicker. Also they have a test server but not many that are on the test server have been getting on before giving us this new system soooo, in my opinion because we are in beta we then become the testers. There was a lot of pressure being put on the devs by people constantly wanting the new system put into effect... to me this is what happens when given this pressure along with not enough people on the test server. I had several people tell me that most of the time you would not find anymore than 8 people on the test server at one time. 100 people were chosen to be testers. So what are the devs to do?? You can't force people to get on the test server. If you have a better solution please help the devs.I have been in IT since 1983 (37 years), including stints as a programmer in 3 different industries using very different platforms and technologies. I spent years managing programmers in a highly regulated industry. Today I am helping my largest client to gain control over their own software vendor (programmers) (now my 4th industry) because that vendor isn't wielding good testing methodologies and keeps introducing new bugs.
Sound familiar?
I am a [very] senior consultant and expert. My comments are not only completely fair and objective, they are accurate.
There are a lot more problems here than just user system profiles. When you deploy a new version and there are substantial problems, you should roll it back to a version that was working. You should not leave your customers wallowing in your new problems. These guys have never rolled anything back. They just expect everyone to deal with the new pain they caused until it's fixed-- but as I pointed out, each next "fix" just presents new problems. This is a conglomeration of cultural and process problems. Sadly it doesn't seem like they are interested in evolving.
100 people were chosen to be testers.