This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - farin
16
« on: February 08, 2018, 01:06:20 PM »
forumisto: that is bug, i am going to fix it
17
« on: February 05, 2018, 12:27:10 PM »
German monasteries is still there (last expansion in minor expansion list, just before minis)
18
« on: February 05, 2018, 05:44:45 AM »
Java 8 is required (since 4.0)
19
« on: February 04, 2018, 07:08:49 AM »
Can be caused by lot of 4.x rewrite regressions related to (not only) Abbey and Mayor.
Sorry for inconvenience, this is price for big app rewrite needed to future development (when future means eg already added Count expansion)
Lot of issues is addressed in 4.2.0 which should be much more stable. (will be out soon)
20
« on: February 04, 2018, 07:05:41 AM »
Solved. Will be released in 4.2.0 as "Abbey&Mayor and The Count of Carcassonne big fix"
21
« on: February 01, 2018, 07:53:02 AM »
Stange error.
You don't need to turn off connection. You can instead comment out update url in config file. This disables update check.
22
« on: February 01, 2018, 07:51:18 AM »
Please send me a save. I want to make fixing session this weekend and put out release next week. Don't promise anything but I will try to fix most annoying bugs.
23
« on: January 19, 2018, 12:48:08 PM »
Durbs, bug thanks for confirmation
It really looks that new JavaWebsocket sucks. I am going to use old one (and put it out officially asap)
In long term horizont I will probably migrate to different websocket library, but seems not big issue now.
24
« on: January 12, 2018, 02:40:46 PM »
Anybody who suffer from connection issues (which may include reported message above) please try http://jcloisterzone.com/builds/JCloisterZone-4.1.X.7zIt is just 4.1.0 repacked with old version of Java-Websockers. With exact same version used in JCZ 3.x Nothing else change. Which should make pretty clear answer if these troubles are cause by networking lib or not. Because it looks like some messages are lost sometimes. And JCZ network layer was almost unchaged from JCZ 3 to 4, except lib update to much newer version. I would be glad for any observation. Thx
25
« on: December 24, 2017, 03:11:19 PM »
rfielder - please try 4.1.0. and let me know
At least it uses latest websocket library + fixes some important issues related to networking on my side
Eg reconnecting really means reconnection and not crash ;-)
I still wonder why you have troubles on local network, but if remains we can continue with investigation.
26
« on: December 19, 2017, 12:28:35 AM »
4.0.2 doesn't help you, wait with update.
I am going to replace it with 4.1.0 in few days, hopefully tomorrow.
Shame on me. Making it stable it's top priority for me now. Current release it unsatisfying.
27
« on: December 17, 2017, 03:11:49 PM »
hmmm my connection lost handling is terribly broken.
Good news is that I know what to do :-) New hotfix release will be needed asap.
28
« on: December 17, 2017, 12:24:53 AM »
Hi guys
at least whole 4.x branch behaves badly when messages are lost network. That something which needs some care too.
Which shouldn't be you case when you are playing locally.
I looked at JavaWebsocket library, and since 3.x there is many many changes. I would like to rather not revert it to version used in 3.x
Instead I am just trying to make it work smoothly on recent version (an truth is that 4.0.2 wan't built with latest)
Current checlist:
- use really latest JavaWebsocet
- disable hearthbeat
- solve lost message bug
then I am going to rebuild it and you can try if it helps. It should happen tomorrow.
Sorry for these troubles, 4.x is rather complete rewrite then just app update. Which causes all regression bugs. But i was needed if I can be able to make new great things.
29
« on: December 13, 2017, 01:52:44 PM »
1. this is probably connected to you previous post. I susspect JavaWebsocket library. It's possible that it adds some default timeout which wasn't present in old version.
2. That is bug.
30
« on: December 13, 2017, 01:43:07 PM »
I don't know. Network layer is rare case of code which is almost untouched from 3.x.
So I would not expect problems just here.
On the other hand java-websocket dependency was upgraded, and it can be related to it.
As far as I remeber I observed similar behaviour when laptop was sleep for a while. I am going to experiment with it.
|
Show Posts
