I have not seen much posted concerning the release of 3.12 and wanted to find out if there are any problems with it or if it is a stable release. I am still currently running 3.11.55 on my server and was looking at upgrading to 3.12 but wanted to make sure there were no major problems being reported first. Thanks in advance.

Well Boss, I've been running 3.12 for some time now with no problems whatsoever. There were a couple of instances where a couple of players were using j-twat and having a few problems with macros and such working properly but that is the only problem I've heard of from my end. I would say it's a very stable release.

macros are most likely user error, v3.12 so far is bug free

quote:Originally posted by Slim Shady

macros are most likely user error, v3.12 so far is bug free


Can anyone from EIS lend some official confirmation on this? I know I've seen what looked like 'possible bug' reports posted a few times about 3.12 and I don't recall that there was every any kind of conclusion or follow-up about whether they had been valid or not.

quote:Originally posted by Ahab

Well Boss, I've been running 3.12 for some time now with no problems whatsoever. There were a couple of instances where a couple of players were using j-twat and having a few problems with macros and such working properly but that is the only problem I've heard of from my end. I would say it's a very stable release.


That would be me

I still can't run J-TWAT with ANSIs on with version 3.12...

I've re-loaded J-TWAT from the net, so I got a new J-TWAT proggy on.

Scrolling still "jams", "stalls", whatever...I have to be at keyboard and press a key, any key, to get it scrolling again. This affects trading/haggling, engaging figs/paying tolls, etc.

If I turn ANSI off, I can navigate no problem, but I'm stuck with monochrome foreground, and it hurts my eyes. Also, little thing like going to Shipyards and not seeing which ships I can afford highlighted...

The only replies I got so far is that me, the user's fault. It's something to do with my "specific configuration"...

How do I change my configuration so that ANSIs will work?

Help me!

Just guesing here, so bear with me. I will write a solution to try, then explain what I am thinking.

Try this. Go to http://www.swath.net and download it (it will be in demo mode for 30 days so this is all you want for now) or http://www.emtec.com/download.html#zocfiles (I have not used ZOC for quite some time, but it used to be free). Try one on them to connect to same game, problem may be JTWAT.

My thinking is this; TWGS updated like 4 times in about a month. Just using scripts from others some will not work with 3.12, but worked in 3.11.55. So the way scripts/helpers interact is not the same under the newer conditions. JTWAT is (or was anyway) written to interact with 3.11.55 and it is my understanding they have not worked on that helper lately, so it may be a JTWAT thing. I am not trying to get you to buy one of the above, just a couple addresses I already knew is all.

with ansi's on, you have to abort displays, with ansi's off you can NOT abort displays. i have never used jtwat (i am under the impression that it no longer has anyone working on it and shouldn't be used like twar for windows) i use zoc/twx and everything runs good for me (cept twx bites me sometimes.. Darn that xide, hehe)
Slim
(also, if you read some past posts, you will find EIS confirming that all supposed "bugs" is 3.12 are not bugs, but user error (or helper/script error)
go 3.12!!

quote:Originally posted by severian
My thinking is this; TWGS updated like 4 times in about a month. Just using scripts from others some will not work with 3.12, but worked in 3.11.55. So the way scripts/helpers interact is not the same under the newer conditions. JTWAT is (or was anyway) written to interact with 3.11.55 and it is my understanding they have not worked on that helper lately, so it may be a JTWAT thing.[/red]


Thanks. The above is the best reply/explanation I've had so far.

Now, any way to make 3.12 "compatible" again? Can they be made to "interact" like they used to?

That would be groovy

Kivas - Changes are made in the best interest of game play. While we make every effort possible to not break any current helpers, ultimately, changes are sometimes required that may cause problems. While we do regret this, EIS can not be responsible for fixing 3rd party applications.

As to 3.12's stability, the only valid error report I've seen was in SGO's 28 alien races game, and I think that was a result of so many aliens, since I haven't seen it reported anywhere else.

quote:Originally posted by Harley Nuss (teamEIS)

As to 3.12's stability, the only valid error report I've seen was in SGO's 28 alien races game, and I think that was a result of so many aliens, since I haven't seen it reported anywhere else.


Thanks for the response! It's good to know that things are running smoothly. [:)]

I'm definitely interested in this ANSI problem. I hate not knowing what's causing something, regardless whether it's user error or program error. I will say that during the stretch of releases from .55 to 3.12, I made some changes that I expected to effect helpers and scripts. This change was in the way the game will now queue up messages while the player is sitting at a sub-prompt. So before, if you were at a Y/N prompt, you would get messages like "Player enters sector", but now, at such a prompt, no messages are sent until you drop back to a main prompt, at which time a list of messages might display. This change could definitely effect helpers in scripts, but I can't predict that it would cause the problem being described here. One way to test, obviously, is to make sure the gameop has turned this feature off in TEDIT, since it's optional. If we find that the lockups occur with the change enabled but it works fine when it's disabled, that would certainly shed some light on the subject.

Other than that, if I knew exactly which new revision between 3.11.55 and 3.12 created this problem, I could narrow down the possible causes.

There is the problem with planet displays not updating (for shielded status) untill someone lands or tries to land on the planet. This is a pre-existing issue from an earlier version......is this not considered a bug? I know there is another post on that here somewhere.

So I just went and checked and that is the next topic here.

BUG OR NO?

quote:Originally posted by John Pritchett (EIS)

I'm definitely interested in this ANSI problem. I hate not knowing what's causing something, regardless whether it's user error or program error. I will say that during the stretch of releases from .55 to 3.12, I made some changes that I expected to effect helpers and scripts. This change was in the way the game will now queue up messages while the player is sitting at a sub-prompt. So before, if you were at a Y/N prompt, you would get messages like "Player enters sector", but now, at such a prompt, no messages are sent until you drop back to a main prompt, at which time a list of messages might display. This change could definitely effect helpers in scripts, but I can't predict that it would cause the problem being described here. One way to test, obviously, is to make sure the gameop has turned this feature off in TEDIT, since it's optional. If we find that the lockups occur with the change enabled but it works fine when it's disabled, that would certainly shed some light on the subject.

Other than that, if I knew exactly which new revision between 3.11.55 and 3.12 created this problem, I could narrow down the possible causes.


The problem started with Version 3.12, and persists with 3.13.

Just so you know...

MrDon is working on a new -- and hopefully free -- helper that will hopefully rectify all this. I LOVE the ANSIs !

did u try zoc or swath? (do u use twx)? i can only assume that this is a jtwat issue that will never be resolved. try zoc (as its not a twars helper) or swath (which has people working on it still) and see if your problem still persists. ive tried to recreate it with all sorts of CN9 settings, and i cant get it to pause where its not supposed to pause.

Slim

quote:There is the problem with planet displays not updating (for shielded status) untill someone lands or tries to land on the planet. This is a pre-existing issue from an earlier version......is this not considered a bug? I know there is another post on that here somewhere.


I addressed this with 3.13, so hopefully it has been fixed. Let me know if it hasn't.